The connection of Jetson Orin NX to the streaming camera failed

Robotics & Edge Computing Jetson Systems Jetson Orin NX
1

I’m trying to interface an camera. Can anyone give any insight into this error?

kworker/4:1-11285   [004] ....  1186.329937: rtcpu_string: tstamp:37844597383 id:0x04010000 str:"VM0 deactivating."

        v4l2-ctl-29623   [002] ....  1200.199442: tegra_channel_open: vi-output, ORB mux 2-001a

        v4l2-ctl-29623   [002] ....  1200.201167: tegra_channel_set_power: ORB mux 2-001a : 0x1

        v4l2-ctl-29623   [002] ....  1200.201169: tegra_channel_set_power: 13e40000.host1x:nvcsi@15a00000- : 0x1

        v4l2-ctl-29623   [002] ....  1200.201171: csi_s_power: enable : 0x1

        v4l2-ctl-29623   [002] ....  1200.201263: tegra_channel_capture_setup: vnc_id 0 W 1280 H 960 fmt 5

        v4l2-ctl-29623   [001] ....  1200.207135: tegra_channel_set_stream: enable : 0x1

     kworker/4:1-11285   [004] ....  1200.210018: rtcpu_string: tstamp:38278483431 id:0x04010000 str:"VM0 activating."

        v4l2-ctl-29623   [002] ....  1200.211606: tegra_channel_set_stream: 13e40000.host1x:nvcsi@15a00000- : 0x1

        v4l2-ctl-29623   [002] ....  1200.211609: csi_s_stream: enable : 0x1

        v4l2-ctl-29623   [002] ....  1200.211899: tegra_channel_set_stream: ORB mux 2-001a : 0x1

     kworker/4:1-11285   [004] ....  1200.265941: rtcpu_vinotify_event: tstamp:38278928281 cch:0 vi:1 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:1224915226240 data:0x759e300010000000

     kworker/4:1-11285   [004] ....  1200.265943: rtcpu_vinotify_event: tstamp:38278928440 cch:0 vi:1 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:1224915232704 data:0x0000000031000001

     kworker/4:1-11285   [004] ....  1200.265943: rtcpu_vinotify_event: tstamp:38278928597 cch:0 vi:1 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:1224915273056 data:0x759e2d0010000000

     kworker/4:1-11285   [004] ....  1200.265944: rtcpu_vinotify_event: tstamp:38278928731 cch:0 vi:1 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:1224915279648 data:0x0000000031000002

     kworker/4:1-11285   [004] ....  1200.321937: rtcpu_nvcsi_intr: tstamp:38281971421 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:2 vc:14 status:0x00000002

     kworker/4:1-11285   [004] ....  1200.321939: rtcpu_nvcsi_intr: tstamp:38281971421 class:CORRECTABLE_ERR type:STREAM_VC phy:0 cil:0 st:2 vc:14 status:0x00000002

     kworker/4:1-11285   [004] ....  1200.321939: rtcpu_nvcsi_intr: tstamp:38281972003 class:GLOBAL type:STREAM_NOVC phy:0 cil:0 st:2 vc:0 status:0x00000001

     kworker/4:1-11285   [004] ....  1200.321940: rtcpu_nvcsi_intr: tstamp:38281972003 class:CORRECTABLE_ERR type:STREAM_NOVC phy:0 cil:0 st:2 vc:0 status:0x00000001

     kworker/4:1-11285   [004] ....  1200.321940: rtcpu_n vcsi_intr: tstamp:38281972663 class:GLOBAL type:STREAM_NOVC phy:0 cil:0 st:2 vc:0 status:0x00000001

     kworker/4:1-11285   [004] ....  1200.321940: rtcpu_nvcsi_intr: tstamp:38281972663 class:CORRECTABLE_ERR type:STREAM_NOVC phy:0 cil:0 st:2 vc:0 status:0x00000001

     kworker/4:1-11285   [004] ....  1200.321940: rtcpu_nvcsi_intr: tstamp:38281973326 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:2 vc:2 status:0x0000000a

     kworker/4:1-11285   [004] ....  1200.321941: rtcpu_nvcsi_intr: tstamp:38281973326 class:CORRECTABLE_ERR type:STREAM_VC phy:0 cil:0 st:2 vc:2 status:0x0000000a

     kworker/4:1-11285   [004] ....  1200.321941: rtcpu_nvcsi_intr: tstamp:38281974101 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:2 vc:2 status:0x0000000a

     kworker/4:1-11285   [004] ....  1200.321941: rtcpu_nvcsi_intr: tstamp:38281974101 class:CORRECTABLE_ERR type:STREAM_VC phy:0 cil:0 st:2 vc:2 status:0x0000000a

     kworker/4:1-11285   [004] ....  1200.321941: rtcpu_nvcsi_intr: tstamp:38281974699 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:2 vc:2 status:0x00000008

     kworker/4:1-11285   [004] ....  1200.321942: rtcpu_nvcsi_intr: tstamp:38281974699 class:CORRECTABLE_ERR type:STREAM_VC phy:0 cil:0 st:2 vc:2 status:0x00000008

     kworker/4:1-11285   [004] ....  1200.321942: rtcpu_nvcsi_intr: tstamp:38281975367 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:2 vc:2 status:0x0000000a

     kworker/4:1-11285   [004] ....  1200.321942: rtcpu_nvcsi_intr: tstamp:38281975367 class:CORRECTABLE_ERR type:STREAM_VC phy:0 cil:0 st:2 vc:2 status:0x0000000a

     kworker/4:1-11285   [004] ....  1200.321942: rtcpu_nvcsi_intr: tstamp:38281975984 class:GLOBAL type:STREAM_NOVC phy:0 cil:0 st:2 vc:0 status:0x00000001

     kworker/4:1-11285   [004] ....  1200.321943: rtcpu_nvcsi_intr: tstamp:38281975984 class:CORRECTABLE_ERR type:STREAM_NOVC phy:0 cil:0 st:2 vc:0 status:0x00000001

     kworker/4:1-11285   [004] ....  1200.321943: rtcpu_nvcsi_intr: tstamp:38281976666 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:2 vc:2 status:0x0000000a

     kworker/4:1-11285   [004] ....  1200.321943: rtcpu_nvcsi_intr: tstamp:38281976666 class:CORRECTABLE_ERR type:STREAM_VC phy:0 cil:0 st:2 vc:2 status:0x0000000a

     kworker/4:1-11285   [004] ....  1200.321944: rtcpu_vinotify_error: tstamp:38281977811 cch:-1 vi:1 tag:CSIMUX_STREAM channel:0x00 frame:32 vi_tstamp:1225023144768 data:0x0000000000000100

     kworker/4:1-11285   [004] ....  1200.321944: rtcpu_nvcsi_intr: tstamp:38281977313 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:2 vc:2 status:0x0000000a

     kworker/4:1-11285   [004] ....  1200.321945: rtcpu_nvcsi_intr: tstamp:38281977313 class:CORRECTABLE_ERR type:STREAM_VC phy:0 cil:0 st:2 vc:2 status:0x0000000a

     kworker/4:1-11285   [004] ....  1200.321945: rtcpu_nvcsi_intr: tstamp:38281977951 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:2 vc:2 status:0x0000000a
3

hello 1173873393,

may I know…
(1) which Jetpack release version you’re now working with?
(2) what’s your camera sensor types, for instance, is it a bayer raw, or YUV sensor?
(3) what’s your test pipeline?

beisdes,
had you validate this sensor driver on any previous Jetpack release?
please refer to Camera Driver Porting for driver examination.
you may see-also Debugging Tips section for troubleshooting.

4

Thank you for your reply.

  1. We are using Jetpack 5.1.2.
  2. The camera transmits RGB and the format is YUV422-8bit. It is connected to Orin NX through MAX9296A + MAX9295D.
  3. We conducted tests using V4L2.
    Additionally, we have used this camera on AGX Xavier with version 5.0.2 and AGX ORIN with version 6.0, and it worked normally.
6

[quote=“1173873393, post:5, topic:316075, full:true”]

     kworker/4:1-11285   [004] ....  1200.321943: rtcpu_nvcsi_intr: tstamp:38281975984 class:CORRECTABLE_ERR type:STREAM_NOVC phy:0 cil:0 st:2 vc:0 status:0x00000001

     kworker/4:1-11285   [004] ....  1200.321943: rtcpu_nvcsi_intr: tstamp:38281976666 class:GLOBAL type:STREAM_VC phy:0 cil:0 st:2 vc:2 status:0x0000000a

     kworker/4:1-11285   [004] ....  1200.321943: rtcpu_nvcsi_intr: tstamp:38281976666 class:CORRECTABLE_ERR type:STREAM_VC phy:0 cil:0 st:2 vc:2 status:0x0000000a

What do “status:0x0000000a” and “status:0x00000001” indicate in terms of errors?

7

hello 1173873393,

there’re several camera software bugs within early JP-5.x release version.
is it possible for moving forward to the latest JP-5.1.4 (r35.6.0) since it has include some bug fixes.

or…
you may see-also Topic 268833 to apply camera firmware to update deskew algorithm, and also stability fixes on JP-5.1.2 for verification.

they’re streaming issues.
for instance, STREAM_NOVC with error code 0x1 means multi bit error in the DPHY packet header has detected.

8

Okay, but the rate we’re using is not greater than 1.5G. Is there an enumeration table showing what error each bit of the status code represents?

9

no, there’s no public documentation for sharing to analysis the logs.

11

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