ADRV9002
Recommended for New Designs
The ADRV9002 is a highly integrated RF transceiver that has dual-channel transmitters, dual-channel receivers, integrated synthesizers, and digital signal...
Datasheet
ADRV9002 on Analog.com
Good morning,
I have set up the EVAL-ADRV9002 and ZCU102 for evaluation but I am having some trouble getting the TES to talk to the eval platform.
My progress so far:
1) I set up following the ADRV9002 Zynq UltraScale+ MPSoC ZCU102 Quick Start Guide. Initially I tried to boot the ZCU102 using the SD card provided with the ADRV9002 eval kit, marked "R0.2 2020.12". Using this, the ZCU would not boot, I had no output on the serial port whatsoever. It did not even get as far as sending "Xilinx Zynq MP First Stage Boot Loader", PS_ERR_OUT LED was illuminated.
2) I then imaged my own SD card with the latest version of the Analog Devices Kuiper Linux and moved the appropriate files to root as described in the instructions.
3) Using this, the ZCU102 booted fine and I was able to control it through the serial port. The kernel boot log was not identical, but similar, to the provided example; there doesn't appear to be anything problematic in there. All LEDs on the ZCU102 and the ADRV9002 eval board were illuminated as expected.
4) The Transceiver eval software would not talk to the device, providing the following error message:
A connection to the remote host could not be established. This might happen if the evaluation board is powered down or if the operating system did not boot properly. Check that you can connect to 192.168.1.10 via PuTTY. If using a router with DHCP enabled, you may need to change the IP address to the one assigned dynamically.
Alternatively, I sometimes get this error message:
The remote server failed to start. If you recently updated evaluation software, you may need to re-image your SD card. Otherwise, this might happen if another process is already connected to the server, or if the server executable was not loaded correctly on the platform. Close other programs and verify that /home/analog/adrv9001_server/resources/Adi.Adrv9001.Server/Adrv9001_C0 is present on the remote host 192.168.1.10
Pinging the device through the command line also failed, so in the serial terminal I saw with 'ifconfig' that the eth0 IP was not 192.168.1.10 as expected; I manually set it to this IP address and I can now ping both the ZCU102 and my windows PC in the command line.
5) I have worked through all the suggestions in the TES Connection Issues page ( TES Connection Issues ) and have had no luck, however the "Server Failed to Start" section appears to be leading me in the direction of the problem.
When attempting to manually restart the server:
root@analog:/home/analog/adrv9001_server/resources/Adi.Adrv9001.Server# ./Adrv9001Server_C0_68.10.1 Unable to memory map register space (uio-0): Invalid argument
Any advice on how to resolve this issue is appreciated.
Thanks in advance,
A
Hi SDRfan,
I suspect that your issue is caused by using the incorrect SD card image.
As you can see from the ADRV9001 Software and Hardware Selection Guide, there are two separate software development paths available for the ADRV9001 family of products. the Product Line SDK/TES is one (which is supported on these forums), and the Open Source/IIO is the other. The Kuiper image is part of the latter.
The SD card image that you should be using can be found here: Wideband RF Transceiver Evaluation Software | Analog Devices.
Try that and let me know how it goes.
Kind Regards,
Michał
Hi Michał,
Thanks for the reply.
It looks like this was the problem; simply getting mixed up with the other development path.
F.Y.I the SD card image I downloaded after following your link (ADRV9001 SD Card image for ZCU102 FPGA) had some problem with it. I was unable to extract the zip file using windows built-in, 7zip and WinRAR all provided some sort of error during decompression, and resulted in an image file which failed checksum or no file at all. For some reason, rather than using a decompression tool, simply dragging the file out of the .zip to a normal folder worked, and I have been able to get the device working using this image now.
Thanks,
Andrew
hi,I have the same problem with you now, I downloaded the zip image file but can't decompression it, how do you get the right image file?