Visible to Intel only — GUID: syk1546556269863
Ixiasoft
1. About the P-tile Avalon® Intel® FPGA IPs for PCI Express
2. IP Architecture and Functional Description
3. Parameters
4. Interfaces
5. Advanced Features
6. Troubleshooting/Debugging
7. Document Revision History for the P-tile Avalon® Memory-mapped Intel FPGA IP for PCI Express User Guide
A. Configuration Space Registers
4.1. Overview
4.2. Clocks and Resets
4.3. Avalon® -MM Interface
4.4. Serial Data Interface
4.5. Hard IP Status Interface
4.6. Interrupt Interface
4.7. Hot Plug Interface (RP Only)
4.8. Power Management Interface
4.9. Configuration Output Interface
4.10. Hard IP Reconfiguration Interface
4.11. PHY Reconfiguration Interface
A.2.1. Intel-Defined VSEC Capability Header (Offset 00h)
A.2.2. Intel-Defined Vendor Specific Header (Offset 04h)
A.2.3. Intel Marker (Offset 08h)
A.2.4. JTAG Silicon ID (Offset 0x0C - 0x18)
A.2.5. User Configurable Device and Board ID (Offset 0x1C - 0x1D)
A.2.6. General Purpose Control and Status Register (Offset 0x30)
A.2.7. Uncorrectable Internal Error Status Register (Offset 0x34)
A.2.8. Uncorrectable Internal Error Mask Register (Offset 0x38)
A.2.9. Correctable Internal Error Status Register (Offset 0x3C)
A.2.10. Correctable Internal Error Mask Register (Offset 0x40)
Visible to Intel only — GUID: syk1546556269863
Ixiasoft
4.3.1. Endpoint Mode Interface (512-bit Avalon® -MM Interface)
Avalon-MM Type | Data Bus Width | Max Burst Size | Byte Enable Granularity | Max Outstanding Read Request |
---|---|---|---|---|
Bursting Slave | 512 bits | 8 cycles | byte | 64 |
Bursting Master | 512 bits | 8 cycles | byte | 32 |
Read Data Mover Write Master | 512 bits | 8 cycles | dword | N/A |
Write Data Mover Read Master | 512 bits | 8 cycles | dword | 128 |
Control Register Access | 32 bits | 1 cycle | byte | 1 |
These interfaces are standard Avalon® interfaces. For timing diagrams, refer to the Avalon Interface Specifications.
Note: The number of read requests issued by the Write Data Mover's Avalon-MM Read Master is controlled by the assertion of waitrequest by the connected slave(s). The Read Master can handle 128 outstanding cycles of data. You cannot set this parameter in Platform Designer. The slave needs to correctly back-pressure the master once it cannot handle the incoming requests.
Note: The 512-bit Bursting Slave interface does not support transactions where byte enables are set to 0.