GMSL2 8MP Camera Extension - How to access the deserializer registers

[CharlesDias]

Dear,

Is there a way to access the MAX96716A register? I ran the i2cdetect -y 10, but I got only the addresses 0x0C and 0x10. My module is Arducam GMSL2 8MP Camera Extension Kit for Raspberry Pi and I’m using Raspberry Pi 4B.

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

I appreciate your support.

[Dion]

Hi,
Unfortunately, we cannot access the MAX96716A register. It’s closed-source to the customers.

[CharlesDias]

Thanks for your reply.

[Vedant]

Hey Dion what is the purpose of

BP DIP switches which are present on the deserializer board

[Dion]

Hi there,

I see the switches you are referring to on your UC-C44 Rev.E board.

The BP DIP switches stand for Address Strap (Bypass) configuration. Their primary purpose is to set the I2C address of the deserializer chip on the board.

Unless you have a specific I2C address conflict, please do not move these switches. Our standard drivers and the device tree overlays for the Raspberry Pi 5 are hardcoded to look for the camera and deserializer at their factory default I2C addresses. If you flip these to “ON,” the Pi will no longer detect the camera module because the hardware will be “hidden” on a different address than the one the driver is targeting.

[MatteoUtopia]

Dear Dion,
If the deserializer I2C is closed source, what’s the device we see on bus at address 0x0c?
Moreover, I would need to access the deserializer registers to test with other GMSL2 cameras I’m designing. Isn’t there any workaround for accessing it?

Thank you