Hello,
I have a Jetson Orin Nano 8GB Developer Kit.
The board was working perfectly before. It was booting Ubuntu from an NVMe SSD and I had successfully flashed this exact board multiple times using the same laptop.
Unfortunately, the board accidentally fell from approximately desk height while the power adapter was NOT connected. The NVMe SSD was installed at the time of the fall.
After that incident, the board has never booted normally again.
Current behavior
Every time I power the board:
-
The power LED turns on normally.
-
The fan spins for about 2-3 seconds.
-
The fan stops and repeats this cycle 2-3 times.
-
The board never boots Linux.
-
It is always detected by the host PC as 0955:7523 NVIDIA Corp. APX.
The Recovery jumper is NOT installed, yet the board always appears in APX mode.
The behavior is exactly the same whether the NVMe SSD is installed or completely removed.
Physical inspection
I carefully inspected the board after the fall.
I do not see any obvious physical damage such as:
-
PCB cracks
-
Broken components
-
Bent pins
-
Loose connectors
-
Visible damage around the USB-C connector
-
Visible damage around the M.2 connector
I have attached clear photos of the module and carrier board (top and bottom), including the USB-C port and M.2 slot.
photos are in this zip:
jetson images.zip (655.2 KB)
Troubleshooting already performed
I have already tried all of the following:
-
Multiple fresh Ubuntu Live USB sessions
-
Completely reinstalling SDK Manager
-
Rebuilding Linux_for_Tegra
-
Flashing with sdk Manager
-
Manual command-line flashing using sdk manager files
-
Flashing with the NVMe SSD installed
-
Removing all external USB devices
-
Removing every peripheral except power and USB-C
-
Different USB ports on the host PC
-
A different USB-C cable
-
Multiple recovery attempts
-
Multiple complete power cycles
Nothing changes.
Flashing behavior
SDK Manager correctly detects the board.
It successfully reads:
-
EEPROM
-
ECID
-
Board information
However, flashing always fails during blob transfer.
The SDK Manager log shows:
Sending bct_mem
Sending blob
ERROR: might be timeout in USB write.
Error: Return value 3
log file here:
NV_L4T_JETSON_LINUX_FLASH_COMP.log (429.2 KB)
Sometimes SDK Manager reaches approximately 99% and remains there indefinitely.
Other times it fails immediately after “Sending blob”.
During flashing, the device repeatedly disconnects and reconnects as APX.
Manual flashing
I also tried command-line flashing.
The process fails with:
Stat for blob_boot0.imgimg failed
Error: Return value 19
The generated command references:
kernel boot0.imgimg
instead of
kernel boot0.img
which looks incorrect.
Power supply
I am using the original NVIDIA-recommended power supply for the Jetson Orin Nano Developer Kit.
Also this is result of lsusb command when I got when recovery jumper was not installed
ubuntu@ubuntu:~$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 014: ID 0955:7523 NVIDIA Corp. APX
Bus 003 Device 003: ID 04f2:b7ba Chicony Electronics Co., Ltd Integrated Camera
Bus 003 Device 005: ID 8087:0aaa Intel Corp.
Bus 003 Device 002: ID 346d:5678 USB Disk 2.0
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
My question
Since this problem started immediately after the accidental drop, could this indicate hardware damage?
Could a damaged USB-C interface, carrier board, module connector, QSPI, RAM, PMIC, or another hardware component allow the board to remain permanently in APX mode while consistently failing during blob transfer? (It didn’t fall very hard.)
Any advice or additional diagnostic steps would be greatly appreciated.
Thank you.
jetson images.zip (655.2 KB)