November 2012
Altera Corporation
Arria V GZ Hard IP for PCI Express
15. Hard IP Reconfiguration and
Transceiver Reconfiguration
This chapter describes features of the Arria V GZ Hard IP for PCI Express that you can
use to reconfigure the core after power-up. It includes the following sections:
■
Hard IP Reconfiguration Interface
■
Transceiver PHY IP Reconfiguration
Hard IP Reconfiguration Interface
The Arria V GZ Hard IP for PCI Express reconfiguration block allows you to
dynamically change the value of configuration registers that are
read-only
. You access
this block using its Avalon-MM slave interface. For a complete description of the
signals in this interface, refer to
“Hard IP Reconfiguration Interface” on page 6–45
The Hard IP reconfiguration block provides access to
read-only
configuration registers,
including Configuration Space, Link Configuration, MSI and MSI-X capabilities,
Power Management, and Advanced Error Reporting (AER).
The procedure to dynamically reprogram these registers includes the following three
steps:
1. Bring down the PCI Express link by asserting the
hip_reconfig_rst_n
reset signal,
if the link is already up. (Reconfiguration can occur before the link has been
established.)
2. Reprogram configuration registers using the Avalon-MM slave Hard IP
reconfiguration interface.
3. Release the
npor
reset signal.
1
You can use the LMI interface to change the values of configuration registers that are
read/write
at run time. For more information about the LMI interface, refer to
.
lists all of the registers that you can update using the PCI Express
reconfiguration block interface.
Table 15–1. Dynamically Reconfigurable Registers in the Hard IP Implementation (Part 1 of 8)
Address
Bits
Description
Default
Value
Additional Information
0x00
0
When 0, PCIe reconfig mode is enabled. When 1, PCIe
reconfig mode is disabled and the original read only
register values set in the programming file used to
configure the device are restored.
b’1
—
0x01-0x88
Reserved.
—
0x89
15:0 Vendor
ID.
0x1172
,
0x8A
15:0
Device ID.
0x0001
,
November 2012
UG-01097-1.4