R35.4.1 jetson orin bring up raw8 sensor,failed to capture the frame rate

hi:
i bring up the raw8 sensor,1024*768 30fps,then v4l2-ctl -d /dev/video0 -V --set-ctrl bypass_mode=0 --stream-mmap --stream-count=100. I didn’t get the frame rate,
the trace log upload,please check the log,thanks.
trace.log (339.0 KB)


the kernel log
[20798.721707] tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 131072
[20798.755026] tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 131072
[20798.788229] tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 131072
[20798.821534] tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 131072

hello mingming,

even though there’re FS/FE in the VI tracing logs, there’s no CHANSEL_PXL_SOF/ CHANSEL_PXL_EOF to indicate a good frame received by VI engine.
besides, CHANSEL_NOMATCH is outputting with 0x549, is your Raw8 as RGB888? if yes, the data-type should be 0x489

hi:
raw8: data type: 0x2a
now i can get frame rate,bug the kernel log have a log error
tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 131072,
upload the log,please check log,thanks
trace-1.log (961.1 KB)

hello mingming,

may I confirm what’s the frame-rate reported below v4l2 pipeline? is it as same as your sensor capability?
$ v4l2-ctl -d /dev/video0 --set-ctrl bypass_mode=0 --stream-mmap --stream-count=100

hi:
is it as same as your sensor capability?—》yes,the sensor set frame-rate 30fps,soc get 29.46fps

hello mingming,

discarding frame logs it’s sometime a warning messages, due to unsuccess capture state, it’s dropping frames and issue a requeue for new buffers.
since it looks okay by checking reported frame-rate, could you please setup a terminal for gather logs, i.e.$ dmesg --follow

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.