Issue when probing devices

[ikram.el.moussaoui]

Hello,

Iam currently facing an issue when i probe my two devices. I want to enable virtual channels, here are my specs:

• Imager: AR0820

• Serializer: MAX9295

• Deserializer: MAX9296

• Jetson AGX Orin

• Jetpack 5.1.3 / L4T 35.5.0

I use proxy addresses for my devices 0x1b and 0x1c with a physical address of 0x10.
The issue is that when i probe the first device 0x1b , it choses well the right device which is ar0820 30-001b. Here is a print of the logs to clarify :

Now the issue is with the second device 0x1c, it detects a sensor ar0820 30-001b to probe for ar0820 30-001c . As shown in the logs here :

For media-ctl seems to be good :

And for v4l2-ctl not setting the devices well:

My question is that why we do have this mismatch between v4l2-ctl and media-ctl ?

My device tree :

tegra234-p3737-0000-camera-ar0820-a00.dtsi.txt (5.8 KB)
tegra234-camera-ar0820-a00.dtsi.txt (18.2 KB)

Thanks

[JerryChang]

hello ikram.el.moussaoui,

@ikram.el.moussaoui

it detects a sensor ar0820 30-001b to probe for ar0820 30-001c .

please examine the device tree from your system.
for instance, /proc/device-tree/i2c@3180000/tca9546@70/i2c@0/
do you have those two camera nodes (ar0820_a@1b and ar0820_b@1c) declare to the device-tree hierarchy correctly?
besides, are you able to fetch the stream?

[ikram.el.moussaoui]

Hello,
Thanks for the reply.
As shown on my device tree above, i use both nodes (ar0820_a@1b and ar0820_b@1c )
For the stream, iam not able to fetch it.

[JerryChang]

hello ikram.el.moussaoui,

please share the complete logs for reference.
besides, please check with Applications Using V4L2 IOCTL Directly to use V4L2 IOCTL to verify basic camera functionality.

[ikram.el.moussaoui]

Hello @JerryChang

Here is the output of both commands

[JerryChang]

hello ikram.el.moussaoui,

had you verified this on previous Jetpack release version?
please gather the complete kernel logs, (i.e. $ dmesg > klogs.txt) and, attach it as single text file for reference.

besides,
please refer to Topic 284939 to apply pre-built update to enable infinite timeout property.
you may see-also developer guide, for the steps running with infinite timeouts while waiting for camera frames.

[ikram.el.moussaoui]

Hello @JerryChang ,
For the previous Jetpack version, did not try it because we already switched to the new version * Jetpack 5.1.3 / L4T 35.5.0

Here are the logs :

logs.txt (127.5 KB)
trace_argus.txt (21.9 KB)

Thanks

[JerryChang]

hello ikram.el.moussaoui,

you’ve two camera node register to linux kernel according to the logs.

[   12.722131] tegra-camrtc-capture-vi tegra-capture-vi: subdev ar0820 30-001b bound
[   12.731865] ar0820 30-001b: Detected AR0820 sensor
[   12.879845] tegra-camrtc-capture-vi tegra-capture-vi: subdev ar0820 30-001c bound
[   12.888868] ar0820 30-001c: Detected AR0820 sensor

there’re lots of logs for register writing when you’ve camera enabled.
I don’t see any error reported, then, you’ve terminate the stream, i.e. ar0820 30-001c: ar0820_power_off
besides, by checking your tracing logs, it might be issue on GMSL chip. since there’s no SOF nor EOF has detected.