Jetson ORIN-NX camera capture error

Hi NV team:

I use MAX9296+MAX96705+ar0231 in R35.2.1 with ORIN-NX16. My camera output format is YUV422 8bit.

I have done my drivers,and try to capture the camera with command:

gst-launch-1.0 v4l2src device=/dev/video0 ! 'video/x-raw,format=UYVY,width=1920,height=1080' ! videoconvert ! fpsdisplaysink video-sink=xvimagesink sync=false

Kernel log:

[ 1640.613852] tegra194-vi5 15c10000.vi: no reply from camera processor
[ 1640.614037] tegra194-vi5 15c10000.vi: uncorr_err: request timed out after 2500 ms
[ 1640.614183] tegra194-vi5 15c10000.vi: err_rec: attempting to reset the capture channel
[ 1640.617314] tegra194-vi5 15c10000.vi: unexpected response from camera processor
[ 1640.617540] tegra194-vi5 15c10000.vi: vi capture setup failed
[ 1640.617648] tegra194-vi5 15c10000.vi: fatal: error recovery failed


Boot the clock for debug and enable trace for more information

sudo su
echo 1 > /sys/kernel/debug/bpmp/debug/clk/vi/mrq_rate_locked
echo 1 > /sys/kernel/debug/bpmp/debug/clk/isp/mrq_rate_locked
echo 1 > /sys/kernel/debug/bpmp/debug/clk/nvcsi/mrq_rate_locked
cat /sys/kernel/debug/bpmp/debug/clk/vi/max_rate |tee /sys/kernel/debug/bpmp/debug/clk/vi/rate
cat /sys/kernel/debug/bpmp/debug/clk/isp/max_rate | tee  /sys/kernel/debug/bpmp/debug/clk/isp/rate
cat /sys/kernel/debug/bpmp/debug/clk/nvcsi/max_rate | tee /sys/kernel/debug/bpmp/debug/clk/nvcsi/rate

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
cat /sys/kernel/debug/tracing/trace

Here is the camera debug logs:

st-plugin-scan-3475    [001] ....   200.260905: tegra_channel_open: vi-output, imx185 30-0040
 gst-plugin-scan-3475    [001] ....   200.261001: tegra_channel_close: vi-output, imx185 30-0040
 gst-plugin-scan-3475    [001] ....   200.261009: tegra_channel_open: vi-output, imx185 30-001c
 gst-plugin-scan-3475    [001] ....   200.261080: tegra_channel_close: vi-output, imx185 30-001c
 gst-plugin-scan-3475    [001] ....   200.261086: tegra_channel_open: vi-output, imx185 31-0040
 gst-plugin-scan-3475    [001] ....   200.261157: tegra_channel_close: vi-output, imx185 31-0040
 gst-plugin-scan-3475    [001] ....   200.261163: tegra_channel_open: vi-output, imx185 31-001e
 gst-plugin-scan-3475    [001] ....   200.261174: tegra_channel_close: vi-output, imx185 31-001e
  gst-launch-1.0-3474    [003] ....   200.338184: tegra_channel_open: vi-output, imx185 30-0040
  gst-launch-1.0-3474    [003] ....   200.338280: tegra_channel_close: vi-output, imx185 30-0040
  gst-launch-1.0-3474    [003] ....   200.338289: tegra_channel_open: vi-output, imx185 30-001c
  gst-launch-1.0-3474    [003] ....   200.338358: tegra_channel_close: vi-output, imx185 30-001c
  gst-launch-1.0-3474    [003] ....   200.338365: tegra_channel_open: vi-output, imx185 31-0040
  gst-launch-1.0-3474    [003] ....   200.338434: tegra_channel_close: vi-output, imx185 31-0040
  gst-launch-1.0-3474    [003] ....   200.338441: tegra_channel_open: vi-output, imx185 31-001e
  gst-launch-1.0-3474    [003] ....   200.338451: tegra_channel_close: vi-output, imx185 31-001e
  gst-launch-1.0-3474    [003] ....   200.350882: tegra_channel_open: vi-output, imx185 30-0040
    v4l2src0:src-3477    [002] ....   200.358654: tegra_channel_set_power: imx185 30-0040 : 0x1
    v4l2src0:src-3477    [002] ....   200.358662: camera_common_s_power: status : 0x1
    v4l2src0:src-3477    [002] ....   200.359082: tegra_channel_set_power: 13e40000.host1x:nvcsi@15a00000- : 0x1
    v4l2src0:src-3477    [002] ....   200.359085: csi_s_power: enable : 0x1
    v4l2src0:src-3477    [002] ....   200.359632: tegra_channel_capture_setup: vnc_id 0 W 1920 H 1080 fmt 13
    v4l2src0:src-3477    [003] ....   200.365380: tegra_channel_set_stream: enable : 0x1
    v4l2src0:src-3477    [003] ....   200.367120: tegra_channel_set_stream: 13e40000.host1x:nvcsi@15a00000- : 0x1
    v4l2src0:src-3477    [003] ....   200.367123: csi_s_stream: enable : 0x1
    v4l2src0:src-3477    [003] ....   200.367494: tegra_channel_set_stream: imx185 30-0040 : 0x1
     kworker/1:3-576     [001] ....   200.415179: rtcpu_string: tstamp:7676297143 id:0x04010000 str:"VM0 activating."
     kworker/1:3-576     [001] ....   200.415182: rtcpu_vinotify_event: tstamp:7676739097 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:245645175328 data:0x399d580010000000
     kworker/1:3-576     [001] ....   200.415183: rtcpu_vinotify_event: tstamp:7676739238 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:245645181760 data:0x0000000031000001
     kworker/1:3-576     [001] ....   200.415183: rtcpu_vinotify_event: tstamp:7676739399 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:245645222112 data:0x399d550010000000
     kworker/1:3-576     [001] ....   200.415183: rtcpu_vinotify_event: tstamp:7676739530 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:245645228672 data:0x0000000031000002
     kworker/1:3-576     [001] ....   200.471175: rtcpu_nvcsi_intr: tstamp:7678074116 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000008
     kworker/1:3-576     [001] ....   200.471177: rtcpu_nvcsi_intr: tstamp:7678075326 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000008
     kworker/1:3-576     [001] ....   200.471177: rtcpu_nvcsi_intr: tstamp:7678085003 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000008
     kworker/1:3-576     [001] ....   200.471178: rtcpu_nvcsi_intr: tstamp:7678087424 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000008
     kworker/1:3-576     [001] ....   200.471178: rtcpu_nvcsi_intr: tstamp:7678089844 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000008
     kworker/1:3-576     [001] ....   200.471178: rtcpu_nvcsi_intr: tstamp:7678092263 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000008
     kworker/1:3-576     [001] ....   200.471178: rtcpu_nvcsi_intr: tstamp:7678093473 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000008
     kworker/1:3-576     [001] ....   200.471179: rtcpu_nvcsi_intr: tstamp:7678097104 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000008
     kworker/1:3-576     [001] ....   200.471179: rtcpu_nvcsi_intr: tstamp:7678101943 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000008
     kworker/1:3-576     [001] ....   200.471179: rtcpu_nvcsi_intr: tstamp:7678106781 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000008
     kworker/1:3-576     [001] ....   200.471180: rtcpu_nvcsi_intr: tstamp:7678109202 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000008
     kworker/1:3-576     [001] ....   200.471180: rtcpu_nvcsi_intr: tstamp:7678111620 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000008
     kworker/1:3-576     [001] ....   200.471180: rtcpu_nvcsi_intr: tstamp:7678114040 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000008
     kworker/1:3-576     [001] ....   200.471180: rtcpu_nvcsi_intr: tstamp:7678115248 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000008
     kworker/1:3-576     [001] ....   200.471181: rtcpu_nvcsi_intr: tstamp:7678123718 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000008
     kworker/1:3-576     [001] ....   200.471181: rtcpu_nvcsi_intr: tstamp:7678128557 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000008
     kworker/1:3-576     [001] ....   200.471181: rtcpu_nvcsi_intr: tstamp:7678130977 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000008
     kworker/1:3-576     [001] ....   200.471182: rtcpu_nvcsi_intr: tstamp:7678132188 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000008
     kworker/1:3-576     [001] ....   200.471182: rtcpu_nvcsi_intr: tstamp:7678135816 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000008
     kworker/1:3-576     [001] ....   200.471182: rtcpu_nvcsi_intr: tstamp:7678137026 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000008
     kworker/1:3-576     [001] ....   200.471182: rtcpu_nvcsi_intr: tstamp:7678145496 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000008
     kworker/1:3-576     [001] ....   200.471183: rtcpu_nvcsi_intr: tstamp:7678152754 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000008
     kworker/1:3-576     [001] ....   200.471183: rtcpu_nvcsi_intr: tstamp:7678153963 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000008
     kworker/1:3-576     [001] ....   200.471183: rtcpu_nvcsi_intr: tstamp:7678158805 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000008
     kworker/1:3-576     [001] ....   200.471183: rtcpu_nvcsi_intr: tstamp:7678167272 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000008
     kworker/1:3-576     [001] ....   200.471184: rtcpu_nvcsi_intr: tstamp:7678170902 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000008
     kworker/1:3-576     [001] ....   200.471184: rtcpu_nvcsi_intr: tstamp:7678175741 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x000000


hello hang.zheng,

please seea-also developer guide for the SerDes Pixel Clock session,
please note that… skew calibration is required if sensor or deserializer is using DPHY, and the output data rate is > 1.5Gbps.

according to tracing logs.
there’s PHY interrupts,

     kworker/1:3-576     [001] ....   200.471177: rtcpu_nvcsi_intr: tstamp:7678075326 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000008
     kworker/1:3-576     [001] ....   200.471177: rtcpu_nvcsi_intr: tstamp:7678085003 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000008

this failure reported there’s LP sequence error detected on data-lane.
typically, there should be sequence follow by… LP11->LP01->LP00->LP11, please examine your signal is following MIPI spec.

Hi JerryChang :
Thanks for you reply.

please seea-also developer guide for the SerDes Pixel Clock session,
please note that… skew calibration is required if sensor or deserializer is using DPHY, and the output data rate is > 1.5Gbps.

A : The camera output data rate is 300Mbps.

this failure reported there’s LP sequence error detected on data-lane.
typically, there should be sequence follow by… LP11->LP01->LP00->LP11, please examine your signal is following MIPI spec.

A: The same board, Xavier-NX is good, and ORIN-NX has an error. Are Xavier-NX and ORIN-NX the same in camera?

hello hang.zheng,

there’s difference of the polarity swap, you may see-also Topic 244037 for reference.
thanks

Thanks JerryChang , I’ll try it .

Hi JerryChang:

I have another question , are Xavier and ORIN the same in camera?

hello hang.zheng,

there’re not.
please refer to Technical Specifications for comparison.

Xavier and Orin they’re sharing the same VI driver. (i.e. VI-5)
if you have the camera sensor worked on Xavier series, it’ll works by porting the device tree to Orin series.

however, Xavier and Orin they’re using different ISP engine. for image quality related tuning stuffs, you’ll need to based-on Orin series to tune the IQ again.

hope this answer your questions.

Hi JerryChang:

Thanks for you reply! The explanation of this problem is very clear,thank you!

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