Flashing failure for jetson orin NX

flash.log.txt (256.3 KB)
uart.log.txt (35.0 KB)

Hello, I am trying to write the system of orin nx module on the official orin nano carrier board with BSP version L4TR35.3.1, and the R231 pulp-up resistor on the carrier board has also been welded, and the SSD used is M.2 aigo P2000 Gen3.0 256GB, but I have tried for many times, but I have not been successful. Waiting for target to boot-up… In this step, tar: Read checkpoint 70000 prompts an unidentified USB device.

The refresh command to be executed is:
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 p3509-a02+p3767-0000 internal

Are you talking about official orin nano devkit carrier board?

If so, it seems you use the wrong board config. p3509-a02 is for xavier nx devkit board.

Hello, I am talking about official orin nano devkit carrier board.I tried again with this command, the error is the same as before, this is a new log.

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

flash.log.txt (545.6 KB)
uart.log.txt (99.4 KB)

What is your purpose to add this?

I think there are something to check here

  1. If this is devkit, then please also try with rel-35.4.1/jeptack5.1.2 from sdkmanager.

  2. Please also try other kind of nvme. Or even usb drive.

Hello, according to your suggestion, I tried to use SDK Manager Jetpack5.1.2, and the result was almost the same as before.It showed that USB device could not be detected and then failed to exit after brushing. The SSD I used to brush the Orin nano system on this official kit was successful. As for what you said about changing a solid-state hard drive or a USB hard drive, I have also tried these methods, but still failed, looking forward to your reply.
SDKM_logs_JetPack_5.1.2_Linux_for_Jetson_Orin_NX_modules_2023-12-04_17-36-28.zip (160.1 KB)
uart.log.txt (107.9 KB)

Could you share the boot failure log with a usb drive?

image

According to the schematic diagram provided by the official orin nano board, when the Orin nx module is burned, the power supply is 5V when R231 is not attached, and the power supply is 19V when R231 is attached. When I tried to power the orin nx module 5V, the operating system could not be burned. I tried to write the operating system to the orin nx module with 19V power supply, but the result was still unsuccessful.

Hello, this is the log that failed to use USB hard drive.


SDKM_logs_JetPack_5.1.2_Linux_for_Jetson_Orin_NX_modules_2023-12-04_19-08-47.zip (243.5 KB)
uart.log_USB.txt (142.3 KB)

請問你這台host PC有成功燒過任何其他的Orin NX/Nano過嗎?

還有為什麼有Windows的東西出現在這?

Hello, I have successfully burned Orin nano on this host PC. Orin nano can be successfully burned on both the official board and my custom board, but Orin NX has not succeeded once.

Hello, because I am using a virtual machine, so in the process of burning the system, when the virtual machine cannot detect the device, it will cause the windows prompt interface to appear. And I use the same virtual machine to burn Orin nano will not have this problem, can burn successfully.

Do you have other Orin NX module that can test on devkit on your side?

I only have one orin nx module at present, is there any other way to try it besides changing the module? I can try other methods as much as possible during the purchase of the module.

Are you sure same nvme can got flashed with sdkmanager on same carrier board you are using now with Orin Nano?

Hello, I am very sure that I have tried for many times, both SDK manager and BSP can write normally, and I have tried two versions, Jetpack5.1.1 and Jetpack5.1.2

Then please get a new Orin NX module first.

Ok, thank you very much

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.