Understanding err_data 0 in tegra-camrtc-capture-vi: corr_err Logs

[jyhwang1]

Hello,

I am currently debugging an issue with my Tegra-based camera setup, and I have noticed frequent log messages like the following:

yaml

코드 복사

[tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 0]

These logs appear repeatedly during operation and always include err_data 0. However, I am not sure what err_data 0 specifically indicates or why these messages are being generated.

Could anyone provide insights into:

1. What err_data 0 signifies in this context?
2. Potential causes or scenarios that might trigger these logs.
3. Any recommended steps to debug or resolve this issue.

Thank you in advance for your help!

[JerryChang]

hello jyhwang1,

please visit Jetson Linux Archive, for instance, jetson-linux-r3640 to download [Driver Package (BSP) Sources] for the public release source package.

here’s discarding frame error report by VI engine.
discarding frame it’s due to unsuccessful capture state, it’s VI dropping frames and issue a requeue for new buffers.
as you can see…
$public_sources/r36.4.0/Linux_for_Tegra/source/kernel_src/nvidia-oot/drivers/media/platform/tegra/camera/vi/vi5_fops.c

static void vi5_capture_dequeue(...)
{
...
        } else if (descr->status.status != CAPTURE_STATUS_SUCCESS) {
        ...
            } else {
                    dev_warn(vi->dev,
                     "corr_err: discarding frame %d, flags: %d, "
                     "err_data %d\n",
                     descr->status.frame_id, descr->status.flags,
                     descr->status.err_data);
                   frame_err = true;

you may see-also CaptureStatusCodes and CaptureStatusFlags from below for more details.
the err_data content it depends on the value of CaptureStatusCodes.
$public_sources/r36.4.0/Linux_for_Tegra/source/kernel_src/nvidia-oot/include/soc/tegra/camrtc-capture.h
let me give you another example, i.e. err_data=4194404.
it represents below…
CAPTURE_STATUS_NOTIFY_BIT_CSIMUX_FRAME_PXL_ENABLE_FAULT
CAPTURE_STATUS_NOTIFY_BIT_CSIMUX_FRAME_RESERVED_1
CAPTURE_STATUS_NOTIFY_BIT_CSIMUX_STREAM_FIFO_OVERFLOW

anyways,
please examine your sensor pixel clock settings, it must be set correctly to avoid potential issues.
please see-also Camera Driver Porting if you’ve porting drivers from previous Jetpack release version.
you may dig into Debugging Tips section for troubleshooting.

[jyhwang1]

Thank you for your detailed response.
Based on your explanation, it is clear that an err_data value of 0 is unrelated to specific errors, and I only need to debug the reason why the capture status was unsuccessful, leading to the VI discarding the frame and requesting a new buffer.

[JerryChang]

hello jyhwang1,

please debug the capture status.
you may also try to comment-out frame_err = true for quick testing your software capture pipeline.

[jyhwang1]

Yes, I will check it. Thank you so much!!