AGX ORIN and self-developed boadrd ZED MINI camera

Hardware ZED Mini
1

Hi，I am a novice when it comes to using the ZED camera.
I am currently using an AGX Orin module with a self-developed carrier board. The L4T version is 35.4.1.
I am working on adapting the ZED MINI camera via the GMSL interface and have encountered some issues.
I would appreciate your assistance.

LOG.txt
log.txt (77.9 KB)

When I execute the command python3 hello_zed.py, I didn’t see the SN of the camera.

(upload://kTlWHBpLWG902QduFYQ0YYHFy3d.png)

p1
p11920×1080 293 KB

p2
p21920×1080 301 KB

sudo ZED_Diagnostic --dmesg
dmesg.log (10.3 KB)

2

Hi,
Is there anyone who can help me? What’s the reason for that?

3

If you are creating a driver with a custom board, we would recommend checking if the v4l2 devices are correctly created with this command:

v4l2-ctl -d /dev/video0 --stream-mmap

As we focus on supporting our products and the systems of our partners, we do not have the resources to support all carrier boards that are available.

For this reason we will not be able to assist in the development of a driver for your specific carrier board.

I will leave the post open for other users to help if you are willing to share information on your board / capture card.

Thanks for your understanding.

4

Hi,very glad to see your reply.
v4l2-ctl -d /dev/video0 --stream-mmap

p1
p1546×511 76 KB

And command:
$ v4l2-ctl --stream-mmap --stream-count=1 -d /dev/video0 --set-fmt-video=width=1920,height=1200,pixelformat=UYVY --stream-to=output.yuv

I get output.yuv

1742537797766
17425377977661526×861 237 KB

5

But when I input the command nvgstcapture-1.0 or other, I fail to capture the image.
And when I execute the files in the engineering directory, I still fail to obtain the images from the camera.

6

You should be able to view the video stream with the following command:

gst-launch-1.0 nvarguscamerasrc sensor-id=0 ! nvvidconv ! autovideosink
7

Hi,
Thank you very much for your support.
Yes, I can display the video stream through the command you provided. However, after I installed the SDK package provided by ZED officially, When I used the files in the directory /usr/local/zed/tools, I failed.
I would like to know the reason for this so that I can use the files in the /usr/local/zed/tools directory to open the camera. Is it because of the driver source code, or is there a problem with the device tree configuration?
If I want to use the files in /usr/local/zed/tools to open the camera, how should I modify my source code and device tree file?
Thank you.

8

The ZED SDK package that I installed is:
ZED_SDK_Tegra_L4T35.4_v4.2.5.zstd.run
Thanks.

9

Hi, are you able to detect the cameras when you run ZED_Explorer -a ?

10

Hi, when I run ./ZED_Explorer -a, I get

No ZED detected

And, when I run python3 hello_zed.py in the directory /usr/local/zed/samples/turotials/tutorial 1-hello ZED/python/, I fail to obtain the camera’s SN.
Thanks.

11

It seems you based your custom driver on an old version, do you get the same results on an older SDK version maybe 4.2.2 ?

12

I haven’t found the SDK package of version 4.2.2 on the ZED official website. Could you please provide a link for me to download this package?

13

Sorry 4.2.2 is indeed not available on the website please try this version instead ZED SDK 4.1 - Download | Stereolabs

14

Hi，
I can now use the ZED camera normally. The reason is the difference in SDK versions.
Thank you all very much for your help.

15

HI,
I have a similar issue with SDK 5.0.0 for jetpack 5.1.1.
We are using your ZEDLink mono.
Also, when using gst-launch-1.0 nvarguscamerasrc sensor-id=0 ! nvvidconv ! autovideosink we get the error
(Argus) Error BadParameter: (propagating from src/eglstream/FrameConsumerImpl.cpp, function initialize(), line 89)
and also using your /usr/local/zed/tools/.
We are using ZED_SDK_Tegra_L$T35.3_v5.0.0 as SDK
The camera is not recognized. Can you help us?