Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changing "enable VP/VN" to false #48

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Changing "enable VP/VN" to false #48

wants to merge 1 commit into from

Conversation

wnew
Copy link

@wnew wnew commented Aug 2, 2023

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

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant