ISP driver crashed when launching 12 cameras

Hi

I am trying to port the camera driver to launch 12 camera modules on Xavier-Industrial platform.
When I validate the driver behavior for 4 and 8 cameras, everything is good, but some crashed messages occurs when testing 12 cameras.

Below files are the crashed log and my device tree settings.
Please help to provide me some ideas.

tegra194-p2822-camera-0233.dtsi (50.9 KB)
dmesg_isp_crash_20230719.log (134.4 KB)

may I know which Jetpack release you’re working with? you may check release tag, $ cat /etc/nv_tegra_release for confirmation.
besides, please also narrow down this by refer to Applications Using V4L2 IOCTL Directly for using V4L2 IOCTL to verify basic camera functionality.

Hi @JerryChang

Regarding the release, it is 35.2.1.

R35 (release), REVISION: 2.1, GCID: 32413640, BOARD: t186ref, EABI: aarch64, DATE: Tue Jan 24 23:38:33 UTC 2023

Regarding the V4L2 IOCTL commands, I think it is impossible because the device nodes, /dev/video*, are not generated since nvcsi@15a00000 is not probed successfully.

hello frank_cf_weng,

please check $ ls /dev/video*, it should register video nodes since kernel has reported Detected AR0233 sensor during its initialization stage.
furthermore, please also share the camera device tree settings within tegra-camera-platform {} for checking.

Hi @JerryChang

Regarding the sensor detection, yes I can probe the device from camera driver, but the device node can not be generated because the subdev should be relative to nvcsi@15a00000, and the system fails to probe nvcsi.
And I did check and confirmed the device nodes did not exist.

Regarding the device tree settings, please refer to below file.
tegra-camera-platform.dtsi (7.6 KB)

The log to show ‘Detected AR0233 sensor’ just means that the initialization of the module via I2C bus is success.

Hi @JerryChang

From the log, I notice that tegra_camera_isomgr_register shows some errors for isomgr client of camera before crashed messages, and it seems to be relative to the 15c10000.vi probe.
Is it related with this issue?

Hi @JerryChang

Regarding the device tree settings for tegra-camera-platform, I config num_csi_lanes to 24 for 12 camera modules and some crashed messages occur.
However, after changing the value to 16 from 24, I can see the camera nodes without crashed messages, but I don’t know what it means…

Can you give me some suggestions?

wistron@ubuntu:~$ ls /dev/video* -l
crw-rw----+ 1 root video 81, 0 九 8 17:58 /dev/video0
crw-rw----+ 1 root video 81, 14 九 8 17:58 /dev/video1
crw-rw----+ 1 root video 81, 32 九 8 17:59 /dev/video10
crw-rw----+ 1 root video 81, 34 九 8 17:59 /dev/video11
crw-rw----+ 1 root video 81, 16 九 8 17:58 /dev/video2
crw-rw----+ 1 root video 81, 18 九 8 17:58 /dev/video3
crw-rw----+ 1 root video 81, 20 九 8 17:58 /dev/video4
crw-rw----+ 1 root video 81, 22 九 8 17:58 /dev/video5
crw-rw----+ 1 root video 81, 24 九 8 17:58 /dev/video6
crw-rw----+ 1 root video 81, 26 九 8 17:59 /dev/video7
crw-rw----+ 1 root video 81, 28 九 8 17:59 /dev/video8
crw-rw----+ 1 root video 81, 30 九 8 17:59 /dev/video9

num_csi_lanes settings within tegra-camera-platform{} is the total active lanes for your system. and… the maximum configuration is 16-lane.

@JerryChang

To confirm with you, then the num_csi_lanes of below capture should be 4?
Screenshot from 2023-07-20 14-50-07

let’s taking this as an example,
you’ve enable 2 CSI bricks, there’re total 8-lane enabled for your SerDes chip use-case.
hence, you should configured num_csi_lanes = 8; accordingly.

1 Like

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