The orin nx series often fails to start after burning

[fu.qiang]

The orin nx series often fails to start after burning.Unable to log in to the last step interface after frequent burning.Require duplicate registration after reboot
The probability is high, which leads to many of our products being like this now.

What is the likely cause.

[fu.qiang]

Burning instructions
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

[MarkusHoHo]

Hi @fu.qiang,

I moved your post to the correct category within the Jetson forums, I hope that is ok.

Thanks!

[Jeffli]

Hi fu.qiang,
May I know which BSP version you flashed?

[fu.qiang]

Bsp is based on R35.3.1.

[fu.qiang]

This phenomenon can be encountered with orin nx 8G/16G

[kayccc]

Sorry for the late response.
Is this still an issue to support? Any result can be shared?
Are you using devkit or with custom carrier board?

[alive]

have deal the problem? i still facing this prob, using JetPack_5.1.2_Linux_JETSON_ORIN_NX_TARGETS firmware, and command with

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

[fu.qiang]

The problem has been resolved.I transferred from ubuntu22.04 to ubuntu18.04 for development and there were no issues. Although I don’t understand why

[Jeffli]

Hi fu.qiang,
Could you try c add --no-systemimg in command like this:

For a device with internal QSPI and external NVMe:
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 --no-systemimg” --network usb0
external