R35.3.1 AGX orin bring up ar0820 raw sensor,and capture frame will get stuck

i bring up the sensor ar0820,and then execute this command
“v4l2-ctl -d /dev/video0 --set-ctrl bypass_mode=0 --stream-mmap --stream-count=100”, Polling execution 100 times,will get stuck。
upload the log。
ar0820-trace.log (703.3 KB)
the kernel log


Ca you please enable the V4L2 debug trace and share the information?
You can enable trace to debug the capture process by running the following commands:

sudo su
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 > /sys/kernel/debug/tracing/trace

The trace will give information about VI/CSI.

In order to read the output messages, run:
sudo cat /sys/kernel/debug/tracing/trace


JDiego Delgado
Embedded SW Engineer at RidgeRun
Contact us: support@ridgerun.com
Developers wiki: https://developer.ridgerun.c om/
Website: www.ridgerun.com

ar0820-trace.log (260.0 KB)

upload log

My tests found that the following changes caused the card to die,

the error log

sometime there would have been problems without those modifications
See the attachment for log
ar0820-trace-1.log (11.3 MB)

Does your sensor connect with gmsl or ser/deser chip.
Looks like the output frame have include virtual channel ID =1 cause the problem.

     kworker/7:3-532     [007] ....   321.042584: rtcpu_vinotify_error: tstamp:10905078368 cch:0 vi:0 tag:CHANSEL_NOMATCH channel:0x41 frame:0 vi_tstamp:348962381408 data:0x0000000000000589

we use ser/deser chip, max9295 and max9296.
Looks like the output frame have include virtual channel ID =1 cause the problem.---->How can this problem be fixed。

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