Chapter 5: IP Core Architecture
5–19
Avalon-MM Bridge TLPs
November 2012
Altera Corporation
Arria V GZ Hard IP for PCI Express
This design is consuming 1.25GB of PCIe address space when only 276 MBytes are
actually required. The solution is to edit the address map to place the base address of
each BAR at 0x0000_0000.
illustrates the optimized address map.
h
For more information about changing Qsys addresses using the Qsys address map,
refer to
in Quartus II Help.
shows the number of address bits required when the smaller memories
accessed by BAR2 and BAR4 have a base address of 0x0000_0000.
For cases where the BAR Avalon-MM RX master port connects to more than one
Avalon-MM slave, assign the base addresses of the slaves sequentially and place the
slaves in the smallest power-of-two-sized address space possible. Doing so minimizes
the system address space used by the BAR.
Avalon-MM-to-PCI Express Address Translation Algorithm
The Avalon-MM address of a received request on the TX Avalon-MM slave port is
translated to the PCI Express address before the request packet is sent to the
Transaction Layer. You can specify up to 512 address pages and sizes ranging from
4 KByte to 4 GBytes when you customize your Avalon-MM Arria V GZ Hard IP for
PCI Express as described in
“Avalon to PCIe Address Translation Settings” on
. This address translation process proceeds by replacing the MSB of the
Avalon-MM address with the value from a specific translation table entry; the LSB
remains unchanged. The number of MSBs to be replaced is calculated based on the
total address space of the upstream PCI Express devices that the Avalon-MM Hard IP
for PCI Express can access. The number of MSB bits is defined by the difference
between the maximum number of bits required to represent the address space
supported by the upstream PCI Express device minus the number of bits required to
represent the
Size of address pages
which are the LSB pass-through bits (
N
). The
Size
of address pages
(
N
) is applied to all entries in the translation table.
Figure 5–10. Optimized Address Map
Figure 5–11. Reduced Address Bits for BAR2 and BAR4