Tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 262144

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

kw33000是一个3D TOF的camera，Output Format: MIPI CSI-2(Ver.1.1) 2Lane RAW12，接到jetson orin nx上面，执行了v4l2命令：v4l2-ctl -d /dev/video0 --set-fmt-video=width=640,height=960,pixelformat=RG12 --stream-mmap=3 --stream-to=./raw.out --stream-count=1 --stream-poll
出现错误：tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 262144

image
image1225×849 19.2 KB

设备树配置：

image
image1538×970 86.9 KB

image
image1637×967 92.5 KB

image
image1480×988 89 KB

硬件连接框图：

企业微信截图_1749470729839
企业微信截图_17494707298391497×931 132 KB

3

Get the trace log for to check.

5

jetson_2025-06-11_14_53_10.log (160.5 KB)

Hello, this is the log.

6

Get the log by below step

sudo modprobe rtcpu_debug 
echo 1 > /sys/kernel/debug/tracing/tracing_on
echo 30720 > /sys/kernel/debug/tracing/buffer_size_kb
echo 1 > /sys/kernel/debug/tracing/events/tegra_rtcpu/enable
echo 1 > /sys/kernel/debug/tracing/events/freertos/enable
echo 2 > /sys/kernel/debug/camrtc/log-level
echo 1 > /sys/kernel/debug/tracing/events/camera_common/enable
echo > /sys/kernel/debug/tracing/trace

v4l2-ctl -d /dev/video0 --set-fmt-video=width=640,height=960,pixelformat=RG12 --stream-mmap=3 --stream-to=./raw.out --stream-count=1

cat /sys/kernel/debug/tracing/trace
7

jetson_2025-06-11_15_45_57.log (301.5 KB)

8

The log tell CHANSEL_SHORT_FRAME that means the output size less than 960

9

The data format of the 3D TOF sensor is: Output Format: MIPI CSI-2 (Version 1.1) 2Lane RAW12, Output format: 6404802，Therefore, I filled in 640 and 960. I have also tried this format of 2640480, which is equivalent to 1280*480. The corresponding log is
jetson_2025-06-11_16_09_11.log (339.1 KB)

10

This case not just short frame also show the pixel short.
Suppose the 640 is correct.
Maybe report less lines > 960 to narrow down it.
Confirm the “Width/Height and Bytes per Line” modication by v4l2-ctl --all

Format Video Capture:
	Width/Height      : 3280/2464
	Pixel Format      : 'RG10' (10-bit Bayer RGRG/GBGB)
	Field             : None
	Bytes per Line    : 6560
	Size Image        : 16163840
	Colorspace        : sRGB
	Transfer Function : Default (maps to sRGB)
	YCbCr/HSV Encoding: Default (maps to ITU-R 601)
	Quantization      : Default (maps to Full Range)
11

The log corresponding to v4l2 v4l2-ctl --all
jetson_2025-06-11_17_00_46.log (8.5 KB)

12

You have to report less height one by one to root out of it.

Thanks

13

Hello, I have encountered different errors when changing to different heights.
[ 82.277111] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[ 82.277135] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[ 82.278406] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel

trace log to：
default_2025-06-12_17_06_37.log (139.3 KB)

14

The trace log tell didn’t receive any validate data from the MIPI bus.
Do you report 640x1928?

tegra_channel_capture_setup: vnc_id 0 W 640 H 1928 fmt c4
16

The normal output resolution is 6404802 (640480:depth map + 640480: ir map). I have tried modifying different heights, but the error reported was the same as the one provided above. There was no change and this error “CHANSEL_SHORT_FRAME” could not be eliminated.

This is the data sheet for the KW33000.：
C-[For X-RUN]KW33000A1K_Datasheet_Ver0.66_20221201.pdf (6.1 MB)

17

Do you try report the height less than 960, like 958, 956, 950, 940, 930, 920 …

18

Is it really because of this height that this happened? I made numerous adjustments to the heights.such as 968, 964, 960 ,958,956,954,950,946,940,930,920,910,900,890,880,870,860
And the errors in these reports are consistent and have not changed.

19

Do you only report less lines? Maybe report half lines or 1/3 to check the log.

20

report half lines or 1/3 to check the log
jetson_2025-06-17_13_48_19.log (1.4 MB)

The corresponding error code has changed.：
tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 64

21

This tell the PIXEL_RUNAWAY that tell VI receives more lines than expected(240).

     kworker/4:2-146     [004] .......   106.406243: rtcpu_vinotify_event: tstamp:4172909062 cch:0 vi:1 tag:CHANSEL_FAULT channel:0x23 frame:0 vi_tstamp:133532681344 data:0x0000000000f00040
22

So what should I do next?,
If the height is reduced by more than 480, this PIXEL_RUNAWAY error will occur.Reverting to above 480 would be the same as the aforementioned CHANSEL_SHORT_FRAME error.

25

Hello, I have tried your suggestion with different heights from 960 to 240 (more than 10 different heights). However, it still didn’t work.

When the height is less than 480, the “PIXEL_RUNAWAY” error occurs.
When the height is between 480 and 960, the error reported is “CHANSEL_SHORT_FRAME”.

Our actual tof camera resolution is 640480 and it outputs two frames (one IR and one depth map, both of them are 640480). So it means the height should be 960. I am not sure you suggest us to adjust height is the right direction. Is it possible that CHANSEL_SHORT_FRAME error is caused by another reason? Please help to double check. Thanks.