Error receiving data from GMSL camera

[liviolima80]

Good morning,
I have the following chain connected to Orin AGX (Jetpack 5.1.1):
IMX675 sensor → MAX96717 serializer → MAX96714 deserializer → 4xlane MIPI CSI Orin

Sensor driver and device tree are correct since if I directly connect the sensor to Orin everything works correctly. When I start streaming data the sensor->serializer->deserializer chain seems ok since ser/des have no error and the deserializer activates the flag that indicate receiving of data.

From AGX side, using the following command to test the stream
v4l2-ctl -V --set-ctrl bypass_mode=0 --stream-mmap --stream-count=5 -d /dev/video0
I don’t receive any frames.

From dmesg I have the following errors
[ 1888.564518] tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 2, flags: 0, err_data 2048
[ 1888.626796] tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 4, flags: 0, err_data 131072
[ 1888.659804] tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 5, flags: 0, err_data 512
[ 1888.697096] tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 6, flags: 0, err_data 2048

while enabling the video trace I have the following log

 kworker/2:2-154     [002] ....  1873.251892: rtcpu_string: tstamp:59371600569 id:0x04010000 str:"VM0 deactivating."
    v4l2-ctl-2285    [007] ....  1888.353271: tegra_channel_open: vi-output, imx675 34-001a
    v4l2-ctl-2285    [007] ....  1888.364718: tegra_channel_set_power: imx675 34-001a : 0x1
    v4l2-ctl-2285    [007] ....  1888.364732: camera_common_s_power: status : 0x1
    v4l2-ctl-2285    [007] ....  1888.388778: tegra_channel_set_power: 13e40000.host1x:nvcsi@15a00000- : 0x1
    v4l2-ctl-2285    [007] ....  1888.388781: csi_s_power: enable : 0x1
    v4l2-ctl-2285    [007] ....  1888.389782: tegra_channel_capture_setup: vnc_id 0 W 2608 H 1964 fmt c4
    v4l2-ctl-2285    [007] ....  1888.398296: tegra_channel_set_stream: enable : 0x1
    v4l2-ctl-2285    [007] ....  1888.416861: tegra_channel_set_stream: 13e40000.host1x:nvcsi@15a00000- : 0x1
    v4l2-ctl-2285    [007] ....  1888.416864: csi_s_stream: enable : 0x1
    v4l2-ctl-2285    [007] ....  1888.417481: tegra_channel_set_stream: imx675 34-001a : 0x1
 kworker/2:2-154     [002] ....  1888.431615: rtcpu_string: tstamp:59845024352 id:0x04010000 str:"VM0 activating."
 kworker/2:2-154     [002] ....  1888.431619: rtcpu_vinotify_event: tstamp:59845657768 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:1915045216128 data:0x399d580010000000
 kworker/2:2-154     [002] ....  1888.431620: rtcpu_vinotify_event: tstamp:59845657968 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:1915045222560 data:0x0000000031000001
 kworker/2:2-154     [002] ....  1888.431620: rtcpu_vinotify_event: tstamp:59845658169 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:1915045272992 data:0x399d550010000000
 kworker/2:2-154     [002] ....  1888.431620: rtcpu_vinotify_event: tstamp:59845658336 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:1915045279520 data:0x0000000031000002
 kworker/2:2-154     [002] ....  1888.543598: rtcpu_nvcsi_intr: tstamp:59848293325 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x00000110
 kworker/2:2-154     [002] ....  1888.543599: rtcpu_nvcsi_intr: tstamp:59848293325 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000110
 kworker/2:2-154     [002] ....  1888.543600: rtcpu_nvcsi_intr: tstamp:59848293325 class:CORRECTABLE_ERR type:STREAM_VC phy:0 cil:0 st:0 vc:0 status:0x00000004
 kworker/2:2-154     [002] ....  1888.543600: rtcpu_nvcsi_intr: tstamp:59848294196 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:0 vc:0 status:0x00000004
 kworker/2:2-154     [002] ....  1888.543601: rtcpu_nvcsi_intr: tstamp:59848296312 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:0 vc:0 status:0x00000004
 kworker/2:2-154     [002] ....  1888.543601: rtcpu_nvcsi_intr: tstamp:59848296312 class:CORRECTABLE_ERR type:STREAM_VC phy:0 cil:0 st:0 vc:0 status:0x00000004
 kworker/2:2-154     [002] ....  1888.543603: rtcpu_vinotify_error: tstamp:59848298375 cch:-1 vi:0 tag:CSIMUX_STREAM channel:0x00 frame:0 vi_tstamp:1915145383936 data:0x0000000000000001
 kworker/2:2-154     [002] ....  1888.543603: rtcpu_nvcsi_intr: tstamp:59848298488 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:0 vc:0 status:0x00000004
 kworker/2:2-154     [002] ....  1888.543604: rtcpu_nvcsi_intr: tstamp:59848298488 class:CORRECTABLE_ERR type:STREAM_VC phy:0 cil:0 st:0 vc:0 status:0x00000004
 kworker/2:2-154     [002] ....  1888.543604: rtcpu_nvcsi_intr: tstamp:59848302654 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:0 vc:0 status:0x00000004
 kworker/2:2-154     [002] ....  1888.543604: rtcpu_nvcsi_intr: tstamp:59848302654 class:CORRECTABLE_ERR type:STREAM_VC phy:0 cil:0 st:0 vc:0 status:0x00000004
 kworker/2:2-154     [002] ....  1888.543605: rtcpu_nvcsi_intr: tstamp:59848305434 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:0 vc:0 status:0x00000004
 kworker/2:2-154     [002] ....  1888.543605: rtcpu_nvcsi_intr: tstamp:59848305434 class:CORRECTABLE_ERR type:STREAM_VC phy:0 cil:0 st:0 vc:0 status:0x00000004
 kworker/2:2-154     [002] ....  1888.543606: rtcpu_nvcsi_intr: tstamp:59848309136 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:0 vc:0 status:0x00000004
 kworker/2:2-154     [002] ....  1888.543606: rtcpu_nvcsi_intr: tstamp:59848309136 class:CORRECTABLE_ERR type:STREAM_VC phy:0 cil:0 st:0 vc:0 status:0x00000004
 kworker/2:2-154     [002] ....  1888.543606: rtcpu_nvcsi_intr: tstamp:59848313767 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:0 vc:0 status:0x00000004
 kworker/2:2-154     [002] ....  1888.543607: rtcpu_nvcsi_intr: tstamp:59848313767 class:CORRECTABLE_ERR type:STREAM_VC phy:0 cil:0 st:0 vc:0 status:0x00000004
 kworker/2:2-154     [002] ....  1888.543607: rtcpu_nvcsi_intr: tstamp:59848320709 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:0 vc:0 status:0x00000004

Could you help me to understand the type of error?
Regards

[liviolima80]

Good morning,
I tried to debug a bit and the error messages come from vi5_capture_dequeue function since

descr->status.status != CAPTURE_STATUS_SUCCESS

but has the value CAPTURE_STATUS_FALCON_ERROR. From define of the error I have the following

/** Falcon error.

• Value of @ref err_data “err_data” is defined in
  " VI Microcode IAS v0.5.13, section 2.3.3".
  */
  CAPTURE_STATUS_FALCON_ERROR MK_U32(14)

Since further documentation is not available, could you help me to understand the possible cause of error?

Regards

[liviolima80]

I found a solution using this thread

CHANSEL_NOMATCH with FPDLink-III serdes, incorrectly splitting one camera into two channels?

Could the Falcon failure prevent the CPU cache sync/clean after a frame is written into a DMA memory buffer by NVCSI/VI? I have noticed that the top parts of some frames (0-50 lines of pixel data) appear to be from an earlier frame that was in the same buffer. In my code I am using DMA_BUF_IOCTL_SYNC with DMA_BUF_SYNC_READ | DMA_BUF_SYNC_START before the file write and DMA_BUF_SYNC_READ | DMA_BUF_SYNC_END after the file write, but I’m still getting the glitch in the data written out. This hap…

boosting the clock I solved my issue.

Anyone can better explain what these commands do?

Regards