ORIN NX 16G flash error: “Waiting for target to boot-up...”

[jack.yan]

Hi:
My Hardware Device: orin nx 16G
software version:JetPack 5.1.4

SSD:256G.

I successfully flashed Orin Nano 4g and Orin NX 8G using the command, but failed when flashing Orin NX 16g. The flashing command is as follows:

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_t234_qspi.xml"   --showlogs --network usb0 jetson-orin-nano-devkit internal

I use my own designed hardware for flashing, only replacing the core board. Only Orin NX 16g failed;

I tried to use SDKManager flashed and still failed.

flashing log:

nx_16g_cmd_flash_fail.txt (261.0 KB)

debug uart log:

ÿäERROR:   Exception reason=0 syndrome=0xbe000011^M
ERROR:   **************************************^M
ERROR:   RAS Uncorrectable Error in IOB, base=0xe010000:^M
ERROR:          Status = 0xec000612^M
ERROR:   SERR = Error response from slave: 0x12^M
ERROR:          IERR = CBB Interface Error: 0x6^M
ERROR:          Overflow (there may be more errors) - Uncorrectable^M
ERROR:          MISC0 = 0xc44a0040^M
ERROR:          MISC1 = 0x1acc860000000000^M
ERROR:          MISC2 = 0x0^M
ERROR:          MISC3 = 0x0^M
ERROR:          ADDR = 0x8000000003f300c0^M
ERROR:   **************************************^M
ERROR:   sdei_dispatch_event returned -1^M
Unhandled Exception in EL3.^M
x30            = 0x0000000050011384^M
x0             = 0x0000000000000000^M
x1             = 0x0000000000000000^M
x2             = 0x0000000000000002^M
x3             = 0x0000000000000001^M
x4             = 0x0000000000000000^M
x5             = 0x0000000000000040^M
x6             = 0x0000000000000000^M
x7             = 0x0000000000000002^M
x8             = 0x0000000050001f74^M
x9             = 0x0000000000000000^M
x10            = 0x0000000000011014^M
x11            = 0x000000046e9fe84c^M
x12            = 0x000000043ff55000^M
x13            = 0x0000000000011014^M
x14            = 0x000000043979e398^M

nx_debug_uart.log (45.0 KB)

[carolyuu]

*** 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 16G module using your own designed hardware. You have successfully flashed the Orin Nano 4G and Orin NX 8G modules using the same command, but the Orin NX 16G module fails to flash.

To troubleshoot this issue, let’s compare the differences between the Orin NX 16G and the other modules that you have successfully flashed.

1. Module type: The Orin NX 16G module has a different module type compared to the Orin Nano 4G and Orin NX 8G modules. The Orin NX 16G module has a larger memory capacity (16GB) compared to the other two modules (4GB and 8GB, respectively).
2. Flash command: The flash command you provided is the same for all three modules. However, it’s possible that the command is not compatible with the Orin NX 16G module.
3. Hardware design: You mentioned that you are using your own designed hardware for flashing, which only replaces the core board. It’s possible that the hardware design is not compatible with the Orin NX 16G module.

To resolve this issue, you can try the following:

1. Check the flash command: Verify that the flash command is correct and compatible with the Orin NX 16G module. You can refer to the Jetson Linux Toolchain documentation for more information on flashing commands.
2. Update the hardware design: Ensure that your hardware design is compatible with the Orin NX 16G module. You may need to update the design to accommodate the larger memory capacity of the Orin NX 16G module.
3. Use SDKManager: You mentioned that you tried using SDKManager to flash the Orin NX 16G module, but it failed. Try using SDKManager again, and ensure that you are using the correct version of SDKManager that is compatible with the Orin NX 16G module.
4. Check the flashing log: Analyze the flashing log (nx16g_cmd_flash_fail.txt) to identify any error messages or issues that may be causing the flashing process to fail.
5. Check the debug UART log: Analyze the debug UART log (nx_debug_uart_log) to identify any error messages or issues that may be causing the flashing process to fail.

By comparing the differences between the Orin NX 16G module and the other modules, and by troubleshooting the flashing process, you should be able to identify and resolve the issue preventing you from flashing the Orin NX 16G module.

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

[DavidDDD]

Hi,

Do you mean that using the Orin Nano 4GB with your custom-designed board, and flashing it with the SDK Manager, will be successful?

[jack.yan]

Hi, DavidDDD:

Thanks for your reply.

@DavidDDD

Do you mean that using the Orin Nano 4GB with your custom-designed board, and flashing it with the SDK Manager, will be successful?

yes, and Orin NX 8GB is already successful.only Orin NX 16GB flashing failed.

[DavidDDD]

Hi,

Thanks for your information.

Please try flash with JP5.1.5 with the sdk manager to check whether the issue exists.

Thanks

[jack.yan]

Hi,DavidDDD:

I successfully flashed JetPack5.1.5 on Orin NX 16GB, but why is JetPack5.1.4 not supported?

[DavidDDD]

Hi,

It might be some PCN problem.

Thus, we suggest to update to the latest bsp.

Thanks

[jack.yan]

Hi,DavidDDD:

@DavidDDD

It might be some PCN problem.

Can this issue be fixed in JetPack 5.1.4? We use Orin Nano and Orin NX 8GB both using 5.1.4. If Orin NX 16GB use another JetPack version, it will cause some difficulties.

[DavidDDD]

Hi,

Do you have a development kit to verify if the issue also occurs on JP5.1.4?
If you are using a custom board, we still recommend updating to the latest version, 5.1.5.

Thanks

[jack.yan]

Hi,DavidDDD:

I haven`t development kit with Orin NX 16GB, Only my custom board.Function development has been completed using JetPack 5.1.4, but switching to JetPack5.1.5 may pose risks and affect project progress.

[DavidDDD]

Hi,

Sorry, since we are not familiar with your specific design, if the issue also occurs on our development kit, we will work on providing a fix.
You may refer to the PCN Center to verify if anything is missing.
If no, we still recommend upgrading to JP5.1.5.

Log in

Thanks

[jack.yan]

Hi,DavidDDD:

I have purchased the Orin Nano 4GB development kit before,Can use it to flash Orin NX 16GB?

[DavidDDD]

Hi,

Yes

Thanks

[jack.yan]

Hi,DavidDDD:

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_t234_qspi.xml"   --showlogs --network usb0 p3509-a02+p3767-0000 internal

Using “jetson-orin-nano-devkit” will fail.

[WayneWWW]

Then where is your UART log?

[jack.yan]

Hi,DavidDDD:

My description above is not clear.

When burning JetPack 5.1.4 with Orin nx 16GB, the following command can be used successfully:

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_t234_qspi.xml"   --showlogs --network usb0 p3509-a02+p3767-0000 internal

If I replace “p3509-a02+p3767-0000” in the command with “jetson-orin-nano-devkit”, the burning will fail.

Here is uart log:

@jack.yan

nx_16g_cmd_flash_fail.txt (261.0 KB)

debug uart log:

ÿäERROR:   Exception reason=0 syndrome=0xbe000011^M
ERROR:   **************************************^M
ERROR:   RAS Uncorrectable Error in IOB, base=0xe010000:^M
ERROR:          Status = 0xec000612^M
ERROR:   SERR = Error response from slave: 0x12^M
ERROR:          IERR = CBB Interface Error: 0x6^M
ERROR:          Overflow (there may be more errors) - Uncorrectable^M
ERROR:          MISC0 = 0xc44a0040^M
ERROR:          MISC1 = 0x1acc860000000000^M
ERROR:          MISC2 = 0x0^M
ERROR:          MISC3 = 0x0^M
ERROR:          ADDR = 0x8000000003f300c0^M
ERROR:   **************************************^M
ERROR:   sdei_dispatch_event returned -1^M
Unhandled Exception in EL3.^M
x30            = 0x0000000050011384^M
x0             = 0x0000000000000000^M
x1             = 0x0000000000000000^M
x2             = 0x0000000000000002^M
x3             = 0x0000000000000001^M
x4             = 0x0000000000000000^M
x5             = 0x0000000000000040^M
x6             = 0x0000000000000000^M
x7             = 0x0000000000000002^M
x8             = 0x0000000050001f74^M
x9             = 0x0000000000000000^M
x10            = 0x0000000000011014^M
x11            = 0x000000046e9fe84c^M
x12            = 0x000000043ff55000^M
x13            = 0x0000000000011014^M
x14            = 0x000000043979e398^M

nx_debug_uart.log (45.0 KB)

Is it correct to flashing with “p3509-a02+p3767-0000”? In nvidia documents, I should use “jetson-orin-nano-devkit” to flash device.

[WayneWWW]

No, none of them is correct if you are flashing a custom board.

Default board config does not 100% work with a custom board. You have to modify device tree inside of it to match your board.

address 0x8000000003f300c0 indicates there is problem on 0x3f300c0 which is P2U_GBE1.

Why does C9 get enabled there? Is that thing really in use?

[jack.yan]

Hi,WayneWWW:

I`m flashing custom board, I can successfully flash Orin Nano 4g and Orin NX 8g using the same command,only Orin NX 16G flash failed.

I set C7 pcie x2 to C7 pcie x1 and C9 pcie x1

use C9 to connect wifi modules.

[WayneWWW]

Then please review the ODMDATA is correctly set or not and also the DT.

[jack.yan]

Hi, WayneWWW:

In my understanding, if the ODMDATA configuration is incorrect, the orin nx 8G will also have the same flashing problem.Or is the configuration file used for Orin NX 16G different from Orin NX 8G?