Actions
Forum Thread Details
  • State Not Answered
  • Replies 2 replies
  • Subscribers 339 subscribers
  • Views 441 views
  • Users 0 members are here
Related

Zynq / Analog Devices Software-Defined Radio kit on ZedBoard Rev D

Former Member

The Zynq / Analog Devices Software-Defined Radio kit is now shipping with the latest Zedboard Rev D. However, some kits have shipped with the Getting Started documentation and the factory SD card that still reflect Rev C. To successfully boot the ADI Zynq SDR kit to UBUNTU Linux on ZedBoard Rev D requires the most recent SD card image with 19APR13 timestamp: http://wiki.analog.com/resources/tools-software/linux-software/zynq_images

 

Detailed instructions for re-imaging the SD card are included in the updated Getting Started Guide GS-AES-ZSDR-ADI-G-v4-web.pdf available from the Avnet DRC www.em.avnet.com/adizynqsdr

 

This SD card image was verified on the latest ZedBoard Rev D + FMCOMMS1 Rev B and is also backward compatible with ZedBoard Rev C.

 

NOTE: Upon boot-up to UBUNTU desktop, be aware that the FireFox web browser that displays the network scope is sitting on top of the IIO Oscilloscope window. Minimize FireFox to reveal the IIO oscilloscope. Once in IIO scope, when capturing the frequency domain FFT plot, make sure to select a single channel. To return to network scope, launch FireFox anew.

  • 0

    I just received my Analog Devices SDR kit.

    I've copied the new image to my SD Card, verified that there are two partitions (BOOT, rootfs), and copied the appropriate boot files (BOOT.BIN, devicetree.dtb) to the root of the BOOT partition. However, the ZedBoard fails to boot. I see no activity over the UART after powering on.

    The link above for the updated Getting Started Guide did not work. However, there were some reimaging instructions in the first link. I followed these instructions. Not sure if the instructions in the second link were different.

    I'm using a 64-bit linux machine to reimage.

    Any help would be greatly appreciated.

  • 0

    I was copying the wrong BOOT.BIN and devicetree.dtb to the root of the BOOT partition. Once I corrected that, the board booted up fine.