R35.3.1 jetson orin bring up yuv sensor，failed to capture the frame rate

[mingming]

hi：
the yuv sensor is 640*512 50@fps，now the soc can not get frame rate，
upload the trace log，please check issue，thanks！
trace.log (421.3 KB)

[carolyuu]

Hi,

For the camera basic functionality first needs to check the device and driver configuration.
You can reference to below program guide for the detailed information of device tree and driver implementation.
https://docs.nvidia.com/jetson/archives/r36.3/DeveloperGuide/SD/CameraDevelopment/SensorSoftwareDriverProgramming.html?highlight=programing#sensor-software-driver-programming

Please refer to Applications Using V4L2 IOCTL Directly by using V4L2 IOCTL to verify basic camera functionality.
https://docs.nvidia.com/jetson/archives/r36.3/DeveloperGuide/SD/CameraDevelopment/SensorSoftwareDriverProgramming.html?highlight=programing#to-run-a-v4l2-ctl-test

Once confirm the configure and still failed below link help to get log and some information and some tips for debug.
https://elinux.org/Jetson/l4t/Camera_BringUp#Steps_to_enable_more_debug_messages

Thanks!

[mingming]

hi：
the log use command：
“echo 1 > /sys/kernel/debug/tracing/tracing_on
echo 30720 > /sys/kernel/debug/tracing/buffer_size_kb
echo 1 > /sys/kernel/debug/tracing/events/tegra_rtcpu/enable
echo 1 > /sys/kernel/debug/tracing/events/freertos/enable
echo 2 > /sys/kernel/debug/camrtc/log-level
echo 1 > /sys/kernel/debug/tracing/events/camera_common/enable
echo > /sys/kernel/debug/tracing/trace
cat /sys/kernel/debug/tracing/trace
”
please see the log，thanks

[JerryChang]

hello mingming,

although sensor it putting stream-on, there’s no frames recognized by camera software stack.
for instance,

    v4l2src0:src-2670    [005] ....  1379.161156: csi_s_stream: enable : 0x1
    v4l2src0:src-2670    [005] ....  1379.162039: tegra_channel_set_stream: sgx-yuv-gmsl2 31-002b : 0x1
 vi-output, sgx--2673    [003] ....  1381.827798: tegra_channel_capture_setup: vnc_id 0 W 640 H 512 fmt 13

may I know what’s your test pipeline?
please also examine the sensor supported formats, $ v4l2-ctl -d /dev/video0 --list-formats-ext
see-also developer guide, Applications Using V4L2 IOCTL Directly by using V4L2 IOCTL to verify basic camera functionality, and also, Debugging Tips section for troubleshooting.

[mingming]

hi:
may I know what’s your test pipeline? ----》 I don’t really understand
gst-launch-1.0 v4l2src device=/dev/video0 ! xvimagesink -ev
Setting pipeline to PAUSED …
Pipeline is live and does not need PREROLL …
Setting pipeline to PLAYING …
New clock: GstSystemClock
/GstPipeline:pipeline0/GstV4l2Src:v4l2src0.GstPad:src: caps = video/x-raw, format=(string)UYVY, width=(int)640, height=(int)512, framerate=(fraction)50/1, colorimetry=(string)2:4:7:1, interlace-mode=(string)progressive
/GstPipeline:pipeline0/GstXvImageSink:xvimagesink0.GstPad:sink: caps = video/x-raw, format=(string)UYVY, width=(int)640, height=(int)512, framerate=(fraction)50/1, colorimetry=(string)2:4:7:1, interlace-mode=(string)progressive

[mingming]

hi：
the sensor bring up ok，the max9295 reg is not configured properly，
this log ok
v4l2src0:src-2633 [006] … 393.381128: camera_common_s_power: status : 0x1
v4l2src0:src-2633 [000] … 393.382724: tegra_channel_set_power: 13e40000.host1x:nvcsi@15a00000- : 0x1
v4l2src0:src-2633 [000] … 393.382732: csi_s_power: enable : 0x1
v4l2src0:src-2633 [000] … 393.383917: tegra_channel_capture_setup: vnc_id 0 W 640 H 512 fmt 13
v4l2src0:src-2633 [000] … 393.385014: tegra_channel_set_stream: enable : 0x1
v4l2src0:src-2633 [001] … 393.400948: tegra_channel_set_stream: 13e40000.host1x:nvcsi@15a00000- : 0x1
v4l2src0:src-2633 [001] … 393.400951: csi_s_stream: enable : 0x1
v4l2src0:src-2633 [001] … 393.401051: tegra_channel_set_stream: sgx-yuv-gmsl2 30-002b : 0x1
kworker/5:2-152 [005] … 393.401268: rtcpu_vinotify_event: tstamp:13149959859 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 f
rame:0 vi_tstamp:420797990560 data:0x399d580010000000
kworker/5:2-152 [005] … 393.401270: rtcpu_vinotify_event: tstamp:13149960077 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 f
rame:0 vi_tstamp:420797997088 data:0x0000000031000001
kworker/5:2-152 [005] … 393.401270: rtcpu_vinotify_event: tstamp:13149960336 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 f
rame:0 vi_tstamp:420798057856 data:0x399d550010000000
kworker/5:2-152 [005] … 393.401271: rtcpu_vinotify_event: tstamp:13149960549 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 f
rame:0 vi_tstamp:420798064448 data:0x0000000031000002

[JerryChang]

hello mingming,

this is your test pipeline

@mingming

gst-launch-1.0 v4l2src device=/dev/video0 ! xvimagesink -ev

please test with V4L2 IOCTL by given supported formats to verify basic camera functionality,
for instance,
$ v4l2-ctl -d /dev/video0 --set-fmt-video=width=3840,height=2160,pixelformat=UYVY --set-ctrl bypass_mode=0 --stream-mmap --stream-count=100

[mingming]

hi：
v4l2-ctl -d /dev/video0 --set-fmt-video=width=640,height=512,pixelformat=UYVY --set-ctrl bypass_mode=0 --stream-mmap --stream-count=100
test ok，thanks

[JerryChang]

hello mingming,

all right, it looks that your sensor is able to stream via v4l2 IOCTL.
the failure should be gst pipeline setting issues, let’s adding some sensor supported formats to gst pipeline for verification,
for instance,
$ gst-launch-1.0 -e v4l2src device=/dev/video0 num-buffers=300 ! 'video/x-raw, width=640, height=512, framerate=50/1, format=UYVY' ! fpsdisplaysink text-overlay=0 name=sink_0 video-sink=fakesink sync=0 -v