Flashing Orin NX 16GB with JP5.1.5 and JP6.2.1 fails

Robotics & Edge Computing Jetson Systems Jetson Orin NX
1

Continuing the discussion from Flashing Orin NX Release 35.3.1 fails:

I can share that this is a Jetson module (not part of a dev kit), installed on a Seeed Studio J401 board.

This method has worked for us before on the Xavier NX modules and J202 boards, but with Orin NX 16GB fails.

Any idea as to what has changed? How to resolve this?

Thanks,

Moti.

2

*** Please note that this reply is generated by LLM automatically ***

Based on the provided context, it appears that you are experiencing issues with flashing the Jetson Orin NX 16GB module on a Seeed Studio J401 board. You mentioned that this method has worked for you before on Xavier NX modules and J202 boards, but it’s failing with the Orin NX 16GB module.

After reviewing the context, I found a few potential leads that might help resolve the issue:

  1. Pin compatibility: According to the context, Jetson Orin NX & Jetson Orin Nano series modules are not pin-compatible with Jetson Xavier NX series modules. However, it’s mentioned that you can design a carrier board for the I/Os they have in common, such that both modules are supported. It’s possible that the J401 board is not compatible with the Orin NX 16GB module, or there might be some interface differences that need to be addressed.
  2. Boot partitions: There’s a discussion about the differences in boot partitions between manual flash and OTA update. It’s possible that the flashing process is not correctly configuring the boot partitions for the Orin NX 16GB module.
  3. UEFI secure boot: There’s a mention of UEFI secure boot in the context, and it’s possible that the Orin NX 16GB module requires a specific configuration for UEFI secure boot to work correctly.
  4. Hardware-specific issues: There are several discussions about hardware-specific issues, such as thermal management, fan control, and HDMI display issues. It’s possible that the Orin NX 16GB module is experiencing some hardware-specific issues that are preventing it from booting correctly.

To resolve the issue, I would recommend the following steps:

  1. Verify the carrier board compatibility: Double-check that the J401 board is compatible with the Orin NX 16GB module, and that all necessary interfaces are correctly connected.
  2. Check the boot partitions: Verify that the boot partitions are correctly configured for the Orin NX 16GB module. You can try using the flash.sh script with the --boot-partitions option to specify the correct boot partitions.
  3. Configure UEFI secure boot: If UEFI secure boot is enabled on the Orin NX 16GB module, ensure that it’s correctly configured. You can try disabling UEFI secure boot to see if it resolves the issue.
  4. Monitor the system logs: Check the system logs for any error messages or warnings that might indicate the cause of the issue.
  5. Try a different flashing method: If the above steps don’t resolve the issue, try using a different flashing method, such as using the flash.sh script with the --no-flash option to flash the module without booting it.

I hope these suggestions help you resolve the issue. If you have any further questions or need more specific guidance, feel free to ask!

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

5

We don’t guarantee a custom board could get flashed by sdkmanager. Please contact your board vendor instead.

6

Dear @WayneWWW ,

Thank you for the response, I do notice that seeed have a separate wiki for the orin line, but the problem persists.

When referring to carrier boards that are supported by sdkmanager, do you mean for example:

AVerMedia D133S or ConnectTech NGX027?

Moti.

7

Sdkmanager could only guarantee flashing NVIDIA developer kit. Anything from either Avermedia or ConnectTech is their own carrier board which we call custom board.

8

Okay @WayneWWW, I get it, so the only measure would be buy a dev kit for a jetson nano for example, replacing the module with a NX 16 GB and test with sdkmanager?

9

I don’t know what is your purpose here.

I didn’t mean you need to buy anything. My point is just if you want to use a custom board, then you should check with the board vendor how to flash their board.
Generally they will provide their own package (mostly based on sdkmanager image but with modification to meet their hardware)

I just checked your post. The error you got there for now is just your host PC does not support IPv6.

IPv6 is disabled. Please enable ipv6 to use this tool
Error: ipv6: IPv6 is disabled on this device.
Error: ipv6: IPv6 is disabled on this device.

If you don’t fix this, then even getting a NV devkit will not help. The problem is the setting on your host PC, not Jetson.

10

Thanks @WayneWWW , I’ll look into that first.

Since I was hoping to proceed with the quickest supported way to flash the board, without going through external vendors.

Like you mentioned, the problem is probably in another thing, as the error with their custom BSP flashing process remains the same.

Giving it a try.

11

@WayneWWW apparently ipv6 is supported, but on physical interfaces.

Specifically on the USB interface that is created by the flash script (denoted enx76176c2d07d5) only the ipv4 address is set as 192.168.123.120, but no ipv6 is attached to it.

Running on ubuntu 24.04.

I’ll try to look after this, as I understand there is no bypass to use ipv4 addressing instead?

12

Quick update, despite manual configuration of /etc/sysctl.con, the usb ethernet connection didn’t get ipv6 enabled, so had to enable it manually through the system settings / network manager screen.

13

@WayneWWW I can confirm that it was that subtle issue with the USB network tethering not having IPv6 enabled automatically.

After doing so, even going through the procedure of the cli or sdkmanager flash works well for JP6.2.1.

THANKS!

Moti.