PMOD AD5 issue on 2020.2

[Jorgepfm]

Hello, I installed Vivado 2020.2 on a new machine, and tried to get the PMOD AD5 working by following these instructions (I had it working before on a 2018.3 machine without issues). Bitstream failed with the following errors:

[DRC NSTD-1] Unspecified I/O Standard: 4 out of 138 logical ports use I/O standard (IOSTANDARD) value 'DEFAULT', instead of a user assigned specific value. This may cause I/O contention or incompatibility with the board power or connectivity affecting performance, signal integrity or in extreme cases cause damage to the device or the components to which it is connected. To correct this violation, specify all I/O standards. This design will fail to generate a bitstream unless all logical ports have a user specified I/O standard value defined. To allow bitstream creation with unspecified I/O standard values (not recommended), use this command: set_property SEVERITY {Warning} [get_drc_checks NSTD-1]. NOTE: When using the Vivado Runs infrastructure (e.g. launch_runs Tcl command), add this command to a .tcl file and add that file as a pre-hook for write_bitstream step for the implementation run. Problem ports: jc_pin9_io, jc_pin8_io, jc_pin7_io, and jc_pin10_io.

[DRC UCIO-1] Unconstrained Logical Port: 4 out of 138 logical ports have no user assigned specific location constraint (LOC). This may cause I/O contention or incompatibility with the board power or connectivity affecting performance, signal integrity or in extreme cases cause damage to the device or the components to which it is connected. To correct this violation, specify all pin locations. This design will fail to generate a bitstream unless all logical ports have a user specified site LOC constraint defined. To allow bitstream creation with unspecified pin locations (not recommended), use this command: set_property SEVERITY {Warning} [get_drc_checks UCIO-1]. NOTE: When using the Vivado Runs infrastructure (e.g. launch_runs Tcl command), add this command to a .tcl file and add that file as a pre-hook for write_bitstream step for the implementation run. Problem ports: jc_pin9_io, jc_pin8_io, jc_pin7_io, and jc_pin10_io.

I'm using a Zybo Z7-20.

How do I fix this?

[artvvb]

Reproduced with both the Pmod AD5 IP core and with the Pmod Bridge with a disabled bottom row interface. The issue will extend to any other Pmod IPs that disable the bottom row interface (those with 1x6 connectors).

A workaround is as follows:

1. Select the AD5 IP's "Edit IP in IP packager" option to begin editing the IP.
2. Run Reports > Report IP Status and upgrade each IP contained in the core.
3. Expand Design Sources and double click on the Pmod Bridge to edit its settings.
4. Change the bottom row interface to "None".
5. OK out, merge changes as necessary, and re-package the AD5 IP.
6. Upgrade into the new version of the IP.

This doesn't specify the tie-offs for the unconnected pins, which is not the best, but does seem to be enough to get a bitstream.
SPI driver issues may also present themselves when upgrading QSPI, so it may be better to only upgrade the bridge (in order to unlock it).