Orin camera capture video failed on Jetpack5.0.2

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
1

Hi Experts,

I develop the max9295-max96712 camera driver with jetson agx orin in Jetpack5.0.2.

Number of CSI lanes is 4. Output data rate is 1.2Gbps per lane.

I set pix_clk_hz = “300000000” , serdes_pix_clk_hz = “1200000000” in the device-tree.

V4l2-ctl can capture video sometimes.
camera-ok.log (8.7 MB)

sometimes failed.
camera-fail.log (29.5 KB)

   kworker/4:2-114     [004] ....   894.052578: rtcpu_nvcsi_intr: tstamp:28447901588 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x06000000
     kworker/4:2-114     [004] ....   894.444199: rtcpu_nvcsi_intr: tstamp:28459117197 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x0e000000
     kworker/4:2-114     [004] ....   894.444203: rtcpu_nvcsi_intr: tstamp:28459117197 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x06000000
     kworker/4:2-114     [004] ....   894.780197: rtcpu_nvcsi_intr: tstamp:28470141659 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x0e000000
     kworker/4:2-114     [004] ....   894.780201: rtcpu_nvcsi_intr: tstamp:28470141659 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x06000000
     kworker/4:2-114     [004] ....   895.116200: rtcpu_nvcsi_intr: tstamp:28481235203 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x0e000000
     kworker/4:2-114     [004] ....   895.116203: rtcpu_nvcsi_intr: tstamp:28481235203 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x06000000
 vi-output, ov27-2832    [002] ....   895.296470: tegra_channel_capture_setup: vnc_id 0 W 1920 H 1080 fmt 13
     kworker/4:2-114     [004] ....   895.340034: rtcpu_vinotify_event: tstamp:28487100981 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:911586816352 data:0x379d580010000000
     kworker/4:2-114     [004] ....   895.340035: rtcpu_vinotify_event: tstamp:28487101139 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:911586841952 data:0x0000000031000001
     kworker/4:2-114     [004] ....   895.340036: rtcpu_vinotify_event: tstamp:28487101274 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:911586852576 data:0x379d550010000000
     kworker/4:2-114     [004] ....   895.340036: rtcpu_vinotify_event: tstamp:28487101423 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:911586888800 data:0x0000000031000002
     kworker/4:2-114     [004] ....   895.508195: rtcpu_nvcsi_intr: tstamp:28492450610 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x0e000000
     kworker/4:2-114     [004] ....   895.508197: rtcpu_nvcsi_intr: tstamp:28492450610 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x06000000
     kworker/4:2-114     [004] ....   895.848195: rtcpu_nvcsi_intr: tstamp:28503474430 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x0e000000
     kworker/4:2-114     [004] ....   895.848198: rtcpu_nvcsi_intr: tstamp:28503474430 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x06000000
     kworker/4:2-114     [004] ....   896.184186: rtcpu_nvcsi_intr: tstamp:28514568831 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x0e000000
     kworker/4:2-114     [004] ....   896.184189: rtcpu_nvcsi_intr: tstamp:28514568831 class:GLOBAL type:PHY_INThttps://forums.developer.nvidia.com/t/226574/4R0 phy:0 cil:1 st:0 vc:0 status:0x06000000

Update rce-fw follow Topic 226574,it doesn’t work.

The camera works well on jetson agx orin in Jetpack4.6.2.

3

hello liucz19,

this should be typo, Jetpack-4.6.2 doesn’t support AGX Orin.
you meant you’ve verified this camera driver on AGX Xavier, right?

that’s firmware with debug logs enabled, rest of them is identical to Jetpack-5.0.2
besides, had you apply this debug firmware to gather tracing logs? your attach log i.e. camera-fail.log. it doesn’t looks like debug flag enabled.


back-to your VI tracing logs. here shows PHY interrupts.
for example,
rtcpu_nvcsi_intr: tstamp:28581236060 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x0e000000
rtcpu_nvcsi_intr: tstamp:28581236060 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x06000000

these error indicate there’s DPHY deskew calibration has not complete on data-lane A/B.
it happened when the calibration sequence length is not long enough.

5

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