I have a ZCU102 and an ADRV9009.
I followed this
And run the commands
root@analog:~# iio_info | grep iio:device iio:device3: adrv9009-phy iio:device1: ad9528-1 iio:device6: axi-adrv9009-rx-hpc (buffer capable) iio:device4: axi-adrv9009-rx-obs-hpc (buffer capable) iio:device2: ad7291 iio:device0: ams iio:device5: axi-adrv9009-tx-hpc (buffer capable)
root@analog:~# fru-dump -b /sys/bus/i2c/devices/16-0050/eepromread 256 bytes from /sys/bus/i2c/devices/16-0050/eepromDate of Man : Wed Aug 30 14:05:00 2017Manufacturer : Analog DevicesProduct Name : 9379RC0,9528Serial Number : 1716630014Part Number : 9379FRU File ID : Empty FieldPCB Rev : 01BPCB ID : 9379CE01BUses LVDS : Y
Then I would like to use the IIO Oscillscope on my PC connected with Ethernet to the ZCU102+ADRV9009.
What IP address to use to connect to ZCU102 ?
Standard as used with TES ADRV9371 and ZC706. 192.168.1.2
By the way, another stange thing, that the ZCU102 is not able to display to Monitor the IIO Oscilloscope as the ADRV9371 and ZC706 can do...
To talk to a locally attached board requires being in the same subnet. So to talk to the board with an IP 192.168.0.101 your local NIC must have an address 192.168.0.X (but not 101).
Yes, ZCU102 has video out problems. There is a fix you can try here: https://wiki.analog.com/resources/tools-software/linux-build/generic/zynqmp#displayport_-_no_picture
However, this is really a Xilinx bug and they are aware of the issue. We are hoping in their next kernel release there will be a fix. For now, only a small subset of monitors work.