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

IOSTANDARD to use for PUDC_B PULLUP is unknown #1104

Open
litghost opened this issue Oct 15, 2019 · 2 comments
Open

IOSTANDARD to use for PUDC_B PULLUP is unknown #1104

litghost opened this issue Oct 15, 2019 · 2 comments

Comments

@litghost
Copy link
Contributor

An unused PUDC_B pin should be configured as IN_ONLY and PULLUP. In order to configure IN_ONLY, an IOSTANDARD is required. This appears to be somewhat variable, but it is unclear why certain IOSTANDARDs are used.

  • xc7a50tfgg484-1: IOSTANDARD appears to be LVCMOS33
  • xc7k70tfbg676-2: IOSTANDARD appears to be LVCMOS15
  • xc7z010clg400-1: IOSTANDARD appears to be LVCMOS33

Currently fasm2frames always emits the IN_ONLY as LVCMOS33 if --emit_pudc_b_pullup is set.

One theory to be tested is whether the IOSTANDARD is only variable based on whether the IO bank with the PUDC_B pin is HR or HP.

@JakeMercer
Copy link
Contributor

From UG471

The 7 series FPGAs offer both high-performance (HP) and high-range (HR) I/O banks. The
HP I/O banks are designed to meet the performance requirements of high-speed memory
and other chip-to-chip interfaces with voltages up to 1.8V. The HR I/O banks are designed
to support a wider range of I/O standards with voltages up to 3.3V.

So this would suggest a pin in the HP bank should never be LVCMOS33 or LVCMOS25.

@litghost
Copy link
Contributor Author

So this would suggest a pin in the HP bank should never be LVCMOS33 or LVCMOS25.

Agreed. The question is whether there are packages that use something other than LVCMOS33 for HR and LVCMOS15 for HP.

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

2 participants