Vivado - pin location conflict. Bug?

[JohnnyMalaria]

Hi,

I'm trying to elaborate/synthesize a design but I'm getting this error:



Vivado is complaining that it can't place port max261_0[2] because the target pin is already assigned to ltc2357_spi_ss_io. But that isn't true according to my constraints file.

Any ideas???

[JohnnyMalaria]

UPDATE:

I found a workaround but I have no idea what was happening. When I tried an implementation, I got a slew of errors about not enough locations remaining and stuff I fundamentally don't understand.

I moved some of my ports from one of the Arty Z7's chipkit connectors to one of its Pmod connectors. That allowed me to create a bitstream successfully.

(But I don't like not knowing what was wrong )

[miken]

This sounds too basic to be a bug in Vivado. The assignment must be being made somewhere... check the xdc associated with the Zynq Block.

[SiliconWizard]

This sounds too basic to be a bug in Vivado. The assignment must be being made somewhere... check the xdc associated with the Zynq Block.

Yes, I suspect another definition for the same port (ltc2357_spi_ss_io), either in them xdc file (although I guess the OP already checked that), or in another one. A given project can have multiple xdc files AFAIK so that could be the culprit.