Thank you, that solved the problem.
It would be helpful if you could update that in point 3.45 on the site: http://wiki.veye.cc/index.php/CS-MIPI-X_i2c
is it possible to change the YUV-sequence of the CSSC132?
Using the given command ./veye_mipi_i2c.sh -w -f yuvseq I get the correct value "YUYV" reading it out in the command line, but the output is still in "UYVY" sequence.
Why isn't it a cs_mipi_i2c.sh command?
I am struggling with the software trigger of the CSSC132 camera on the AGX Xavier and how to use it.
I am taking the following steps:
But I can not get an image out of the camera. What steps do I have to do to get a picture using the software trigger?
I know that the camera works as in free running mode I get a video stream using gstreamer.
The problem was a wrong assumption of the camera that I am using. After adjusting the dtb-file of the correct camera the camera gets detected properly.
I am using the CS-MIPI-IMX-307 and installed the kernel image and the device tree on a Xavier NX according to step 3.5 from the wiki:
but when I checked the result from the command "dmesg | grep csx307" I get the following:
csx307 9-003b: probing v4l2 sensor
csx307 9-003b: tegracam sensor driver:csx307_v2.0.6
csx307 9-003b: read sensor id 0132
csx307 9-003b: cs_imx307_board_setup: invalid sensor model id: 306
csx307 9-003b: board setup failed
csx307 10-003b: probing v4l2 sensor
csx307 10-003b: tegracam sensor driver:csx307_v2.0.6
csx307 10-003b: read sensor id 0132
csx307 10-003b: cs_imx307_board_setup: invalid sensor model id: 306
csx307 10-003b: board setup failed
why did it fail? What is the problem with the invalid sensor model id?