Do pinmux document version 1.01 for production module support L4T 32.3.1?

Autonomous Machines Jetson & Embedded Systems Jetson Nano
1

Hi All,

The official site,Jetson Nano Developer Kit Pinmux, says the Jetson Nano Pinmux “NOTE: This spreadsheet assumes L4T 32.2.x.”. Then what should I do if I want customize a carrier board for a Nano production module?

Thanks

2

Please give it a try. If it hits any issue with rel-32.3, please let us know.

3

Hi WayneWWW

We have no production module in hand. What we do now is making a FW for a production far away, so we can’t have a try.

4

Hi WayneWWW,

Use Jetson Nano Pinmux,
and Exporting Pinmux for U-Boot,
In tegra-pinmux-scripts/

./csv-to-board.py p3450-porg

I got configs/p3450-porg.board in the end.
And after

./board-to-uboot.py p3450-porg > pinmux-config-p3450-porg.h

I found there is no pinmux-config-p3450-porg.h exists anymore in u-boot R32.3.1.

In R32.3.1, I think pinmux config of u-boot is here, arch/arm/mach-tegra/tegra210/pinmux.c
It seems that the Driver Package Developer Guide is out-of-date.

On the other hand,
after modify arch/arm/mach-tegra/tegra210/pinmux.c, and do make,
copy u-boot.bin to Linux_for_Tegra/bootloader/t210ref/p3450-porg/
And

sudo ./flash.sh -k LNX jetson-nano-emmc mmcblk0p1

the result is success though, but still same u-boot version after reboot.

I find no any other documents mention about pinmux config for R32.3.1.
Could you kindly give me some hints?

Many thanks.

5

Hi imbrandon,

Please refer to https://devtalk.nvidia.com/default/topic/1069483.
Now you only need to use dtb to do the pinmux work.

As for the document, we’ve removed this section but new document will be ready until next release of jetpack.