it’s because memory were allocated with T_R16_I. you may check TRM for more details.
are you able to enable test-pattern-generator on your Ser/Des chip?
please also contact with your bridge vendor to ask the steps to enable test-pattern-generator, it’s useful for issue narrow-down.
please also refer to below similar discussion threads for reference,
such as
you should have device tree configurations to match the actual CSI signaling,
there’s reported data type shows NvCsiDataType_YUV422_8; you should also have extend the VI support formats.
please also refer to Topic 74804, and Topic 69251 for reference, thanks
please update VI kernel drivers to extend the support formats.
for example, $L4T_Sources/r32.4.4/Linux_for_Tegra/source/public/kernel/nvidia/drivers/media/platform/tegra/camera/sensor_common.c
$L4T_Sources/r32.4.4/Linux_for_Tegra/source/public/kernel/nvidia/drivers/media/platform/tegra/camera/camera_common.c
since the reported data type shows NvCsiDataType_YUV422_8.
you may update the kernel driver to report the fourcc as 8-bit YUV,
for example,
Jerry:
camera output format is YUV422 8bit UYVY.
In videodev2.h, I think I can only choose th following V4L2_PIX_FMT_UYVY, #define V4L2_PIX_FMT_UYVY v4l2_fourcc(‘U’, ‘Y’, ‘V’, ‘Y’) /* 16 YUV 4:2:2 */
#define V4L2_PIX_FMT_HI240 v4l2_fourcc(‘H’, ‘I’, ‘2’, ‘4’) /* 8 8-bit color /
This is 8-bit color, not yuv. #define V4L2_PIX_FMT_HM12 v4l2_fourcc(‘H’, ‘M’, ‘1’, ‘2’) / 8 YUV 4:2:0 16x16 macroblocks */
This is yuv 420.
please refer to TC358840 bride driver, which could configure as UYVY or ABGR32.
the device tree settings there simply define port bindings, let driver side to handle other stuffs.
for example, $L4T_Sources/r32.4.4/Linux_for_Tegra/source/public/hardware/nvidia/platform/t19x/common/kernel-dts/t19x-common-modules/tegra194-camera-imx274-hdmi.dtsi
descr->status.status = 14 means CAPTURE_STATUS_FALCON_ERROR
(1)What does CAPTURE_STATUS_FALCON_ERROR mean?
(2)What is RTCPU?
Why many logs are from RTCPU?
Is RTCPU another soc devoted to mipi data?
For example,
kworker/0:0-4 [000] … 237.555297: rtcpu_vinotify_event: tstamp:7768803875 tag:FS channel:0x00 frame:0 vi_tstamp:7768486658 data:0x00000010
short frame errors means the image sensor outputs a smaller frame as the one registered through the V4L2 driver.
please have a try to modify active regions, you may adjust the active_h for verification.
thanks