Sensor VI error print reason

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

hello:
I use orin NX 16G custom board，SDK version is R36.4.4. when I see error dmesg pint as follow:

image
image1230×231 7.02 KB

drive file wrong position is in Linux_for_Tegra/source/nvidia-oot/drivers/media/platform/tegra/camera/vi/vi5_fops.c function is static void vi5_capture_dequeue(struct tegra_channel *chan, struct tegra_channel_buffer *buf)

image
image874×554 39.9 KB

status err is :

/**
 * Capture error reported by VI falcon. See @ref notify_bits
 * for detailed @ref ViFalconErrorBits "errors".
 */
#define CAPTURE_STATUS_FALCON_ERROR		MK_U32(14)

but I not find err code: 8192 not include in file:camrtc-capture.h , CAPTURE_STATUS_NOTIFY_BIT_CSIMUX_* ,as follow:

image
image754×471 33.1 KB

Can you help confirm how to solve this error code？This issue was discovered during the testing of the following problem:Custom hard ROI mmap API flow issue - #12 by asfsdgag thanks.

4

hello asfsdgag,

just for confirmation, did you meant the discarding frame has reported for the first six frames?
let me re-cap below from Topic 352532, post#12.

Basically, the data collected is almost always abnormal in the first 6.

5

hello:
first six frames data is incomplete, corr_err is always exist:

image
image1168×539 79.4 KB

6

hello asfsdgag,

it looks expected for VI to drop those buffers.
you may try the workaround to ignore frame_err from the VI driver,
and, using --stream-skip=6 in the v4l capture pipeline to bypass those incomplete frames.

7

hello:
Do these errors not affect the complete data of VI mapping? Then use Linux C code to disable these error configurations. Which CID command? thanks

8

hello asfsdgag,

here’s code snippet to ignore frame_err from the VI driver.

diff --git a/drivers/media/platform/tegra/camera/vi/vi5_fops.c 
@@ -558,7 +558,7 @@ static void vi5_capture_dequeue(struct tegra_channel *chan,
                                        "err_data %d\n",
                                        descr->status.frame_id, descr->status.flags,
                                        descr->status.err_data);
-                               frame_err = true;
+                               // frame_err = true;
                        }

please check below v4l capture pipeline as an example for calling stream-skip to drop buffers.
it’ll request for 10-frames in total, and saving single capture frame into test.raw.
$ v4l2-ctl -d /dev/video0 --set-fmt-video=width=1920,height=1080,pixelformat=RG10 --set-ctrl bypass_mode=0 --stream-mmap --stream-skip=9 --stream-count=1 --stream-to=test.raw