ADI GMSL GUI communicates with both the Deserializer and Serializer via both I2C and UART to identify which devices may be connected and whether to communicate via i2C or UART after proper link has been established.
This article is intended to explain the hardware configuration required to use the AD-GMSL717MIPIEVK with MAX96716A in pixel mode.
An on board Teensy micro-controller acts as a bridge between GUI and the EV-kit. This article talks about establishing connection between MAX96716A-BAK-EVK# (DES with on board Teensy micro controller) and AD-GMSL717MIPI-EVK (SER with no on board Teensy microcontroller)
1) The CFG0 and CFG1 pins are hardwired on the AD-GMSL717MIPI-EVK board. Lets read the configurations and then program the DES accordingly so the GUI detects it. The user needs to read the schematic to understand the configuration of AD-GMSL717 (because it is hardwired) the GUI does not read it.
2)Below is the snippet from the schematic
If you observe CFG0 value is 0 because R2 is DNI and the R3 is connected to GND. The value of CFG1 is VDDIO because R5 is DNI.
Now lets go to data sheet and compare these values in the table11 and table 12
This confirms that theAD-GMSL717MIPI-EVK board is hardwired to
CFG0 → I2C, ROR and device address 0x80
CFG1 → COAX, 6Gbps, Pixel
Now we need to launch the GUI and select the same under CFG pin settings under MAX96716A.
Make sure the USB is connected to Deserializer and after programming the Deserializer with above CFG pin configuration the customer needs to power cycle the setup.
As soon as you launch the GUI it automatically detects the DES, there is no need to change the CFGO. Just change the CFG1 below is the example with MAX96716A and you can see the SER is detected too