Unable to flash Orin NX devkit

[rstubbs]

Hi all,

I am running into an issue where I cannot flash this Orin NX devkit (Orin NX + orin nano carrier board) using Nvidia SDK and command line. Every attempt fails with the same “ERROR: might be timeout in USB write”.

Some data points:

1. The host is native Ubuntu 20.04.
2. The devkit is in recovery mode and can the host can detect the board via lsusb.
3. Nvidia SDK can also detect the board in recovery mode and can detect the module type with no issues.
4. I can successfully flash a Xavier NX devkit, and an Orin Nano devkit with no issues.
5. I have tried jetpack versions 5.1.1, 5.1.2, 5.1.3, 6.0 rev1, and 6.0 rev 2. All versions terminate with the same error when attempting to flash the Orin NX
6. If I put the Orin Nano module in the carrier board that came with the Orin NX devkit, I can flash the Orin Nano SD card, and also the external nvme drive.

I have used the recommended flash command to attempt to flash both NVME and USB:

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

and

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device sda1 \ -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

Attached is the log.
orin_nx_flash_log.txt (12.3 KB)

[DaveYYY]

Hi,

[   0.2708 ] Sending bct_br
[   0.2708 ] ERROR: might be timeout in USB write.
Error: Return value 3

Jetson AGX Orin FAQ

Q: How do I know which Jetson Linux release I am using? Please execute the command to get information: $ cat /etc/nv_tegra_release # R35 (release), REVISION: 1.0, GCID: 31346300, BOARD: t186ref, EABI: aarch64, DATE: Thu Aug 25 18:41:45 UTC 2022 If you see R34, the release is developer preview, and please upgrade to at least >= r35.1 Q: How to know if I use Orin developer kit or Orin 32GB module? Please execute the command: $ cat /etc/nv_boot_control.conf And check the information: [Orin d…

Also, you should be using jetson-orin-nano-devkit for flashing, instead of p3509-a02+p3767-0000 if it’s really an Orin Nano DevKit board.

[rstubbs]

I had already disabled autosuspend on my host. I forgot to mention that it did not help in this case.

I attached a log after changing the device name to jetson-orin-nano-devkit.

orin_nx_flash_log_2.txt (222.5 KB)

[DaveYYY]

Board ID() version() sku() revision()
Chip SKU() ramcode() fuselevel(fuselevel_production) board_FAB()
emc_opt_disable_fuse:(0)

Are you sure the device is in force recovery mode?
The board info is not even detected.

/home/user/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra
Success
Cleaning up...
Finish generating flash package.
No devices to flash

[DaveYYY]

Also, I just found the vendor provides their own customized BSP, so you should be using this instead of the one downloaded with SDK Manager:
https://drive.google.com/drive/folders/1hvd9qg5qz9AKugmed2dBMvl684AzFMXM

[rstubbs]

Are you sure the device is in force recovery mode?

The device is in recovery mode.

user@workstation:~/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 0a5c:5842 Broadcom Corp. 58200
Bus 003 Device 003: ID 1bcf:2ba9 Sunplus Innovation Technology Inc. Integrated_Webcam_FHD
Bus 003 Device 030: ID 0955:7423 NVIDIA Corp. APX
Bus 003 Device 005: ID 8087:0026 Intel Corp. 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Regarding the vendor BSP: we are attempting to integrate another 3rd party product with an Orin NX on a custom carrier board… if at all possible we would like to use the stock nvidia images to show a proof-of-concept. The version of jetpack in that BSP (5.1.1) is incompatible with the software package needed for the 3rd party product we are integrating.

[DaveYYY]

@rstubbs

Regarding the vendor BSP: we are attempting to integrate another 3rd party product with an Orin NX on a custom carrier board… if at all possible we would like to use the stock nvidia images to show a proof-of-concept.

You should first try the one that the board vendor gives.

[rstubbs]

I already have. The product software bricks the vendor OS image. The product overwrites the kernel and device tree along with some kernel modules, and they specify it only works on systems that are JetPack 5.1.2.

[rstubbs]

On my desk I have a Xavier NX dev kit, an Orin Nano devkit, and this Orin NX devkit. I can flash all of them except for the NX. I am willing to gather whatever information needed to solve this issue, but I need some way of flashing a bootable 5.1.2 image onto this Orin NX.

[DaveYYY]

@rstubbs

The product software bricks the vendor OS image. The product overwrites the kernel and device tree along with some kernel modules, and they specify it only works on systems that are JetPack 5.1.2.

What exactly do you mean here?

[rstubbs]

They have an installation script that overwrites the boot Image, device tree binary, and kernel modules pertaining to their camera product. When these components are replaced, the board fails to boot into the Ubuntu installation. After the bootloader, there is just a black screen and no output.

[DaveYYY]

Then put the serial console log here.
I still have no idea what’s going on.

[rstubbs]

I am able to flash the Orin NX only after I manually format the nvme drive, by putting it into one of the other dev kits, booting from the internal memory, removing all the existing partitions, formatting one partition to ext4 format, and then reinstalling on the NX board.

This is an issue with the flashing software, it fails to format the drive and then it gives a USB timeout error. I don’t know the reason. Is there any update for this issue?

[DaveYYY]

There is no update from you for a period, assuming this is not an issue any more.
Hence we are closing this topic. If need further support, please open a new one.
Thanks

Put the log, please.