Done, here is the log:
trace-gst-wait-boost.log (4.9 MB)
CHANSEL_SHORT_FRAME and looks like lost the FE of frame 2.
kworker/5:0-3622 [005] .... 6071.613471: rtcpu_vinotify_error: tstamp:190277126363 cch:2 vi:0 tag:CSIMUX_FRAME channel:0x01 frame:2 vi_tstamp:6088867943552 data:0x00000003000000a0
kworker/5:0-3622 [005] .... 6071.613471: rtcpu_vinotify_event: tstamp:190277130488 cch:2 vi:0 tag:CSIMUX_FRAME channel:0x01 frame:2 vi_tstamp:6088867943552 data:0x00000003000000a0
kworker/5:0-3622 [005] .... 6071.613471: rtcpu_vinotify_event: tstamp:190277130742 cch:2 vi:0 tag:CHANSEL_SHORT_FRAME channel:0x41 frame:2 vi_tstamp:6088867943552 data:0x001c000001000400
kworker/5:0-3622 [005] .... 6071.613472: rtcpu_vinotify_event: tstamp:190277442438 cch:2 vi:0 tag:VIFALC_ACTIONLST channel:0x0a frame:2 vi_tstamp:6088867959136 data:0x0000000001020001
kworker/5:0-3622 [005] .... 6071.613472: rtcpu_vinotify_event: tstamp:190277442690 cch:2 vi:0 tag:FS channel:0x01 frame:3 vi_tstamp:6088867943552 data:0x0000000300000010
kworker/5:0-3622 [005] .... 6071.613472: rtcpu_vinotify_event: tstamp:190277442982 cch:2 vi:0 tag:ATOMP_FE channel:0x00 frame:2 vi_tstamp:6088867943584 data:0x0000000000000400
kworker/5:0-3622 [005] .... 6071.613472: rtcpu_vinotify_event: tstamp:190277443232 cch:2 vi:0 tag:ATOMP_FS channel:0x00 frame:3 vi_tstamp:6088867943584 data:0x0000000000000400
kworker/5:0-3622 [005] .... 6071.613472: rtcpu_vinotify_event: tstamp:190277443513 cch:2 vi:0 tag:CHANSEL_EMBED_SOF channel:0x0a frame:3 vi_tstamp:6088867981536 data:0x0000000000000004
kworker/5:0-3622 [005] .... 6071.613472: rtcpu_vinotify_event: tstamp:190277443757 cch:2 vi:0 tag:CHANSEL_EMBED_EOF channel:0x0a frame:3 vi_tstamp:6088867987232 data:0x0000000000000008
kworker/5:0-3622 [005] .... 6071.613473: rtcpu_vinotify_event: tstamp:190277444032 cch:2 vi:0 tag:ATOMP_EMB_DATA_DONE channel:0x0a frame:3 vi_tstamp:6088867988064 data:0x0000000000000000
kworker/5:0-3622 [005] .... 6071.613473: rtcpu_vinotify_event: tstamp:190277444278 cch:2 vi:0 tag:VIFALC_ACTIONLST channel:0x0a frame:3 vi_tstamp:6088868004928 data:0x0000000003020002
kworker/5:0-3622 [005] .... 6071.613473: rtcpu_vinotify_event: tstamp:190277444553 cch:2 vi:0 tag:CHANSEL_NOMATCH channel:0x41 frame:3 vi_tstamp:6088868013536 data:0x00000000000006e9
kworker/5:0-3622 [005] .... 6071.613473: rtcpu_vinotify_event: tstamp:190277444798 cch:2 vi:0 tag:VIFALC_TDSTATE channel:0x0a frame:0 vi_tstamp:6088868171424 data:0x759cc20010000000
kworker/5:0-3622 [005] .... 6071.613473: rtcpu_vinotify_event: tstamp:190277445069 cch:2 vi:0 tag:VIFALC_TDSTATE channel:0x0a frame:0 vi_tstamp:6088868181440 data:0x0000000031000003
kworker/5:0-3622 [005] .... 6071.613474: rtcpu_vinotify_event: tstamp:190277445309 cch:2 vi:0 tag:CHANSEL_PXL_SOF channel:0x0a frame:3 vi_tstamp:6088868653536 data:0x0000000000000001
Any idea why CHANSEL_SHORT_FRAME only shows up, when using nvarguscamerasrc? I don’t see this error in the v4l2-ctl trace log.
It’s could be the sensor control function incorrect setting cause it.
You may modify those function as dummy function to verify it.
Thanks
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.