Hello,
I am posting this inquiry in regards to the Analog Devices AD-FMCLIDAR1-EBZ Lidar prototyping platform. We have been in the process of following the instructions on the Analog Devices wiki in order to run the Lidar prototype via a Xilinx Zynq UltraScale+ MPSoC ZCU102. We have successfully booted up the Linux image supplied to us via the link here, and we are able to access the Linux system over serial terminal, as well as through an attached keyboard/mouse and computer monitor. When we set up the SD card, we made sure to copy the necessary files to the boot of the SD card. These files included zynqmp-zcu102-rev10-fmclidar1/BOOT.BIN, zynqmp-zcu102-rev10-fmclidar1/system.dtb, and zynqmp-common/Image. IIO_Oscilloscope is installed, and we have had no trouble launching it.
However, we are unable to see any of the ADC outputs from the AD-FMCLIDAR1-EBZ. We can confirm their absence by running the iio_info | grep device command, which results in the following list of devices:
IIO context has 5 devices:
iio:device0: ams
1 device-specific attributes found:
No trigger on this device
iio:device1: pll
No trigger on this device
iio:device2: ad5627
No trigger on this device
iio:device3: ad7091 (buffer capable)
1 device-specific attributes found:
2 device-specific attributes found:
No trigger on this device
Furthermore, when booting up IIO_Oscilloscope, the only windows available are the main scope interface, as well as the DMM and Debug windows. The wiki seems to suggest that we should have more options relating to the Lidar available, but these are nowhere to be found.
We also made sure to build the HDL environment using the repository found here, and the instructions found here. We had no trouble running synthesis & implementation, and we were able to generate the bitstream and program the device on the zcu102. However, doing this did not help, and we remained unable to see the ADC channels on the Lidar board. After this, we ran the commands sudo adi_update_tools.sh and sudo adi_update_boot.sh, which ran without issue. This failed to fix the behavior we were seeing. We also attempted a soft reboot, which fixed nothing. In order to attempt debugging, we probed all of the test points on the DAC board, and we were able to verify that the ADP5054 is functional, and that it is supplying two 1.3 V outputs, one 2.4 V output, and one 3.0 V output. Still, we get the same output for the iio_info. We also probed the lines for DUT_CLK+, DUT_CLK-, D_SYSREF_P, and D_SYSREF_N, and all of them sit at 750 mV without any sign of clocking.
Can you please inform us of what actions we need to take to get this board operational? We want to get to the point where we are able to capture distance readings with the Lidar sensor, but we cannot do that until we resolve this.
Thank You
Additional Note:
We noticed that the DAQ board said Rev C on it, but the link (https://wiki.analog.com/_media/resources/eval/user-guides/ad-fmclidar1-ebz/revb_daq.zip) to download the BOM, schematics and layout are Rev B (it's in the link filename at the end, which is why I pasted it in). We also noticed, in this link, that there were multiple changes in the io constraints file from Rev A to Rev B, so maybe there should be some from Rev B to C too?
Added Updates
[edited by: AlexJT at 6:20 PM (GMT -4) on 17 Mar 2022]
