I captured the correct picture. The error was in Hsync. I changed it to DE.
But I cannot access the camera via nvarguscamerasrc.
#gst-launch-1.0 nvarguscamerasrc sensor_id=0 ! nvoverlaysink
Setting pipeline to PAUSED …
Pipeline is live and does not need PREROLL …
Setting pipeline to PLAYING …
New clock: GstSystemClock
Error generated. /dvs/git/dirty/git-master_linux/multimedia/nvgstreamer/gst-nvarguscamera/gstnvarguscamerasrc.cpp, execute:557 No cameras available
Got EOS from element “pipeline0”.
Execution ended after 0:00:00.188862563
Setting pipeline to PAUSED …
Setting pipeline to READY …
Setting pipeline to NULL …
Freeing pipeline …
thank
Can’t get the motherboard (A02) and Nano (B01) to work. Doesn’t work with my Toshiba. Doesn’t work with Imx219. Gives error TEGRA_CSI_CILX_STATUS 0x00040040 (No data)
I can not understand…
But with the motherboard (A02) and Nano (A02) everything works.
hello djager471,
it’s NOT supported to make motherboard (A02) and Nano (B01) to works. please use same version of each boards.
thanks
But I cannot access the camera via nvarguscamerasrc.
#gst-launch-1.0 nvarguscamerasrc sensor_id=0 ! nvoverlaysink
Setting pipeline to PAUSED …
Pipeline is live and does not need PREROLL …
Setting pipeline to PLAYING …
New clock: GstSystemClock
Error generated. /dvs/git/dirty/git-master_linux/multimedia/nvgstreamer/gst-nvarguscamera/gstnvarguscamerasrc.cpp, execute:557 No cameras available
Got EOS from element “pipeline0”.
Execution ended after 0:00:00.188862563
Setting pipeline to PAUSED …
Setting pipeline to READY …
Setting pipeline to NULL …
Freeing pipeline …
Why doesn’t it work?
thank
Can you help with the question above?
hello djager471,
there’s error report from camera application side that camera device did not available.
execute:557 No cameras available
since you’re able to access the camera stream with v4l2 standard controls.
suggest you should review the port binding and also check the pixel clock settings in the sensor device tree.
you may also have a try to configure to performance mode, which boost VI, NvCsi clocks to have testing,
thanks
Device tree:
tegra210-tc358746_4mode.txt (16.7 KB)
Thanks!
hello djager471,
it seems you had 4 camera device to works with CSI-A/ CSI-C/ CSI-E/ CSI-F.
however, you define all your sensor to serial_a in the sensor definition.
for example,
i2c@546c0000 {
tcCam0@0e {
compatible = "nvidia,tc358746";
mode0 { /*1920x1080_25FPS */
tegra_sinterface = "serial_a";
...
i2c@7000c000 {
tcCam1@0e {
compatible = "nvidia,tc358746";
mode0 { /*1920x1080_25FPS */
tegra_sinterface = "serial_a";
...
i2c@7000c400 {
tcCam2@0e {
compatible = "nvidia,tc358746";
mode0 { //1920x1080_25FPS
tegra_sinterface = "serial_a";
...
i2c@7000c500 {
tcCam3@0e {
compatible = "nvidia,tc358746";
mode0 { //1920x1080_25FPS
tegra_sinterface = "serial_a";
please update your sensor device tree,
you may also having definition of tegra_sinterface assign to CSI-A/ CSI-C/ CSI-E/ CSI-F accordingly.
thanks
Hey.
I fixed it. But I get the same error.
Thank!
hello djager471,
may I know what’s the latest kernel failures from your side, please share logs for reference.
BTW,
is it possible to enable test-pattern-generator of TC358748 to narrow down the issue.
thanks
dmesg.txt (72.3 KB)
I included a test pattern. Everything is working.
hello djager471,
please check those i2c transfer timed out errors, you should solve them if there’re related issue.
you could also have a try to extend the waiting time for the first frame.
please add set_mode_delay_ms property in your sensor device tree, to request a longer delay for the capture engine to prevent timeouts.
you may also refer to Sensor Software Driver Programming Guide for more details.
thanks
