Use l4t_initrd_flash.sh to update the pinmux on the device without reinstalling the original system on the device

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin Nano
,
1

I used Jetson_Orin_NX_and_Orin_Nano_series_Pinmux_Config_Template.xlsm to generate the three files pinmux.dtsi & gpio.dtsi & padvoltage.dtsi, and i
Copy the “pinmux.dtsi” and “padvoltage.dtsi” files to the “<l4t_top>/bootloader/generic/BCT/” directory.
Copy the “gpio.dtsi” file to the “<l4t_top>/bootloader/” directory.

I want to update jetson-orin-nano-devkit via l4t_initrd_flash.sh, but I don’t want to format the existing Ubuntu system of jetson-orin-nano-devkit. How can I update it without affecting the system?

3

Hi chichen345,

Are you using the devkit or custom board for Orin Nano?
What’s the Jetpack version in use?

Sorry that it is not applicable since reflashing the board would erase and repartition the disk.

Are there some contents important on your board?
Have you considered backup the APP partition before flash?

4

Hi KevinFFF

I using the devkit for Orin Nano.(L4T 36.3, Jetpack-6)

So I can’t simply update the files I need to update? Or is there another way to achieve my idea? Can you provide it?
(For example, use the dtsi file generated by Jetson_Orin_NX_and_Orin_Nano_series_Pinmux_Config_Template.xlsm)

I also want to make sure that I have placed the generated files in the corresponding folders and also changed the
PINMUX_CONFIG=“Replace with the new file name.dtsi”;
PMC_CONFIG=“Replace with the new file name.dtsi”;

After the changes are made, can I only update by reflashing?

5

Please note that pinmux/gpio dtsi are loaded in MB1(early boot) so that you have to reflash the board to apply the change.

Alternative, you can also generate an overlay dtbo(e.g. jetson-io-hdr40-user-custom.dtbo), which will be loaded during boot up and handled by pinctrl-tegra driver to re-configure the pinmux register if you don’t want to re-flash the board.