I compile the kernel source in an ubuntu 20.04 x86_64(HostA), and flash Orin nano 8G module and 128G PCIe SSD by
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --keep --external-device nvme0n1p1
-c tools/kernel_flash/flash_l4t_external.xml -p “-c bootloader/t186ref/cfg/flash_t234_qspi.xml”
–showlogs --network usb0 jetson-orin-nano-devkit internal
I want to flash Orin nano on other ubuntu 20.04 x86_64(HostB), and my procedures are
1.I zip the Linux_for_Tegra folder by “tar -jcvf Linux_for_Tegra.tbz2 Linux_for_Tegra” on HostA
2.Copy the Linux_for_Tegra.tbz2 from HostA to HostB
3.Unzip Linux_for_Tegra.tbz2 on HostB
4.Flash the Orin Nano on HostB by
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --external-device nvme0n1p1
-c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml --no-systemimg "
–showlogs --network usb0 jetson-orin-nano-devkit internal
[Flash by HostA]
I can enter the UEFI boot manager GUI by monitor when I use HostA to flash Orin Nano, all the functions are correctly.
[Flash by HostB]
But I can’t enter UEFI boot manager GUI by monitor when I use HostB to flash Orin Nano.
I can login to Ubuntu GUI by monitor, and can enter UEFI boot manager GUI by debug UART.
What flash command should I use on HostB to enter UEFI boot manager GUI by monitor ?
Are you using the devkit or custom board for Orin Nano?
A: Yes.
What’s the Jetpack version in use?
A: R35.4.1
Could you use the same command(as you run on HostA) on HostB PC to flash the board?
A: No, it looks the image has been signed.
If I use the same command to flash on HostB, I can’t see the Ubuntu login GUI by monitor, but can
login by debug uart.
What do you mean “can’t enter UEFI boot manager GUI by monitor”?
Do you mean that there’s no display on the monitor before desktop showing?
A: Yes, it should be able to enter the UEFI boot manager by pressing ESC key.
When I flash on HostA , I can enter the UEFI boot manager through monitor by pressing ESC key.
When I flash on HostB, I can’t enter the UEFI boot manager through monitor by pressing ESC key,
the UEFI boot manager can display through debug UART.
The command you used on HostB to flash the board specifying above parameter, which would skip generating system image during flash.
I’m not sure if it could cause your issue.
This behavior is not expected to me since you can get the UEFI menu from debug Uart but not on monitor.
What would you get on the monitor at this moment?
1.If I don’t use “–no-systemimg” parameter, and use the same flash command on HostA. I can’t see the Ubuntu login GUI by monitor, but can login by debug uart.
Does UEFI menu control by uefi_Jetson_RELEASE.bin ?
2.What would you get on the monitor at this moment?
A: The monitor is on with black background.
I replace the uefi_jetson.bin from r35.4.1 to r35.5.0 , and flash by command
./flash.sh -k A_cpu-bootloader -c bootloader/t186ref/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit nvme0n1p1