# Carrier board mini - cameras not detected

**URL:** <https://community.stereolabs.com/t/carrier-board-mini-cameras-not-detected/10924>\
**Category:** ZED X\
**Created:** [February 27, 2026, 8:55pm UTC](https://community.stereolabs.com/t/carrier-board-mini-cameras-not-detected/10924 "2026-02-27T20:55:50Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![andrwr\_rev](https://community.stereolabs.com/letter_avatar_proxy/v4/letter/a/e0b2c6/32.png) [@andrwr\_rev](https://community.stereolabs.com/u/andrwr_rev)\
**Post date:** [February 27, 2026, 8:55pm UTC](https://community.stereolabs.com/t/carrier-board-mini-cameras-not-detected/10924/1 "2026-02-27T20:55:50Z")

</div>

Hi,

I have a fresh install on the mini carrier board with Jetson Orin NX 8GB, according to these instructions:

> **[Flash your ZED Box Mini - Stereolabs](https://www.stereolabs.com/docs/embedded/zed-box-mini/reset-update)**
>
> Should I flash my ZED Box Mini? # The ZED Box Mini is shipped with a pre-configured operating system and drivers optimized for its hardware.

> **[Install your ZED Box Mini - Stereolabs](https://www.stereolabs.com/docs/embedded/zed-box-mini/installation)**
>
> 01. \[Optional\] Connect your ZED camera # The ZED Box Mini is an embedded Linux device that operates as a standard Linux-based PC. While it is designed for seamless compatibility with ZED cameras, …

When I try to run the diagnostics, no cameras are detected. When running `ZED_Explorer --all`, it returns `(Argus) Error Timeout: (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function openSocketConnection(), line 220)`  
`(Argus) Error Timeout: Cannot create camera provider (in src/rpc/socket/client/SocketClientDispatch.cpp, function createCameraProvider(), line 107)`  
`No ZED detected`

Diagnostic files generated with `sudo ZED_Diagnostic --dmesg` and `sudo ZED_Diagnostic -c` below.

[dmesg.log](https://community.stereolabs.com/uploads/short-url/8yHe17weyqp0xhSFciKPDfibx2t.log) (11.3 KB)

[ZED\_Diagnostic\_Results.json](https://community.stereolabs.com/uploads/short-url/u6j8qyVcVm6Ich2qm8dA8poyFS3.json) (19.3 KB)

Best,

Andreas

---

<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:** [March 2, 2026, 3:27pm UTC](https://community.stereolabs.com/t/carrier-board-mini-cameras-not-detected/10924/2 "2026-03-02T15:27:07Z")

</div>

Hi @andrwr_rev  
Have you connected the camera or modified the hardware setup after booting the device?

---

<div class="post-metadata">

**Author:** ![andrwr\_rev](https://community.stereolabs.com/letter_avatar_proxy/v4/letter/a/e0b2c6/32.png) [@andrwr\_rev](https://community.stereolabs.com/u/andrwr_rev)\
**Post date:** [March 2, 2026, 4:47pm UTC](https://community.stereolabs.com/t/carrier-board-mini-cameras-not-detected/10924/3 "2026-03-02T16:47:19Z")

</div>

I have not changed the hardware setup in any way after booting the device.

Some more information though, it _seems_ like the issue occurs after installing NVidia Deepstream according to the instructions [here](https://docs.nvidia.com/metropolis/deepstream/7.1/text/DS_Installation.html).

---

<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:** [March 2, 2026, 5:00pm UTC](https://community.stereolabs.com/t/carrier-board-mini-cameras-not-detected/10924/4 "2026-03-02T17:00:28Z")

</div>

If the Deepstream installer modifies the DTB setup, then you must reinstall the ZED X Driver to fix if.

---

<div class="post-metadata">

**Author:** ![andrwr\_rev](https://community.stereolabs.com/letter_avatar_proxy/v4/letter/a/e0b2c6/32.png) [@andrwr\_rev](https://community.stereolabs.com/u/andrwr_rev)\
**Post date:** [March 4, 2026, 2:20pm UTC](https://community.stereolabs.com/t/carrier-board-mini-cameras-not-detected/10924/5 "2026-03-04T14:20:41Z")

</div>

We are going to containerize our application to work around this

---

<div class="post-metadata">

**Author:** ![andrwr\_rev](https://community.stereolabs.com/letter_avatar_proxy/v4/letter/a/e0b2c6/32.png) [@andrwr\_rev](https://community.stereolabs.com/u/andrwr_rev)\
**Post date:** [March 4, 2026, 4:10pm UTC](https://community.stereolabs.com/t/carrier-board-mini-cameras-not-detected/10924/6 "2026-03-04T16:10:23Z")

</div>

Ok, so we immediately ran into issues with running the OpenCV calibration tool in the containerized version ([this topic)](https://community.stereolabs.com/t/virtual-zed-x-one-calibration-fails-segmentation-fault/10953). As part of workaround attempts I installed the ZED SDK outside the container, and it immediately caused the same issues as in my original post. ZED\_Diagnostic fails with the log below.

[dmesg.log](https://community.stereolabs.com/uploads/short-url/vED4sdYRNRWFKU1ktqfiycZlv7X.log) (11.3 KB)

> [@Myzhar](#):
>
> If the Deepstream installer modifies the DTB setup, then you must reinstall the ZED X Driver to fix if.

Removing and reinstalling the driver and SDK does not solve the issue. That is, the Diagnostics will always fail until the carrier mini is flashed again. Please advise @Myzhar

---

<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:** [March 4, 2026, 6:23pm UTC](https://community.stereolabs.com/t/carrier-board-mini-cameras-not-detected/10924/7 "2026-03-04T18:23:33Z")

</div>

I met internally with the team to try to understand more about this problem.  
We used Deepstream internally, and we have not faced issues, so there’s something in your installation process that is breaking the GMSL2 functionalities.

> [@andrwr\_rev](#):
>
> Removing and reinstalling the driver and SDK does not solve the issue.

If Deepstream modified the DTB or the kernel, you should have made the ZED X Camera work again by reinstalling the driver.  
The fact that this does not work makes us believe that the Argus libraries, at some point, have been modified.

Can you please share the procedure that you are following to configure the Jetson to install and configure Deepstream (or anything else that is not ZED-related)?

---

<div class="post-metadata">

**Author:** ![andrwr\_rev](https://community.stereolabs.com/letter_avatar_proxy/v4/letter/a/e0b2c6/32.png) [@andrwr\_rev](https://community.stereolabs.com/u/andrwr_rev)\
**Post date:** [March 4, 2026, 8:31pm UTC](https://community.stereolabs.com/t/carrier-board-mini-cameras-not-detected/10924/8 "2026-03-04T20:31:13Z")

</div>

Sure, here is the procedure:

- Initial hardware setup: Carrier Mini W/Orin NX 8GB. 2x ZED X One connected.
- Flash the card according to the instructions for Zed box mini.
- `sudo apt update `, `sudo apt upgrade -y`, `sudo apt-dist upgrade`
- Reboot
- `sudo apt install nvidia-jetpack`
- Install driver 1.4.0
- Install ZED SDK 5.2
- Install the following (probably some duplicates, they are installed over multiple scripts)
  - sudo

  - apt-utils

  - python3-pip

  - clang-format

- Install zenoh according to [These instructions](https://github.com/eclipse-zenoh/zenoh-c)
- Install deepstream 7.1 for Jetson (we use the .deb): [Installation — DeepStream documentation](https://docs.nvidia.com/metropolis/deepstream/7.1/text/DS_Installation.html)
  - This also modifies glib and installs kafka
  - Also installs the below
  - libssl3 \  
libssl-dev \  
libgstreamer1.0-0 \  
gstreamer1.0-tools \  
gstreamer1.0-plugins-good \  
gstreamer1.0-plugins-bad \  
gstreamer1.0-plugins-ugly \  
gstreamer1.0-libav \  
libgstreamer-plugins-base1.0-dev \  
libgstrtspserver-1.0-0 \  
libjansson4 \  
libyaml-cpp-dev \  
libmosquitto1

---

<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:** [March 5, 2026, 1:55pm UTC](https://community.stereolabs.com/t/carrier-board-mini-cameras-not-detected/10924/9 "2026-03-05T13:55:23Z")

</div>

What method of the 4 have you used to install DeepStream?

> **[DeepStreamSDK - Installation — DeepStream documentation](https://docs.nvidia.com/metropolis/deepstream/7.1/text/DS_Installation.html#install-the-deepstream-sdk)**
>
> This section explains how to prepare a Jetson device before installing the DeepStream SDK.

Why have you installed Zenoh? (This is a curiosity of mine…)

---

<div class="post-metadata">

**Author:** ![andrwr\_rev](https://community.stereolabs.com/letter_avatar_proxy/v4/letter/a/e0b2c6/32.png) [@andrwr\_rev](https://community.stereolabs.com/u/andrwr_rev)\
**Post date:** [March 5, 2026, 2:10pm UTC](https://community.stereolabs.com/t/carrier-board-mini-cameras-not-detected/10924/10 "2026-03-05T14:10:41Z")

</div>

Method 3, the .deb install.

As far as Zenoh goes, it is our choice of protocol for pub/sub comms between the Jetson device and a separate CPU (No, we do not use ROS)

---

<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:** [March 5, 2026, 2:51pm UTC](https://community.stereolabs.com/t/carrier-board-mini-cameras-not-detected/10924/11 "2026-03-05T14:51:16Z")

</div>

> [@andrwr\_rev](#):
>
> Method 3, the .deb install.

This is the same method we tested with no issues.

> [@andrwr\_rev](#):
>
> As far as Zenoh goes, it is our choice of protocol for pub/sub comms between the Jetson device and a separate CPU (No, we do not use ROS)

Interesting choice 👍

---

<div class="post-metadata">

**Author:** ![andrwr\_rev](https://community.stereolabs.com/letter_avatar_proxy/v4/letter/a/e0b2c6/32.png) [@andrwr\_rev](https://community.stereolabs.com/u/andrwr_rev)\
**Post date:** [March 5, 2026, 3:42pm UTC](https://community.stereolabs.com/t/carrier-board-mini-cameras-not-detected/10924/12 "2026-03-05T15:42:47Z")

</div>

I have to prioritize an upcoming tech demo and will not follow this up immediately, insofar as our current containerized setup seems to be working at the moment.
