How to understand the tegra-vi-capture error codes 160

Hi, Nvidia teams, I use JetPack 5.1.2 on Orin ,4 sensing SG1-OX01F10C-GMSL cameras module connected to port index=0 4x1 lanes (vc0~vc3); At present, VC1~VC3 are displaying normally without any issues. VC0 can only display one frame at a time when opened, with a prompt:
[138.193323] tega camrtc capture vi tega capture vi: uncorr_err: flags 2, err_data 0
[140.764857] tega camrtc capture vi tega capture vi: uncorr_err: request timed out after 2500 ms
[140.765161] tegra camrtc capture vi tegra capture vi: errrec: attacking to reset the capture channel
[140.766497] (NULL device *): vi_capture_control_message: NULL VI channel received
[140.766723] t194 nvcsi 13e40000. host1x: nvcsi@15a00000 : csi5_stream close: Error in closing stream_id=0, csi_port=0
[140.767012] (NULL device *): vi_capture_control_message: NULL VI channel received
[140.767224] t194 nvcsi 13e40000. host1x: nvcsi@15a00000 : csi5_stream open: VI channel not found for stream -0 VC -0
[140.769878] tega camrtc capture vi tega capture vi: errrec: successfully reset the capture channel
[140.826248] tega camrtc capture vi tega capture vi: corr_err: discarding frame 0, flags: 0, err_data 160
[140.859549] tega camrtc capture vi tega capture vi: corr_err: discarding frame 0, flags: 0, err_data 160
[140.892875] tega camrtc capture vi tega capture vi: corr_err: discarding frame 0, flags: 0, err_data 160
[140.926197] tega camrtc capture vi tega capture vi: corr_err: discarding frame 0, flags: 0, err_data 160

Camera trace log:
kworker/3:4-101 [003] … 99.208823: rtcpu_string: tstamp:3698145559 id:0x04010000 str:“tegra_nvcsi_stream_set_config(vm0, stream=0, csi”
kworker/3:4-101 [003] … 99.208826: rtcpu_string: tstamp:3698145661 id:0x04010000 str:"=0)
"
kworker/3:4-101 [003] … 99.208834: rtcpu_string: tstamp:3698146031 id:0x04010000 str:“MIPI clock = 297000 kHz, tHS-SETTLE = 0, tCLK-SE”
kworker/3:4-101 [003] … 99.208835: rtcpu_string: tstamp:3698146133 id:0x04010000 str:“TTLE = 0
"
kworker/3:4-101 [003] … 99.208837: rtcpu_string: tstamp:3698146344 id:0x04010000 str:”===== NVCSI Stream Configuration =====
"
kworker/3:4-101 [003] … 99.208838: rtcpu_string: tstamp:3698146588 id:0x04010000 str:"stream_id: PP 0, csi_port: PORT A
"
kworker/3:4-101 [003] … 99.208840: rtcpu_string: tstamp:3698146841 id:0x04010000 str:"Brick: PHY 0, Mode: D-PHY
"
kworker/3:4-101 [003] … 99.208842: rtcpu_string: tstamp:3698147124 id:0x04010000 str:"Partition: CIL A, LP bypass: Enabled, Lanes: 4
"
kworker/3:4-101 [003] … 99.208845: rtcpu_string: tstamp:3698147303 id:0x04010000 str:"Clock information:
"
kworker/3:4-101 [003] … 99.208847: rtcpu_string: tstamp:3698147601 id:0x04010000 str:"MIPI clock rate: 297.00 MHz
"
kworker/3:4-101 [003] … 99.208849: rtcpu_string: tstamp:3698147846 id:0x04010000 str:“T_HS settle: 0, T_CLK settle: 0
"
kworker/3:4-101 [003] … 99.208851: rtcpu_string: tstamp:3698148070 id:0x04010000 str:”======================================
"
kworker/3:4-101 [003] … 99.208853: rtcpu_string: tstamp:3698149910 id:0x04010000 str:"tegra_nvcsi_stream_open(vm0, stream=0, csi=0)
"
kworker/3:4-101 [003] … 99.208855: rtcpu_string: tstamp:3698150515 id:0x04010000 str:“nvcsi_reset_data_lanes: NVCSI_PHY_0_NVCSI_CIL_A_”
kworker/3:4-101 [003] … 99.208856: rtcpu_string: tstamp:3698150617 id:0x04010000 str:"SW_RESET_0 = 00000003
"
kworker/3:4-101 [003] … 99.208858: rtcpu_string: tstamp:3698150979 id:0x04010000 str:“nvcsi_reset_data_lanes: NVCSI_PHY_0_NVCSI_CIL_B_”
kworker/3:4-101 [003] … 99.208858: rtcpu_string: tstamp:3698151081 id:0x04010000 str:"SW_RESET_0 = 00000003
"
kworker/3:4-101 [003] … 99.208860: rtcpu_string: tstamp:3698151771 id:0x04010000 str:“nvcsi_reset_lane_merger: NVCSI_PHY_0_LM_SW_RESET”
kworker/3:4-101 [003] … 99.208861: rtcpu_string: tstamp:3698151871 id:0x04010000 str:“0 = 00000001
"
kworker/3:4-101 [003] … 99.208863: rtcpu_string: tstamp:3698157899 id:0x04010000 str:“nvcsi_reset_lane_merger: NVCSI_PHY_0_LM_SW_RESET”
kworker/3:4-101 [003] … 99.208864: rtcpu_string: tstamp:3698158002 id:0x04010000 str:“0 = 00000000
"
kworker/3:4-101 [003] … 99.208866: rtcpu_string: tstamp:3698158594 id:0x04010000 str:"nvcsi_calc_ths_settle ths_settle 67
"
kworker/3:4-101 [003] … 99.208868: rtcpu_string: tstamp:3698158860 id:0x04010000 str:"nvcsi_calc_ths_settle ths_settle 67
"
kworker/3:4-101 [003] … 99.208870: rtcpu_string: tstamp:3698161114 id:0x04010000 str:"nvcsi_calc_ths_settle ths_settle 67
"
kworker/3:4-101 [003] … 99.208872: rtcpu_string: tstamp:3698161377 id:0x04010000 str:"nvcsi_calc_tclk_settle tclk_settle 75
"
kworker/3:4-101 [003] … 99.208874: rtcpu_string: tstamp:3698161833 id:0x04010000 str:"nvcsi_reset_data_lanes: NVCSI_PHY_0_NVCSI_CIL_A

kworker/3:4-101 [003] … 99.208874: rtcpu_string: tstamp:3698161938 id:0x04010000 str:"SW_RESET_0 = 00000000
"
kworker/3:4-101 [003] … 99.208877: rtcpu_string: tstamp:3698162299 id:0x04010000 str:"nvcsi_reset_data_lanes: NVCSI_PHY_0_NVCSI_CIL_B

kworker/3:4-101 [003] … 99.208877: rtcpu_string: tstamp:3698162401 id:0x04010000 str:"SW_RESET_0 = 00000000
"
kworker/3:4-101 [003] … 99.208881: rtcpu_vinotify_error: tstamp:3698167867 cch:-1 vi:0 tag:CSIMUX_STREAM channel:0x00 frame:1 vi_tstamp:118341218496 data:0x0000000000000001
kworker/3:4-101 [003] … 99.208881: rtcpu_vinotify_error: tstamp:3698168795 cch:-1 vi:0 tag:CSIMUX_STREAM channel:0x00 frame:3 vi_tstamp:118341223424 data:0x0000000000000001
kworker/3:4-101 [003] … 99.208882: rtcpu_vinotify_error: tstamp:3698169700 cch:-1 vi:0 tag:CSIMUX_STREAM channel:0x00 frame:0 vi_tstamp:118341229088 data:0x0000000000000001
kworker/3:4-101 [003] … 99.208882: rtcpu_vinotify_error: tstamp:3698170596 cch:-1 vi:0 tag:CSIMUX_STREAM channel:0x00 frame:2 vi_tstamp:118341234016 data:0x0000000000000001
kworker/3:4-101 [003] … 99.208883: rtcpu_vinotify_event: tstamp:3698171176 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:118324980576 data:0x359d580010000000
kworker/3:4-101 [003] … 99.208884: rtcpu_vinotify_event: tstamp:3698171308 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:118324987104 data:0x0000000031000001
kworker/3:4-101 [003] … 99.208884: rtcpu_vinotify_event: tstamp:3698171461 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:118325043232 data:0x359d550010000000
kworker/3:4-101 [003] … 99.208884: rtcpu_vinotify_event: tstamp:3698171592 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:118325049888 data:0x0000000031000002
kworker/3:4-101 [003] … 99.208885: rtcpu_vinotify_event: tstamp:3698704162 cch:-1 vi:0 tag:CSIMUX_STREAM channel:0x00 frame:1 vi_tstamp:118341218496 data:0x0000000000000001
kworker/3:4-101 [003] … 99.208885: rtcpu_vinotify_event: tstamp:3698704297 cch:-1 vi:0 tag:CSIMUX_STREAM channel:0x00 frame:3 vi_tstamp:118341223424 data:0x0000000000000001
kworker/3:4-101 [003] … 99.208885: rtcpu_vinotify_event: tstamp:3698704450 cch:-1 vi:0 tag:CSIMUX_STREAM channel:0x00 frame:0 vi_tstamp:118341229088 data:0x0000000000000001
kworker/3:4-101 [003] … 99.208886: rtcpu_vinotify_event: tstamp:3698704581 cch:-1 vi:0 tag:CSIMUX_STREAM channel:0x00 frame:2 vi_tstamp:118341234016 data:0x0000000000000001
kworker/3:4-101 [003] … 99.208886: rtcpu_vinotify_event: tstamp:3698704730 cch:0 vi:0 tag:FS channel:0x00 frame:0 vi_tstamp:118355827168 data:0x0000000000000010
kworker/3:4-101 [003] … 99.208886: rtcpu_vinotify_event: tstamp:3698704864 cch:0 vi:0 tag:ATOMP_FS channel:0x00 frame:0 vi_tstamp:118355827264 data:0x0000000800000000
kworker/3:4-101 [003] … 99.208886: rtcpu_vinotify_event: tstamp:3698705018 cch:0 vi:0 tag:CHANSEL_PXL_SOF channel:0x23 frame:0 vi_tstamp:118356740096 data:0x0000000000000001
kworker/3:4-101 [003] … 99.208886: rtcpu_vinotify_event: tstamp:3698705149 cch:0 vi:0 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:118356750976 data:0x0000000008020001
kworker/3:4-101 [003] … 99.208887: rtcpu_vinotify_event: tstamp:3698705299 cch:-1 vi:0 tag:FS channel:0x01 frame:0 vi_tstamp:118358305408 data:0x0000000000000010
kworker/3:4-101 [003] … 99.208887: rtcpu_vinotify_error: tstamp:3698729600 cch:-1 vi:0 tag:CHANSEL_NOMATCH channel:0x41 frame:0 vi_tstamp:118359218304 data:0x00000000000003c9
kworker/3:4-101 [003] … 99.208887: rtcpu_vinotify_error: tstamp:3698891470 cch:-1 vi:0 tag:CHANSEL_NOMATCH channel:0x81 frame:0 vi_tstamp:118364389376 data:0x00000000000003c9
kworker/3:4-101 [003] … 99.208888: rtcpu_vinotify_event: tstamp:3698892041 cch:-1 vi:0 tag:CHANSEL_NOMATCH channel:0x41 frame:0 vi_tstamp:118359218304 data:0x00000000000003c9
kworker/3:4-101 [003] … 99.208888: rtcpu_vinotify_event: tstamp:3698892187 cch:-1 vi:0 tag:FS channel:0x02 frame:0 vi_tstamp:118363474688 data:0x0000000000000010
kworker/3:4-101 [003] … 99.208888: rtcpu_vinotify_event: tstamp:3698892317 cch:-1 vi:0 tag:CHANSEL_NOMATCH channel:0x81 frame:0 vi_tstamp:118364389376 data:0x00000000000003c9
kworker/3:4-101 [003] … 99.208888: rtcpu_vinotify_error: tstamp:3699057480 cch:-1 vi:0 tag:CHANSEL_NOMATCH channel:0xc1 frame:0 vi_tstamp:118369712032 data:0x00000000000003c9
kworker/3:4-101 [003] … 99.264836: rtcpu_vinotify_event: tstamp:3699409486 cch:-1 vi:0 tag:FS channel:0x03 frame:0 vi_tstamp:118368794496 data:0x0000000000000010
kworker/3:4-101 [003] … 99.264840: rtcpu_vinotify_event: tstamp:3699409617 cch:-1 vi:0 tag:CHANSEL_NOMATCH channel:0xc1 frame:0 vi_tstamp:118369712032 data:0x00000000000003c9
kworker/3:4-101 [003] … 99.264842: rtcpu_vinotify_error: tstamp:3699668990 cch:0 vi:0 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:118389160160 data:0x00000000000000a0
kworker/3:4-101 [003] … 99.264843: rtcpu_vinotify_event: tstamp:3699741605 cch:0 vi:0 tag:CHANSEL_PXL_EOF channel:0x23 frame:0 vi_tstamp:118388699552 data:0x0000000002cf0002
kworker/3:4-101 [003] … 99.264843: rtcpu_vinotify_event: tstamp:3699741737 cch:0 vi:0 tag:ATOMP_FRAME_DONE channel:0x23 frame:0 vi_tstamp:118388700544 data:0x0000000000000000
kworker/3:4-101 [003] … 99.264844: rtcpu_vinotify_event: tstamp:3699741890 cch:0 vi:0 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:118388720800 data:0x0000000002020001
kworker/3:4-101 [003] … 99.264844: rtcpu_vinotify_event: tstamp:3699742020 cch:0 vi:0 tag:CSIMUX_FRAME channel:0x00 frame:0 vi_tstamp:118389160160 data:0x00000000000000a0
kworker/3:4-101 [003] … 99.264844: rtcpu_vinotify_event: tstamp:3699742169 cch:0 vi:0 tag:FS channel:0x00 frame:0 vi_tstamp:118389160160 data:0x0000000000000010
kworker/3:4-101 [003] … 99.264845: rtcpu_vinotify_event: tstamp:3699742304 cch:0 vi:0 tag:ATOMP_FE channel:0x00 frame:0 vi_tstamp:118389160256 data:0x0000000800000000
kworker/3:4-101 [003] … 99.264845: rtcpu_vinotify_event: tstamp:3699742453 cch:0 vi:0 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:118389215840 data:0x0000000000020001
kworker/3:4-101 [003] … 99.264846: rtcpu_vinotify_event: tstamp:3699742584 cch:0 vi:0 tag:ATOMP_FS channel:0x00 frame:0 vi_tstamp:118389160256 data:0x0000000800000000
kworker/3:4-101 [003] … 99.264846: rtcpu_vinotify_event: tstamp:3699742737 cch:0 vi:0 tag:CHANSEL_PXL_SOF channel:0x23 frame:0 vi_tstamp:118390073056 data:0x0000000000000001
kworker/3:4-101 [003] … 99.264846: rtcpu_vinotify_event: tstamp:3699742865 cch:0 vi:0 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:118390083904 data:0x0000000008020002
kworker/3:4-101 [003] … 99.264847: rtcpu_vinotify_event: tstamp:3699743013 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:118390305760 data:0x359d580010000000
kworker/3:4-101 [003] … 99.264847: rtcpu_vinotify_event: tstamp:3699743143 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:118390349120 data:0x0000000031000003

The camera trace log above opens vc0

From 160, it can be seen that bit 5 and bit 7:

define CAPTURE_CHANNEL_ERROR_PIXEL_MISSING_LE MK_BIT32(5)
define CAPTURE_CHANNEL_ERROR_PIXEL_SPURIOUS MK_BIT32(7)

SPURIOUS DATA STREAM ?

hello 305248199,

there’s NULL VI reported for your 1st camera
since you’re having these four camera connected to the same CSI brick (CSI-A),
it’s more like an issue of SerDes chip configuration.

BTW,
could you please give it a try to refer to Topic 268833,
please apply the pre-built binary, which has updated deskew algorithm, and also stability fixes.

yes,gmsl max96712+max96705.
I tried the new firmware of Topic268833, but the problem still persists.

as mentioned, it’s more like an issue of SerDes chip configuration. please double check driver side settings.

Okay, I’ll go communicate with you on my end. Thank you

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