Hi,
I would like to access GMSL camera LI-AR0231-GMSL2-CFM-176H-010 that connected to GMSL1 connector on Navigation Mezzanine.
I could access main camera and tracking camera using your sample code:
sample-apps-for-Qualcomm-Robotics-RB5-platform/Gstreamer-Applications/gst_camera/ispcam_display
Could you show me how to access GMSL camera using/modifying ispcam_display code?
Thanks,
hs
Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.
I'll look into this. Are you using LE or LU?
I am using LU.
Thanks,
I am trying to aquire a compatible GMSL camera module, I don't have it on site.
I believe the command camx-hal3-test is accessible through adb shell.
If you run this command I believe you should see more "cameras" that what you have connected. So if you disconnected all other cameras I believe it will still display cameras which I believe are the GMSL camera drivers. camx-hal3-test always list cameras starting from 0 so the camera number is not necessarily the true camera number used in gstreamer.
The GMSL camera looks like it is YUV 1920x1080 fps 28.5 if I recall correctly.
The ISP camera program is just trying to connect to "camera" using gstreamer without position. I believe you will have to modify the gstreamer command to access a specific camera position. Also change the gstreamer camera video parameters to match the properties of the GMSL camera.
Then you can try to stream from it. I believe the GMSL will be cameras 4 or 5 (there are 7 camera positions on an RB5). See if you can get it to talk. Or you can try using camx-hal3-test to pass configuration to the cameras enumerated by the command and see if you can get the camera to talk using the test command.
I tried camx-hal3-test, it shows Camera 0 to 3.
I tried to add id=4 and 5 using
A:id=4,psize=1920x1080
Then camx-hal3.test was crashed.
-----------------------------------------------------------
I tried to use gstreamer but it also does not work.
qtiqmmfsrc camera=0 and 1 worked fine for main camera and tracking camera.
With hal3_test, the gmsl camera would be one of the cameras 0-3. Hal3_test generates camera number independent of the system numbers.
With gstreamers you can enable debug output GST_DEBUG= set it to the logging level you want.
If you collect kernel logs with only the GMSL camera connected I can look into the log and see what is happening.
hal3-test crashes on lots of things. If you fail to release the last camera before starting a new camera it will crash. If you can run hal3-test and don't crash but don't get any results it's possible that the parameters for the camera are incorrect. It's easiest to look at both the ADB and /dev/kmsg logs to see what is happening.
Assuming that you don't crash the command by attaching to two cameras at the same time. The command with take the parameters and then talk to the system and try to find a matching mode exposed by the camera driver. If you pass incorrect parameters its possible that it simply silently fail without notification.
If hal3-test crashes or if gstreamer crashes I recommend rebooting as the crash may have included parts of the camera system which may not recover fully.
Be careful when checking the output voltage on GMSL you can short and damage the chip.
gstreamer while hard to configure can also be helpful in that you can set the GST_DEBUG parameter to 1/2/3 and get a ton of information then filter through that and find the point of failure.
I'll try to pull the driver code and see if I can find the correct sensor parameters. Camera commands tend to be very sensitive to the parameters that are passed and can be inconsistent in response depending on the point of failure.
Hi jlowman,
Thanks.
I tried to watch /dev/kmsg during test. Please see below. I rebooted before every try.
I also have /dev/kmsg dump between cam-hal3-test and its prompt. But it is pretty long, so I did not put it here.
It looks camera rejects or ignored i2c requests.
Are there any way to identify "id" for camera on "GMSL1" connector ?
TRY 1
The i2 errors most likely indicate that the system is trying to configure the camera but there is no camera present on that connection or that the system can't talk to the camera.
The i2 errors most likely indicate that the system is trying to configure the camera but there is no camera present on that connection or that the system can't talk to the camera.
Hi,
Does it mean current LU firmware for RB5 does not support LI-AR0231-GMSL2-CFM-176H-010 ?
Hi HS,
have you finally make this GMSL camera work with RB5? I'm looking now some options to connect cameras to Vizion mezzanine .
Regards, Max.
Hi Max,
No luck. I tried to dig into lower level source code but all lower level camera access code is closed source. I just found binary only.
I guess my camera is broken.
I couldn't find a way to determine if the camera was dead or alive.
Please let me know if your camera worked with RB5.
Thanks,