Hi everyone.
I am trying to reflash the kernel device-tree partition on the external NVMe device after some updates for my Jetson NX. I am using Jetpack 4.6. I am on the module that has an internal eMMC, which I am not using right now (not for booting nor storage).
While booting after initially flashing works fine, I wanted to update just the kernel dtb partition and using initrd flash to add some devices. The problem is that when I follow Workflow 8 of the README. The device is unable to boot afterwards, as it is not able to find a partition to mount (by uuid).
If I put the actual NVMe partition as argument (unlike Workflow 8 suggests), then (all) my partition(s) get reset. Most hurtfully the rootfs and I have to reinitialize everything.
So executing
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1 -c flash_nvme_GP-GSM2NE3512GNTD_512gb.xml -S 128GiB --external-only --showlogs -k kernel-dtb jetson-nx-customdtb mmcblk0p1
makes the PART UUID error appear-
and
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1 -c flash_nvme_GP-GSM2NE3512GNTD_512gb.xml -S 128GiB --external-only --showlogs -k kernel-dtb jetson-nx-customdtb nvme0p1
will reflash everything. The customdtb config is just the same as the base eMMC config with the new device-tree.
Any ideas or workarounds?
Thanks