ORIN NX 16G sdk manager Flashing failed。

ORIN NX 16G sdk manager Flashing failed。
Flashing JetPack 5.1.6。
sdk manager LOG:
14:41:47 INFO: [ 0.3144 ] Sending bct_mem

14:41:47 INFO: [ 0.3247 ] Sending blob

14:41:50 INFO: [ 2.9250 ] RCM-boot started

14:41:50 INFO: /mnt/ssd/rae/JetPack_5.1.6_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra

14:41:50 INFO: ***************************************

14:41:50 INFO: * *

14:41:50 INFO: * Step 3: Start the flashing process *

14:41:50 INFO: * *

14:41:50 INFO: ***************************************

14:41:50 INFO: Waiting for target to boot-up…

14:41:51 INFO: Waiting for target to boot-up…

14:41:52 INFO: Waiting for target to boot-up…

14:41:53 INFO: Waiting for target to boot-up…

14:41:54 INFO: Waiting for target to boot-up…

14:41:56 INFO: Waiting for target to boot-up…

14:41:57 INFO: Waiting for target to boot-up…

14:41:58 INFO: Waiting for target to boot-up…

14:41:59 INFO: Waiting for target to boot-up…

14:42:00 INFO: Waiting for target to boot-up…

14:42:01 INFO: Waiting for target to boot-up…

14:42:02 INFO: Waiting for target to boot-up…

14:42:04 INFO: Waiting for target to boot-up…

14:42:05 INFO: Waiting for target to boot-up…

14:42:06 INFO: Waiting for target to boot-up…

14:42:07 INFO: Waiting for target to boot-up…

14:42:08 INFO: Waiting for target to boot-up…

14:42:09 INFO: Waiting for target to boot-up…

14:42:10 INFO: Waiting for target to boot-up…

14:42:12 INFO: Waiting for target to boot-up…

14:42:13 INFO: Waiting for target to boot-up…

14:42:14 INFO: Waiting for target to boot-up…

14:42:15 INFO: Waiting for target to boot-up…

14:42:16 INFO: Waiting for target to boot-up…

14:42:17 INFO: Waiting for target to boot-up…

14:42:19 INFO: Waiting for target to boot-up…

14:42:20 INFO: Waiting for target to boot-up…

14:42:21 INFO: Waiting for target to boot-up…

14:42:22 INFO: Waiting for target to boot-up…

14:42:23 INFO: Waiting for target to boot-up…

14:42:24 INFO: Waiting for target to boot-up…

14:42:25 INFO: Waiting for target to boot-up…

14:42:27 INFO: Waiting for target to boot-up…

14:42:28 INFO: Waiting for target to boot-up…

14:42:29 INFO: Waiting for target to boot-up…

14:42:30 INFO: Waiting for target to boot-up…

14:42:31 INFO: Waiting for target to boot-up…

14:42:32 INFO: Waiting for target to boot-up…

14:42:33 INFO: Waiting for target to boot-up…

14:42:35 INFO: Waiting for target to boot-up…

14:42:36 INFO: Waiting for target to boot-up…

14:42:37 INFO: Waiting for target to boot-up…

14:42:38 INFO: Waiting for target to boot-up…

14:42:39 INFO: Waiting for target to boot-up…

14:42:40 INFO: Waiting for target to boot-up…

14:42:41 INFO: Waiting for target to boot-up…

14:42:43 INFO: Waiting for target to boot-up…

14:42:44 INFO: Waiting for target to boot-up…

14:42:45 INFO: Waiting for target to boot-up…

14:42:46 INFO: Waiting for target to boot-up…

14:42:47 INFO: Waiting for target to boot-up…

14:42:48 INFO: Waiting for target to boot-up…

14:42:50 INFO: Waiting for target to boot-up…

14:42:51 INFO: Waiting for target to boot-up…

14:42:52 INFO: Waiting for target to boot-up…

14:42:53 INFO: Waiting for target to boot-up…

14:42:54 INFO: Waiting for target to boot-up…

14:42:55 INFO: Waiting for target to boot-up…

14:42:56 INFO: Waiting for target to boot-up…

14:42:58 INFO: Waiting for target to boot-up…

14:42:59 INFO: Timeout

14:42:59 INFO: Cleaning up…

14:42:59 ERROR: [exec_command]: /bin/bash -c /home/zme/.nvsdkm/replays/scripts/JetPack_5.1.6_Linux/NV_L4T_FLASH_JETSON_LINUX_COMP.sh; [error]: 86439 blocks

14:42:59 INFO: [ Component Install Finished with Error ]

14:42:59 INFO: [host] [ 72.00 KB released. Disk Avail on Partition /dev/sda: 395.78 GB ]

14:42:59 INFO: [ NV_L4T_FLASH_JETSON_LINUX_COMP Install took 6m41s ]

14:42:59 ERROR: command error code: 11

14:42:59 DEBUG: command terminated with error

14:42:59 SUMMARY: Installation failed.

Hi,

Please provide the following information:

  1. Carrier board: Is this the NVIDIA Jetson Orin Nano reference carrier board (P3768-0000), or a custom/third-party carrier board?
  2. Target storage: Are you flashing NVMe, USB storage, or an SD card?
  3. Host environment: Which Ubuntu version are you using, and is it a native installation or a virtual machine?
  4. Serial console log: Please capture the complete UART boot log from the start of flashing through the Waiting for target to boot-up timeout.

For reference, Jetson Orin NX uses the initrd flash workflow described in the Jetson Linux 35.6.4 Flashing Support documentation.

Thanks.

  1. Target storage: NVMe
  2. **Host environment:ubuntu20.04,not a virtual machine
  3. See the attachment
    flashlog.log (96.4 KB)

So are you using custom board or NV devkit? Why didn’t answer that question?

The log looks like from a custom board.

is custom

Hi,

The UART log shows that the initrd boots and detects the NVMe, but no packets are exchanged through rndis0. It is also loading the P3768 reference-board DTB even though you are using a custom carrier board.

Please use the JetPack 5.1.6 BSP/flash package supplied for your custom carrier board. It must include the carrier-specific DT, MB1/MB2 settings, ODM data, flash configuration, and USB device-mode support. The stock P3768 configuration should not be used directly on a different carrier board.

Please refer to the Jetson Orin NX/Nano adaptation guide and the custom-carrier initrd flash requirement.

Thanks.

This device failed to flash due to SSH connection failure. But I’m not sure how to solve this problem?
Thanks.

I know it’s an SSH connection issue.
However, only if the correct carrier BSP is already installed should we proceed to host-side USB enumeration, IPv6 routing, and firewall checks.
So, obtain the JetPack 5.1.6/L4T 35.6.4 BSP and flashing instructions from the carrier-board vendor if you use a third-party carrier or Follow the Jetson Orin NX/Nano adaptation guide to create the board-specific configuration and enable USB device mode for initrd flashing if you use a self-designed carrier.

HI,
We are follow Nvidia’s development board. I burn according to the document, but it also times out
com COM3 (2026-07-31_090651) COM3 (USB Serial Port (COM3)).log (96.5 KB)
flash.log (234.4 KB)

Thanks.


USB mode

[ 7.331584] tegra-xudc 3550000.xudc: EP 0 (type: ctrl, dir: out) enabled

If this line comes out only once in UART log, it means device mode is not working.

Please share your hardware schematic for us to check. I don’t really see many people truly “follow NVIDIA devkit” before.

Also check if your host PC is really fine to flash the board when using NV devkit first.

1.The burning port has not changed
2.This PC can burn JetPack 5.1.2 normally
3.Are you saying that although this controller has enabled UDC mode, it is not working properly?
[ 7.331584] tegra-xudc 3550000.xudc: EP 0 (type: ctrl, dir: out) enabled

So you carrier board is using FUSB301 type C controller on it too? Are you sure your design is really using that?

HI ,
1.Yes, because we haven’t changed the number of devices tree to support it yet. We are currently using the original SDK.
2.I checked the logs of Ubuntu and indeed did not recognize the USB device. You’re right


3.Where should I check to make the PC recognize this USB
Thanks.

Hi,

請問用中文溝通會比較清楚嗎? 我感覺你並沒有很完整回答我們問的問題…

1.Yes, because we haven’t changed the number of devices tree to support it yet. We are currently using the original SDK.

我這裡問的是你們板子上的硬體設計. 跟device tree無關. 你這裡回答的有點答非所問. 你用sdkmanager燒的狀況下device tree本來就沒有改過. 這件事情不用特別提起. 我們早就知道了

这个FUSB301 type C 是对我们这个烧录有影响吗?

我不清楚 为什么要问这个问题

因為你的回答有點矛盾… 所以要問這問題.

NV devkit上的type C controller是fusb301這一個chip. 當你回答"我的底板設計跟NV devkit一樣"的時候. 我們預期你也在使用這一顆當作type C控制器…

但我實際上很少看過客製化底板真的有用這一顆晶片. 所以我才會特別又問你一次這個問題

如果你們並沒有用這一顆, 那就請不要說你們的設計跟NV devkit一樣… 因為很明顯就是不一樣…

不一樣的話那devkit的device tree在你們那裡就不能正常使用… 直接套用就會有問題

沒有使用fusb301的話請先參考文件把fusb301部份的remote endpoint給拿掉. 然後照你們的設計重寫device tree.

上面只有Orin AGX的範例, 但Orin NX也是類似的概念.

首先我们是使用了一个FUSB301这个芯片 [ 3.749182] fusb301 1-0025: device id: 0x12