*** Please note that this reply is generated by LLM automatically ***
The error message you’re encountering, [ 1610.751831] tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 64, suggests that there’s an issue with the camera capture on your Tegra-based system, likely related to the nvarguscamerasrc component or the camera interface itself. This error is often associated with problems in capturing frames from the camera, where the system is discarding frames due to some error condition.
Given that you’re using VLC in the graphical interface to display videos and encountering this error, it’s possible that the issue lies in the interaction between VLC, the camera capture component (nvarguscamerasrc), and the underlying Tegra-based system. Here are a few potential explanations and solutions:
Camera Compatibility: Ensure that your camera is compatible with the nvarguscamerasrc component and the Tegra-based system. The context mentions specific camera modules like IMX290 and IMX477, which are supported. If you’re using a different camera, check if it’s listed under Supported Cameras.
EGLDisplay Permissions: The error might also be related to permissions or capabilities issues with the EGLDisplay API handle. Ensure that your application has the necessary permissions to modify output attributes. If the application or operating system revokes these permissions, it could lead to undefined behavior, including errors like the one you’re seeing.
Bug Fix for Tegra-Based Systems: Since the error is specific to Tegra-based systems, applying the latest bug fixes, especially those related to camera capture and video processing, might resolve the issue. Ensure you’re running the latest version of JetPack (in this case, JetPack 6.0) and that your system is updated with the latest patches.
Modifying embedded_metadata_height: The fact that modifying the embedded_metadata_height value has no effect suggests that the issue might not be directly related to the metadata settings but rather to the underlying capture process or system configuration.
Comparison with Other Capture Tools: Try using other camera capture tools like NvGstCapture to see if the issue persists. This can help isolate whether the problem is specific to VLC and its interaction with the camera capture component or if it’s a more general issue with the camera interface on your Tegra-based system.
CSI Cameras and Interface: Since the error involves tegra-camrtc-capture-vi, which is related to the CSI (Camera Serial Interface) camera standard, ensure that your camera is properly connected and configured according to the CSI standard. Also, verify that the nvarguscamerasrc component is correctly configured to work with CSI cameras.
To troubleshoot further, you might need to provide more details about your setup, including the specific camera model, how VLC is configured, and any recent changes to your system or software.
jetpack 5.1.4
gmsl （max96712+max9295，gmsl2 6G modemodule camera sensor：OX08B40
Use Command
v4l2-ctl --stream-mmap -d /dev/video0
as well as
gst-launch-1.0 -v v4l2src device=“/dev/video0” ! video/x-raw,framerate=30/1,width=3840,height=2160,format=UYVY ! autovideosink
There will also be similar issues
let’s try specify the sensor supported format into v4l pipeline for testing.
for instance, you may check.. v4l2-ctl -d /dev/video0 --list-formats-ext.
after that, please update below with your sensor supported formats to test sensor stream. $ v4l2-ctl -d /dev/video0 --set-fmt-video=width=1920,height=1080,pixelformat=RG10 --set-ctrl bypass_mode=0 --stream-mmap --stream-count=100
I doubt why the frame number has keeping at 0 from your messages.
since this is a SerDes chip, could you please double check it’s sending out the frame packets onto CSI channel correctly?
may I know what’s the modification you’ve tried?
please see-also Individual Imaging Devices, there’s device tree property, embedded_metadata_height to configure it as well.
