Vivado 2016.2 & Zybo mio problem

[omikron]

Hello

I installed the newest Vivado 2016.2 and the newest Zybo board files from git repo.

Any attemp to build the project ends with multiple Warnings during the place phase, saying that some Mio ports have more than one voltage standard. And the placement never ends.

It happens even when I try the simplest BD with Zyng core and two AXI_GPIOs for leds and buttons.

any idea?

[D@n]

Looking over my own copy of the board files for Zybo, I don't have the MIO pins defined within it at all.

Are you using the master .XDC file for Zybo as part of your project as well?  This might well be your problem.  You can find a link to that, as well as other resources, on the Zybo reference page.

Dan

[omikron]

8 hours ago, D@n said:

Looking over my own copy of the board files for Zybo, I don't have the MIO pins defined within it at all.

Are you using the master .XDC file for Zybo as part of your project as well?

Yes, I do.

This one exactly, with buttons, leds and switches uncommented.

[D@n]

@omikron,

Okay, so this is strange.  Usually your error is reserved for undefined pins--pins either whose location or voltage standard is not defined.  Vivado then tries to assign locations and voltage standards to them, and typically does it incorrectly.

Can you tell me which pins it is complaining about?   and are these pins used in your design?

Dan

[omikron]

It started, when I updated both XDC and the board files to the newest from Git.

I packed everything together with simple I/O project at http://test.gstavka.cz/project_1.zip

 

[omikron]

On 12. 8. 2016 at 11:38 PM, D@n said:

@omikron,

Can you tell me which pins it is complaining about?   and are these pins used in your design?

Dan

 

[D@n]

Take a peek at this link for a moment, I think it'll help.  It describes how to set the voltage standards on the various MIO lines.  I'd suggest trying this on a couple of lines at first, just to see if it helps.

Dan

[omikron]

It must be something strange with the new Vivado vesrion 2016.2. When I imported the same project_1 from above into 2016.1, everything works OK.

 

[D@n]

Go figure.

Okay, then, I'm glad to hear that it works!

Dan