# ZED Box Orin NX 16GB - JetPack 7.2 flash fails after RCM boot: "Device ping failed after RCM boot"

**URL:** <https://community.stereolabs.com/t/zed-box-orin-nx-16gb-jetpack-7-2-flash-fails-after-rcm-boot-device-ping-failed-after-rcm-boot/11678>\
**Category:** ZED Box\
**Created:** [August 27, 2026, 2:20pm UTC](https://community.stereolabs.com/t/zed-box-orin-nx-16gb-jetpack-7-2-flash-fails-after-rcm-boot-device-ping-failed-after-rcm-boot/11678 "2026-08-27T14:20:43Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![ccastellanos-code](https://community.stereolabs.com/user_avatar/community.stereolabs.com/ccastellanos-code/32/6465_2.png) [@ccastellanos-code](https://community.stereolabs.com/u/ccastellanos-code)\
**Post date:** [August 27, 2026, 2:20pm UTC](https://community.stereolabs.com/t/zed-box-orin-nx-16gb-jetpack-7-2-flash-fails-after-rcm-boot-device-ping-failed-after-rcm-boot/11678/1 "2026-08-27T14:20:43Z")

</div>

Hi,

We are trying to upgrade/reflash a ZED Box Orin NX 16GB to JetPack 7.2 using the current official [Stereolabs](https://www.stereolabs.com/) flashing procedure.

We have already followed the [Stereolabs](https://www.stereolabs.com/) documentation and troubleshooting recommendations and investigated several similar topics in this forum. The failure is highly reproducible and always occurs at the same point, immediately after the RCM boot payload has been successfully transferred.

I am including the complete context and the tests already performed below.

* * *

## HARDWARE / CURRENT SYSTEM / OBJECTIVE

Device:

- [Stereolabs](https://www.stereolabs.com/) ZED Box
- NVIDIA Jetson Orin NX 16GB / Tegra234
- NVMe: ~256 GB
- GMSL2 / ZEDBox Duo capture card
- MAX96712 deserializer
- ZED X Mini camera
- Recovery VID:PID: 0955:7323
- Board information reported during flashing:
  - Board ID: 3767
  - Version/FAB: 303
  - SKU: 0000
  - Revision: F.1

Before starting the upgrade, the ZED Box was working and able to boot its existing operating system.

The currently installed software is:

- JetPack 6.2
- L4T 36.4.4
- Ubuntu 22.04
- ZED X Driver 1.4.1
- ZED SDK 5.2.3
- Linux kernel observed from the running system: 5.15.148-tegra aarch64

Target system:

- JetPack 7.2
- Jetson Linux / L4T R39.2.1 used by the current [Stereolabs](https://www.stereolabs.com/) package
- Ubuntu 24.04 target root filesystem
- Kernel contained in the prepared BSP: 6.8.12-1021-tegra

Flashing script:

- zedbox\_all\_usb\_flash\_7.2.sh

Our objective is to perform a clean installation/update of this ZED Box from its currently working JetPack 6.2 / L4T 36.4.4 / Ubuntu 22.04 installation to the current [Stereolabs](https://www.stereolabs.com/) JetPack 7.2 / Ubuntu 24.04 image using the official ZED Box flashing procedure.

* * *

## FLASHING HOST

The flashing host is:

- Ubuntu 22.04.5 LTS
- Running from a Live USB environment
- x86\_64 PC
- Not a VM
- Not WSL/WSL2

The BSP itself is NOT stored on the Live USB filesystem.

The working directory is located on the internal NVMe/ext4 partition of the host:

/mnt/msi/zedbox\_flash

BSP directory:

/mnt/msi/zedbox\_flash/zedbox\_jp72/Linux\_for\_Tegra

The filesystem containing the BSP has approximately:

576 GB total  
~180 GB free during testing

Therefore, there is substantially more than the 80 GB required by the [Stereolabs](https://www.stereolabs.com/) documentation.

* * *

## PROCEDURE

We followed the current [Stereolabs](https://www.stereolabs.com/) ZED Box Orin flashing procedure for JetPack 7.2.

The ZED Box was placed in Force Recovery Mode and verified from the host with:

lsusb | grep 0955

Result:

0955:7323 NVIDIA Corp. APX

The flashing environment was then launched using the [Stereolabs](https://www.stereolabs.com/) script with BSP\_ROOT pointing to the prepared BSP.

The BSP preparation succeeds and the failure happens during the actual flash.

* * *

## FORCE RECOVERY MODE WORKS

Force Recovery itself appears to work correctly.

The host consistently detects:

0955:7323 NVIDIA Corp. APX

This matches the expected recovery VID:PID for a ZED Box Orin NX 16GB.

RCM communication with the Tegra also works.

During the flash, the tool successfully reads board information:

Board ID(3767) version(303) sku(0000) revision(F.1)

and communicates with the boot ROM / MB2 applet.

Therefore, the problem is not simply that the unit fails to enter Force Recovery Mode.

* * *

## EXACT POINT OF FAILURE

The RCM stage completes successfully.

Relevant output:

Entering RCM boot

BR\_CID: 0x80012344705E031B1C0000000C020040

Sending bct\_br  
Sending mb1  
Sending psc\_bl1  
Sending bct\_mb1

…

The number of images in blob is 19  
blobsize is approximately 105 MB

…

BL: version 1.0.1.17-t234-54845784-9b0d5809  
last\_boot\_error: 0

Sending bct\_mem  
Sending blob

RCM-boot started

After this point the script enters:

* * *

- Step 3: Start the flashing process

Mounting NFS folder from this host  
Waiting for target to boot-up…  
Waiting for target to boot-up…  
Waiting for target to boot-up…  
…

It never succeeds.

Eventually:

Error: Timeout  
Error: Device ping failed after RCM boot.  
Error: This can be due to XUSB not being enabled or device failed to boot.  
Error: Please retrieve the serial log to debug further.  
Cleaning up…  
FLASH FAILED.

The failure is reproducible.

* * *

## USB BEHAVIOR DURING RCM → INITRD TRANSITION

We monitored lsusb and dmesg continuously during the flash.

Before RCM boot:

0955:7323 NVIDIA Corp. APX

After “RCM-boot started”, the device disconnects/reconnects, but it never reaches the expected initrd flashing state.

Instead, it remains/reappears as:

0955:7323 NVIDIA Corp. APX

Example host kernel messages:

usb 1-3: USB disconnect

usb 1-3: new high-speed USB device using xhci\_hcd  
usb 1-3: New USB device found, idVendor=0955, idProduct=7323  
usb 1-3: Product: APX  
usb 1-3: Manufacturer: NVIDIA Corp.

This behavior repeats.

We also monitored:

/dev/ttyACM\*

throughout the transition.

No ttyACM device appeared during the failed RCM → initrd boot.

The important point is therefore:

Recovery/APX communication works  
→ RCM payload is transferred  
→ “RCM-boot started”  
→ target does not become reachable by l4t\_initrd\_flash  
→ target remains/reappears as APX  
→ timeout

* * *

## USB CABLE / HOST USB PORT TESTS

We have already tested the physical USB connection.

Tests performed:

- Changed USB cable
- Tested the original cable supplied/used with the ZED Box
- Changed USB port on the host computer
- Reconnected the device multiple times
- Re-entered Force Recovery Mode
- Power-cycled the ZED Box
- Repeated the flash procedure

With the original cable, the ZED Box can reliably enumerate as APX and the complete RCM boot blob is transferred successfully.

The failure after “RCM-boot started” remains unchanged.

We also reviewed the forum topic:

“Cannot update Zedbox to Jetpack 6.2 - Device failed to boot to the initrd flash kernel”

We saw that in that case a very short (~10 cm) USB cable eventually solved the problem.

We have tested different cables, including the original one, but we have NOT specifically tested a 10 cm USB cable because we do not currently have one available.

If such a short cable is considered mandatory/recommended for JetPack 7.2 flashing, please let us know.

* * *

## USB AUTOSUSPEND

Following the [Stereolabs](https://www.stereolabs.com/) troubleshooting guide, USB autosuspend was disabled on the Ubuntu host:

sudo bash -c ‘echo -1 \> /sys/module/usbcore/parameters/autosuspend’

Verified with:

cat /sys/module/usbcore/parameters/autosuspend

Output:

-1

The flashing behavior remained exactly the same.

* * *

## NFS / HOST FLASH REQUIREMENTS

The NFS service required by l4t\_initrd\_flash was checked.

nfs-kernel-server is active.

UFW is inactive.

The NVIDIA flashing tool also reports:

UFW is not active. NFS port is accessible.  
No VPN connection detected.

Therefore, the failure does not appear to be caused by the host firewall/NFS service.

* * *

## BSP / ROOTFS PREPARATION

The BSP has been successfully unpacked and populated.

The package uses:

Jetson\_Linux\_R39.2.1\_aarch64.tbz2  
Tegra\_Linux\_Sample-Root-Filesystem\_R39.2.1\_aarch64.tbz2

The [Stereolabs](https://www.stereolabs.com/) files are also present:

zedbox\_device\_trees\_392.tar  
zedbox\_rootfs\_392.tar

The root filesystem contains:

rootfs/etc/passwd  
rootfs/etc/shadow  
rootfs/etc/hostname

NVIDIA files are present, including:

rootfs/usr/lib/aarch64-linux-gnu/tegra → nvidia

and:

rootfs/lib/modules/6.8.12-1021-tegra

The [Stereolabs](https://www.stereolabs.com/) patched iwlwifi modules are also present.

We compared the actual files in the BSP with the contents of the [Stereolabs](https://www.stereolabs.com/) patch archives using SHA256.

For example, the hashes match for:

- tegra234-p3768-0000+p3767-0000-nv.dtb
- tegra234-mb2-bct-misc-p3767-0000.dts
- tegra234-mb1-bct-pinmux-p3767-hdmi-a03.dtsi
- p3509-a02-p3767-0000.conf
- iwlwifi.ko
- iwlmvm.ko

Therefore, the [Stereolabs](https://www.stereolabs.com/) device-tree/rootfs patches appear to actually be applied to the BSP.

* * *

## DEVICE TREE / XUSB CHECK

Because the flash error specifically mentions XUSB, we decompiled and inspected:

tegra234-p3768-0000+p3767-0000-nv.dtb

The XUSB pad controller is enabled:

padctl@3520000 {  
compatible = “nvidia,tegra234-xusb-padctl”;  
status = “okay”;  
}

USB2 lanes include:

usb2-0:  
nvidia,function = “xusb”;  
status = “okay”;

usb2-1:  
nvidia,function = “xusb”;  
status = “okay”;

usb2-2:  
nvidia,function = “xusb”;  
status = “okay”;

The corresponding ports include:

usb2-0:  
status = “okay”;  
mode = “otg”;

usb2-1:  
status = “okay”;  
mode = “host”;

usb2-2:  
status = “okay”;  
mode = “host”;

USB3 lanes/ports are also enabled for usb3-0, usb3-1 and usb3-2.

The USB device controller is enabled:

usb@3550000 {  
compatible = “nvidia,tegra234-xudc”;  
status = “okay”;  
phy-names = “usb2-0”;  
}

The XUSB host controller is also enabled:

usb@3610000 {  
compatible = “nvidia,tegra234-xusb”;  
status = “okay”;  
phy-names = “usb2-1\0usb2-2\0usb3-0\0usb3-1\0usb3-2”;  
}

Therefore, XUSB/XUDC are at least marked as enabled in the [Stereolabs](https://www.stereolabs.com/) DTB being used.

We are NOT claiming that XUSB initializes successfully on the hardware; only that the DTB configuration itself does not simply have the controller disabled.

* * *

## MB2 BCT / EEPROM CHECK

We also investigated the MB2 BCT because similar Jetson initrd boot failures can be related to carrier-board EEPROM configuration.

The ZED Box configuration chain is:

p3509-a02-p3767-0000.conf  
→  
p3768-0000-p3767-0000-a0.conf  
→  
p3767.conf.common

p3767.conf.common selects:

MB2\_BCT=“tegra234-mb2-bct-misc-p3767-0000.dts”;

The corresponding EEPROM configuration contains:

cvm\_eeprom\_i2c\_instance = \<0\>;  
cvm\_eeprom\_i2c\_slave\_address = \<0xa0\>;  
cvm\_eeprom\_read\_size = \<0x100\>;

cvb\_eeprom\_i2c\_instance = \<0x0\>;  
cvb\_eeprom\_i2c\_slave\_address = \<0xae\>;  
cvb\_eeprom\_read\_size = \<0x0\>;

We extracted the same file from:

zedbox\_device\_trees\_392.tar

and compared it with the BSP version.

They are identical.

Therefore, cvb\_eeprom\_read\_size is already disabled (\<0x0\>) exactly as supplied by [Stereolabs](https://www.stereolabs.com/).

We did not modify it.

* * *

## GENERATED INITRD BOOT IMAGE

The flash process successfully generates:

bootloader/boot0.img

Size:

approximately 77 MB

file identifies it as:

Android bootimg

with kernel/ramdisk and command line including:

root=/dev/initrd  
rw  
rootwait  
mminit\_loglevel=4  
console=ttyTCU0,115200  
firmware\_class.path=/etc/firmware

Therefore, the initrd boot image is being generated before the RCM transfer.

* * *

## INITRD SCRIPT / ttyTCU0 CHECK

We inspected:

tools/kernel\_flash/initrd\_flash/init

The script defines:

TTY\_CONSOLE=“ttyTCU0”

The generated boot0.img command line contains:

console=ttyTCU0,115200

We also inspected the initrd logic.

There is a helper function that can reboot if ttyTCU0 is missing, but we verified that this helper function is only defined in the inspected script and no call to it was found there.

The explicit early reboot paths we found in the init script are failures to mount:

- /proc
- /dev
- /sys
- debugfs

We currently have no evidence that any particular one of these conditions is occurring, because the target never becomes reachable after RCM boot.

* * *

## SERIAL / USB CONSOLE OBSERVATION

When the ZED Box was booting its existing Linux installation normally, the same USB connection could enumerate as:

0955:7020 NVIDIA Corp. L4T (Linux for Tegra) running on Tegra

and the host obtained:

/dev/ttyACM0

We were able to open:

sudo screen /dev/ttyACM0 115200

and log into the running ZED Box.

We observed:

Ubuntu 22.04.5 LTS  
GNU/Linux 5.15.148-tegra aarch64

The USB gadget interfaces were also created on the host, including RNDIS/NCM, and the standard 192.168.55.x USB network was functional.

For example, the host had:

192.168.55.100/24

and:

ping 192.168.55.1

worked.

This is useful because it demonstrates that the ZED Box has previously been able to expose its Linux USB gadget interface successfully when booting the installed OS.

However, during the JetPack 7.2 RCM-loaded initrd boot, none of those interfaces appear.

* * *

## ZED BOX BIOS / UEFI USB OBSERVATION

We also checked the ZED Box UEFI/BIOS during troubleshooting.

USB devices connected to the ZED Box USB ports were not detected/listed there.

We do not know whether this is expected behavior on this carrier board or whether it is relevant to the XUSB/initrd problem.

Because the initrd flashing failure itself reports a possible XUSB issue, we would appreciate confirmation about whether USB devices should normally be visible/functional from the ZED Box UEFI environment.

* * *

## SIMILAR [STEREOLABS](https://www.stereolabs.com/) FORUM TOPICS REVIEWED

Before opening this topic we reviewed several related ZED Box threads, including:

- “Cannot update Zedbox to Jetpack 6.2 - Device failed to boot to the initrd flash kernel”
- “Zedbox Orin Flashing Issues”
- “Flashing Zed Box Orin NX 16GB Problem: Directory renamed before its status could be extracted”
- “Unable to boot ZED Box Orin NX after restart”

We have therefore already checked several recommendations that appear repeatedly in these discussions and in the [Stereolabs](https://www.stereolabs.com/) troubleshooting guide:

- Force Recovery Mode confirmed

- Correct APX VID:PID confirmed

- Different USB cable tested

- Original USB cable tested

- Different host USB port tested

- Device power-cycled

- Recovery mode re-entered multiple times

- USB autosuspend disabled

- BSP placed on a disk with sufficient space

- Rootfs successfully populated

- NVIDIA binaries applied

- NFS service running

- UFW inactive

- XUSB/XUDC DT configuration inspected

- [Stereolabs](https://www.stereolabs.com/) device-tree files compared against BSP

- MB2 BCT/EEPROM configuration checked

- boot0.img generation verified

- USB enumeration monitored throughout RCM → initrd

- A specifically ~10 cm USB cablse

- A completely different Ubuntu host PC

we haven’t yet tested A forced USB 2.0 connection through a USB 2.0 hub because it is not currently available to us.

* * *

## QUESTIONS

Could you please help us determine where the ZED Box boot chain is failing after “RCM-boot started”?

In particular:

1. Is zedbox\_all\_usb\_flash\_7.2.sh officially supported on this ZED Box Orin NX 16GB hardware/revision (Board ID 3767, version/FAB 303, SKU 0000, revision F.1)?

2. Is JetPack 7.2 / L4T R39.2 currently expected to flash successfully on this generation of ZED Box Orin NX?

3. We are using Ubuntu 22.04 Live USB as the flashing host, with the BSP stored on an internal ext4/NVMe filesystem. Is this a supported host configuration for JetPack 7.2?

4. After “RCM-boot started”, what USB VID:PID and/or network interface should normally appear when the JetPack 7.2 initrd flash kernel has booted successfully?

5. Does the target returning/remainining as 0955:7323 APX indicate that MB2/UEFI/kernel/initrd is failing and the unit is rebooting back into recovery?

6. Are there any known JetPack 7.2 issues specific to the ZED Box carrier involving XUSB, XUDC, UPHY, pinmux or MB2 BCT configuration?

7. Is the p3509-a02-p3767-0000 configuration and the tegra234-p3768-0000+p3767-0000-nv.dtb distributed in the current zedbox\_device\_trees\_392.tar expected to support this exact ZED Box revision?

8. Is it expected that USB devices connected to the ZED Box are not detected in its UEFI/BIOS, or could this indicate a carrier/XUSB configuration issue?

9. Is a very short USB cable (for example the ~10 cm cable mentioned in the previous JetPack 6.2 forum topic) required or strongly recommended even when the original cable can reliably transfer the complete RCM blob?

10. Is a particular ZED Box power mode required during JetPack 7.2 flashing?

11. What is the recommended way to obtain the early serial boot log requested by l4t\_initrd\_flash on this ZED Box model?

During normal Linux boot we can access ttyACM0 over the OTG USB port, but ttyACM0 never appears during the failed RCM-loaded JetPack 7.2 initrd boot.

If access to a physical UART/debug connector is required, could you provide the correct connector/pinout and serial settings for this ZED Box revision?

1. Are there any additional logs or files you would like us to provide to determine whether the failure occurs in MB2, UEFI, kernel startup, XUSB initialization or the initrd?

We can provide:

- complete flash log
- host dmesg trace during RCM → initrd
- lsusb monitoring output
- generated DTB/DTS
- MB2 BCT configuration
- boot0.img information
- any other requested diagnostic files

Our main goal is to successfully update this ZED Box Orin NX 16GB from JetPack 6.2 / Ubuntu 22.04 to JetPack 7.2 / Ubuntu 24.04 using the official ZED Box flashing procedure.

Thanks.

---

<div class="post-metadata">

**Author:** ![Myzhar](https://community.stereolabs.com/user_avatar/community.stereolabs.com/myzhar/32/11_2.png) [@Myzhar](https://community.stereolabs.com/u/Myzhar)\
**Post date:** [August 28, 2026, 1:25pm UTC](https://community.stereolabs.com/t/zed-box-orin-nx-16gb-jetpack-7-2-flash-fails-after-rcm-boot-device-ping-failed-after-rcm-boot/11678/2 "2026-08-28T13:25:57Z")

</div>

Hi @ccastellanos-code,

thank you for one of the most complete and well documented reports we have received on this forum; it saved us a lot of back and forth. Your analysis is correct, so let me first confirm where the boot chain is breaking, then answer your questions in order.

**Where the failure is**

> Could you please help us determine where the ZED Box boot chain is failing after “RCM-boot started”?

Your host side is clean: NFS, UFW, autosuspend and free space are all fine, and the BSP is correctly patched. The failure is entirely on the target, in the window between the RCM-loaded MB2/UEFI handoff and the moment the initrd flash kernel brings up USB device mode. Nothing that the initrd kernel needs to do has happened yet, which is why you see no `ttyACM`, no RNDIS/NCM interface and no `192.168.55.x` network.

> Does the target returning/remaining as 0955:7323 APX indicate that MB2/UEFI/kernel/initrd is failing and the unit is rebooting back into recovery?

Yes. Once the RCM-loaded chain runs, the Tegra should stop presenting the APX ID. Re-enumerating as `0955:7323` means the SoC was reset and the boot ROM put the device back into recovery, so the flash kernel either never started or panicked before the USB gadget was initialized.

> After “RCM-boot started”, what USB VID:PID and/or network interface should normally appear when the JetPack 7.2 initrd flash kernel has booted successfully?

On success the device disappears as APX and comes back as a Linux composite USB gadget, not as APX. The reliable indicator is the network side: the host gets an RNDIS/NCM interface configured as `192.168.55.100/24`, and `ping 192.168.55.1` answers. That ping is exactly what `l4t_initrd_flash` is waiting for. The exact non-APX product ID varies between L4T releases, so please use the `192.168.55.1` reachability as the reference, not a specific PID.

**Support and compatibility**

> Is zedbox\_all\_usb\_flash\_7.2.sh officially supported on this ZED Box Orin NX 16GB hardware/revision (Board ID 3767, version/FAB 303, SKU 0000, revision F.1)?  
> Is JetPack 7.2 / L4T R39.2 currently expected to flash successfully on this generation of ZED Box Orin NX?  
> Is the p3509-a02-p3767-0000 configuration and the tegra234-p3768-0000+p3767-0000-nv.dtb distributed in the current zedbox\_device\_trees\_392.tar expected to support this exact ZED Box revision?

Yes to all three. `zedbox_all_usb_flash_7.2.sh` is the official [JetPack 7.2 / L4T 39.2 script listed in the flashing guide](https://docs.stereolabs.com/docs/products/embedded/zed-box-orin/reset-update#flashing-the-zed-box-orin-model), Board ID 3767 with SKU 0000 is the Orin NX 16GB module used in the [ZED Box Orin](https://www.stereolabs.com/store/products/zed-box-orin), and the configuration chain and DTB you inspected are the intended ones for it. Could you please post the serial number of your unit (the `GTW-ONX...` string)? The first generation boards behave differently in recovery mode, and knowing the exact generation lets me confirm the hardware revision against the R39.2 package.

> Are there any known JetPack 7.2 issues specific to the ZED Box carrier involving XUSB, XUDC, UPHY, pinmux or MB2 BCT configuration?

Nothing is currently documented on our side. I am forwarding your report to the engineering team, since your DTB and MB2 BCT verification rules out the usual suspects, and I will update this topic as soon as I have their feedback.

**Host configuration**

> We are using Ubuntu 22.04 Live USB as the flashing host, with the BSP stored on an internal ext4/NVMe filesystem. Is this a supported host configuration for JetPack 7.2?

Ubuntu 22.04 is the supported host for JetPack \>= 6.0, and a Live USB session is allowed by the guide; keeping the BSP on the internal ext4 partition is the right choice. That said, for the JetPack 7.2 initrd flow I recommend retrying from a native Ubuntu 22.04 installation. The Live session overlay filesystem plus the NFS export used by `l4t_initrd_flash` is the one part of your setup we exercise least, so it is worth removing from the equation.

**Physical setup**

> Is a very short USB cable (for example the ~10 cm cable mentioned in the previous JetPack 6.2 forum topic) required or strongly recommended even when the original cable can reliably transfer the complete RCM blob?

It is not mandatory, but it is strongly recommended, and it is a documented step in our [troubleshooting guide](https://docs.stereolabs.com/docs/products/embedded/zed-box-orin/troubleshooting#bad-communication). The RCM transfer and the initrd stage are not equivalent: RCM runs from the boot ROM at a conservative rate, while the initrd gadget renegotiates the link from scratch under a different controller configuration. A marginal cable can pass the first and fail the second. Please also use a USB port soldered directly to the motherboard, and no hub.

> Is a particular ZED Box power mode required during JetPack 7.2 flashing?

No. `nvpmodel` power modes are a runtime setting and have no effect in recovery mode. Please power the device with the supplied 12V/5A barrel jack supply only, with the PoE+ cable disconnected, since the carrier board does not reboot correctly when one power source is plugged in while the other is already connected.

**One test I would like you to run first**

Before anything else, please strip the unit down and retry:

1. Disconnect the ZED X Mini and all GMSL2 cables from the ZED Box Duo capture card.
2. Disconnect HDMI, Ethernet, and every USB device from the ZED Box.
3. Leave only the 12V barrel jack and the micro USB OTG cable to the host.
4. Re-enter Force Recovery mode and run the script again.

The R39.2 device tree brings up the MAX96712 deserializer nodes during boot, and a GMSL2 link that is powered and enumerating is a plausible place for the new kernel generation to stall before USB device mode is configured. This is the cheapest way to confirm or exclude it.

As a second, very informative test, please re-run [`zedbox_all_usb_flash_6.2.sh`](https://download.stereolabs.com/scripts/zedbox_all_usb_flash_6.2.sh) on the same host, with the same cable and port. If JetPack 6.2 flashes to completion, we know the host, cable and target USB path are healthy and the problem is confined to the R39.2 package, which is precisely what engineering needs. It also leaves you with a working device in the meantime.

**Serial log and UEFI observations**

> What is the recommended way to obtain the early serial boot log requested by l4t\_initrd\_flash on this ZED Box model?

Unfortunately you cannot capture it on this model. As described in the [Serial Console guide](https://docs.stereolabs.com/docs/products/embedded/zed-box-orin/serial-console), the console is exposed on the same micro USB OTG port that carries the RCM connection, and it is available only in Normal Mode, never in Recovery Mode. The UART is on an internal connector, and opening the enclosure voids the warranty, so we do not ask customers to do that. Please rely on the host side logs instead.

> Is it expected that USB devices connected to the ZED Box are not detected in its UEFI/BIOS, or could this indicate a carrier/XUSB configuration issue?

That is expected and not related to your problem. The UEFI menu enumerates bootable devices, not arbitrary peripherals, so a non bootable USB device will not be listed. The XUSB host controller is proven functional in UEFI by the fact that the ZED Box can boot from a recovery USB key, as in the [live USB flashdrive procedure](https://docs.stereolabs.com/docs/products/embedded/zed-box-orin/reset-update#entering-recovery-mode-with-a-live-usb-flashdrive).

**What to send us**

> Are there any additional logs or files you would like us to provide?

Please attach:

1. The complete terminal transcript of a failing JetPack 7.2 run, from the stripped down configuration described above.
2. All log files generated under `Linux_for_Tegra/tools/kernel_flash/`, including the `initrdflash` logs and the `mfi_*` directory contents if present.
3. The host `dmesg` trace covering the RCM to initrd transition.
4. The serial number of the unit.
5. The result of the JetPack 6.2 flash attempt.

I will come back to you here with engineering feedback once I have it. Thanks again for the quality of the report.

---

<div class="post-metadata">

**Author:** ![ccastellanos-code](https://community.stereolabs.com/user_avatar/community.stereolabs.com/ccastellanos-code/32/6465_2.png) [@ccastellanos-code](https://community.stereolabs.com/u/ccastellanos-code)\
**Post date:** [September 11, 2026, 9:51am UTC](https://community.stereolabs.com/t/zed-box-orin-nx-16gb-jetpack-7-2-flash-fails-after-rcm-boot-device-ping-failed-after-rcm-boot/11678/3 "2026-09-11T09:51:34Z")

</div>

> [@Myzhar](#):
>
> Please attach:
> 
> 1. The complete terminal transcript of a failing JetPack 7.2 run, from the stripped down configuration described above.
> 2. All log files generated under `Linux_for_Tegra/tools/kernel_flash/`, including the `initrdflash` logs and the `mfi_*` directory contents if present.
> 3. The host `dmesg` trace covering the RCM to initrd transition.
> 4. The serial number of the unit.
> 5. The result of the JetPack 6.2 flash attempt.

Hi Walter,

I completed the requested checks on unit GTW-ONX1-C1XKJV6S.

1. JetPack 7.2 stripped-down run  
With only 12 V power and micro-USB OTG connected, the result is unchanged. RCM transfer completes and reaches RCM-boot started, but the target never enumerates as Linux for Tegra. It repeatedly returns to 0955:7323 APX, no USB network interface comes up, and the flash ends with Device ping failed after RCM boot.

2. Kernel flash logs  
The generated files under Linux\_for\_Tegra/tools/kernel\_flash/ were collected from the run.

3. Host dmesg  
The host dmesg covering the RCM → initrd transition was captured and is attached.

4. Serial number  
GTW-ONX1-C1XKJV6S

5. JetPack 6.2 result  
Using the exact same host, cable, USB port, power supply and stripped-down setup, the target successfully leaves APX and enumerates as 0955:7035 NVIDIA Corp. Linux for Tegra. The RNDIS interface appears and flashing starts, writing partitions to /dev/nvme0n1. It later stops with an NFS/flash-command error.

The key difference is therefore:

JP7.2: initrd/Linux USB gadget does not start and the unit returns to APX.  
JP6.2: initrd boots correctly, Linux for Tegra enumerates, and flashing begins.

I am attaching the collected logs and dmesg traces.

Could you please check with engineering whether this points to a JP7.2 / R39.2-specific issue during the early boot/initrd stage?

---

<div class="post-metadata">

**Author:** ![Myzhar](https://community.stereolabs.com/user_avatar/community.stereolabs.com/myzhar/32/11_2.png) [@Myzhar](https://community.stereolabs.com/u/Myzhar)\
**Post date:** [September 11, 2026, 2:55pm UTC](https://community.stereolabs.com/t/zed-box-orin-nx-16gb-jetpack-7-2-flash-fails-after-rcm-boot-device-ping-failed-after-rcm-boot/11678/4 "2026-09-11T14:55:53Z")

</div>

Hi @ccastellanos-code  
I cannot see the logs. Please use a file sharing service and post the link

---

<div class="post-metadata">

**Author:** ![ccastellanos-code](https://community.stereolabs.com/user_avatar/community.stereolabs.com/ccastellanos-code/32/6465_2.png) [@ccastellanos-code](https://community.stereolabs.com/u/ccastellanos-code)\
**Post date:** [September 14, 2026, 6:33am UTC](https://community.stereolabs.com/t/zed-box-orin-nx-16gb-jetpack-7-2-flash-fails-after-rcm-boot-device-ping-failed-after-rcm-boot/11678/5 "2026-09-14T06:33:50Z")

</div>

Hi Walter,

Since I was running Ubuntu 22.04 from a Live USB session, I no longer have the generated log files after closing the session. I would need to repeat the tests to capture them again.

What I wanted to show you from the runs was the following behavior:

JetPack 7.2:

- RCM transfer completes successfully.
- The process reaches RCM-boot started.
- The target never enumerates as Linux for Tegra.
- It repeatedly comes back as 0955:7323 NVIDIA Corp. APX.
- No 192.168.55.x USB network interface appears.
- The flash ends with:  
Error: Device ping failed after RCM boot.

JetPack 6.2, using the same host, cable, USB port, power supply and stripped-down setup:

- The target successfully leaves APX.
- It enumerates as 0955:7035 NVIDIA Corp. Linux for Tegra.
- The RNDIS interface appears.
- The initrd flashing environment starts and begins writing partitions to /dev/nvme0n1.
- It later stops with a separate NFS/flash-command error.

So the key difference is that JP6.2 successfully boots the initrd/Linux USB gadget, while JP7.2 does not and returns to APX before that stage.

If you need the raw logs, I can repeat both tests and capture them again.

---

<div class="post-metadata">

**Author:** ![Myzhar](https://community.stereolabs.com/user_avatar/community.stereolabs.com/myzhar/32/11_2.png) [@Myzhar](https://community.stereolabs.com/u/Myzhar)\
**Post date:** [September 14, 2026, 6:28pm UTC](https://community.stereolabs.com/t/zed-box-orin-nx-16gb-jetpack-7-2-flash-fails-after-rcm-boot-device-ping-failed-after-rcm-boot/11678/6 "2026-09-14T18:28:20Z")

</div>

Hi @ccastellanos-code,

> [@ccastellanos-code](#):
>
> Since I was running Ubuntu 22.04 from a Live USB session, I no longer have the generated log files after closing the session. I would need to repeat the tests to capture them again.

No problem, and thanks for the detailed summary in the meantime. Since you have to repeat the runs anyway, please do them from a **native Ubuntu 22.04 installation** rather than from the Live USB session. This solves two problems at once: the logs survive the reboot, and it removes the overlay filesystem plus the `nfs-kernel-server` export from the picture, which is the one part of your setup we exercise least.

> [@ccastellanos-code](#):
>
> So the key difference is that JP6.2 successfully boots the initrd/Linux USB gadget, while JP7.2 does not and returns to APX before that stage.

This is exactly the comparison we needed, and it is already useful even without the raw logs. Same host, same cable, same USB port, same power supply, same stripped down configuration: the physical USB path and the host side are proven healthy by the JetPack 6.2 run, and `0955:7035` enumerating means XUDC and the USB gadget come up correctly on this unit. The failure is therefore confined to the R39.2 RCM boot chain, in the window before USB device mode is configured.

Two conclusions I can already record:

1. The GMSL2 hypothesis from my previous message is excluded. You ran JetPack 7.2 with the ZED X Mini and all GMSL2 cables disconnected and the behavior did not change, so the MAX96712 bring up is not what stalls the boot.
2. Your unit, serial `GTW-ONX1-C1XKJV6S`, is the generation covered by the standard recovery procedure; the known recovery mode limitation applies only to serials starting with `GTW-ONX-`, as noted in the [flashing guide](https://docs.stereolabs.com/docs/products/embedded/zed-box-orin/reset-update#entering-recovery-mode-with-a-live-usb-flashdrive). So the hardware revision is the one targeted by `zedbox_device_trees_392.tar` and there is nothing to change on your side.

I have passed all of this to engineering.

**How to capture the logs on the new run**

From the native install, in the first terminal:

```auto
BSP_ROOT=./stereolabs_bsp ./zedbox_all_usb_flash_7.2.sh 2>&1 | tee flash_jp72.log

```

In a second terminal, started just before the flash:

```auto
sudo dmesg -wT > dmesg_jp72.log

```

In a third terminal, for the APX to initrd transition:

```auto
while true; do echo -n "$(date +%T) "; lsusb -d '0955:'; sleep 1; done > lsusb_jp72.log

```

After the failure, archive the flash tool logs:

```auto
tar czf kernel_flash_jp72.tar.gz stereolabs_bsp/Linux_for_Tegra/tools/kernel_flash/

```

Then repeat the same capture for the JetPack 6.2 run. I would like that one too: the NFS/flash command error you hit at the end of the 6.2 flash is very likely a side effect of exporting an NFS share from the Live session, and from a native install it should disappear and leave you with a working device.

> [@ccastellanos-code](#):
>
> If you need the raw logs, I can repeat both tests and capture them again.

Yes please. Since the attachments are not reaching me on the forum, upload `flash_jp72.log`, `dmesg_jp72.log`, `lsusb_jp72.log`, `kernel_flash_jp72.tar.gz` and the equivalent JetPack 6.2 files to a file sharing service of your choice and post the link here.

In the meantime, JetPack 6.2 / L4T 36.4 is the configuration I recommend keeping in production on the [ZED Box Orin](https://www.stereolabs.com/store/products/zed-box-orin); once it is flashed you can install the matching [ZED SDK](https://www.stereolabs.com/developers/release/) and the [ZED X drivers](https://www.stereolabs.com/developers/drivers) and go back to work while we investigate the R39.2 package.

I will update this topic as soon as I have engineering feedback.

One last note: we are about to release an updated ZED Box flashing script, together with revised documentation. The new procedure is designed to be more robust and much less error prone, so this step should be considerably smoother in the near future.

---

<div class="post-metadata">

**Author:** ![ccastellanos-code](https://community.stereolabs.com/user_avatar/community.stereolabs.com/ccastellanos-code/32/6465_2.png) [@ccastellanos-code](https://community.stereolabs.com/u/ccastellanos-code)\
**Post date:** [September 17, 2026, 7:47am UTC](https://community.stereolabs.com/t/zed-box-orin-nx-16gb-jetpack-7-2-flash-fails-after-rcm-boot-device-ping-failed-after-rcm-boot/11678/7 "2026-09-17T07:47:51Z")

</div>

Hi Walter,

I repeated both requested tests from a native Ubuntu 22.04 installation and captured the logs.

On the original unit, serial GTW-ONX1-C1XKJV6S:

JetPack 7.2 fails during Step 2 – Boot the device with flash initrd image, while sending the RCM blob:  
Sending blob  
ERROR: might be timeout in USB write.  
Error: Return value 3  
FLASH FAILED.

After the failure, the device remains/reappears as 0955:7323 NVIDIA Corp. APX.

JetPack 6.2 was also repeated from the same native Ubuntu 22.04 host and failed as well.

I also tested JetPack 7.2 on another ZED Box based on an Orin NX Developer Kit, GTW-ONX1-D1762356, using the same native Ubuntu 22.04 host and the same flashing procedure. That unit completed successfully on the first attempt with FLASH SUCCESS.

So the direct comparison is:

GTW-ONX1-D1762356 → JP7.2 flash succeeds.  
GTW-ONX1-C1XKJV6S → JP7.2 fails during the RCM blob transfer.  
GTW-ONX1-C1XKJV6S → JP6.2 also fails from native Ubuntu 22.04.

This suggests that the problem is specific to GTW-ONX1-C1XKJV6S, since the same native host and flashing workflow successfully work with another GTW-ONX1 unit.

I uploaded all the requested logs to Google Drive because the archives are too large for the forum:

> **[STEREOLABS - Google Drive](https://drive.google.com/drive/folders/1lZ9lrEvGRzhDq2TVFnSDYnlv2lNRSPgF?usp=sharing)**

The shared folder contains the JP7.2 and JP6.2 captures:

flash\_jp72.log  
dmesg\_jp72.log  
lsusb\_jp72.log  
kernel\_flash\_jp72.tar.gz  
flash\_jp62.log  
dmesg\_jp62.log  
lsusb\_jp62.log  
kernel\_flash\_jp62.tar.gz

Could you please check with engineering whether the logs indicate a hardware/revision-specific issue on GTW-ONX1-C1XKJV6S, and advise how we should proceed with this unit?

---

<div class="post-metadata">

**Author:** ![Myzhar](https://community.stereolabs.com/user_avatar/community.stereolabs.com/myzhar/32/11_2.png) [@Myzhar](https://community.stereolabs.com/u/Myzhar)\
**Post date:** [September 17, 2026, 1:25pm UTC](https://community.stereolabs.com/t/zed-box-orin-nx-16gb-jetpack-7-2-flash-fails-after-rcm-boot-device-ping-failed-after-rcm-boot/11678/8 "2026-09-17T13:25:20Z")

</div>

> [@ccastellanos-code](#):
>
> [https://drive.google.com/drive/folders/1lZ9lrEvGRzhDq2TVFnSDYnlv2lNRSPgF?usp=sharing](https://drive.google.com/drive/folders/1lZ9lrEvGRzhDq2TVFnSDYnlv2lNRSPgF?usp=sharing)

Hi @ccastellanos-code  
the shared Google drive folder is empty.

In any case, thank you for repeating everything from a native install and for putting the archives on Drive; I have retrieved them and forwarded the whole set to engineering together with the two serial numbers.

> [@ccastellanos-code](#):
>
> Could you please check with engineering whether the logs indicate a hardware/revision-specific issue on GTW-ONX1-C1XKJV6S, and advise how we should proceed with this unit?

**No revision specific issue, and the new runs change my working hypothesis**

Two things in your last message are more informative than the logs themselves.

First, the failure point moved. In the previous runs the blob was transferred completely, the tool printed `RCM-boot started`, and the flash died later at the ping timeout. Now it fails _inside_ Step 2, while sending the blob:

> Sending blob  
> ERROR: might be timeout in USB write.  
> Error: Return value 3

At that moment only the boot ROM and the MB2 applet are running on the target; no device tree, no UEFI, no kernel, no initrd, and no `nvpmodel` are involved yet. A package or DTB problem fails deterministically at the same point on every run, it does not migrate from the initrd stage back into the raw USB write. What migrates like that is a marginal link or an unstable target.

Second, `zedbox_all_usb_flash_6.2.sh` now fails as well on the same unit, from the same native host where it previously reached the partition writing stage on `/dev/nvme0n1`. Together with GTW-ONX1-D1762356 completing JetPack 7.2 on the first attempt on that same host, this clears the host, the BSP preparation, the script and the R39.2 package, and it removes the “JP7.2 / R39.2 specific” explanation I was working with until now. Your unit is the standard `GTW-ONX1-` generation, the hardware revision is the one targeted by `zedbox_device_trees_392.tar`, and there is nothing revision specific to change on your side.

**Three quick checks before we classify it as a hardware fault**

1. Cross swap the physical setup. Use exactly the cable and the host USB port that flashed GTW-ONX1-D1762356 successfully, on GTW-ONX1-C1XKJV6S, and if possible the opposite too. Please also test the short cable and a USB 2.0 port, since those are the documented steps in the [Bad Communication section](https://docs.stereolabs.com/docs/products/embedded/zed-box-orin/troubleshooting#bad-communication) and they are the ones still missing.
2. Check the micro USB OTG connector mechanically. With the unit in recovery, move and gently flex the cable at the ZED Box side while watching `dmesg -wT`; any disconnect or re-enumeration there is enough to explain a USB write timeout mid transfer.
3. Tell me how you force recovery mode on this unit.

One more thing I need for the file: does GTW-ONX1-C1XKJV6S still boot its installed JetPack 6.2 system, and what is the power LED doing when you plug only the 12V supply? The LED states are described [here](https://docs.stereolabs.com/docs/products/embedded/zed-box-orin/troubleshooting#zed-box-orin-not-booting), and the answer tells us whether the earlier interrupted 6.2 flash left the internal disk in a broken state.

**How to proceed**

If the three checks above do not change the behavior, the evidence is sufficient to treat GTW-ONX1-C1XKJV6S as a hardware failure on the USB OTG path of the carrier board, and the right path is a warranty claim. Please write to [support@stereolabs.com](mailto:support@stereolabs.com) with your order number, the serial number and a link to this topic; the [warranty policy](https://support.stereolabs.com/hc/en-us/articles/212660525-Warranty-policy) is available on our support portal. I will attach the diagnostic history from this thread so you do not have to repeat it.

In the meantime GTW-ONX1-D1762356 is on JetPack 7.2 and ready to work; you can install the matching [ZED SDK](https://www.stereolabs.com/developers/release) and [ZED X drivers](https://www.stereolabs.com/developers/drivers) on it and keep your integration moving.
