CHANSEL_NOMATCH in JetPack 5.1.3

Hi,

I used JetPack 5.0.2 until now and I updated to 5.1.3 some days ago.
However, the image sensor fps in gstreamer is dropped (30->28) and I found that CHANSEL_NOMATCH in the vi trace.

# tracer: nop
#
# entries-in-buffer/entries-written: 11858/11858   #P:8
#
#                                _-----=> irqs-off
#                               / _----=> need-resched
#                              | / _---=> hardirq/softirq
#                              || / _--=> preempt-depth
#                              ||| /     delay
#           TASK-PID     CPU#  ||||   TIMESTAMP  FUNCTION
#              | |         |   ||||      |         |
     kworker/4:4-224     [004] ....   621.794900: rtcpu_vinotify_event: tstamp:20081518540 cch:0 vi:0 tag:CHANSEL_PXL_EOF channel:0x23 frame:0 vi_tstamp:642606177504 data:0x00000000086f0002
     kworker/4:4-224     [004] ....   621.794903: rtcpu_vinotify_event: tstamp:20081518674 cch:0 vi:0 tag:ATOMP_FRAME_DONE channel:0x23 frame:0 vi_tstamp:642606178048 data:0x0000000000000000
     kworker/4:4-224     [004] ....   621.794903: rtcpu_vinotify_event: tstamp:20081518825 cch:0 vi:0 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:642606180992 data:0x0000000002023ce0
     kworker/4:4-224     [004] ....   621.794903: rtcpu_vinotify_event: tstamp:20081518956 cch:0 vi:0 tag:FE channel:0x00 frame:0 vi_tstamp:642606178112 data:0x0000000000000024
     kworker/4:4-224     [004] ....   621.794904: rtcpu_vinotify_event: tstamp:20081519109 cch:0 vi:0 tag:ATOMP_FE channel:0x00 frame:0 vi_tstamp:642606178112 data:0x0000000800000000
     kworker/4:4-224     [004] ....   621.794904: rtcpu_vinotify_event: tstamp:20081519240 cch:0 vi:0 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:642606187200 data:0x0000000000023ce0
     kworker/4:4-224     [004] ....   621.794904: rtcpu_vinotify_event: tstamp:20081519389 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:642607539328 data:0x359d580010000000
     kworker/4:4-224     [004] ....   621.794904: rtcpu_vinotify_event: tstamp:20081519520 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:642607545792 data:0x0000000031003ce1
     kworker/4:4-224     [004] ....   621.794904: rtcpu_vinotify_event: tstamp:20081519668 cch:0 vi:0 tag:FS channel:0x00 frame:0 vi_tstamp:642607572896 data:0x0000000000000014
     kworker/4:4-224     [004] ....   621.794905: rtcpu_vinotify_event: tstamp:20081519802 cch:0 vi:0 tag:ATOMP_FS channel:0x00 frame:0 vi_tstamp:642607572896 data:0x0000000800000000
     kworker/4:4-224     [004] ....   621.794905: rtcpu_vinotify_event: tstamp:20081519955 cch:0 vi:0 tag:CHANSEL_PXL_SOF channel:0x23 frame:0 vi_tstamp:642608200800 data:0x0000000000000001
     kworker/4:4-224     [004] ....   621.794905: rtcpu_vinotify_event: tstamp:20081520088 cch:0 vi:0 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:642608202336 data:0x0000000008023ce1
     kworker/4:4-224     [004] ....   621.794905: rtcpu_vinotify_event: tstamp:20082481163 cch:0 vi:0 tag:CHANSEL_PXL_EOF channel:0x23 frame:0 vi_tstamp:642639326976 data:0x00000000086f0002
     kworker/4:4-224     [004] ....   621.794905: rtcpu_vinotify_event: tstamp:20082481299 cch:0 vi:0 tag:ATOMP_FRAME_DONE channel:0x23 frame:0 vi_tstamp:642639327552 data:0x0000000000000000
     kworker/4:4-224     [004] ....   621.794905: rtcpu_vinotify_event: tstamp:20082481450 cch:0 vi:0 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:642639330464 data:0x0000000002023ce1
     kworker/4:4-224     [004] ....   621.794906: rtcpu_vinotify_event: tstamp:20082481578 cch:0 vi:0 tag:FE channel:0x00 frame:0 vi_tstamp:642639327552 data:0x0000000000000024
     kworker/4:4-224     [004] ....   621.794907: rtcpu_vinotify_error: tstamp:20082542981 cch:0 vi:0 tag:CHANSEL_NOMATCH channel:0x10 frame:0 vi_tstamp:642641350400 data:0x0000000000000589
     kworker/4:4-224     [004] ....   621.794907: rtcpu_vinotify_event: tstamp:20082803141 cch:0 vi:0 tag:ATOMP_FE channel:0x00 frame:0 vi_tstamp:642639327584 data:0x0000000800000000
     kworker/4:4-224     [004] ....   621.794907: rtcpu_vinotify_event: tstamp:20082803274 cch:0 vi:0 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:642639337856 data:0x0000000000023ce1
     kworker/4:4-224     [004] ....   621.794907: rtcpu_vinotify_event: tstamp:20082803426 cch:0 vi:0 tag:FS channel:0x00 frame:0 vi_tstamp:642640722400 data:0x0000000000000014
     kworker/4:4-224     [004] ....   621.794907: rtcpu_vinotify_event: tstamp:20082803556 cch:0 vi:0 tag:CHANSEL_NOMATCH channel:0x10 frame:0 vi_tstamp:642641350400 data:0x0000000000000589
     kworker/4:4-224     [004] ....   621.794908: rtcpu_vinotify_event: tstamp:20082803711 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:642641603072 data:0x359d550010000000
     kworker/4:4-224     [004] ....   621.794908: rtcpu_vinotify_event: tstamp:20082803842 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:642641609536 data:0x0000000031003ce2
 vi-output, sami-3434    [001] ....   621.836692: tegra_channel_capture_frame: sof:642.674499872
 vi-output, sami-3434    [001] ....   621.836695: tegra_channel_capture_frame: eof:642.705626720

In JetPack 5.0.2, FPS is not dropped and CHANSEL_NOMATCH also doesn’t exist.

I used the same sensor setting, gstreamer pipeline, and the same driver and device tree that I used in 5.0.2.

I boosted the clock with this command V4L2 sensor shows low FPS with CHANSEL_NOMATCH - #9 by ShaneCCC but there is no noticeable difference.

Thanks.

The CHANSEL_NOMATCH tell the sensor output unsupported data type.
Looks like JP5.1.2 RCE firmware have more checking.
Maybe you can apply the JP5.0.2 RCE firmware on JP5.1.2 to confirm it.

Thanks for the answer. I updated JP 5.0.2 RCE fw on JP 5.1.3 with the following command in Linux_for_Tegra.

sudo ./flash.sh -r -k A_rce-fw jetson-agx-orin-devkit mmcblk0p1

But the issue remains the same as before. Do you have any idea?
Thanks.

Could you confirm the RTCPU firmware by below command.
Confirm the shal# is different.

sudo dmesg | grep -i rtcpu

I have two orins. The first one is 5.0.2 and the other is 5.1.3. Two orins have the same rce-fw version which is included in 5.0.2.

The results of

are the same as followed.

[    0.417681] camchar: rtcpu character device driver loaded
[    4.189723] tegra186-cam-rtcpu bc00000.rtcpu: Adding to iommu group 9
[    4.196660] tegra186-cam-rtcpu bc00000.rtcpu: Trace buffer configured at IOVA=0xbff00000
[    4.207454] tegra-ivc-bus bc00000.rtcpu:ivc-bus: region 0: iova=0xbfec0000-0xbfee01ff size=131584
[    4.212994] tegra-ivc-bus bc00000.rtcpu:ivc-bus:echo@0: echo: ver=0 grp=1 RX[16x64]=0x1000-0x1480 TX[16x64]=0x1480-0x1900
[    4.224110] tegra-ivc-bus bc00000.rtcpu:ivc-bus:dbg@1: dbg: ver=0 grp=1 RX[1x448]=0x1900-0x1b40 TX[1x448]=0x1b40-0x1d80
[    4.234851] tegra-ivc-bus bc00000.rtcpu:ivc-bus:dbg@2: dbg: ver=0 grp=1 RX[1x8192]=0x1d80-0x3e00 TX[1x8192]=0x3e00-0x5e80
[    4.245819] tegra-ivc-bus bc00000.rtcpu:ivc-bus:ivccontrol@3: ivccontrol: ver=0 grp=1 RX[64x320]=0x5e80-0xaf00 TX[64x320]=0xaf00-0xff80
[    4.257613] tegra-ivc-bus bc00000.rtcpu:ivc-bus:ivccapture@4: ivccapture: ver=0 grp=1 RX[512x64]=0xff80-0x18000 TX[512x64]=0x18000-0x20080
[    4.270130] tegra-ivc-bus bc00000.rtcpu:ivc-bus:diag@5: diag: ver=0 grp=1 RX[1x64]=0x20080-0x20140 TX[1x64]=0x20140-0x20200
[    4.281695] tegra186-cam-rtcpu bc00000.rtcpu: using cam RTCPU IRQ (117)
[    4.288214] tegra186-cam-rtcpu bc00000.rtcpu: tegra_camrtc_mon_create is successful
[    4.296558] tegra186-cam-rtcpu bc00000.rtcpu: firmware version cpu=rce cmd=6 sha1=7a10e4613e151d2bf1df37dd80d456800f5b94d0