Gstreamer camera not initializing

Hi
Have a set of cameras on a remote controlled machine, which has been working fine until now. I do get an error message when using both v4l2src and nvv4l2camerasrc with the properties they both goes along with.
The problem only occurs on two out of six cameras, with the rest working just fine. Any suggestions? See attached photos for dump of terminal for both of the sources.


Hello @severinss,

Can you try a simplified pipeline ?

gst-launch-1.0 nvarguscamerasrc device=/dev/video4 ! fakesink

and

gst-launch-1.0 v4l2src device=/dev/video4 ! fakesink

This will help us isolate the cameras on the test.
Please let us know how it goes.

regards,
Andrew
Embedded Software Engineer at ProventusNova

The failed camera connect to which CSI port?

Hi @proventusnova

I tried simplifying the pipeline without any luck, by going straight to fakesink.

I got one worker on site to swap the two cameras that didn’t work, and now the machine is up and running again.
Turned out the cameras were defective, however they both showed up in the list of initialized sensors when running dmesg | grep -i "Detected ar0233 sensor". They also got listed when using command ls /dev/video* so thats why I thougt there was a Gstreamer/Nvidia issue. We’ll get the cameras sent back to our office for further investigation, and possibly return them to E-con (STURDeCAM21) for replacement.

@ShaneCCC I’m not so sure about this. We’re using a Syslogic RPC RML A3 computer with built-in deserializer for GMSL2 cameras. So just random ports 1-8. Link: Rugged Computer RPC RML A3 (E2) - Syslogic

Hello @severinss,

Great to hear that you managed to pinpoint the issue.
Those HW issues are always the hardest to debug, great job!

It is hard to know what exactly might be wrong with the camera modules. If you were using regular MIPI cameras, we would be able to deduce that the Jetson was at least able to interact with the sensors via i2c, however, since in this case you are using GMSL2 cameras, its even harder to know if the issue is the serializer or the sensor module itself.

Regardless, we are glad you are now past that problem, please keep us posted if you find something interesting during further testing.

Also, don’t hesitate to reach out if you require further assistance.

regards,
Andrew
Embedded Software Engineer at ProventusNova

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.