I noticed that we can change the boot order for the available devices by changing the data variable inside the L4TConfiguration file
…
gNVIDIATokenSpaceGuid {
DefaultBootPriority {
data = “usb,nvme,emmc,sd,ufs”;
Now if data = “usb,nvme,emmc,sd,ufs” and the flash is done to mmcblk0p1:
Does the device still try to boot from nvme first?
In the above order, If there is an image on nvme and another image on EMMC and the nvme has its /boot directory removed (so it is not bootable), does the bootloader try the nvme first and when it fails it tries to see if it can boot from EMMC next?
We want to know how we can make a device unbootable and then make it bootable again. Is there any place we can look at the bootloader code that does this selection?
Thank you DaveYY,
Previously (with CBOOT) we could change the boot device (using nvbootctrl, change the boot device from ssd to emmc and from emmc to ssd), so occasionally when our SSDs were bad we booted from EMMC and then we generated the rootfs again (on SSD), then once SSD was fixed we switched back to SSD. Since changing the boot device is no longer supported through UEFI (via command line), I was thinking that we could take out the /boot directory on SSD and reboot, the Jetson Device should boot from EMMC (correct?). Once booted from EMMC we can regenerate the rootfs (and recreate /boot) then we reboot the device again. This time it should boot from SSD again. Please let me know if this is not clear.
The device will just hang in the booting process if the /boot is corrupted, so please use UEFI menu for changing the booting device.
The UEFI menu can also be accessed from the serial console, so it’s not like that you need a monitor to do so.