MAX 9296/MAX 9295 AR0233 GMSL Camera are not visible in the system. No probe in dmesg Jetson Orin Nano

Robotics & Edge Computing Jetson Systems Jetson Orin Nano
,
1

Hello. I have a Quanta J AR0233 GMSL2 car camera. I rebuilt the kernel and installed the drivers. I enabled DTS overlay and connected a MAX 9296 CSI to the CAM0 connector on the Waveshare Carrier Board, but I don’t see a probe of AR0233 or a probe of MAX9296 in dmesg. Please give your suggestions. Also max9296 is https://www.waveshare.com/wiki/MAX9296-GMSL-Camera-Board?srsltid=AfmBOor0J_Z8UOQLAGpl3RUZwQ7VGnn6o2L-SRk2NPUNRAdpY_MxAeXF

jetpack 6.2 l4t 36.4 3

i2cdetect.txt (499 Bytes)

sudo i2cdetect -y -r 2
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: – – – – – – – –
10: – – – – – – – – – – – – – – – –
20: – – – – – – – – – – – – – – – –
30: – – – – – – – – – – – – – – – –
40: – – – – – – – – 48 – – – – – – –
50: – – – – – – – – – – – – – – – –
60: – – – – – – – – – – – – – – – –
70: – – – – – – – –

jetson@tegra-ubuntu:~$ lsmod | grep ar0233
ar0233 16384 0
max9295 16384 1 ar0233
max9296 20480 1 ar0233
v4l2_fwnode 20480 2 tegra_camera,ar0233
videodev 270336 5 v4l2_async,videobuf2_v4l2,tegra_camera,videobuf2_common,ar0233
mc 61440 5 videodev,videobuf2_v4l2,tegra_camera,videobuf2_common,ar0233

ar0233.c.txt (12.3 KB)

ar0233-max9296-camera-overlay.dts.txt (4.8 KB)

max9296.c.txt (21.4 KB)

max9295.c.txt (13.2 KB)

3

*** Please note that this reply is generated by LLM automatically ***

Based on the provided information, it appears that you are trying to connect a Quanta J AR0233 GMSL2 car camera to a Waveshare Carrier Board using a MAX 9296 CSI. You have rebuilt the kernel, installed the drivers, and enabled the DTS overlay, but you are not seeing a probe of AR0233 or MAX9296 in dmesg.

Here are a few suggestions to help you troubleshoot the issue:

  1. Verify the connections: Double-check that the MAX 9296 CSI is properly connected to the CAM0 connector on the Waveshare Carrier Board. Make sure that the connections are secure and not loose.
  2. Check the DTS overlay: Ensure that the DTS overlay is correctly configured and enabled. You can check the DTS overlay configuration by running the command dtc -I fs /sys/firmware/devicetree/base.
  3. Verify the kernel configuration: Check that the kernel configuration is correct and that the necessary modules are loaded. You can check the kernel configuration by running the command zcat /proc/config.gz.
  4. Check the device tree: Verify that the device tree is correctly configured for the MAX 9296 CSI and the AR0233 camera. You can check the device tree by running the command dtc -I fs /sys/firmware/devicetree/base.
  5. Check the I2C bus: The MAX 9296 CSI uses the I2C bus to communicate with the camera. Check that the I2C bus is correctly configured and that the necessary modules are loaded. You can check the I2C bus configuration by running the command i2cdetect -y 1.
  6. Check the camera driver: Verify that the camera driver is correctly configured and loaded. You can check the camera driver by running the command lsmod | grep ar0233.
  7. Check the kernel logs: Check the kernel logs for any error messages related to the camera or the MAX 9296 CSI. You can check the kernel logs by running the command dmesg | grep -i error.

Comparing the provided information with the Jetson Orin Nano documentation, it appears that the MAX 9296 CSI is a compatible camera module for the Waveshare Carrier Board. However, the AR0233 camera is not a standard camera module for the Jetson Orin Nano.

To further troubleshoot the issue, you may want to try the following:

  • Check the Waveshare Carrier Board documentation for any specific instructions on connecting the MAX 9296 CSI and the AR0233 camera.
  • Check the NVIDIA Jetson Orin Nano documentation for any specific instructions on connecting camera modules.
  • Try using a different camera module that is known to be compatible with the Jetson Orin Nano.
  • Try using a different CSI connector on the Waveshare Carrier Board.

I hope these suggestions help you troubleshoot the issue and get the camera working correctly.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

4

Hello @TheSevaOne,

It seems to me that your driver is not even loading.
Mostly because when a driver’s compatible matches the DTB node’s compatible, the driver gets loaded and the i2c address gets owned by the driver. And when you run the i2cdetect command you should see UU instead of the address.

A few questions:

  1. Can you verify your DTB overlay is applying by checking /proc/device-tree?
  2. Can you confirm your driver and dtb node match their compatibles ?
  3. Can you provide the output of dmesg | grep ar0233?

best,
Andrew
Embedded Software Engineer at ProventusNova

2 Likes
6

IMG_8415
IMG_84151179×517 180 KB

Here is dmesg