IP-PCI/MT32 Altera, IP-PCI/MT32 Datasheet - Page 353

• Manufacturer Part Number: IP-PCI/MT32
• Description: IP CORE - 32-bit 66MHz PCI Master/Target
• Manufacturer: Altera
• Type: MegaCorer

Specifications of IP-PCI/MT32

• Software Application: IP CORE, Interface And Protocols, PCI
• Supported Families: Arria GX, Cyclone, HardCopy II, MAX II, Stratix
• Core Architecture: FPGA
• Core Sub-architecture: Arria, Cyclone, Stratix
• Rohs Compliant: NA
• Function: PCI Compiler, Master/Target, 32 bit
• License: Initial License
• Lead Free Status / RoHS Status: na
• Lead Free Status / RoHS Status: na

proc get_user_pin_name { internal_pin_name } {
#---------------- Do NOT change -------------------------------
array set map_user_pin_name_to_internal_pin_name { ad
Altera Corporation
January 2011
#---------------- Do NOT change -------------------------------
array set map_user_pin_name_to_internal_pin_name { ad
Upgrading PCI Assignments Containing Nondefault PCI Pin
Names
The PCI constraint file uses the default PCI pin names to make PCI
assignments. When removing the existing PCI assignments the PCI
constraint file checks the PCI pin names against the default PCI pin
names. If there is a mismatch between your PCI pin names and the
default PCI pin names, do one of the following:
■
■
In both of the above methods the PCI constraint files use the default PCI
pin names to make new PCI pin assignments in your project. You must
manually edit your QSF to change the default PCI pin names to your
project-specific pin names.
To edit the PCI constraint file, follow these steps:
1.
2.
3.
Manually delete all the existing PCI assignments from your QSF,
then use the PCI constraint file as shown in
page
Update the pin list in the PCI constraint file. The PCI constraint file
has a mapping of default PCI pin names to user PCI pin names. Edit
the get_user_pin name procedure in the PCI constraint file to
match the default PCI pin names to your PCI pin names, then use the
PCI constraint file as shown in
Open the PCI constraint file in a text editor of your choice. Make
sure that any automatic line-wrapping functionality is disabled.
Go to the get_user_pin_name procedure. This procedure maps
the default PCI pin names to user PCI pin names. The first few lines
of the procedure are shown below.
Edit the pin names under the "Change" header in the file to match
the PCI pin names used in your Quartus II project. In the example
line below, the name ad is changed to pci_ad:
A–1.
PCI Compiler Version 10.1
“PCI Constraint Files” on page
“PCI Constraint Files” on
PCI Compiler User Guide
---- Change -----
---- Change -----
pci_ad
ad
A–1.
A–7
}
}