Jetson_Xavier_NX_Pinmux_Configuration_Template_v1.06.xlsm & pinmux-dts2cfg.py

Hi,

I modified Jetson_Xavier_NX_Pinmux_Configuration_Template_v1.06.xlsm for my custom carrier board, and then generated a cfg file using pinmux-dts2cfg.py as below:


python pinmux-dts2cfg.py --pinmux addr_info.txt gpio_addr_info.txt por_val.txt --mandatory_pinmux_file mandatory_pinmux.txt tegra19x-cus-pinmux.dtsi tegra19x-cus-gpio-default.dtsi 1.0 > tegra19x-mb1-pinmux-p3668-a01.cfg

But the follwoing error messages showed up:


ERROR: pin eqos_rd3_pf1(0x00022470) field nvidia,lpbk(0x00000020) is not matching, val = 0x01 expected = 0x00
ERROR: pin eqos_sma_mdio_pf4(0x00022440) field nvidia,pull(0x0000000c) is not matching, val = 0x00 expected = 0x02
ERROR: pin sdmmc4_cmd(0x00002440) field nvidia,pull(0x0000000c) is not matching, val = 0x00 expected = 0x02
ERROR: pin soc_gpio10_pg6(0x00000410) field nvidia,tristate(0x00000010) is not matching, val = 0x01 expected = 0x00
ERROR: pin gp_pwm2_px2(0x00000410) field nvidia,tristate(0x00000010) is not matching, val = 0x01 expected = 0x00

Those pins are hidden in the excel file for Xavier NX; They are unavailable pins.

Can I ignore these messages? I am using L4T 35.05.0.

Thank you.

Hi minseok.choi,

What’s your Jetpack version in use?

Have you generated the pinmux cfg file after you see those errors?
If so, you can just update that cfg file in your custom BSP package and reflash the board to apply the change.

Hi KevinFFF,

I’m using L4T 35.5.0 in Jetpack 5.1.3.
The cfg file had generated and I did flashed with the cfg file, and then the my board are boot normally.

Thank you.

If you want to eliminate those error messages during generating cfg, you can just remove --mandatory_pinmux_file mandatory_pinmux.txt in your command.

$ python pinmux-dts2cfg.py --pinmux addr_info.txt gpio_addr_info.txt por_val.txt tegra19x-cus-pinmux.dtsi tegra19x-cus-gpio-default.dtsi 1.0 > tegra19x-mb1-pinmux-p3668-a01.cfg

Please also remember to update the new PINMUX file name (tegra19x-mb1-pinmux-p3668-a01.cfg) in board config.

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.