Camera模组接入驱动配置问题

hello,最近在接入一个5M的yuv格式的camera模组:

    sensor输出格式 2592*1944 YUYV 30fps
    camera链路是ox5b → max9295 → max9296 → agx orin

我的jetson驱动配置如下:

mode4 {
    mclk_khz = "24000";
    num_lanes = "4";
    tegra_sinterface = "serial_a";
    vc_id = "3";
    discontinuous_clk = "yes";
    dpcm_enable = "false";
    cil_settletime = "0";
    dynamic_pixel_bit_depth = "16";
    csi_pixel_bit_depth = "16";
    mode_type = "yuv";
    pixel_phase = "yuyv";

    active_w = "2592";
    active_h = "1944";
    readout_orientation = "0";
    line_length = "3800";
    inherent_gain = "1";
    pix_clk_hz = "115500000";
    serdes_pix_clk_hz = "375000000";
};

启动camera采集时,内核capture线程反复报错:

[ 2658.338236] video4linux video1: vi-output, ar0233 10-001b corr_err: status e, flags: 0, err_data 40 notify_bits 80000000
[ 2658.371555] video4linux video1: vi-output, ar0233 10-001b corr_err: status e, flags: 0, err_data 40 notify_bits 80000000
[ 2658.404887] video4linux video1: vi-output, ar0233 10-001b corr_err: status e, flags: 0, err_data 40 notify_bits 80000000
[ 2658.438237] video4linux video1: vi-output, ar0233 10-001b corr_err: status e, flags: 0, err_data 40 notify_bits 80000000
[ 2658.471554] video4linux video1: vi-output, ar0233 10-001b corr_err: status e, flags: 0, err_data 40 notify_bits 80000000
[ 2658.504891] video4linux video1: vi-output, ar0233 10-001b corr_err: status e, flags: 0, err_data 40 notify_bits 80000000
[ 2658.538237] video4linux video1: vi-output, ar0233 10-001b corr_err: status e, flags: 0, err_data 40 notify_bits 80000000
[ 2658.571554] video4linux video1: vi-output, ar0233 10-001b corr_err: status e, flags: 0, err_data 40 notify_bits 80000000
[ 2658.604887] video4linux video1: vi-output, ar0233 10-001b corr_err: status e, flags: 0, err_data 40 notify_bits 80000000
[ 2658.638236] video4linux video1: vi-output, ar0233 10-001b corr_err: status e, flags: 0, err_data 40 notify_bits 80000000
[ 2658.671556] video4linux video1: vi-output, ar0233 10-001b corr_err: status e, flags: 0, err_data 40 notify_bits 80000000
[ 2658.704888] video4linux video1: vi-output, ar0233 10-001b corr_err: status e, flags: 0, err_data 40 notify_bits 80000000
[ 2658.738235] video4linux video1: vi-output, ar0233 10-001b corr_err: status e, flags: 0, err_data 40 notify_bits 80000000
[ 2658.771538] video4linux video1: vi-output, ar0233 10-001b corr_err: status e, flags: 0, err_data 40 notify_bits 80000000

请问,这个错误是什么原因造成的?

*** Please note that this reply is generated by LLM automatically ***

The question seems to be asking about the Jetson AGX Orin’s camera capabilities, specifically with regards to the “hello5Myuvcamera” and “jetson cameracapture” commands.

The Jetson AGX Orin is a high-performance AI computing module designed for edge AI applications, including computer vision and robotics. It features a powerful NVIDIA Ampere GPU, a quad-core ARM Cortex-A78 CPU, and 32 GB of LPDDR5 memory.

Regarding camera support, the Jetson AGX Orin has a 40-pin header and an M.2 Key E slot, which can be used to connect various camera modules. The module also supports the CSI (Camera Serial Interface) connector, which is a standard interface for connecting cameras to the Jetson module.

The “hello5Myuvcamera” command is likely a custom script or program that is designed to work with the Jetson AGX Orin’s camera module. Without more information, it’s difficult to provide a detailed explanation of what this command does.

The “jetson cameracapture” command is likely a part of the Jetson SDK, which provides a set of tools and libraries for developing camera applications on the Jetson platform. This command may be used to capture images or video from a connected camera module.

In comparison to other Jetson modules, the Jetson AGX Orin has a more powerful GPU and CPU, which makes it better suited for demanding computer vision and AI workloads. However, the camera support and capabilities are similar to other Jetson modules, such as the Jetson Xavier NX and Jetson Nano.

Here’s a summary of the camera support and capabilities of the Jetson AGX Orin and other Jetson modules:

  • Jetson AGX Orin:
    • 40-pin header
    • M.2 Key E slot
    • CSI connector (128-pin)
    • Supports various camera modules
  • Jetson Xavier NX:
    • 40-pin header
    • M.2 Key E slot
    • CSI connector (30-pin, also known as CSI Nano connector)
    • Supports various camera modules
  • Jetson Nano:
    • 40-pin header
    • M.2 Key E slot
    • CSI connector (128-pin)
    • Supports various camera modules

In summary, the Jetson AGX Orin has similar camera support and capabilities to other Jetson modules, but its more powerful GPU and CPU make it better suited for demanding computer vision and AI workloads.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

Get the trace log.

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 3 > /sys/kernel/debug/camrtc/log-level
echo 1 > /sys/kernel/debug/tracing/events/camera_common/enable
echo > /sys/kernel/debug/tracing/trace

v4l2-ctl --stream-mmap -c bypass_mode=0

cat /sys/kernel/debug/tracing/trace

rce.log (194.5 KB)

kworker/8:0-235003  [008] ....... 72336.716546: rtcpu_vinotify_event: tstamp:2261328564722 cch:0 vi:1 tag:CHANSEL_PXL_EOF channel:0x23 frame:0 vi_tstamp:72362513953120 data:0x
     kworker/8:0-235003  [008] ....... 72336.716546: rtcpu_vinotify_event: tstamp:2261328564879 cch:0 vi:1 tag:ATOMP_FRAME_DONE channel:0x23 frame:0 vi_tstamp:72362513953728 data:0
     kworker/8:0-235003  [008] ....... 72336.716547: rtcpu_vinotify_event: tstamp:2261328565015 cch:0 vi:1 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:72362513956032 data:0
     kworker/8:0-235003  [008] ....... 72336.716547: rtcpu_vinotify_event: tstamp:2261328565171 cch:0 vi:1 tag:CHANSEL_FAULT channel:0x23 frame:0 vi_tstamp:72362513962880 data:0x00
     kworker/8:0-235003  [008] ....... 72336.716547: rtcpu_vinotify_event: tstamp:2261328565307 cch:0 vi:1 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:72362513968384 data:0
     kworker/8:0-235003  [008] ....... 72336.716548: rtcpu_vinotify_event: tstamp:2261328565459 cch:0 vi:1 tag:FE channel:0x00 frame:0 vi_tstamp:72362514014912 data:0x0000000000000
     kworker/8:0-235003  [008] ....... 72336.716548: rtcpu_vinotify_event: tstamp:2261328565596 cch:0 vi:1 tag:ATOMP_FE channel:0x00 frame:0 vi_tstamp:72362514014912 data:0x0000000
     kworker/8:0-235003  [008] ....... 72336.716549: rtcpu_vinotify_event: tstamp:2261328565749 cch:0 vi:1 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:72362514019808 data:0
     kworker/8:0-235003  [008] ....... 72336.716549: rtcpu_vinotify_event: tstamp:2261328565884 cch:0 vi:1 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:72362514046944 data:0x3
     kworker/8:0-235003  [008] ....... 72336.716549: rtcpu_vinotify_event: tstamp:2261328893094 cch:0 vi:1 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:72362514067776 data:0x0
     kworker/8:0-235003  [008] ....... 72336.716549: rtcpu_vinotify_event: tstamp:2261328893231 cch:0 vi:1 tag:FS channel:0x00 frame:0 vi_tstamp:72362516843456 data:0x0000000000000
     kworker/8:0-235003  [008] ....... 72336.716550: rtcpu_vinotify_event: tstamp:2261328893389 cch:0 vi:1 tag:ATOMP_FS channel:0x00 frame:0 vi_tstamp:72362516843488 data:0x0000000
     kworker/8:0-235003  [008] ....... 72336.716550: rtcpu_vinotify_event: tstamp:2261328893524 cch:0 vi:1 tag:CHANSEL_PXL_SOF channel:0x23 frame:0 vi_tstamp:72362516857216 data:0x
     kworker/8:0-235003  [008] ....... 72336.716550: rtcpu_vinotify_event: tstamp:2261328893678 cch:0 vi:1 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:72362516858592 data:0
     kworker/8:0-235003  [008] ....... 72336.716550: rtcpu_vinotify_event: tstamp:2261329694613 cch:0 vi:1 tag:CHANSEL_PXL_EOF channel:0x23 frame:0 vi_tstamp:72362547301920 data:0x
     kworker/8:0-235003  [008] ....... 72336.716550: rtcpu_vinotify_event: tstamp:2261329694769 cch:0 vi:1 tag:ATOMP_FRAME_DONE channel:0x23 frame:0 vi_tstamp:72362547302464 data:0
     kworker/8:0-235003  [008] ....... 72336.716551: rtcpu_vinotify_event: tstamp:2261329694903 cch:0 vi:1 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:72362547304832 data:0
     kworker/8:0-235003  [008] ....... 72336.716551: rtcpu_vinotify_event: tstamp:2261329695054 cch:0 vi:1 tag:CHANSEL_FAULT channel:0x23 frame:0 vi_tstamp:72362547311744 data:0x00
     kworker/8:0-235003  [008] ....... 72336.716551: rtcpu_vinotify_event: tstamp:2261329695187 cch:0 vi:1 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:72362547317216 data:0
     kworker/8:0-235003  [008] ....... 72336.716551: rtcpu_vinotify_event: tstamp:2261329695337 cch:0 vi:1 tag:FE channel:0x00 frame:0 vi_tstamp:72362547363680 data:0x0000000000000
     kworker/8:0-235003  [008] ....... 72336.716552: rtcpu_vinotify_event: tstamp:2261329695472 cch:0 vi:1 tag:ATOMP_FE channel:0x00 frame:0 vi_tstamp:72362547363712 data:0x0000000
     kworker/8:0-235003  [008] ....... 72336.716552: rtcpu_vinotify_event: tstamp:2261329695622 cch:0 vi:1 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:72362547368608 data:0
     kworker/8:0-235003  [008] ....... 72336.716552: rtcpu_vinotify_event: tstamp:2261329695762 cch:0 vi:1 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:72362547395616 data:0x3
     kworker/8:0-235003  [008] ....... 72336.716552: rtcpu_vinotify_event: tstamp:2261329695911 cch:0 vi:1 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:72362547402144 data:0x0
     kworker/8:0-235003  [008] ....... 72336.716553: rtcpu_vinotify_event: tstamp:2261329696044 cch:0 vi:1 tag:FS channel:0x00 frame:0 vi_tstamp:72362550161664 data:0x0000000000000
     kworker/8:0-235003  [008] ....... 72336.716553: rtcpu_vinotify_event: tstamp:2261330008620 cch:0 vi:1 tag:ATOMP_FS channel:0x00 frame:0 vi_tstamp:72362550161664 data:0x0000000
     kworker/8:0-235003  [008] ....... 72336.716553: rtcpu_vinotify_event: tstamp:2261330008755 cch:0 vi:1 tag:CHANSEL_PXL_SOF channel:0x23 frame:0 vi_tstamp:72362550175424 data:0x
     kworker/8:0-235003  [008] ....... 72336.716553: rtcpu_vinotify_event: tstamp:2261330008908 cch:0 vi:1 tag:VIFALC_ACTIONLST channel:0x23 frame:0 vi_tstamp:72362550176800 data:0
     VI3-Dequeue-270093  [005] ....... 72336.732783: tegra_channel_capture_frame: sof:72362.550175424
     VI3-Dequeue-270093  [005] ....... 72336.732783: tegra_channel_capture_frame: eof:72362.580634752

rec.log contains detailed log information

Looks like lost the data value. Shouldn’t be 0x00

     kworker/8:0-235003  [008] ....... 72336.716551: rtcpu_vinotify_event: tstamp:2261329695054 cch:0 vi:1 tag:CHANSEL_FAULT channel:0x23 frame:0 vi_tstamp:72362547311744 data:0x00

这个错误具体表示是什么意思?是丢行?多行?还是其他别的错误呢?

还是说日志不全,我上传了rec.log全部的日志文件,可以阅读rec.log

PIXEL_RUNAWAY of CHANSEL_FAULT that tell receive more pixels as driver reported.

     kworker/8:0-235003  [008] ....... 72334.844546: rtcpu_vinotify_event: tstamp:2261270232287 cch:0 vi:1 tag:CHANSEL_FAULT channel:0x23 frame:0 vi_tstamp:72360647314208 data:0x0000000007980040

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.