HELP Can't flash Jetson Orin Nano 8GB with SDK Manager

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin Nano
1

Hi everyone,

I have a new 8GB Orin Nano Devkit that I am trying to flash with SDK Manager (2.1.0.11682). I have a 512GB NVME SSD installed in the Nano and no SDCard. I’m using Ubuntu 22.04. I have the recovery jumper installed on the Nano and SDK Managers sees my Nano via the USB connection.

Packages get downloaded but the flash always fails. I have tried multiple times. Can someone take a look at my attached log and give me some advice?

20240626_162025
20240626_1620251920×1895 557 KB

SDKM_logs_JetPack_6.0_(rev._2)_Linux_for_Jetson_Orin_Nano_modules_2024-06-26_16-12-23.zip (107.7 KB)

thanks
David

3 
16:12:39.254 - Info: [   0.2096 ] Sending bct_br
16:12:39.254 - Info: 
16:12:49.314 - Info: [   0.2515 ] ERROR:
16:12:49.314 - Info:  might be timeout in USB write.
16:12:49.314 - Info: 
16:12:49.351 - Info: Error: Return value 3

This has been asked countless times on the forum.
You can easily find the solution with Google.

4

Thanks for the fast reply, I have moved past that issue and now I am seeing an error of “can’t read rcm_state”. I’m attaching my full logs. Can you please advise?

thanks
David
SDKM_logs_JetPack_6.0_(rev._2)_Linux_for_Jetson_Orin_Nano_modules_2024-06-28_14-47-35.zip (283.5 KB)

5 
14:55:12.761 - Info: Timeout
14:55:12.761 - Info: Device failed to boot to the initrd flash kernel. Please retrive the serial log during flashing to debug further.
14:55:12.761 - Info: 
14:55:12.762 - Info: Cleaning up...
6

I connected the UART and I am seeing a problem with the NVMe drive (output below). It was working in another motherboard, but maybe it is bad now. Do you have any suggestions besides replacing the NVMe drive?

[ 2.926804] tegra194-pcie 1416000036100000…0x00361fffff → 0x0036100000
[ 2.930436] tegra194-pcie 14160000.pcie: iATU unroll: enabled
[ 2.930440] tegra:00: root bus resource [io 0x200000-0x2fffff] (bus address)
[ 3.039568] pci_bus 0004:00: root bus .041400] hub 2-1:1.0: USB hub found
[ 3.043446] pci 0004:01:00.0: [144d:a808] type 00 class 0x010802
[ 3.043641] pci 00 3.061796] tegra194-pcie 141e0000.pcie: MEM 0x322800
[ 3.061800] tegra194-pcie 141[ 5.174296] tegra194-pcie 141e0000.pcie: Phyp
[ 5.174367] tegra194-pcie 141e0000.pcie: PCI host bridge to bus 0007:00
[ 5[ 35.699857] nvme nvme0: Device not ready; aborting initialisation, CST0
[ 35.699861] nvme nvme0: Removing after probe failureb/typec/typec.ko
insmod /lib/modules/5.15.136-tegra/kernel/drivers/usb/typec/ucsi/typec_ucsi.ko
insmod /lib/modules/5.15.4643] In-situ OAM (IOAM) with IPv6
insmod /lib/modules/5.15.136-tegra/updates/drivers/nvpps/nvpps.ko
insmod /lib/modules/5.mmu group 9
[ 35.778621] tegra-qspi 3270000.spi: Prod config not found for QSPI: -19
[ 35.780214] spi-nor spi0.0: mx25u51Connection timeout: device /dev/nvme0n1 i.

7

Not really.
Get another disk and try again.

8

Hi, i purchased a new nvme ssd and i was able to get past this problem and install successfully. Thanks for the help and fast replies.

1 Like
10

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