I have spent many hours trying to just use your documentation to create a new pinout for my new custom carrier board for my Nano, which right now I have the tegra210-p3448-0000-p3449-0000-b00.dts devicetree map in place, which is what comes out of the box for this SODIMM.
I have these links to follow, and have been all day trying to “decode” what is really needed.
NVIDIA Jetson Linux Developer Guide : Platform Adaptation and Bring-Up | NVIDIA Docs
NVIDIA Jetson Linux Developer Guide : Kernel Customization | NVIDIA Docs
NVIDIA Jetson Linux Developer Guide : Kernel Customization | NVIDIA Docs
Each and every one of those links above, if you try to follow them, end up in a frustration because the directory, the file, the whatever is not what the documentation says.
For example,
## Obtaining the Kernel Sources with Git
Prerequisites
•You have installed Git. Install Git with the following command:
$ sudo apt install git-core
•Your system has the default Git port 9418 open for outbound connections.
To sync the kernel sources
•Get the kernel source by running the source_sync.sh script:
$ ./source_sync.sh
When prompted enter a ‘tag’ name, as provided in the release notes.
You can sync to any Linux tag you like. However, the tag provided in the release notes syncs the sources to the same source revision the release binary was built from. To see a list of the available release tags, use:
$ git tag –l tegra-l4t*
which is right out of the documentation , leads you to NOT be able to locate ./source_sync.sh, which is of course how the build all happens. Without that script, nothing.
So I go and download the source and do find public_sources.tbz2, which is great, but after following
5.Copy the generated .dtsi files from the directory that contains the spreadsheet to the following locations:
jetson_nano_module-pinmux.dtsi to <src_path>/hardware/nvidia/platform/t210/porg/kernel-dts/porg-platforms/tegra210-porg-pinmux-p3448--.dtsi
jetson_nano_module-gpio.dtsi to <src_path>/hardware/nvidia/platform/t210/porg/kernel-dts/porg-platforms/tegra210-jetson-cv-gpio-p2597-2180-a00.dtsi
Where:
•<src_path> is the pathname of the kernel sources that you downloaded in step 1.
•jetson_nano_module is the filename prefix that you entered in step 7 of To customize the pinmux spreadsheet. If you did not use the recommended default, change the filenames accordingly.
• is the module’s SKU number. You must specify it as a four-digit number, i.e. 0000 or 0002.
• is the version of the Jetson Nano device tree that you identified in step 3.
but guess what, there is no "hardware"dir, much less the entire tree is not accurate.
I am stuck I just need to engage the new pinmux and be on my way, and the entire day has been all like this, get something, extract it, and it is NOTHING like what the documentation says it is.
I am on a timecrunch, as everyone else is, and this is not supposed to happen. Why put up instructions that are not accurate?