Flash Orin nano over USB Micro-B custom board error -> waiting for target to boot-up


we have developed a new custom board for a Jetson Orin nano 4GB, as memory we use a NVMe. I have flashed it as a test with the sdkmanager or :

$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -p “-c ./bootloader/generic/cfg/flash_t234_qspi.xml” -c ./tools/kernel_flash/flash_l4t_t234_nvme.xml --showlogs --network usb0 jetson-orin-nano-devkit nvme0n1p1

Unfortunately the flashing of the NVMe cannot be completed, the Transfer (flashing) stops at:

waiting for target to boot-up…

I suspect that the flashing tool is waiting for the /dev/ttyACM0 usb ncm interface, which is not created in the host.

Note: SDK Manager flash to NVMe with flash checkpoint error - #54 by WayneWWW and SDK Manager flash to NVMe with flash checkpoint error - #48 by lhoang

Description of the custom board recovery port:
The recovery port is a USB Micro-B (as described in the Nano Series Product Design Guide 7.1 USB Figure 7-1) and not a USB-C port as in the devkit. We use the original device tree from the devkit.

Can the ncm interface mode also be provided via the USB Micro-B socket, i.e. only USB0_D_N/P?


Are you referring to serial debug console with ncm interface?

then the answer is NO.
They are different pins, and you are supposed to use UART2_TXD/RXD for serial debug console.

Basically your question is same as this one.

You need to make the usb device tree to have correct otg setup so that the flash could proceed.


No, we use USB as described in the Design Guide 7.1 USB Figure 7-1:

This is what our USB design looks like:

Are you talking about the port for debug console or the port for flashing/OTG?

These were the first tests on the new custom board yesterday, I had already thought something like this. I will stick to the description for customizing the device tree →

» Jetson Module Adaptation and Bring-Up » Jetson Orin NX and Nano Series

Thanks for the answer I will adjust the device tree.

It is about the recovery port (USB OTG) (Figure 7-1) and not the UART2 debug port…

Just a reminder, if this is a new custom board, I would suggest you should use rel-35.4.1, and refer to rel-35 document.

Rel-36 is still a developer preview and we have heard some known issue in flash.

1 Like

Thanks for the hint, I will use rel-35.4.1. I will adjust the device tree in the next few days. If there is a difficult question about the device tree, I will contact you again :-)

1 Like

Hello WayneWWW,

I have just customized the device tree, now everything works as desired. It was a bit naive of me to flash the new Paltine via the SDK tool :-) Maybe I’ll have another question about the device tree at some point, then I’ll be happy to get back to you.

Best regards!

1 Like

Glad to know it works.

Many thanks again, see you soon…

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