Rtcpu_vinotify_event: CHANSEL_NOMATCH on AGX xavier

[xumm_td]

Hi,
I am trying to access a raw8 data interface mipi camera on agx xavier with system version Jetpack 5.0.2. The bringup prompts the following error:

 kworker/3:0-30      [003] ....    93.646556: rtcpu_vinotify_event: tstamp:3682457872 cch:0 vi:0 tag:FS channel:0x00 frame:140 vi_tstamp:117834563424 data:0x0000000000000015
 kworker/3:0-30      [003] ....    93.646556: rtcpu_vinotify_event: tstamp:3682458034 cch:0 vi:0 tag:CHANSEL_NOMATCH channel:0x20 frame:140 vi_tstamp:117835420224 data:0x0000000000000549
 kworker/3:0-30      [003] ....    93.702549: rtcpu_vinotify_error: tstamp:3683052003 cch:0 vi:0 tag:CHANSEL_NOMATCH channel:0x20 frame:141 vi_tstamp:117857638752 data:0x0000000000000549
 kworker/3:0-30      [003] ....    93.702550: rtcpu_vinotify_event: tstamp:3683083666 cch:0 vi:0 tag:FE channel:0x00 frame:140 vi_tstamp:117856754400 data:0x0000000000000025
 kworker/3:0-30      [003] ....    93.702551: rtcpu_vinotify_event: tstamp:3683083833 cch:0 vi:0 tag:FS channel:0x00 frame:141 vi_tstamp:117856781952 data:0x0000000000000015
 kworker/3:0-30      [003] ....    93.702551: rtcpu_vinotify_event: tstamp:3683084022 cch:0 vi:0 tag:CHANSEL_NOMATCH channel:0x20 frame:141 vi_tstamp:117857638752 data:0x0000000000000549
 kworker/3:0-30      [003] ....    93.702552: rtcpu_vinotify_event: tstamp:3683718667 cch:0 vi:0 tag:FE channel:0x00 frame:141 vi_tstamp:117878972992 data:0x0000000000000025
 kworker/3:0-30      [003] ....    93.702552: rtcpu_vinotify_error: tstamp:3683746329 cch:0 vi:0 tag:CHANSEL_NOMATCH channel:0x20 frame:142 vi_tstamp:117879857376 data:0x0000000000000549
 kworker/3:0-30      [003] ....    93.702553: rtcpu_vinotify_event: tstamp:3684022617 cch:0 vi:0 tag:FS channel:0x00 frame:142 vi_tstamp:117879000576 data:0x0000000000000015
 kworker/3:0-30      [003] ....    93.702554: rtcpu_vinotify_event: tstamp:3684022783 cch:0 vi:0 tag:CHANSEL_NOMATCH channel:0x20 frame:142 vi_tstamp:117879857376 data:0x0000000000000549
 kworker/3:0-30      [003] ....    93.702554: rtcpu_vinotify_error: tstamp:3684440700 cch:0 vi:0 tag:CHANSEL_NOMATCH channel:0x20 frame:143 vi_tstamp:117902075936 data:0x0000000000000549
 kworker/3:0-30      [003] ....    93.758547: rtcpu_vinotify_event: tstamp:3684648612 cch:0 vi:0 tag:FE channel:0x00 frame:142 

I tried some search in the forum.
This error suggests that my camera outputs a mipi package of type 0x2a, which is raw8, but the datatype configured in xavier’s vi module is not 0x2a
So I add a log in vi5_capture_enqueue() from vi5_fops.c, proved that vi’s configuration is correct.
In addition camera is not output embeded line, DTS also did not configure this.

This camera has been successfully connected to nano.
I have been struggling with this problem for a few days and ask for some help. Thanks in advance.

[JerryChang]

@xumm_td

but the datatype configured in xavier’s vi module is not 0x2a

hello xumm_td,

because it is not supported. VI did not support RGB888 memory formats due to it’ll add luminance format.
you may also check the Xavier TRM, please refer to [RGB Memory Formats] session, and check [Table 7.35 RGB Formats Supported by VI] for details.

[xumm_td]

@JerryChang
Maybe I didn’t make it clear, my camera output format is raw8, corresponding to FOURCC is GREY, not RGB888.
And I have a similar camera that is already connected to xavier in the same way.

I would like to check the setting of datatype of the CHANLSEL module of VI, which register do I need to check? Is there a convenient way to read out the value of this register?

In the driver, I see that the configuration of these registers is done by rtcpu.

Thanks in advance.

[JerryChang]

hello xumm_td,

may I also know what’s the pipeline you’re going to process?
for example, is it through standard v4l, or you would like to use Argus with ISP?

[xumm_td]

Hi @JerryChang ，
I use v4l2-ctl to get the frame now. No use of Argus and ISP.

[JerryChang]

hello xumm_td,

GRAY format is supported, you may test with MMAPI sample, for example, 12_camera_v4l2_cuda.

for using gst pipeline, you may test with v4l2src, here’s sample pipeline to test the stream to check fps.
for example,
$ gst-launch-1.0 v4l2src ! video/x-raw,format=GRAY8, width=_W_,height=_H_,framerate=_FR_ ! nvvidconv ! video/x-raw(memory:NVMM),format=I420 ! fpsdisplaysink text-overlay=0 video-sink=fakesink sync=0 -v

please also share your test results for reference,
thanks