Adapting a Zedboard code to Microzed

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?

Parents

0 Former Member over 10 years ago

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Former Member over 10 years ago

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data