D457 with max96712 deserializer link lock issue

[Earlyao]

Hello RealSense Team,

I am currently connecting and using a D457 camera on my Jetson Thor board. My board utilizes a MAX96712 deserializer, with a MAX20087 providing Power-over-Coax (PoC) to the camera.

While my power delivery chain is functioning correctly, the MAX96712 fails to establish a link lock with the D457's MAX9295 serializer.

I attempted to adjust the GMSL rate of the MAX96712 to 6Gbps. However, after this change:
I can write to the MAX96712 registers via I2C, but I cannot read from them.
Scanning devices on this I2C bus using i2cdetect causes the system to hang or become unresponsive.

Have you previously validated or adapted the D457 for use with the MAX96712 deserializer? Could you shed some light on what might be causing this issue?

Best regards！

[MartyG-RealSense]

Hi @Earlyao We do not validate Maxim deserializers for use with D457. To date, the only third-party deserializer that has been recommended by the RealSense team as compatible with D457 is the Leopard Imaging LI-GMSL2-IPX-DESER

https://leopardimaging.com/product/accessories/adapters-carrier-boards/for-nvidia-jetson/li-gmsl2-ipx-deser/

RealSense D457 users of GMSL have also confirmed that the LI-GMSL2-IPX-DESER Leopard Imaging product works successfully with D457.

D457 is compatible with products that contain Maxim MAX9296 de-serializer technology such as Leopard Imaging's module which contains the Maxim MAX9296A component.

[MartyG-RealSense]

My RealSense support colleagues confirmed that only the MAX9296 deserializer is currently supported. Support for the MAX96712 that you are using is already being worked on and a driver for it will be posted soon.