Troubleshooting

Here are some common issues that you could face with your ZED Box Orin NX.

If you are unable to resolve your issue using the following suggestions, please reach out to us at support@stereolabs.com for further assistance.

ZED Box Orin NX not booting #

If your ZED Box Orin NX does not turn on after a shutdown, follow these steps to diagnose the issue.

1. Check Power Connection #

Try these steps to force a boot:

  • Unplug both the power cable and the Ethernet PoE+ cable.
  • Plug in only one of them (either the power cable or the PoE+ cable) and check if the device powers on.

📌 Note: The carrier board of the ZED Box Orin NX cannot reboot if one power cable is already connected when plugging in the other.

2. Check the Power LED Status #

Locate the power LED on the front panel and determine its status:

🟢 LED is ON #

  • This indicates a software issue requiring a hard reset of the device.
  • The ZED Box software may have been corrupted due to an improper shutdown.
  • Important: Always shut down the device properly by software before removing power to avoid software corruption.
  • Solution: Perform a software reset.

⚫ LED is OFF #

  • If you have already tried the power cable procedure, this suggests a hardware failure.
  • Solution: Contact Stereolabs Support for further assistance.

I cannot retrieve any GNSS data, whereas I’m in open air #

Please make sure that you plugged a male antenna into the port 5 on the side of ZED Box. Then reboot, and run cgps.

gpsd has know incompatibilities when working with systemd, which is the default behavior. For that reason, we strongly advise you NOT to use gpsd with systemd. Usual trouble are that your host will need to reboot every time you want to stop your application and run it again.

The easiest way to run gpsd is with

sudo gpsd -nG -P /run/gpsd.pid /dev/ttyACM0

You can run this in a CRON job :

@reboot sleep 10 && /usr/sbin/gpsd -nG -P /run/gpsd.pid /dev/ttyACM0

The WiFi does not work anymore after a system update #

After daily operating system updates, the WiFi module on the ZED Box Orin NX may stop working.

This issue occurs when the Ubuntu Software Updater or apt installs an incorrect WiFi driver.

Solution Follow these steps to remove the incorrect driver and reload the correct one:

Remove the incorrect driver file #

Run the following command to delete the problematic firmware file:

sudo rm /lib/firmware/iwlwifi-ty-a0-gf-a0-66.ucode

now you can reboot (sudo reboot) the device to automatically load the correct driver, or continue to do that manually without a reboot.

Unload the incorrect driver #

Unload the currently loaded (incorrect) WiFi driver:

sudo modprobe -r iwlwifi

Load the correct driver #

Reload the correct default WiFi driver:

sudo modprobe iwlwifi

After completing these steps, your WiFi module should function properly again.

Issues flashing the ZED Box Orin NX #

If you encounter issues while flashing your ZED Box Orin NX, follow these steps to troubleshoot the problem.

Force Recovery Mode #

If the flash procedure fails, it is likely because the ZED Box Orin NX is not in Recovery Mode before launching the flash script.

To verify that the ZED Box is in “Recovery Mode,” enter the following command in the host PC’s command line console:

lsusb -d '0955:'

If the device is correctly in Recovery Mode, the command should return:

  • ZED Box Orin NX 16 GB: An NVIDIA® device with VID:PID 0955:7323 should be listed. Example: Bus xxx Device yyy: ID 0955:7323 NVIDIA Corp. APX
  • ZED Box Orin NX 8 GB: An NVIDIA® device with VID:PID 0955:7423 should be listed. Example: Bus xxx Device yyy: ID 0955:7423 NVIDIA Corp. APX

If the ZED Box Orin NX is not in Recovery Mode, follow again the Force the ZED Box in Recovery Mode guide accurately.

If the problem persists and you cannot force the device into Recovery Mode, follow the alternative guide to use a live USB flash drive.

If the issue continues after following both guides, contact Stereolabs Support for further assistance.

Bad Communication #

If the device is in Recovery Mode and the flash procedure fails, please verify the following conditions and retry:

  • Avoid using virtual machines.

  • Avoid using WSL2.

  • Use a shorter USB cable.

  • Use a different USB port, preferably one directly soldered to the motherboard.

  • Try using a different host Ubuntu PC.

  • Disable USB autosuspend with the following command:

    sudo bash -c 'echo -1 > /sys/module/usbcore/parameters/autosuspend'

If the problem persists, collect all the flash log information and contact Stereolabs Support for further assistance.