Orin nx boot order changer after restore system

[848145724]

Dear all:

1. Orin NX SOM with custom board in Jetpack5.1_R35.2.1

2. We backup Orin system Image , this moment the first boot order is NVME.
   2.1: this is dmesg log for backup device
   backup_dmesg.log (70.3 KB)

3. After flash another Orin NX SOM`S QSPI the first boot order is NVME.
   But after restore that Orin nx, the first order is HTTPV4 which cause the Orin NX startup time takes 5 minutes .
   3.1: this is dmesg for rstore device
   restore_dmesg.log (70.0 KB)

4. which we try
   4.1: refer this link change boot order

   4.2: modify kernel/dtb/L4TConfiguration.dts DefaultBootPriority , but this did not include httpv4 or httpv6,
   we move nvme to first order, not solve this problem

   4.3: add ADDITIONAL_DTB_OVERLAY=“BootOrderNvme.dtbo” to flash cmd, not solve this problem.

5. The only way which can work is : enter UEFI and change boot order, but this way may increase the risk and burden of mass production

So， could you provide some suggestions for change boot order during the brushing process, rather than change boot order by enter UEFI one by one for Orin NX device?

Thank you very much.

[KevinFFF]

Hi 848145724,

@848145724

2.1: this is dmesg log for backup device

How do you backup for Orin NX? There’s no internal eMMC for Orin NX, you might backup for NVMe drive. We need the command you use to backup the NVMe and the backup log from host side.

@848145724

3.1: this is dmesg for rstore device

We also need the commands you use for restore and the log from host side.

@848145724

4.2: modify kernel/dtb/L4TConfiguration.dts DefaultBootPriority , but this did not include httpv4 or httpv6,
we move nvme to first order, not solve this problem

Maybe you could just left nvme in the list because you won’t use other storage as boot device.

[848145724]

1： backup command: sudo ./tools/backup_restore/l4t_backup_restore.sh -b p3509-a02+p3767-0000
backup flash_1-12_0_20230414-143048.log (6.5 KB)

2： restore command： sudo ./tools/backup_restore/l4t_backup_restore.sh -r p3509-a02+p3767-0000
restore flash_1-12_0_20230414-141259.log (6.5 KB)

3： If we just left nvme, first we can not enter UEFI; second it is not related with HTTPv4 or httpv6.

[KevinFFF]

From you backup/restore logs, it seems not completed to me.
Have you modified the l4t_backup_restore.sh script for NVMe drive?
just like the following thread:
How to clone Orin NX APP partition to host PC - #6 by lhoang

@848145724

f we just left nvme, first we can not enter UEFI; second it is not related with HTTPv4 or httpv6.

Do you have ethernet cable connecting on you carrier board?

[848145724]

About Orin nx flash :
1: change l4t_backup_restore.sh nvbackup_partitions.sh nvrestore_partitions.sh for nvme
2: change tegra234-mb2-bct-misc-p3767-0000.dts for cvb_eeprom_read_size to 0x0
3: just connect power cord and MicroUSB for flash during backup and restore.

[KevinFFF]

@848145724

3: just connect power cord and MicroUSB for flash during backup and restore.

Is there the TypeC port on your custom board for flash?

Could you help to use latest JP5.1.1(R35.3.1) for Orin NX and reproduce with above modification?
There should be more fixes for Orin NX due to new module.

[848145724]

In JetPack5.1.1_R35.3.1, the problem is exist as follow.
1:create mfi

sudo ./tools/backup_restore/l4t_backup_restore.sh -b -c p3509-a02+p3767-0000

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --use-backup-image --no-flash --external-device nvme0n1p1 -p “-c bootloader/t186ref/cfg/flash_t234_qspi.xml --no-systemimg” -c ./tools/kernel_flash/flash_l4t_external.xml --massflash 5 --showlogs --network usb0 p3509-a02+p3767-0000 nvme0n1p1

2: flash

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --network usb0 --massflash 5 --showlogs

After restore, device can work but first boot order is HTTP.
Follow is uart log during device poweron.
minicom.cap (90.9 KB)

[KevinFFF]

From you log, it seems the board boot up successfully.

Could you use the following command to generate mfi package and flash?

Generate

$sudo ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash --external-device nvme0n1p1 -p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml --no-systemimg" -c ./tools/kernel_flash/flash_l4t_external.xml --massflash 5 --showlogs --network usb0 p3509-a02+p3767-0000 nvme0n1p1

Flash

$sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --network usb0 --massflash 5 --showlogs

[848145724]

@KevinFFF

Flash

$sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --network usb0 --massflash 5 --showlogs

After that ,I get a new system rather backup and restore system. And the first boot order change to nvme rather HTTP .

[KevinFFF]

Is the result as expected?

[848145724]

Not as expected, First , we need to backup and restore system. But in this way, just flash Orin nx device, that not at all useful.
I would backup and restore Orin NX rather just change boot-order.

[KevinFFF]

Could you help to use the following command to backup/restore the board with R35.3.1?
Backup:

$ sudo ./tools/backup_restore/l4t_backup_restore.sh -b p3509-a02+p3767-0000

Restore:

$ sudo ./tools/backup_restore/l4t_backup_restore.sh -r p3509-a02+p3767-0000

Use above commands instead of mfi package for backup/restore.

[848145724]

Please take a look at the reply above

[KevinFFF]

Sorry, I mean using R35.3.1 to verify again.
It seems you were using R35.2.1.

@848145724

modify kernel/dtb/L4TConfiguration.dts DefaultBootPriority , but this did not include httpv4 or httpv6,
we move nvme to first order, not solve this problem

Do you mean that modifying DefaultBootPriority in uefi binary not help on boot order issue?
Do you update the modified UEFI binary before backup/restore?