Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Vivado IP "system management wizard" sets the "enable VP/VN" to true by default. This exposes these 2 ports on the IP which are supposed to be connected to pins on the FPGA. But these signals are not broken out in the wrapper nor to the top level. The problem comes in where the IP automatically adds "IOSTANDARD Analog" pin constraints to the design which causes a critical warning because these pins do not exist.
See System Management Wizard v1.3 Product Guide (PG185)
"The System Management Wizard writes the required ANALOG IOSTANDARD constraint on VP/VN ports. Setting the Analog Bank Selection for vaux pins (shown in Figure 4-14) writes the pin LOC and IOSTANDARD constraint for vaux ports."
It makes sense that if these signals are not being routed to the top level that they not be configured in the first place.
-Wes