I tried to flash Jetpack 6.2.2 and 7.2 on the Jetson Orin Nano device (NVMe). But, neither of them were successfully flashed. When I flash it using sdk manager to NVMe, “The connected Jetson device is not ready for flash” error is occuring .
SDKM_logs_JetPack_6.2.2_Linux_for_Jetson_Orin_Nano_8GB_developer_kit_version_2026-06-29_22-45-13.zip (1.2 MB)
Hi!
It seems that it is not an issue related with the NVMe memory, but with the USB connection itself. The script is failing before the flashing procedure even starts:
Checking target board connection … 1 connections found
Reading ECID … OK
Reading EEPROM …
Boot Rom communication
Sending bct_br
ERROR: might be timeout in USB write.
Error: Reading board information failed.
Error: Parsing boardid failed.
Bootrom status check failed.
Check the USB connection by running lsusb | grep -i 0955, you should see a similar output to:
Bus 001 Device XXX: ID 0955:7523 NVIDIA Corp. APX
Also, check the kernel log messages by running on a terminal sudo dmesg -w, and on a different terminal, go to the ~/nvidia/nvidia_sdk/JetPack_6.2.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra directory and run sudo ./nvsdkmanager_flash.sh --check-all. If in the kernel logs you see a message saying the USB is being disconnected/reset, this indicates there’s an issue on the host side/physical connection. Try avoiding using USB hubs when flashing, another USB port or resetting the USB service:
sudo systemctl stop udisks2
echo -1 | sudo tee /sys/module/usbcore/parameters/autosuspend
Also, you could try flashing via the CLI by running the following command from the ~/nvidia/nvidia_sdk/JetPack_6.2.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegradirectory:
sudo ./tools/kernel_flash/l4t_initrd_flash.sh \
–external-device nvme0n1p1 \
-c tools/kernel_flash/flash_l4t_external.xml \
-p “-c bootloader/generic/cfg/flash_t234_qspi.xml --no-systemimg” \
–network usb0 \
jetson-orin-nano-devkit \
external
I hope this helps and if you have any other questions, please let me know!
Fabian Munoz
Embedded SW Engineer at RidgeRun
Contact us: support@ridgerun.com
Developers wiki: https://developer.ridgerun.com/
Website: www.ridgerun.com
I think this not ready for flash error usually means the board isn’t in recovery mode. Power the Orin nano off fully, then jumper the FC REC and GND pins (9 and 10 on the button header) before powering on to force recovery. Run lsusb on your host and look for NVIDIA Corp APX, if it’s not there SDK Manager won’t detect it. what got was me the table, use a good data cable straight into the host (no hub) and flash from native Ubuntu 22.04 for JetPack 6.x, since a VM drops the USB mid-flash and throws this same error.
Hi, thanks for the support.
Bus 001 Device 040: ID 0955:7523 NVIDIA Corp. APX
--- dmesg ---
[73591.481742] usb 1-5: new high-speed USB device number 40 using xhci_hcd
[73591.631433] usb 1-5: New USB device found, idVendor=0955, idProduct=7523, bcdDevice= 4.01
[73591.631446] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[73591.631452] usb 1-5: Product: APX
[73591.631457] usb 1-5: Manufacturer: NVIDIA Corp.
~/nvidia/nvidia_sdk/JetPack_6.2.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra$ sudo ./nvsdkmanager_flash.sh --check-all
...
[ 0.1265 ] BR_CID: 0x80012344705E00852800000006FF01C0
[ 0.1533 ] Sending bct_br
[ 0.1536 ] ERROR: might be timeout in USB write.
Error: Return value 3
Command tegrarcm_v2 --new_session --chip 0x23 0 --uid --download bct_br br_bct_BR.bct --download mb1 mb1_t234_prod_aligned_sigheader.bin.encrypt --download psc_bl1 psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt
--- Error: Reading board information failed.
19:56:04.032 - Error: Parsing boardid failed.
[ 10.3983 ] File tmp.bct open failed
[ 10.3987 ] Error: try getting custinfo fail. Moving on
[ 10.3987 ] Rebooting to recovery mode
[ 10.3999 ] tegrarcm_v2 --chip 0x23 0 --ismb2
[ 10.4015 ] Rebooting to recovery mode
[ 10.4027 ] tegrarcm_v2 --chip 0x23 0 --reboot recovery
Parsing board information failed.
Error: failed to generate images
Cleaning up...
-- dmesg --
[74236.644733] nfsd: last server has exited, flushing export cache
[74236.853660] NFSD: Using nfsdcld client tracking operations.
[74236.853666] NFSD: no clients to reclaim, skipping NFSv4 grace period (net f0000000)
note.txt (32.5 KB) → Full Logs I copied from terminal.
For all steps, FC_REC - GND are connected all the time.
Hi!
Since the Jetson is being detected in recovery mode and the ECID can be read successfully, but the process fails immediately when sending the initial BCT (ERROR: might be timeout in USB write), I suspect there is a communication issue between the host and the device rather than an NVMe or JetPack related issue.
Could you please try:
If the same behavior appears with different cables, ports, and hosts, then the issue may be related to the carrier board, such as USB interface, the USB-C connector, or the module. I would also recommend to test, if possible, with another Jetson Orin Nano, just to confirm if the issue is related to the board itself.
Fabian Munoz
Embedded SW Engineer at RidgeRun
Contact us: support@ridgerun.com
Developers wiki: https://developer.ridgerun.com/
Website: www.ridgerun.com
Hi,
Some questions to confirm:
Thanks
I am using native Ubuntu 22.04 run on Lenovo M920q.
Hi,
Do you have the serial console log?
Please provide the serial console log during the sdk manager flashing.
Thanks
I am connecting to uart serial during the sdkmanager flash. But no logs is printed after recovery mode. I can only see the serial logs after leaving the recovery mode.
Hi,
It’s unusual that no logs appear in recovery mode.
A question to confirm:
Is your Orin Nano a developer kit or a custom board?
Thanks
It’s a Jetson Orin Nano development board 8GB
Hi,
Please follow below steps to set up serial console log:
Please upload the log although logs show after leaving the recovery mode.
Thanks