I’m trying to move the dtbo and corresponding driver from Jetson 5.1.2, Orin nx to Jetson 6.0, Orin nx, the dtbo seems work normally, I can see /dev/video, and media-ctl command can get a whole link list, Sensor→NVCSI→VI, but when I use the v4l2-ctl to try to receive CSI data, the data is all zero. I confirm that the image size and mode defined in dtbo is same with the last version, but I can’t receive non-zero data, I also use oscilloscope, there is physical signal show on oscilloscope.
I want to know what I can do to check which part is wrong will cause this problem.
*** Please note that this reply is generated by LLM automatically ***
Based on the provided context, I’ll try to help you troubleshoot the issue.
Firstly, it’s great that you’ve confirmed the dtbo and driver are working normally, and you can see the /dev/video device and retrieve the media link list using mediactl. However, the issue arises when trying to receive CSI data using v4l2ctl, which returns all zeros.
To help you identify the problem, let’s break down the possible causes:
Hardware issue: You’ve already checked the physical signal using an oscilloscope, and it shows a signal present on the CSI lines. This suggests that the hardware is likely working correctly.
dtbo configuration: You’ve mentioned that the image size and mode defined in the dtbo are the same as the previous version. However, it’s essential to double-check the dtbo configuration to ensure that it matches the sensor’s capabilities and the desired output format.
Sensor configuration: Verify that the sensor is configured correctly, and its output format matches the expected format defined in the dtbo. You can check the sensor’s datasheet or consult with the sensor manufacturer to confirm its configuration.
nvvidconv and nvv4l2camerasrc: Since you’re using the nvvidconv and nvv4l2camerasrc plugins, ensure that they are configured correctly. Check the output format of nvvidconv and the input format of nvv4l2camerasrc to ensure they match the expected formats.
VIC and CUDA: As you’re using the VIC-based nvvidconv on Jetson, ensure that the VIC engine is configured correctly. Also, verify that the CUDA-based nvvidconv on GPU is not interfering with the VIC-based conversion.
To further troubleshoot the issue, you can try the following:
Use the v4l2-ctl command to check the sensor’s output format and ensure it matches the expected format.
Use the gst-debug-viewer tool to visualize the pipeline and check for any errors or warnings.
Try using a different sensor or camera module to rule out any issues with the current sensor.
Check the kernel logs for any error messages related to the CSI or video capture.
By systematically checking these potential causes and using the suggested troubleshooting tools, you should be able to identify the root cause of the issue and resolve the problem.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
There is no update from you for a period, assuming this is not an issue anymore.
Hence, we are closing this topic. If need further support, please open a new one.
Thanks ~1008