Jetpack6.2 to jetpack5.1.5

hi every body;
I am using an Orin NX and have installed JetPack 6.2 on it. For some reasons, I need to have JetPack 5.1.5 on the board. I can do this using SDK Manager, but I am unable to do it with the command line. How can I resolve this issue?
I am using the following command for flashing.
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_t234_nvme.xml -p "-c bootloader/generic/cfg/flash_t234_qspi.xml" --showlogs --network usb0 jetson-orin-nano-devkit-super internal

Hi,

Please refer to JP5.1.5 Quick Start — NVIDIA Jetson Linux Developer Guide 1 documentation .

The command is slightly different to JP6.2

Thanks

thanks for your reply,
I reviewed this document and followed the procedure, but after the flashing is complete, the board only gives me a shell, and there is no operating system.


I/TC: WARNING: UEFI variable protection is not fully enabled !
I/TC: WARNING: Test UEFI variable auth key is being used !
I/TC: WARNING: UEFI variable protection is not fully enabled !
I/TC: WARNING: Test UEFI variable auth key is being used !
I/TC: WARNING: UEFI variable protection is not fully enabled !
I/TC: WARNING: Test UEFI variable auth key is being used !
I/TC: WARNING: UEFI variable protection is not fully enabled !
I/TC: WARNING: Test UEFI variable auth key is being used !
I/TC: WARNING: UEFI variable protection is not fully enabled !
I/TC: WARNING: Test UEFI variable auth key is being used !
I/TC: WARNING: UEFI variable protection is not fully enabled !
I/TC: WARNING: Test UEFI variable auth key is being used !
I/TC: WARNING: UEFI variable protection is not fully enabled !
I/TC: WARNING: Test UEFI variable auth key is being used !
I/TC: WARNING: UEFI variable protection is not fully enabled !
I/TC: WARNING: Test UEFI variable auth key is being used !
I/TC: WARNING: UEFI variable protection is not fully enabled !
I/TC: WARNING: Test UEFI variable auth key is being used !
I/TC: WARNING: UEFI variable protection is not fully enabled !
I/TC: WARNING: Test UEFI variable auth key is being used !
I/TC: WARNING: UEFI variable protection is not fully enabled !
I/TC: WARNING: Test UEFI variable auth key is being used !
I/TC: WARNING: UEFI variable protection is not fully enabled !
I/TC: WARNING: Test UEFI variable auth key is being used !
I/TC: WARNING: UEFI variable protection is not fully enabled !
I/TC: WARNING: Test UEFI variable auth key is being used !
I/TC: WARNING: UEFI variable protection is not fully enabled !
I/TC: WARNING: Test UEFI variable auth key is being used !
I/TC: WARNING: UEFI variable protection is not fully enabled !
I/TC: WARNING: Test UEFI variable auth key is being used !
I/TC: WARNING: UEFI variable protection is not fully enabled !
I/TC: WARNING: Test UEFI variable auth key is being used !
I/TC: WARNING: UEFI variable protection is not fully enabled !
��Jetson UEFI firmware (version 6.1-39721438 built on 2025-03-04T09:36:16+00:00)
ESC   to enter Setup.
F11   to enter Boot Manager Menu.
Enter to continue boot.
**  WARNING: Test Key is used.  **
......L4TLauncher: Unable to locate L4T Support protocol: Not Found
L4TLauncher: Using legacy interface. Support would be deprecated soon!!!
L4TLauncher: Failed to get PlatformResourceInfo

  Error: Could not detect network connection.

  Error: Could not detect network connection.


UEFI Interactive Shell v2.2
EDK II
UEFI v2.70 (EDK II, 0x00010000)
Mapping table
      FS2: Alias(s):HD2b:;BLK1:
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x1416000
0,0x1417FFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,B6-8A-B5-11-A8-38-
25-00)/HD(1,GPT,03FA9759-0C82-429F-B13A-F1023079521A,0x28EE28,0x6E00000)
      FS3: Alias(s):HD2k:;BLK2:
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x1416000
0,0x1417FFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,B6-8A-B5-11-A8-38-
25-00)/HD(10,GPT,4461E56F-4DB4-4F88-A28C-C02C6CD56135,0xC8A28,0x96000)
      FS4: Alias(s):HD2l:;BLK3:
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x1416000
0,0x1417FFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,B6-8A-B5-11-A8-38-
25-00)/HD(11,GPT,7CC574B5-1BD5-4A1F-A17A-FA4368267629,0x15EA28,0x20000)
      FS1: Alias(s):F1:
          MemoryMapped(0xB,0x46E600000,0x46E8BFFFF)
      FS0: Alias(s):F0:
          Fv(49A79A15-8F69-4BE7-A30C-A172F44ABCE7)
     BLK0: Alias(s):
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x1416000
0,0x1417FFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,B6-8A-B5-11-A8-38-
25-00)
     BLK8: Alias(s):
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x1416000
0,0x1417FFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,B6-8A-B5-11-A8-38-
25-00)/HD(2,GPT,30C46C14-DA55-41AE-B0AC-EA770796B028,0x28,0x40000)
     BLK9: Alias(s):
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x1416000
0,0x1417FFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,B6-8A-B5-11-A8-38-
25-00)/HD(3,GPT,70FFEFFD-2701-4D3D-B38E-5E2DF5A4980E,0x40028,0x600)
    BLK10: Alias(s):
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x1416000
0,0x1417FFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,B6-8A-B5-11-A8-38-
25-00)/HD(4,GPT,2CB0B1B3-B02D-4852-84B2-6F41A1771726,0x40628,0xFD00)
    BLK11: Alias(s):
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x1416000
0,0x1417FFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,B6-8A-B5-11-A8-38-
25-00)/HD(5,GPT,184440E9-8F5B-4A55-A6EF-0253CD60D429,0x50328,0x40000)
    BLK12: Alias(s):
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x1416000
0,0x1417FFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,B6-8A-B5-11-A8-38-
25-00)/HD(6,GPT,48ADBE99-33F7-44BE-B9F4-1027CD410561,0x90328,0x600)
    BLK13: Alias(s):
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x1416000
0,0x1417FFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,B6-8A-B5-11-A8-38-
25-00)/HD(7,GPT,34569F38-FCAD-4F98-A458-EF08AB004253,0x90928,0xFD00)
    BLK14: Alias(s):
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x1416000
0,0x1417FFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,B6-8A-B5-11-A8-38-
25-00)/HD(8,GPT,481DD14A-315D-4820-8DCE-515B2878E129,0xA0628,0x28000)
    BLK15: Alias(s):
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x1416000
0,0x1417FFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,B6-8A-B5-11-A8-38-
25-00)/HD(9,GPT,534B8AC6-0B1A-42B3-84A1-9D47DBF60F04,0xC8628,0x400)
     BLK4: Alias(s):
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x1416000
0,0x1417FFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,B6-8A-B5-11-A8-38-
25-00)/HD(12,GPT,4271CC02-2CE5-456A-899E-8D4FEB0CB65A,0x17EA28,0x28000)
     BLK5: Alias(s):
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x1416000
0,0x1417FFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,B6-8A-B5-11-A8-38-
25-00)/HD(13,GPT,5FBFBC41-8D2F-4290-B86D-8A04DA7A6D28,0x1A6A28,0x400)
     BLK6: Alias(s):
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x1416000
0,0x1417FFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,B6-8A-B5-11-A8-38-
25-00)/HD(14,GPT,274EC127-61F2-4B9B-A7BC-72095F60A55B,0x1A6E28,0x20000)
     BLK7: Alias(s):
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x1416000
0,0x1417FFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,B6-8A-B5-11-A8-38-
25-00)/HD(15,GPT,6B345E9F-150C-4262-8A61-E72EE92F5233,0x1C6E28,0xC8000)
Press ESC in 1 seconds to skip startup.nsh or any other key to continue.
Shell>

Is my issue solvable?

Hi,

Is your Orin NX plugged into any Ethernet devices?
If yes, please remove it and boot again.

Also the command mentioned in UEFI Adaptation — NVIDIA Jetson Linux Developer Guide could change the boot order.

Thanks

thanks for your reply,
No Ethernet device is connected to the board.
We used the following command for flashing, and the result was the same as before.

sudo ADDITIONAL_DTB_OVERLAY_OPT="BootOrderNvme.dtbo" ./tools/kernel_flash/l4t_initrd_flash.sh --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-super internal

Is my issue solvable?

Hi,

One question to confirm:

Is your carrier board a dev kit or a custom board?
Also please provide the serial console log during flashing process for further check.

Thanks

Hi,
thanks for your reply,
I have a custom board. the serial console log is attached.
flash.log (127.7 KB)

My problem still hasn’t been resolved.

Hi,

Some questions to confirm:

You could flash JP 5.1.5 using SDK Manager, but flashing it via the command line might fail?

Thanks

Hi,
Yes, we could flash JP 5.1.5 using SDK Manager, but flashing it via the command line might fail.

Hi,

Got it.

Based your log, it might enter in PXE boot.
Could you try to enter Boot Manager in UEFI and manually choose NVMe as a boot device.

Jetson UEFI firmware (version 6.1-39721438 built on 2025-03-04T09:36:16+00:00)
ESC   to enter Setup.
F11   to enter Boot Manager Menu.
Enter to continue boot.

Thanks

I’ll check on this and let you know.

When I select the option to boot from NVMe, no changes are observed, and practically, there is no possibility of selection.

I hope the issue gets resolved.

Hi,

Sorry, we need the more log to reivew.

Please use sdk manager to flash your device again, and provide two log:

  1. press EXPORT LOG button and attach the sdk log
  2. Record the serial log during flashing

Please use command line and also provide two log:

  1. flashing log
  2. serial log

One question to confirm:
How do you prepare the command line way bsp?
Do you flash it under the ~/nvidia/nvidia_sdk/ or download the bsp from JetPack Archive | NVIDIA Developer?

Thanks

I used sdkmanager to create L4T and set a local path for it.
I’m flashing and will send you the log.

SDKM_logs.zip (1.1 MB)
serialLog_sdkmanager.txt (193.1 KB)

flash_commandlineFlash.txt (286.8 KB)
serialLog_commandlineFlash.txt (134.8 KB)