Good morning,
we have a custom camera sensor based on Sony IMX675 that we have already succesfully integrated and tested on Jetson Orin Nano.
In order to use the camera on Jetson Orin AGX we realize a custom CSI Camera Interposer module following the document "NVIDIA Jetson AGX Xavier Series and Jetson AGX Orin Series Camera Module Hardware Design Guide ".
In order to use the TCA9548 mux and enable the camera i modified and add the attached device tree file, following the files for IMX274.
After the boot i can successfully probe the sensor, so the I2C communication should be ok, but I cannot see the /dev/video0
The system is based on Jetpack 5.1.1 L4T R35-3.1
My guess is that I need to edit some other dts file. Any suggestions about the issue?
Regards
tegra234-p3737-camera-modules.txt (8.1 KB)
tegra234-camera-imx675.txt (4.4 KB)
tegra234-p3737-0000-camera-imx675.txt (1.9 KB)
Good morning,
I moved on a bit editing the device tree files. Now I have /dev/video0 and /dev/media0
Now the problem is that I have errors when I try to capture frames with
v4l2-ctl --set-ctrl bypass_mode=0 --stream-mmap --stream-count=10 -d /dev/video0
Enabling the traces I had the following lines
_-----=> irqs-off
/ _----=> need-resched
| / _---=> hardirq/softirq
|| / _--=> preempt-depth
||| / delay
TASK-PID CPU# |||| TIMESTAMP FUNCTION
| | | |||| | |
kworker/4:2-137 [004] .... 207.453305: rtcpu_string: tstamp:7365056827 id:0x04010000 str:"VM0 deactivating."
v4l2-ctl-2287 [007] .... 223.736403: tegra_channel_open: vi-output, imx675 34-001a
v4l2-ctl-2287 [007] .... 223.755166: tegra_channel_set_power: imx675 34-001a : 0x1
v4l2-ctl-2287 [007] .... 223.755186: camera_common_s_power: status : 0x1
v4l2-ctl-2287 [007] .... 223.779909: tegra_channel_set_power: 13e40000.host1x:nvcsi@15a00000- : 0x1
v4l2-ctl-2287 [007] .... 223.779915: csi_s_power: enable : 0x1
v4l2-ctl-2287 [007] .... 223.781673: tegra_channel_capture_setup: vnc_id 0 W 2608 H 1964 fmt c4
v4l2-ctl-2287 [004] .... 223.795508: tegra_channel_set_stream: enable : 0x1
kworker/4:2-137 [004] .... 223.804652: rtcpu_string: tstamp:7876815208 id:0x04010000 str:"VM0 activating."
v4l2-ctl-2287 [004] .... 223.837090: tegra_channel_set_stream: 13e40000.host1x:nvcsi@15a00000- : 0x1
v4l2-ctl-2287 [004] .... 223.837092: csi_s_stream: enable : 0x1
v4l2-ctl-2287 [004] .... 223.837430: tegra_channel_set_stream: imx675 34-001a : 0x1
kworker/4:2-137 [004] .... 223.860595: rtcpu_vinotify_event: tstamp:7877317471 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:252064134496 data:0x399d580010000000
kworker/4:2-137 [004] .... 223.860596: rtcpu_vinotify_event: tstamp:7877317861 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:252064140992 data:0x0000000031000001
kworker/4:2-137 [004] .... 223.860596: rtcpu_vinotify_event: tstamp:7877318249 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:252064196704 data:0x399d550010000000
kworker/4:2-137 [004] .... 223.860597: rtcpu_vinotify_event: tstamp:7877318540 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:252064203264 data:0x0000000031000002
kworker/4:2-137 [004] .... 223.916590: rtcpu_nvcsi_intr: tstamp:7880708636 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x00000080
kworker/4:2-137 [004] .... 223.916591: rtcpu_nvcsi_intr: tstamp:7880710024 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x00000080
kworker/4:2-137 [004] .... 223.916591: rtcpu_nvcsi_intr: tstamp:7880710024 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x00000080
kworker/4:2-137 [004] .... 223.916591: rtcpu_nvcsi_intr: tstamp:7880718358 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x00000080
kworker/4:2-137 [004] .... 223.916591: rtcpu_nvcsi_intr: tstamp:7880744283 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x00000080
kworker/4:2-137 [004] .... 223.916592: rtcpu_nvcsi_intr: tstamp:7880748450 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x00000080
…
And the dmseg give me the following errors:
[ 223.866045] imx675 34-001a: imx675_start 0
[ 226.516724] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[ 226.525899] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[ 226.536591] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 226.544293] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=0, csi_port=0
[ 226.554945] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 226.562661] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_open: VI channel not found for stream- 0 vc- 0
[ 226.573427] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
[ 229.332701] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[ 229.341844] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[ 229.352421] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 229.360136] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=0, csi_port=0
[ 229.370793] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 229.378496] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_open: VI channel not found for stream- 0 vc- 0
[ 229.389220] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
[ 231.924649] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[ 231.933795] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[ 231.944797] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 231.952525] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=0, csi_port=0
[ 231.963183] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 231.970905] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_open: VI channel not found for stream- 0 vc- 0
[ 231.981621] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
[ 231.991302] imx675 34-001a: StopStream
Any suggestion?
Regards
hello liviolima80,
here’s PHY interrupt, the error code meant LP sequence error detected on data lane.
normally, it should follow by LP11->LP01->LP00->LP11 sequence. so, it’s more like a hardware issue.
Thank you @JerryChang ,
I found the issue. It was the “lane_polarity” field defined in sensor confoguration.
system
Closed
March 12, 2024, 7:32am
7
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.