Summary of issue (what’s wrong):
My Jetson Orin Nano 8GB Dev Kit is effectively “stuck” in Force-Recovery / APX (RCM) mode. On the host it always enumerates as 0955:7523 NVIDIA Corp. APX, and it will not boot (no HDMI output). Flashing with SDK Manager / JetPack 6.2.x fails with “Device failed to boot to the initrd flash kernel” and then times out.
What we tried (so far):
Confirmed the device is consistently detected in recovery: lsusb shows 0955:7523 APX every time.
Attempted serial debugging using a CP2102 USB-UART (/dev/ttyUSB0) at 115200 8N1, no flow control, wired to the carrier header pins labeled UART RXD / UART TXD / GND. Result: no serial output during power cycle / flashing.
Ran SDK Manager flash; it repeatedly gets stuck at “Waiting for target to boot-up…” and ends with timeout:
“Device failed to boot to the initrd flash kernel”
Also saw host-side error: “rpcbind: another rpcbind is already running. Aborting”
Verified cables/host sees both the CP2102 and the Jetson APX device; still can’t get the target to boot into the initrd flash stage.
What we need help with:
How to recover a Jetson Orin Nano that always enumerates as APX and cannot boot into the initrd flash kernel (possible QSPI/firmware issue, power/cable/host services like rpcbind/nfs, or correct procedure to flash QSPI + NVMe/SD).
If you could see the final problem here is with ““Waiting for target to boot-up…” and ends with timeout:”, then it is not about recovery mode. Your board is already in recovery mode and started some flash process.
It is something else that makes flash failure, please provide full UART + host side log.
Ok it looks like we have to get the Serial console output to see what’s wrong - I’ll get onto it and update thanks - I’m using the Robotico CP2102 USB 2.0 to TTL UART Module ✅
Hi there , ok still no results - with the serial connection - is there a possibility that there might be a problem with the Serial on the NVidea device - for the Robotico CP2102 USB 2.0 to TTL UART Module - I purchased for this is brand new - and the loopback test works fine?
Settings for Picocom - picocom v3.1
port is : /dev/ttyUSB0
flowcontrol : none
baudrate is : 115200
parity is : none
databits are : 8
stopbits are : 1
escape is : C-a
local echo is : no
noinit is : no
noreset is : no
hangup is : no
nolock is : no
send_cmd is : sz -vv
receive_cmd is : rz -vv -E
imap is :
omap is :
emap is : crcrlf,delbs,
logfile is : none
initstring : none
exit_after is : not set
exit is : no
Type [C-a] [C-h] to see available commands
Terminal ready
I have also tried swapping the RX and TX cables around - and also first started the terminal - before - applying power to the board - what concern me is that there is -0 - Serial response - But still the Nvidea device boots into - recovery mode and I can perform a command line Flash successfully. Should I purchase another USB-Serial device maybe?