Issue Flashing JetPack 5.1.2 on Orin NX (Previously Flashed with JetPack 6.2)

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin NX
1

Hello,

I am working with a Jetson Orin NX 16GB module along with a carrier board, and I’m trying to flash JetPack 5.1.2 onto the board.

Previously, the Orin NX was flashed with ‘JetPack 6.2’, and everything worked fine. However, after flashing JetPack 5.1.2 today, the system stops at the NVIDIA logo screen and shows the following messages:

L4TLauncher: Unable to locate L4T Support protocol: Not Found
L4TLauncher: Using legacy interface. Support would be deprecated soon!!!
L4TLauncher: Failed to get PlatformResourceInfo

This BSP used to work without any issues, and I haven’t changed anything since. But now, flashing 5.1.2 results in this error.

Could you please help me understand:

  • Why is this happening?
  • Is it still possible to flash JetPack 5.1.2 successfully onto this board?

I would appreciate a response as soon as possible. Thank you in advance.

2

Do you have full log but not just these 3 lines?

Is this a flash problem or a boot problem? Why your comment sounds like you already flashed the board and it is a boot problem?

Or you are not sure what I am asking about here?

3

KakaoTalk_Photo_2025-04-15-13-28-42 002jpeg
KakaoTalk_Photo_2025-04-15-13-28-42 002jpeg1298×1424 148 KB

KakaoTalk_Photo_2025-04-15-13-28-42 001jpeg
KakaoTalk_Photo_2025-04-15-13-28-42 001jpeg1920×2560 835 KB

The flash log indicates that the flashing process completed successfully.
However, during boot (at the NVIDIA logo screen), the following messages appear:

L4TLauncher: Unable to locate L4T Support protocol: Not Found  
L4TLauncher: Using legacy interface. Support would be deprecated soon!!!  
L4TLauncher: Failed to get PlatformResourceInfo

A few seconds after this, the system drops into a shell.
I can’t exit the shell, and I’m not sure how to proceed from here.

Since I’m unable to copy the logs directly, I’ve attached a photo showing the messages.
Thank you for your support.

4

Hi,

Just few items to first

  1. Please learn to dump serial console log by checking this website. We never use such graphic on the monitor to tell what is wrong.
    https://www.jetsonhacks.com/2019/04/19/jetson-nano-serial-console/

  2. Please try to relfash your board again and if it failed, give us the full text log of it. I need both host side and device side log. Device side log is the serial console log mentioned in (1). You need to start the flash process and capture the logs during flash.

5

I connected to the Jetson Orin NX through a serial interface and captured the full boot log. I would appreciate it if you could review it.

serial_console_dump.txt (74.1 KB)

6

Please flash your board again and with your flash log shared.

7

flash log
flash_log_250415.txt (286.0 KB)

serial_console_dump
serial_console_dump_250415.txt (224.2 KB)

Thank you for your support.

8

Is this a NV devkit or custom carrier board?

9

this is custom carrier board.

10

Then are you sure it is correct to use p3509 config to flash your board?

11

Yes.
You can find the command I used to initiate the flash process at the top of the flash_log.txt file I shared. Please refer to it for reference.

12

Hi,

What my point here is the p3509 config files are targeting for Orin NX + Xavier NX devkit combination usecase.

We don’t guarantee the device tree on it really fits your carrier board. Have you ever configured the devicetree + pinmux to fit your board?

13

The BSP I had been using already included a device tree customized for my carrier board, and it had been working without any issues.
However, after flashing JetPack 5 onto a board that was previously running JetPack 6, the message started appearing unexpectedly.

Currently, JetPack 6 was successfully flashed and working without any issues.
However, when I attempted to re-flash the board with JetPack 5, the process failed and is no longer working as expected.

14

Hi,

I don’t know what you are trying to say here.

The BSP for Jetpack6 is for Jetpack6. It cannot be used for Jetpack5. You cannot move the device tree for Jetpack6 directly for Jetpack5. You have to port similar things again.

I don’t see much point to keep mentioning jetpack6 here. It only proves your hardware seems to be good.

But what I am asking here is whether you configured the software for Jetpack5 too.

15

Hi,

Thanks for your response.

Let me clarify. We have successfully ported and used Jetpack 5 with our custom carrier board, and it was working fine. Later, we also ported Jetpack 6 for the same board and verified that it worked properly too.

Recently, we tried to downgrade from Jetpack 6 back to Jetpack 5 and reflashed the board using the Jetpack 5 BSP that was specifically ported for our carrier board. So yes, we did configure the software for Jetpack 5 accordingly.

The reason I brought up Jetpack 6 is because I was wondering if the UEFI version—possibly changed or upgraded during the Jetpack 6 usage—might be causing issues when trying to run Jetpack 5 again. That’s why I mentioned Jetpack 6, not to say we’re trying to reuse its BSP.

Hope this clears things up.

16

Did you ever change the content of BOOTAA64.efi before? This is for the L4TLauncer.

17

I haven’t changed the BOOTAA64.efi file. It’s still the original version.

18

I guess this won’t happen but still want to ask again.

Is your issue able to reproduce on that same module on NV devkit?

19

I’m not entirely sure since this is something I heard from others, but I recall there was a UEFI version issue on the Orin Nano devkit. I remember hearing that UEFI needed to be updated in Jetpack 5 in order to make it work. However, I’m not certain if that issue is directly related to the one I’m experiencing now.

In any case, I haven’t encountered this issue on the devkit.

It seems that the issue occurred on the devkit in this link. Was the root cause not identified in that case?

20

That post is just some Orin Nano users who don’t know how to run initrd flash. Most of them are just newbies who don’t have experience to flash a NV devkit.

You could see that most of them just make that work after using sdkmanager flash.
The point in that post is just “if you use sdcard image, then UEFI version won’t get updated”.

But your case is totally different. There is no sdcard image here.

Please be aware that “changing a UEFI version” is a obvious thing from UART log.

Jetson UEFI firmware (version 4.1-33958178 built on 2023-08-01T19:34:02+00:00)

There is no Jetpack6.2 on 2023 08/01 at all. This means UEFI version is already going back to Jetpack5.