Flashing to jetpack 5.1.2

I have flashed from jetpack4.6 to jetpack5.1.2 R35.4.1 with recovery mode on emmc and then nvme ssd using SDK manager (tried also other 5.1.1 and 5.1.3 the same issue).

I also tried with simply “./flash.sh jetson-xavier-nx-devkit-emmc mmcblk0” and also “sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external_device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p “-c bootloader/t186ref/cfg/flash_l4t_t194_qspi_p3668.xml” --showlogs --network usb0 jetson-xavier-nx-devkit-emmc internal”.

In all of the cases flashing says to be completed successfully, and boots. Only when rebooting, I always enter the following state as in the picture. If usbs are unmounted, it passes quickly and boots normally, otherwise, if I do not select any option → black screen. if I press Esc I get into the UEFI menu with malfunctioning keyboard (cannot properly navigate with arrows to select, although before and after this menu works properly). Checked with nvbootctrl dump-slots-info, versions of QSPI and Jetpack (R35.4.1) match.

The questions are:

  1. why does it enter this menu if I do not call it explicitly (it appears by itself even before NVIDIA logo screen, without any ESC on it)? Is there any problem with flashing of the jetpack5.x
  2. how to get rid of it and boot fast as with Jepack4.x?

Flashing back to Jetpack 4, it works perfectly and I didn’t see that menu while booting.

Jetson xavier nx devkit emmc (16Gb) and Transcend 128Gb nvme ssd. Carrier board 3668-003.

Here’s ERROR logs from flashing nvme using SDK manager:
13:23:39 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 430000
13:23:41 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 440000
13:23:42 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 450000
13:23:42 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 460000
13:23:42 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 470000
13:23:43 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 480000
13:23:43 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 490000
13:23:44 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 500000
13:23:45 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 510000
13:23:45 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 520000
13:23:45 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 530000
13:23:46 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 540000
13:23:46 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 550000
13:23:46 ERROR: Flash Jetson Linux - flash: tar: Write checkpoint 560000
13:24:13 ERROR: Flash Jetson Linux - flash: 42010 blocks
13:24:13 ERROR: Flash Jetson Linux - flash: gzip: /home/bota/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/kernel/Image: not in gzip format
13:24:17 ERROR: Flash Jetson Linux - flash: 58243 blocks
13:24:17 ERROR: Flash Jetson Linux - flash: 20+0 records in
13:24:17 ERROR: Flash Jetson Linux - flash: 20+0 records out
13:24:17 ERROR: Flash Jetson Linux - flash: 20 bytes copied, 0,0001541 s, 130 kB/s
13:24:18 ERROR: Flash Jetson Linux - flash: 131072+0 records in
13:24:18 ERROR: Flash Jetson Linux - flash: 131072+0 records out
13:24:18 ERROR: Flash Jetson Linux - flash: 67108864 bytes (67 MB, 64 MiB) copied, 0,161305 s, 416 MB/s

13:24:23 ERROR: Flash Jetson Linux - flash: /home/bota/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/bootloader/L4TConfiguration_updated.dts: Warning (unit_address_vs_reg): Node /fragment@0 has a unit name, but no reg property

13:24:23 ERROR: Flash Jetson Linux - flash: /home/bota/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/bootloader/L4TConfiguration.dtbo: Warning (unit_address_vs_reg): Node /fragment@0 has a unit name, but no reg property

13:24:23 ERROR: Flash Jetson Linux - flash: /home/bota/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/bootloader/L4TConfiguration_updated.dts: Warning (unit_address_vs_reg): Node /fragment@0 has a unit name, but no reg property

13:24:23 ERROR: Flash Jetson Linux - flash: /home/bota/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/bootloader/L4TConfiguration.dtbo: Warning (unit_address_vs_reg): Node /fragment@0 has a unit name, but no reg property
13:24:27 ERROR: Flash Jetson Linux - flash: 58243 blocks
13:24:31 ERROR: Flash Jetson Linux - flash: 87001 blocks
13:25:31 ERROR: Flash Jetson Linux - flash: Error: The backup GPT table is corrupt, but the primary appears OK, so that will be used.
13:25:33 ERROR: Flash Jetson Linux - flash: Error: The backup GPT table is not at the end of the disk, as it should be. Fix, by moving the backup to the end (and removing the old backup)?
13:30:06 SUMMARY: Flash Jetson Linux - flash: Install completed successfully.

I am not sure what is your exact problem. Are you saying that you don’t know why there is a text there before NVIDIA logo?

I would like to get rid of it and boot normally. First of all, I do not know why it appears and make sure flashing is completed properly. If flashing is not a problem, and if this screen do not affect anything, I would like to boot without unplugging all the usbs for it to complete booting.

Your flash has finished and you can just try to boot up.

I have done it and all works properly. But every time I power it on, I encounter that screen. To complete the booting, I need to unplug usbs before powering it on. Otherwise I get stuck on that menu.

These questions need to be clarified first so that we can go next step

  1. Is this NV devkit or custom board? Or you are not sure what is custom carrier board?

  2. What kind of usb needs to be removed? Is there any specific device that needs to be removed? Or even just one usb mouse will cause such situation?

  1. devkit P3368-0003 with emmc
  2. just with trials I figured out that it always boots when keep keyboard and mouse upluged when power it on. Sometimes it continues to boot with keyboard plugged and pressing Enter; pressing ESC it enter the menu where I lose control of the keyboard. With keyboard plugged and just waiting leads to a black screen.

Hi,

Could you just test this on your board first?

  1. Please use sdkmanager to flash your board with either jetpack5.1.2 or 5.1.3 to the emmc. Do not flash nvme for now.

  2. After flash, please test this situation would happen again or not.

  3. Please use serial console to check the boot status instead of monitor.
    https://www.jetsonhacks.com/2019/04/19/jetson-nano-serial-console/

If this is NV devkit, then such issue would have been reported by many users. However, it didn’t.
Thus, need to do more test to know what is going on.

yes it happens even when only emmc is flashed. Ordered USB to TTL serial cable I’ll update you as soon as I test it with serial console.

1 Like

Could you keep only mouse but no keyboard there and see if you still see such issue?

yes, it entered the menu and keeps randomly walking among the options (Select Language, Device Manager …) without action from my side.

I have run more experiments with different configuration of mouse and keyboard on/off: I looks very random now.
both on - 4/4 booted ok;
mouse on, keyboard off - 2/4 ok, 2/4 UEFImenu;
mouse off, keyboard on - 4/4 ok;
both off - 2/6 no booting-power off by itself, 2/6 - uefi menu, 2/6 booted ok.

Could you take a photo of your carrier board?


Please remove all the peripherals and take the photo and do the test again.

Leave only USB keyboard/mouse there.


In all the cases and all trials the same screen appears but boots properly. Does it mean there is incompatability with any of the peripherals?

When I said peripherals, I mean that nvme and m.2 card also needed to be removed…

Also, there are some misleading situation here.

  1. Your board has a label printed “Jetson Nano IF Board” on it

  2. A real NV devkit - if it is jetson nano, it does not have nvme slot. if it is XNX, it won’t print it is jetson nano.
    Thus, you are using a custom board.

We cannot guarantee custom board issue. If you are not the board vendor, please contact board vendor for this issue.



ok I have removed them, the same outcome.


it is removable, just used to attach some sensors

Yes, this picture showed this is not NV devkit. Please contact board vendor to report this issue.