Actions
Forum Thread Details
  • State Not Answered
  • Replies 3 replies
  • Subscribers 313 subscribers
  • Views 347 views
  • Users 0 members are here
Related

Adapting a Zedboard code to Microzed

Former Member

Hi!
I've been doing some experimentation with MicroZed recently, but I only found guides about what I'm trying to do applied to the Zedboard.
Apart from Vivado, what are the SDK nuances I need to look at in order to make my C code run in the Microzed board?

  • 0

    There are some differences between the two boards.

     

    The ZedBoard has a Zynq 7020 device. MicroZed may have a Zynq 7010 or 7020 device, depending on the version you have. So, if you have the 7010 version of the MicroZed it will have less Programmable Logic resources and less internal BRAM, if you have the 7020 version then ZedBoard and MicroZed have the same internal resources. The device on the MicroZed is in a smaller package with fewer I/O pins.

     

    Both versions of the MicroZed have 1 GB of DDR memory, twice that of the ZedBoard.

    The ZedBoard has an SD Card socket and 256 Mb of QSPI Flash while the MicroZed has a microSD card socket and 128 Mb of QSPI Flash.

     

    There are other obvious differences in the connections available, such as PMOD connections and LPC FMC connector unless you are using a Carrier Card with the MicroZed. You should make sure that any peripheral devices you plan to use, such as I2S and HDMI/VGA interfaces that are on the ZedBoard are on a carrier card for the MicroZed.

     

    Otherwise, from an SDK point of view not many differences. You will need to 'export' your MicroZed hardware to the SDK and rebuild a new BSP. Then, assuming all of the peripherals and drivers are there, your code should run on the MicroZed.

     

    -Gary

  • 0 in reply to Former Member

    Hey, Gary!
    Thank you for your kind answer.
    I'm using MicroZed with a carrier board.
    I've been trying to apply a XADC voltage reader, and found a Zedboard Guide. Everything seems right in vivado (wiring in block diagram, constraints, ports, etc), but when I use the C code in SDK it just doesn't work.
    I'm afraid it is something involving the constraints code and/or a problem with drivers/includes in the SDK code.
    I've been trying to check all the code with ZYNQ documentations, but can't find whats wrong.
    The guide (pdf) I previously commented is on this link:
    https://docs.google.com/viewer?a=v&pid=sites&srcid=ZGVmYXVsdGRvbWFpbnxydGNsYWIwOXxneDoyYTgxZDNjMmVjZjRmZmVm
    Can someone please help me finding out what is the difference?
    I know that's an easy task, but since I'm new to this subject, this is really bugging me out.
    Thanks in advance.

  • 0

    You will need to change the constraints file to match the different Zynq package pin/signals between the ZedBoard and the MicroZed as the two boards have different Zynq packages. I am not familiar with the lab material you refer to, and the constraints file is not available on your linked file, so I can't give you specific changes to make. Take a look at the MicroZed master .xdc files available on the MicroZed documentation page: http://zedboard.org/support/documentation/1519 and the MicroZed Carrier Card documentation pages: 

    http://zedboard.org/support/documentation/2180

    http://zedboard.org/support/documentation/1522

    http://zedboard.org/support/documentation/2182

    depending on which Carrier Card you are using.

     

    There is also a bug in Vivado 2014.4 that causes IO Buffers to be inferred for some of the XADC signals that did not occur in previous Vivado versions. So some location constraints that did not have to be explicitly added to your .xdc file in other versions of Vivado do need to be added in 2014.4. This would cause an error in your Vivado Hardware project though, so if you are able to generate and export your design to SDK successfully that is not your issue. (see this forum post for details): 

    http://zedboard.org/content/vivado-20144-microzed-incompatible-board-definition-file

     

    -Gary