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

Proper handling of IOSTANDARD for the PUDC_B pin site #1263

Open
mkurc-ant opened this issue Jan 14, 2020 · 0 comments
Open

Proper handling of IOSTANDARD for the PUDC_B pin site #1263

mkurc-ant opened this issue Jan 14, 2020 · 0 comments

Comments

@mkurc-ant
Copy link
Collaborator

There is always a "special" IO site driving a pin with the PUDC_B special function. Vivado always configures the site as an input regardless of whether it is used by the design or not. We don't do that in Symbiflow correctly.

The script fasm2frames.py as an option --emit_pudc_b_pullup which forces emission of fasm features which make the site LVCMOS25 or LVCMOS33 input.

However, when the bank uses a different IOSTANDARD (such as eg. LVCMOS18) those features need to be changed accordingly to make the site input of the same IOSTANDARD as the whole bank (or at least compatible).

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

No branches or pull requests

1 participant