> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.stereolabs.com/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.stereolabs.com/_mcp/server. # Troubleshooting Here are some common issues that you could face with your ZED Box Orin. If you are unable to resolve your issue using the following suggestions, please reach out to us at [support@stereolabs.com](mailto:support@stereolabs.com) for further assistance. ## ZED Box Orin not booting If your ZED Box Orin 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 **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**. * The ZED Box software may have been corrupted due to an improper shutdown or the internal disk may be full. * **Important:** Always shut down the device properly by software before removing power to avoid file system corruption. * **Solution:** * Try to follow the [Recover a ZED Box Orin with full disk](/docs/products/embedded/zed-box-orin/troubleshooting/#zed-box-orin-not-booting-when-the-disk-is-full) procedure to verify if the internal disk is full and fix it. * If the issue persists, perform a [hard reset](/docs/products/embedded/zed-box-orin/reset-update/). #### **⚫ LED is OFF** * If you have already tried the [power cable procedure](/docs/products/embedded/zed-box-orin/troubleshooting/#1-check-power-connection), this suggests a possible **file system** or **hardware** failure. * **Solution:** * To identify a **file system issue**, you can try to boot the ZED Box Orin in Force Recovery mode. Read the procedure [in the device flash guide](/docs/products/embedded/zed-box-orin/reset-update/#force-the-zed-box-in-recovery-mode). * If your device does not boot into Force Recovery mode, it is likely due to a **hardware failure**. In this case, contact [StereoLabs Support](mailto:support@stereolabs.com) for further assistance. --- ## ZED Box Orin not booting when the disk is full If your ZED Box Orin is not booting due to a full disk, you can try the following steps to recover it. **Requirements**: * a host PC running **Ubuntu 20.04** or **Ubuntu 22.04**. * a **32 GB or larger** USB 3.0 key. > **Warning** > > **ALL THE INFORMATION STORED IN THE USB KEY WILL BE WIPED DURING THE PROCEDURE** > **Note** > > If the USB Key contains multiple partitions, you must delete them all before proceeding. You can use the `gparted` tool to manage partitions. Create a bootable recovery USB Key and use it to free up space on the internal disk of the ZED Box Orin by following these steps: 1. Connect the USB Key to the host PC. * Open a terminal (`Ctrl+Alt+T`). * Enter the command `lsblk` to identify the device name `sdX` of your USB Key (e.g., `sda`). * Download the flash script to create a bootable recovery USB Key from our servers: * [NVIDIA® JetPack 6.2 / L4T 36.4.3](https://download.stereolabs.com/scripts/zedbox_all_usb_flash_6.2.sh) * [NVIDIA® JetPack 7.2 / L4T 39.2](https://download.stereolabs.com/scripts/zedbox_all_usb_flash_7.2.sh) * Make the script executable: ```bash chmod +x zedbox_all_usb_flash_.sh ``` * Run the script, replacing `` with your USB Key device name, e.g `sda`, and `` with your Jetpack version: ```bash BSP_ROOT=./stereolabs_bsp SDX= ./zedbox_all_usb_flash_.sh ``` * Wait for the script to complete. This will erase all data on the USB Key and create a bootable recovery drive. This operation can take a while according to the USB Key read/write speed (ETA > 60 min). 2. Unplug the USB Key from the host PC and plug it into one of the horizontal USB ports on the ZED Box Orin. 3. Plug the power cable or the Ethernet PoE+ cable to the ZED Box Orin, to turn it on and boot from the USB Key. 4. Connect a micro-USB cable to the OTG port of the ZED Box Orin and to the host PC. 5. On the host PC, open a terminal and start a serial terminal application to connect to the ZED Box Orin via the micro-USB cable: ```bash sudo gtkterm ``` then in the menu `Configuration > Port`, select `/dev/ttyACM0`. > **Note** > > It can take quite a while before the device shows up because of the USB Key initialization process (ETA 5 min). 6. When `ttyACM0` is connected, press `Enter` a couple of times to force the display of the prompt, i.e. `GTW-ONX16-ubuntu login:`. 7. Enter the username and password of the ZED Box Orin (default: `user` / `admin`). 8. Once logged in, run the command `lsblk` to verify that `nvme0n1` exists. You can use `df -h` to check the disk usage. If the root partition `/` is close to 100%, you need to free up some space to allow the ZED Box Orin to boot. 9. Mount the internal disk in read-write mode: ```bash mkdir mnt sudo mount /dev/nvme0n1p1 mnt/ ``` 10. The folder `mnt` now contains the file system of the ZED Box Orin. You can now delete some files to free up space. For example, you can delete old log files in `mnt/var/log/` or old user files in `mnt/home/user/`. If you are using ROS 2, you can delete ROS 2 logs in `mnt/home/user/.ros/log/` to recover space. 11. You can use the command `df -h` to check the available space on the internal disk. 12. Once you have freed up enough space, unmount the internal disk: ```bash sudo umount mnt ``` 13. Enter the command `sudo shutdown -h now` to turn off the ZED Box Orin. 14. Unplug the USB Key and the micro-USB cable. 15. Plug the power cable or the Ethernet PoE+ cable to the ZED Box Orin. 16. The ZED Box Orin should now boot normally. --- ## I cannot retrieve any GNSS data even though I am outdoors 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 known incompatibilities when working with `systemd`, which is the default behavior. For that reason, **we strongly advise you NOT to use `gpsd` with `systemd`.** A common issue is that the host must be rebooted every time you stop your application and want to run it again. The easiest way to run `gpsd` is with ```bash sudo gpsd -nG -P /run/gpsd.pid /dev/ttyACM0 ``` You can run this in a CRON job: ```bash @reboot sleep 10 && /usr/local/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 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 firmware file and reload the correct driver: ### Remove the incorrect firmware file Run the following command to delete the problematic firmware file: ```bash sudo rm /lib/firmware/iwlwifi-ty-a0-gf-a0-66.ucode ``` Now you can reboot the device (`sudo reboot`) to automatically load the correct driver, or load it manually without rebooting. ### Unload the incorrect driver Unload the currently loaded (incorrect) WiFi driver: ```bash sudo modprobe -r iwlwifi ``` ### Load the correct driver Reload the correct default WiFi driver: ```bash sudo modprobe iwlwifi ``` After completing these steps, your WiFi module should function properly again. --- ## I cannot flash the ZED Box Orin If you encounter issues while flashing your ZED Box Orin, follow these steps to troubleshoot the problem. ### Force Recovery Mode If the flash procedure fails, it is likely because the ZED Box Orin 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: ```bash lsusb -d '0955:' ``` If the device is correctly in Recovery Mode, the command should return: * **NVIDIA® Jetson™ Orin Nano 8 GB**: an NVIDIA® device with VID:PID `0955:7523` should be listed. e.g. `Bus xxx Device yyy: ID 0955:7523 NVIDIA Corp. APX` * **NVIDIA® Jetson™ Orin NX 8 GB**: an NVIDIA® device with VID:PID `0955:7423` should be listed. e.g. `Bus xxx Device yyy: ID 0955:7423 NVIDIA Corp. APX` * **NVIDIA® Jetson™ Orin NX 16 GB**: an NVIDIA® device with VID:PID `0955:7323` should be listed. e.g. `Bus xxx Device yyy: ID 0955:7323 NVIDIA Corp. APX` If the ZED Box Orin is not in Recovery Mode, follow again the [Force the ZED Box in Recovery Mode](/docs/products/embedded/zed-box-orin/reset-update/#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](/docs/products/embedded/zed-box-orin/reset-update/#entering-recovery-mode-with-a-live-usb-flashdrive). If the issue continues after following both guides, contact [StereoLabs Support](mailto:support@stereolabs.com) 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: ```bash sudo bash -c 'echo -1 > /sys/module/usbcore/parameters/autosuspend' ``` --- ## Error: "Package nvidia-l4t-kernel is not configured yet" while installing the ZED X Driver After upgrading the ZED Box Orin with `sudo apt upgrade`, reinstall the ZED X Driver to restore full compatibility. In some cases, the reinstallation can fail with the dependency error shown below: ```bash dpkg: dependency problems prevent configuration of stereolabs-zedbox-duo: stereolabs-zedbox-duo depends on nvidia-l4t-rt-kernel (>= 5.15.148-rt-tegra-36.4.0-20240912212859) | nvidia-l4t-kernel (>= 5.15.148-tegra-36.4.0-20240912212859); however: Package nvidia-l4t-rt-kernel is not installed. Package nvidia-l4t-kernel is not configured yet. stereolabs-zedbox-duo depends on nvidia-l4t-rt-kernel (<= 5.15.148-rt-tegra-36.4.4-20250616085344) | nvidia-l4t-kernel (<= 5.15.148-tegra-36.4.4-20250616085344); however: Package nvidia-l4t-rt-kernel is not installed. Package nvidia-l4t-kernel is not configured yet. dpkg: error processing package stereolabs-zedbox-duo (--install): dependency problems - leaving unconfigured Errors were encountered while processing: stereolabs-zedbox-duo ``` To resolve this issue, you can follow these steps: > **Warning** > > This procedure resets the dpkg package metadata (maintainer scripts and file lists) of **all** installed packages. Use it only as a last resort, when `sudo dpkg --configure -a` and `sudo apt-get -f install` alone do not solve the problem. ```bash sudo apt-get autoclean # Clean up the package cache sudo mv /var/lib/dpkg/info/ /var/lib/dpkg/backup/ # Backup the info directory sudo mkdir /var/lib/dpkg/info/ # Create a new info directory sudo apt-get update # Update the package list sudo apt-get -f install # Fix broken dependencies ``` This process will clean up the package cache, backup the existing package information, create a new directory for package information, update the package list, and fix any broken dependencies that may be causing the issue. After completing these steps, you should be able to install the ZED X Driver without encountering the "Package nvidia-l4t-kernel is not configured yet" error. --- ## Chromium and Firefox browser issues with Jetson Linux (L4T) 36.4.4 - JP 6.2.1 Upgrading to Jetson Linux (L4T) 36.4.4 - JP 6.2.1 introduces Snapd 2.70, which breaks all Snap packages with the following error: ```bash cannot set capabilities: Operation not permitted ``` For this reason, the Chromium and Firefox browsers, and other Snap-based applications, fail to launch. This occurs because Jetson Orin devices ship with a minimal kernel that lacks certain security features required by Snapd 2.70 and newer. To resolve this issue, revert Snapd to an earlier working version: ```bash snap download snapd --revision=24724 sudo snap ack snapd_24724.assert sudo snap install snapd_24724.snap sudo snap refresh --hold snapd ``` For more information, refer to [this page of the JetsonHacks website](https://jetsonhacks.com/2025/07/12/why-chromium-suddenly-broke-on-jetson-orin-and-how-to-bring-it-back/). --- ## Blurry images after system update After a system update, if you experience blurry images from the [GMSL2](/docs/products/embedded/zed-link-capture-card/gmsl2#what-is-gmsl2) camera, it may be caused by the overwriting of a patched library used by the ZED Link driver. To fix this issue, please follow this procedure to manually restore the patched library: 1. Download the latest ZED Link driver package for your device from the [ZED X Drivers download page](https://www.stereolabs.com/developers/drivers). 2. Extract the downloaded `.deb` package and copy the patched library to the correct location: ```bash ar x stereolabs-zed_--_arm64.deb tar xvf data.tar.xz sudo cp ./tmp/R/libnvisppg.so /usr/lib/aarch64-linux-gnu/tegra/libnvisppg.so ``` Replace `stereolabs-zed_--_arm64.deb` with the actual filename of the downloaded package. Replace `` in the `cp` command with your current L4T version (for example, `36.4.3`). 3. Reboot the Jetson device: ```bash sudo reboot ``` After following these steps, the [GMSL2](/docs/products/embedded/zed-link-capture-card/gmsl2#what-is-gmsl2) camera should function correctly with clear images. --- ## Contact Support If you are unable to resolve your issue, please visit our [community forum](https://community.stereolabs.com/) or contact [support@stereolabs.com](mailto:support@stereolabs.com) for further assistance.