ZEDX Zedlink Quad Driver

Software
1

Hello everyone,

I am trying to install Quad card driver on AGX Orin DevKit with Jetpack 6.0 (36.3) for my ZEDX Cameras. However while I am installing I have the error

****@****-desktop:~/****/zedx$ sudo dpkg -i stereolabs-zedlink-quad_1.2.0-SL-MAX96712--L4T36.3.0_arm64.deb
Selecting previously unselected package stereolabs-zedlink-quad.
(Reading database ... 229799 files and directories currently installed.)
Preparing to unpack stereolabs-zedlink-quad_1.2.0-SL-MAX96712--L4T36.3.0_arm64.deb ...
Unpacking stereolabs-zedlink-quad (1.2.0-SL-MAX96712--L4T36.3.0) ...
Setting up stereolabs-zedlink-quad (1.2.0-SL-MAX96712--L4T36.3.0) ...
Detected DTB to update : tegra234-p3737
Detected capture card : zedlink-quad
Set FDT to : /boot/dtb/kernel_tegra234-p3737-0000+p3701-0005-nv.dtb
Failed to look up unit file state: Is a directory

and it fails. I couldn’t find a solution. I would be extremely grateful if I could some help.

Thanks!

2

Hi @ba2sakal
Welcome to the Stereolabs community.

This is a rare problem not easily reproducible and appears randomly on some devkits.

You can solve it by following this procedure:

  1. sudo rm -r /etc/systemd/system/zed_x_daemon.service/
  2. Extract files from .deb
  3. In the resulting directory, extract files from data.tar.xz
  4. sudo cp data/tmp/zed_x_daemon.service /etc/systemd/system/
  5. sudo systemctl enable zed_x_daemon.service
  6. sudo systemctl restart zed_x_daemon.service
1 Like
3

Hello @Myzhar

Thank you for your help. It seems the error was because I built and ran the docker image and since it had flag

volume"/etc/systemd/system/zed_x_daemon.service:/etc/systemd/system/zed_x_daemon.service" \

it created a directory and since it was a directory the script gave error. After I deleted the dir and reinstalled the .deb it worked fine.

However, now I am having problem with accesing my ZEDX cameras. I am directly using the SDK on host to eliminate problems regarding docker.

It detecst the camera but it has problem with its initilization and the problem with EEPORM.

[ 7804.920856] sl_max96712 13-0029: sl_max96712_get_camera_model: zedx camera connected to this port
[ 7804.938424] sl_max96712 13-0029: print_sensor_info: camera zedx
[ 7805.426681] sl_max9295 9-0062: probe_serializer: Serializer for zedx detect error
[ 7805.829643] sl_max9295 13-0062: probe_serializer: Serializer for zedx detect success
[ 7806.026048] zedx 9-0010: Driver Version : v1.2.1
[ 7806.026212] zedx 9-0010: tegracam sensor driver:video10_v2.0.6
[ 7806.075208] zedx 9-0010: ZED-X detect error
[ 7806.075246] zedx 9-0010: zedx_probe: ar0234 initialization failed
[ 7806.075293] zedx: probe of 9-0010 failed with error -1
[ 7806.127160] zedx 9-0028: tegracam sensor driver:video8_v2.0.6
[ 7806.175224] zedx 9-0028: ZED-X detect error
[ 7806.175286] zedx: probe of 9-0028 failed with error -1
[ 7806.375244] zedx 13-0010: tegracam sensor driver:video4_v2.0.6
[ 7806.375062] zedx 13-0010: ZED-X detect error
[ 7806.375094] zedx: probe of 13-0010 failed with error -1
[ 7806.489001] zedx 13-0020: zedx_probe: Serial Number : 42975465
[ 7806.493034] zedx 13-0020: zedx_open: Accessing the camera
[ 7806.577692] i2c i2c-13: Failed to register i2c client eeprom_zedx at 0x54 (-16)
[ 7806.577709] zedx 13-0028: zedx_eeprom_device_init: Failed to probe EEPORM at addr = 0x54
[ 7806.577717] zedx 13-0028: Failed to allocate eeprom reg map: -19
[ 7806.586063] zedx 13-0028: Detected ZED-X sensor
[ 7806.586069] zedx 13-0028: zedx_probe: Serial Number : 42975465
[ 7806.634553] zedx 14-0010: ZED-X detect error
[ 7806.634579] zedx 14-0010: zedx_probe: ar0234 initialization failed
[ 7806.694632] zedx 14-0020: ZED-X detect error
[ 7806.694671] zedx 14-0020: zedx_probe: ar0234 initialization failed
[ 7806.750701] zedx 14-0028: ZED-X detect error
[ 7806.750732] zedx 14-0028: zedx_probe: ar0234 initialization failed

To give more info I bought the Jetson Orin AGX from Stereolabs so it shouldn’t be problem with the model or internal configuration, I assume.

I haven’t been able to solve the problem. I would grateful for some help!
Thanks!

4

Hi @ba2sakal
you can ignore the warnings in the log file because they refer to ports where no camera is connected.

You’re ZED X is correctly detected and initialized:

[ 7806.586063] zedx 13-0028: Detected ZED-X sensor
[ 7806.586069] zedx 13-0028: zedx_probe: Serial Number : 42975465

Can you open the stream by using ZED Explorer?
What’s the output of the command ZED_Explroer -a?

5

Hello @Myzhar,

Yes indeed, the camera is initialized successfully.

The problem was the ZED_Explorer doesn’t work with SSH X11 Forwarding. It gives resolution error as I understand. When I connected a screen to Jetson, it worked without problem. Also, I found out that I need to launch it with sudo or as a root user from docker.

Do you have a suggestion how can I use the tools through ssh from a remote PC?

Thanks a lot for your fast responses!

6

We added a support page just yesterday to explain this issue in detail and provide a working solution:

1 Like
7

Thanks a lot for the explanation!

1 Like