How to diagnose a non-responsive AD-FMDADC2 board connected to a Zynq706?

Dear members,

We have an AD-FMCADC2 board that is connected to the HPC connector on a Zynq706 FPGA board from Xilinx. We got the Linaro Linux working, with the supplied image stored in the SD card, and everything went OK. Even though we did not have a signal in the input, we were able to capture data and save it (all zeroes) to a file. We happily turned off the system to prepare for next day actual measurements, but the board is not being identified anymore. In the AD IIO oscilloscope application, the device panel is empty, and in the DMM application, some signal that the board was identified is apparent, from the FRU data that, I think, is being retrieved from the I2C EEPROM in the A/D board (please, see the screenshot below).

Any sugestions on how to verify what's goind on? We can run the BIST on the FPGA board, which passes without problems, and Linux and all other utilities run OK.

I can provide more information or perform tests as suggested.

Thanks,

Julio de Melo

Screenshot of the AD IIO applications:

Parents
  • Hi Michael,

    Thanks for explaining the flash routine.

    So far, we can pinpoint the error to the message related to the AD9625 not being recognized by the SPI routine.


    Our board goes like:

    ad9467 spi32766.0: Unrecognized CHIP_ID 0xFF

    And a working one goes like:

    ad9467 spi32766.0: AD9625 PLL LOCKED

    cf_axi_adc 44a10000.axi-ad9625-hpc: ADI AIM (8.00.b) at 0x44A10000 mapped to 0xf0140000, probed ADC AD9625 as MASTER

    Any hint on what the problem may be? It looks like the AD9625 is not being read properly through the SPI interface, and is returning all 1's.

    Any pointers on what to do next?

    Thanks,

    Julio

Reply
  • Hi Michael,

    Thanks for explaining the flash routine.

    So far, we can pinpoint the error to the message related to the AD9625 not being recognized by the SPI routine.


    Our board goes like:

    ad9467 spi32766.0: Unrecognized CHIP_ID 0xFF

    And a working one goes like:

    ad9467 spi32766.0: AD9625 PLL LOCKED

    cf_axi_adc 44a10000.axi-ad9625-hpc: ADI AIM (8.00.b) at 0x44A10000 mapped to 0xf0140000, probed ADC AD9625 as MASTER

    Any hint on what the problem may be? It looks like the AD9625 is not being read properly through the SPI interface, and is returning all 1's.

    Any pointers on what to do next?

    Thanks,

    Julio

Children
No Data