Flash script sometimes ignores -R rootfs path

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin NX
1

This is a report against r35.3.1, which is a little older. I also reported it against r32.7.2 a few years ago but it was reported as fixed, which doesn’t appear to be the case.

I have built a custom rootfs outside of the Linux_for_Tegra directory. I am running flash.sh -R /path/to/actual_rootfs/ ...to specify the absolute path to this directory.

Occasionally the flash.sh tries to read files from Linux_for_Tegra/rootfs, which is the wrong rootfs. These issues can be found by removing Linux_for_Tegra/rootfs and attempting the flashing process. If the scripts correctly abide by the -R option, there will be no errors.

  1. The flash.sh script tries to access ${LDK_DIR}/rootfs/etc/nv_tegra_release and ${LDK_DIR}/rootfs/etc/user_release_version.

  2. The ota_make_recovery_img_dtb.sh script is invoked where it is hardcoded for local _rootfs_dir="${_ldk_dir}/rootfs".

The consequence of these issues is that you end up with an inconsistently flashed product depending on where your rootfs is stored.

The workaround is to rm -Rf Linux_for_Tegra/rootfs && ln -s /path/to/actual_rootfs/ Linux_for_Tegra/rootfs.

3

Hi,

Some questions to confirm:

  • Do your Orin NX using a custom board or a dev kit?

Thanks

4

Is this still an issue to support? Any result can be shared?

5

It is the ConnectTech Hadron carrier board. Previously I reported the issue while using the Diamond Systems Stevie board.