Can't open ZED Camera on SDK 5.0.6

daiduc · September 12, 2025, 10:08am

Hello everyone,

as the title says, for some reason I cant open the ZED X or the ZED One with the new SDK5.0.6 version. It did work with SDK4.

[2025-09-12 09:25:12 UTC][ZED][INFO] Logging level INFO
[2025-09-12 09:25:15 UTC][ZED][INFO] [Init] Depth mode: NEURAL
bmi08g_init Error [-2] : Communication failure
bmi08g_set_int_config Error [-2] : Communication failure
[2025-09-12 09:25:20 UTC][ZED][ERROR] [ZED] A ZED camera has been detected but the sensors device has failed to open. Please try to unplug/plug the camera again.
[2025-09-12 09:25:21 UTC][ZED][WARNING] CAMERA MOTION SENSORS NOT DETECTED in sl::ERROR_CODE sl::open(sl::InitParameters)

[2025-09-12 09:27:30 UTC][ZED][INFO] Using GMSL input… Switched to default resolution HD1200
bmi08g_init Error [-2] : Communication failure
bmi08g_set_int_config Error [-2] : Communication failure
[2025-09-12 09:27:33 UTC][ZED][ERROR] [ZED] A ZED camera has been detected but the sensors device has failed to open. Please try to unplug/plug the camera again.

My system is a Jetson Xavier NX L4T 35.4.1 Python 3.8.10

Myzhar · September 12, 2025, 10:23am

Hi @daiduc
Welcome to the StereoLabs community.

What version of the ZED X Driver are you using?
Please send me the output of the command sudo dpkg -l | grep zed

daiduc · September 12, 2025, 10:26am

Hi I’m using the ZED Link Duo Driver

ii stereolabs-zedlink-duo 1.3.1-LI-MAX96712-ALL-L4T35.4.1 arm64 NVIDIA Kernel DTB Modified Package by Stereolabs

Myzhar · September 12, 2025, 10:28am

Hi @daiduc
I shared the information with the HW team. I will get back to you as soon as possible.

Myzhar · September 16, 2025, 8:25am

Hi @daiduc
We replicated your setup and were unable to replicate the issue.
The problem could be caused by unstable I2C communication, possibly due to a poor capture card setup.

Please send pictures of the Jetson with all the GMSL2 connections.

daiduc · September 16, 2025, 8:57am

Hi @Myzhar

here are the pictures you asked for

It is kind of odd. I can open the camera in ZED Explorer and through the Python API on SDK 4.2.5. But whenever I try it on SDK 5.x nothing works, it always shows the bmi08g error.

What else can I try?

daiduc · September 23, 2025, 2:37pm

Hi @Myzhar is there anything else that I can try or send?

daiduc · September 24, 2025, 9:33am

So I’ve tried to uninstall the driver and the ZED SDK and even used the newest version 5.0.7.
But I’m getting the same error

python streaming_sender.py
[Sample] Using default resolution
[2025-09-24 09:26:46 UTC][ZED][INFO] Using GMSL input... Switched to default resolution HD1200
bmi08g_init     Error [-2] : Communication failure
bmi08g_set_int_config   Error [-2] : Communication failure
[2025-09-24 09:26:49 UTC][ZED][ERROR] [ZED] A ZED camera has been detected but the sensors device has failed to open. Please try to unplug/plug the camera again.
Camera Open : CAMERA MOTION SENSORS NOT DETECTED. Exit program.

Does this output maybe help?

sudo dmesg | grep zedx
[   29.931995] sl_max9295 30-0060: probe_serializer: Serializer for zedxpro detect error
[   29.968030] sl_max9295 30-0061: probe_serializer: Serializer for zedxpro detect error
[   30.044314] sl_max9295 30-0063: probe_serializer: Serializer for zedx detect error
[   30.080104] sl_max9295 30-0062: probe_serializer: Serializer for zedx detect error
[   30.460106] sl_max9295 31-0060: probe_serializer: Serializer for zedxpro detect error
[   30.496081] sl_max9295 31-0061: probe_serializer: Serializer for zedxpro detect error
[   30.576047] sl_max9295 31-0063: probe_serializer: Serializer for zedx detect error
[   30.612155] sl_max9295 31-0062: probe_serializer: Serializer for zedx detect error
[   30.896741] zedxpro 30-003e: probing v4l2 sensor.
[   30.896973] zedxpro 30-003e: tegracam sensor driver:video7_v2.0.6
[   30.897958] zedxpro 30-003e: zedxpro_probe: Start streaming fail
[   30.898305] zedxpro 30-002e: probing v4l2 sensor.
[   30.898508] zedxpro 30-002e: tegracam sensor driver:video8_v2.0.6
[   30.899402] zedxpro 30-002e: zedxpro_probe: Start streaming fail
[   30.899767] zedxpro 30-003f: probing v4l2 sensor.
[   30.900029] zedxpro 30-003f: tegracam sensor driver:video9_v2.0.6
[   30.900933] zedxpro 30-003f: zedxpro_probe: Start streaming fail
[   30.901227] zedxpro 30-002f: probing v4l2 sensor.
[   30.901408] zedxpro 30-002f: tegracam sensor driver:video10_v2.0.6
[   30.902286] zedxpro 30-002f: zedxpro_probe: Start streaming fail
[   30.902643] zedxpro 30-004e: probing v4l2 sensor.
[   30.902905] zedxpro 30-004e: tegracam sensor driver:video11_v2.0.6
[   30.904224] zedxpro 30-004e: zedxpro_probe: Start streaming fail
[   30.904527] zedxpro 30-004f: probing v4l2 sensor.
[   30.904800] zedxpro 30-004f: tegracam sensor driver:video12_v2.0.6
[   30.905634] zedxpro 30-004f: zedxpro_probe: Start streaming fail
[   30.906001] zedxpro 31-003e: probing v4l2 sensor.
[   30.906170] zedxpro 31-003e: tegracam sensor driver:video20_v2.0.6
[   30.906977] zedxpro 31-003e: zedxpro_probe: Start streaming fail
[   30.907371] zedxpro 31-002e: probing v4l2 sensor.
[   30.907582] zedxpro 31-002e: tegracam sensor driver:video21_v2.0.6
[   30.908472] zedxpro 31-002e: zedxpro_probe: Start streaming fail
[   30.908801] zedxpro 31-003f: probing v4l2 sensor.
[   30.908993] zedxpro 31-003f: tegracam sensor driver:video22_v2.0.6
[   30.909792] zedxpro 31-003f: zedxpro_probe: Start streaming fail
[   30.910127] zedxpro 31-002f: probing v4l2 sensor.
[   30.910311] zedxpro 31-002f: tegracam sensor driver:video23_v2.0.6
[   30.911110] zedxpro 31-002f: zedxpro_probe: Start streaming fail
[   30.911556] zedxpro 31-004e: probing v4l2 sensor.
[   30.911781] zedxpro 31-004e: tegracam sensor driver:video24_v2.0.6
[   30.912590] zedxpro 31-004e: zedxpro_probe: Start streaming fail
[   30.912922] zedxpro 31-004f: probing v4l2 sensor.
[   30.913079] zedxpro 31-004f: tegracam sensor driver:video25_v2.0.6
[   30.913895] zedxpro 31-004f: zedxpro_probe: Start streaming fail
[   30.926716] zedx 30-0028: Driver Version : v1.3.1
[   30.926728] zedx 30-0028: Probing v4l2 sensor.
[   30.927021] zedx 30-0028: tegracam sensor driver:video0_v2.0.6
[   30.984618] zedx 30-0028: ZED-X detect error
[   30.984721] zedx 30-0028: zedx_probe: ar0234 initialization failed
[   30.985025] zedx: probe of 30-0028 failed with error -1
[   30.985221] zedx 30-0020: Driver Version : v1.3.1
[   30.985228] zedx 30-0020: Probing v4l2 sensor.
[   30.985517] zedx 30-0020: tegracam sensor driver:video1_v2.0.6
[   31.036066] zedx 30-0020: ZED-X detect error
[   31.036142] zedx 30-0020: zedx_probe: ar0234 initialization failed
[   31.036464] zedx: probe of 30-0020 failed with error -1
[   31.036689] zedx 30-0038: Driver Version : v1.3.1
[   31.036696] zedx 30-0038: Probing v4l2 sensor.
[   31.037045] zedx 30-0038: tegracam sensor driver:video2_v2.0.6
[   31.088128] zedx 30-0038: ZED-X detect error
[   31.088197] zedx 30-0038: zedx_probe: ar0234 initialization failed
[   31.088505] zedx: probe of 30-0038 failed with error -1
[   31.088703] zedx 30-0030: Driver Version : v1.3.1
[   31.088710] zedx 30-0030: Probing v4l2 sensor.
[   31.089044] zedx 30-0030: tegracam sensor driver:video3_v2.0.6
[   31.150492] zedx 30-0030: ZED-X detect error
[   31.151085] zedx 30-0030: zedx_probe: ar0234 initialization failed
[   31.152034] zedx: probe of 30-0030 failed with error -1
[   31.152459] zedx 30-0010: Driver Version : v1.3.1
[   31.152468] zedx 30-0010: Probing v4l2 sensor.
[   31.153537] zedx 30-0010: tegracam sensor driver:video4_v2.0.6
[   31.239332] zedx 30-0010: Enable gmsl for channel 0 and id 4
[   31.486242] tegra-camrtc-capture-vi tegra-capture-vi: subdev zedx 30-0010 bound
[   31.500416] zedx 30-0010: Detected ZED-X sensor
[   31.500434] zedx 30-0010: zedx_probe: Serial Number : 309165243
[   31.500443] zedx 30-0010: zedx_probe: CHANNEL: 0 ID: 4
[   31.512477] zedx 30-0011: Driver Version : v1.3.1
[   31.512489] zedx 30-0011: Probing v4l2 sensor.
[   31.512832] zedx 30-0011: tegracam sensor driver:video5_v2.0.6
[   31.560331] zedx 30-0011: ZED-X detect error
[   31.560395] zedx 30-0011: zedx_probe: ar0234 initialization failed
[   31.560705] zedx: probe of 30-0011 failed with error -1
[   31.560969] zedx 31-0028: Driver Version : v1.3.1
[   31.560976] zedx 31-0028: Probing v4l2 sensor.
[   31.561313] zedx 31-0028: tegracam sensor driver:video13_v2.0.6
[   31.612038] zedx 31-0028: ZED-X detect error
[   31.612131] zedx 31-0028: zedx_probe: ar0234 initialization failed
[   31.612424] zedx: probe of 31-0028 failed with error -1
[   31.612611] zedx 31-0020: Driver Version : v1.3.1
[   31.612618] zedx 31-0020: Probing v4l2 sensor.
[   31.612954] zedx 31-0020: tegracam sensor driver:video14_v2.0.6
[   31.672160] zedx 31-0020: ZED-X detect error
[   31.672234] zedx 31-0020: zedx_probe: ar0234 initialization failed
[   31.672534] zedx: probe of 31-0020 failed with error -1
[   31.672751] zedx 31-0038: Driver Version : v1.3.1
[   31.672758] zedx 31-0038: Probing v4l2 sensor.
[   31.673053] zedx 31-0038: tegracam sensor driver:video15_v2.0.6
[   31.719989] zedx 31-0038: ZED-X detect error
[   31.720062] zedx 31-0038: zedx_probe: ar0234 initialization failed
[   31.720329] zedx: probe of 31-0038 failed with error -1
[   31.720524] zedx 31-0030: Driver Version : v1.3.1
[   31.720531] zedx 31-0030: Probing v4l2 sensor.
[   31.720845] zedx 31-0030: tegracam sensor driver:video16_v2.0.6
[   31.768097] zedx 31-0030: ZED-X detect error
[   31.768190] zedx 31-0030: zedx_probe: ar0234 initialization failed
[   31.768502] zedx: probe of 31-0030 failed with error -1
[   31.768786] zedx 31-0010: Driver Version : v1.3.1
[   31.768795] zedx 31-0010: Probing v4l2 sensor.
[   31.769214] zedx 31-0010: tegracam sensor driver:video17_v2.0.6
[   31.855370] zedx 31-0010: Enable gmsl for channel 0 and id 5
[   32.097619] tegra-camrtc-capture-vi tegra-capture-vi: subdev zedx 31-0010 bound
[   32.100244] zedx 31-0010: Detected ZED-X sensor
[   32.100258] zedx 31-0010: zedx_probe: Serial Number : 301236339
[   32.100265] zedx 31-0010: zedx_probe: CHANNEL: 0 ID: 5
[   32.101206] zedx 31-0011: Driver Version : v1.3.1
[   32.101214] zedx 31-0011: Probing v4l2 sensor.
[   32.101526] zedx 31-0011: tegracam sensor driver:video18_v2.0.6
[   32.148131] zedx 31-0011: ZED-X detect error
[   32.148249] zedx 31-0011: zedx_probe: ar0234 initialization failed
[   32.148583] zedx: probe of 31-0011 failed with error -1
[   32.163546] zedxone_uhd 30-001a: tegracam sensor driver:video6_v2.0.6
[   32.164330] zedxone_uhd 30-001a: imx678_probe: imx678 initialization failed
[   32.165261] zedxone_uhd 31-001a: tegracam sensor driver:video19_v2.0.6
[   32.165977] zedxone_uhd 31-001a: imx678_probe: imx678 initialization failed

Aldric · September 25, 2025, 9:06am

Hi,

Can you share the log generated by sudo ZED_Diagnostic --dmesg ?

daiduc · September 25, 2025, 10:12am

Hi @Aldric ,

here are the two logs
dmesg_SDK4.2.5.log (28.9 KB)
dmesg_SDK5.0.7.log (29.9 KB)

Aldric · September 26, 2025, 3:27pm

Thank you, it seems one of your sensor is indeed not working as expected.

Can you share the log generated by the following command:

cd /sys/class/video4linux/video0/zed_info/; grep . * > ~/Desktop/log.txt

daiduc · October 1, 2025, 6:57am

Hi @Aldric sorry for the delay

here are the logs with SDK4 installed.
log.txt (152 Bytes)
log2.txt (152 Bytes)

daiduc · October 1, 2025, 7:15am

And I’ve just checked on another device running SDK5 where it’s not working and the logs look the same.

Aldric · October 3, 2025, 8:16am

Hi,

I attached an updated driver which should fix or help us narrow down the issue you are facing, can you update your current drivers with this one:

sudo cp sl_max9295.ko /usr/lib/modules/$(uname -r)/kernel/drivers/stereolabs/max9295/sl_max9295.ko

sl_max9295.ko (591.8 KB)

daiduc · October 3, 2025, 7:41pm

Hi @Aldric

here is the log for sudo ZED_Diagnostic --dmesg
dmesg.log (30.4 KB)

and the log generated by
cd /sys/class/video4linux/video0/zed_info/; grep . * > ~/Desktop/log.txt
looks the same.

The error remains. Could this be because there is no driver for the bmi088?

bmi08g_init Error [-2] : Communication failure
bmi08g_set_int_config Error [-2] : Communication failure

The folder /usr/lib/modules/5.10.120-tegra/kernel/drivers/imu/bmi088 is empty

daiduc · October 8, 2025, 1:24pm

Hi @Aldric @Myzhar

Is there any news yet? I’m having the same problem when I try to use ROS2 with ZED SDK5 installed. However, when I try to run ROS2 with SDK4, I get a different error.
ros2 launch error.txt (3.0 KB)
I pretty much followed the steps from github for the ros2 wrapper, but I had to install ROS Humble from source.
I really hope you guys can help me out here.

Myzhar · October 8, 2025, 1:28pm

If you change the SDK version, you must clean the workspace (delete the folders install, build, and logs) before rebuilding.

daiduc · October 8, 2025, 2:21pm

Ok I tried doing that and then I’m getting some weird error
output.txt (25.8 KB)

aperidon · October 9, 2025, 10:02am

Hi Daiduc,

In ordrer to assess the issue you encounter with your IMU, I’d need you to run few more commands please :

sudo i2cset -y -f 30 0x42 0x00 0x44 0x76 i
sudo i2cset -y -f 30 0x42 0x00 0x45 0x30 i
sudo i2cset -y -f 31 0x42 0x00 0x44 0x76 i
sudo i2cset -y -f 31 0x42 0x00 0x45 0x30 i

You can share the result afterward with a sudo ZED_Diagnostic --dmesg

Thank you

daiduc · October 9, 2025, 12:00pm

Hi @aperidon ,

here are the results one with SDK4 installed and one with SDK5.

dmesg_SDK4.log (29.4 KB)
dmesg_SDK5.log (30.4 KB)

Hope this helps to find the issue.