V4l2-ctl video test error on Jetson Xavier NX

Robotics & Edge Computing Jetson & Embedded Systems Jetson Xavier NX
1

Hi,
We have developed a custom carrier board for Jetson Xavier NX and have used it to capture a 4lane mipi csi-2 video.

v4l2-ctl -d /dev/video0 --set-ctrl bypass_mode=0 --stream-mmap --stream-count=1 --stream-to=test.raw --set-fmt-video=width=1920,height=1080,pixelformat=UYVY

I got error log as follows:

 kworker/1:1-809   [001] ....  1118.433133: rtcpu_nvcsi_intr: tstamp:35209566087 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x0e000000
 kworker/1:1-809   [001] ....  1118.433135: rtcpu_nvcsi_intr: tstamp:35209566087 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x06000000
 kworker/1:1-809   [001] ....  1118.433136: rtcpu_nvcsi_intr: tstamp:35209566087 class:CORRECTABLE_ERR type:PHY_INTR phy:0 cil:0 st:0 vc:0 status:0x00000e00
 kworker/1:1-809   [001] ....  1118.433137: rtcpu_nvcsi_intr: tstamp:35209566087 class:CORRECTABLE_ERR type:PHY_INTR phy:0 cil:1 st:0 vc:0 status:0x00000600
 kworker/1:1-809   [001] ....  1118.433138: rtcpu_nvcsi_intr: tstamp:35209567042 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x1e000000
 kworker/1:1-809   [001] ....  1118.433139: rtcpu_nvcsi_intr: tstamp:35209567042 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x06000000
 kworker/1:1-809   [001] ....  1118.433140: rtcpu_nvcsi_intr: tstamp:35209567042 class:CORRECTABLE_ERR type:PHY_INTR phy:0 cil:0 st:0 vc:0 status:0x00001e44
 kworker/1:1-809   [001] ....  1118.433141: rtcpu_nvcsi_intr: tstamp:35209567042 class:CORRECTABLE_ERR type:PHY_INTR phy:0 cil:1 st:0 vc:0 status:0x00000600
 kworker/1:1-809   [001] ....  1118.433142: rtcpu_nvcsi_intr: tstamp:35209567985 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x00000044
 kworker/1:1-809   [001] ....  1118.433144: rtcpu_nvcsi_intr: tstamp:35209569882 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x10000000
 kworker/1:1-809   [001] ....  1118.433145: rtcpu_nvcsi_intr: tstamp:35209569882 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000044
 kworker/1:1-809   [001] ....  1118.433146: rtcpu_nvcsi_intr: tstamp:35209569882 class:CORRECTABLE_ERR type:PHY_INTR phy:0 cil:0 st:0 vc:0 status:0x00001000
 kworker/1:1-809   [001] ....  1118.433147: rtcpu_nvcsi_intr: tstamp:35209569882 class:CORRECTABLE_ERR type:PHY_INTR phy:0 cil:1 st:0 vc:0 status:0x00000044
 kworker/1:1-809   [001] ....  1118.937559: rtcpu_nvcsi_intr: tstamp:35226206381 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x06000000
 kworker/1:1-809   [001] ....  1118.937559: rtcpu_nvcsi_intr: tstamp:35226206381 class:CORRECTABLE_ERR type:PHY_INTR phy:0 cil:0 st:0 vc:0 status:0x00000e00
 kworker/1:1-809   [001] ....  1118.937559: rtcpu_nvcsi_intr: tstamp:35226206381 class:CORRECTABLE_ERR type:PHY_INTR phy:0 cil:1 st:0 vc:0 status:0x00000600
 kworker/1:1-809   [001] ....  1118.937560: rtcpu_vinotify_event: tstamp:35226207858 tag:CHANSEL_NOMATCH channel:0x01 frame:30409 vi_tstamp:35225683327 data:0x000003c9
 kworker/1:1-809   [001] ....  1118.937561: rtcpu_nvcsi_intr: tstamp:35226209089 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x0e000000
 kworker/1:1-809   [001] ....  1118.937561: rtcpu_nvcsi_intr: tstamp:35226209089 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x06000000
 kworker/1:1-809   [001] ....  1118.937562: rtcpu_nvcsi_intr: tstamp:35226209089 class:CORRECTABLE_ERR type:PHY_INTR phy:0 cil:0 st:0 vc:0 status:0x00000e00
 kworker/1:1-809   [001] ....  1118.937563: rtcpu_nvcsi_intr: tstamp:35226209089 class:CORRECTABLE_ERR type:PHY_INTR phy:0 cil:1 st:0 vc:0 status:0x00000600
 kworker/1:1-809   [001] ....  1118.937564: rtcpu_nvcsi_intr: tstamp:35226210022 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x0e000000

The trace file is 23.8MB big.

3

Check the REG NVCSI_PHY_0_CILA_INTR_0_STATUS_CILA_0 from TRM it show intr_cil_data_lane_sot_mb_err0_a that means multibit error of start of transmit.

4

Hi ShaneCCC,
Could we know the error cause of HW mipi csi signal issue or SW issue?

5

It’s could be the MIPI signal not follow the MIPI spec.