Camera not detected on Jetson Xavier AGX

Hardware ZED1
1

I am using Jetson Xavier AGX with Jetpack version 5.1.2 alongside ZED SDK 5.0, but it is not able to detect the camera, even though it is detected by the OS, and there is a stream that can be read by Cheese.
I would like to add that the Camera works fine in a Windows 11 environment and is detected as a 2.0 USB, which rules out hardware fault possibility

user@ubuntu:\~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 2b03:f582 Technologies, Inc. ZED
Bus 001 Device 004: ID 0bda:b728 Realtek Semiconductor Corp. Bluetooth Radio
Bus 001 Device 002: ID 1ea7:0066 SHARKOON Technologies GmbH \[Mediatrack Edge Mini Keyboard\]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
user@ubuntu:\~$ lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=tegra-xusb/4p, 10000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=tegra-xusb/4p, 480M
|\_\_ Port 2: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|\_\_ Port 2: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|\_\_ Port 3: Dev 4, If 0, Class=Wireless, Driver=btusb, 12M
|\_\_ Port 3: Dev 4, If 1, Class=Wireless, Driver=btusb, 12M
|\_\_ Port 4: Dev 5, If 1, Class=Video, Driver=uvcvideo, 480M
|\_\_ Port 4: Dev 5, If 0, Class=Video, Driver=uvcvideo, 480M

ZED Diagnostic results:
ZED_Diagnostic_Results.json (15.7 KB)

Cheese output

d
d812Ă—841 185 KB

2

Hi @ZiadMontaser
You are using an old ZED “first model” that is no longer officially supported by the new SDK versions because we do not test it any longer.

Furthermore, this indicates that the cable of the camera is damaged.

You could try to replace it by following this unofficial teardown guide.

3

What is the last version that the original ZED camera was tested on?

4

Not easy to say. You can test the v4.2.5.

5

Tested v4.2.5, but no luck.
Will try replacing the cable, but I don’t have high hopes for it, as it is already streaming some data.

6

Your camera is detected as a USB 2 device instead of USB 3. Normally, this abnormal behavior is caused by a damaged cable.

7

Updated: Replaced the cable and it successfully got detected as 3.0 usb and ZED sdk was able to recognise it.

1 Like