here is my v4l2-ctl command of /dev/video7:
v4l2-ctl --device /dev/video7 --stream-mmap --set-ctrl bypass_mode=0 --stream-count=10
trace log:
trace log.txt (12.5 KB)
I have check out my deser and ser register, it seems work because the gmsl video link is locked.
So pls give me some tips.
Thx
hello jackyzlwu,
according to your tracing logs, there’s no frame related signal received by VI engine.
may I confirm the Jetpack release version you’re working with,
since the latest JP-5 release has address some issue of SerDes chip use-case. is it possible for moving to r35.5.0 for verification.
hi, it’s Jetson Linux 35.3.1 is part of [JetPack 5.1.1] .
So may I need to change Jetpack release to r35.5.0 for working?
Thx
is that mean our SerDes chip driver maybe not trigger frame signal? Or is there have some manuals describes for frame signal trigger mode(like external or internal), which is supported by orin.
Thx
ya, usually, it’s due to frame did not send out correctly.
Hi, Jerry
I have checkout the r35.5.0 SerDes chip use-case about max96712,but i have some question about pipe usage in ORIN:
here,
in hawk_owl_mode_tbls.h.
Is that mean streaming issues with max96712 maybe in ORIN ,so I need to copy these Desdes register configure to avoiding pipe issues.
Thx
hello jackyzlwu,
CSI/VI it’s a receiver for waiting sensor’s MIPI signaling, so, you must confirm there’re
signaling on the CSI channel, and effective frame packets (SoF,EoF…etc) for VI engine.
that code snippets shows the configuration on driver side, and… it’s part of Deser/ser programming as you can see in the ar0234_probe().
I’m not sure whether you’re using the exactly same hardware, please check the SerDes spec to ensure those settings are necessary for your use-case.
OK. Could you please offer some specific methods to check signaling on the CSI channel and effective frame packets in VI?
Thx
hello jackyzlwu,
this can be done by probing the MIPI signaling via oscilloscope.
you should see high-speed signaling which indicate sensor frames.
please follow below steps to enable VI tracing logs.
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
cat /sys/kernel/debug/tracing/trace
there should be lot of logs has reported,
the most important logs you may dig into are a pair of CHANSEL_PXL_SOF (start-of-frame) and CHANSEL_PXL_EOF (end-of-frame), which indicate one effective frame for VI engine.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.