Hello,
I am evaluating the AD-GMSLCAMRPI-ADP reference design using a Raspberry Pi 4 Model B. I am using the SD card image provided on the GMSL GitHub repository by ADI, and I am using the provided user guide to setup the hardware.
The following images come from the GMSL GUI and show that the CFG pins are set properly for both the serializer and deserializer. These voltages were confirmed using a DMM and the onboard test points.
The following images show that the evaluation boards properly powered up. Also, the blinking LED indicated that the firmware on both boards' MCUs was good. However, while the LOCK LED is on on the serializer board, it is not on on the deserializer board.
According to the below image from the MAX96724 datasheet, the LOCK LED wont turn on unless all enabled links are locked in.
I only have a single MAX96717 evaluation board, which is connected to J7. J7 connects to SIOAP on the MAX96724. Therefore, I disabled all other links using the GMSL GUI as the below image shows. I changed the value in register 0x06 from 0xFF to 0xF1, enabling only link A. However, when I power cycle the evaluation board and read back register 0x06, I get 0xFF again. I believe this is why the ERRB LED stays on on the deserializer board.
The following shows the ERRB status of the MAX96724 EV board:
The Raspberry Pi successfully booted by using the provided SD card image. The following image shows the desktop, which is different from the desktop provided in the user manual. video_cfg.sh is not located on the desktop and is instead found at the /home/analog/Workspace.
The following shows the desktop I see after the raspberry pi boots:
When running video_cfg.sh, the following errors were obtained:
I used the tips provided by ADI in the user manual, but I ran into some issues. The first is that I2C bus 10 does not exist. Instead, I have I2C bus 20 and 21, and both buses have too many devices that show up as shown below. This tells me there is something wrong with the I2C bus. I made sure to remove jumpers on J18 and J19 to allow the Raspberry Pi to be the host on the bus.
Also, v4l2-ctl fails and cannot open /dev/video0:
The following image shows the kernel and OS I am using:
I was wondering what next steps I should take when debugging. Is it fine that the ERRB LED stays on on the deserializer? Is the SD card image on the GitHub page I linked correct, or is there an older version I can use that is consistent with the documentation provided by ADI?
Thank you for your time and assistance. I look forward to your response.
