Post Go back to editing

FRU version number mismatch

Category: Software
Product Number: CN0585

I am trying to get the CN0585+CN0584 Low-Latency Development Kit working from PyADI-IIO.

I already managed top get a signal generated and captured using IIO Oscilloscope.

I installed Python, PyADDI-IIO, and installed the required packages. Following the steps described here: https://wiki.analog.com/resources/eval/user-guides/circuits-from-the-lab/cn0584
When running the cn0585_fmcz_example.py example, I get an SSHException, telling me that "fru-dump board info command did not execute properly".

I examined the .py files and found that the exception is raised in eeprom.py, when the fru-dump command is sent. I SSH-ed into the zedboard and manually entered the fru-dump command. It tells me "FRU Version number mismatch 0xff should be 0x01".
According to this article (https://wiki.analog.com/resources/eval/user-guides/ad-fmcomms2-ebz/software/linux/applications/fru_dump) that means the EEPROM is not programmed?
I considered programming the EEPROM myself with the steps provided in that article, but I run into two problems:

1) I can't find a .BIN file that I think matches my board.
2) "find /sys/ -name eeprom" finds two eeproms:
    /sys/devices/soc0/fpga-axi@0/41620000.i2c/i2c-1/1-0054/eeprom
    /sys/devices/soc0/fpga-axi@0/41620000.i2c/i2c-1/1-0050/eeprom

Both devices give the same FRU version number mismatch error, but I don't know which one is what.

Anyone that can steer me in the right direction?


btw: I am new to python, and also not a star with Linux. But I am good with Google ;-) 



- small fixes
[edited by: Johannes2 at 11:10 AM (GMT -4) on 1 Oct 2024]