Visible to Intel only — GUID: dom1684726582794
Ixiasoft
3.1.1.1. PCIe* TLP Constructor
3.1.1.2. PCIe* TLP ID Generation
3.1.1.3. PCIe TX Credit Controller
3.1.1.4. PCIe* TX Scheduler
3.1.1.5. PCIe TLP Completer
3.1.1.6. PCIe RX Router
3.1.1.7. PCIe* MSI-X Controller
3.1.1.8. PCIe BAR0
3.1.1.9. PCIe Bursting Manager (BAM)
3.1.1.10. Completion Timeout Parser
3.1.1.11. Control Shadow Parser
4.2.1. Application Packet Receive Interface
4.2.2. Application Packet Transmit Interface
4.2.3. Control Shadow Interface
4.2.4. Transmit Flow Control Credit Interface
4.2.5. Completion Timeout Interface
4.2.6. PCIe* Miscellaneous Signals
4.2.7. Control and Status Register Responder Manager Interface
4.2.8. Bursting Manager Interface
Visible to Intel only — GUID: dom1684726582794
Ixiasoft
3.1.1.4. PCIe* TX Scheduler
The TX Scheduler module performs the following tasks:
- Performs arbitration between different TLPs coming from different modules:
- Memory read or write from TLP Constructor module:
- H2D (host to device) Agents
- D2H (device to host) Agents
- Prefetcher Engine
- MSI-X Controller
- Memory Read Completion from BAM(BAR1) Agent
- Memory Read Completion from BAR0 Agent
- Memory read or write from TLP Constructor module:
- Reads out TLPs from internal FIFO modules based on the advertised partner's credits from TX Credit Controller. Additional to that, the TX Scheduler monitors the occupancy of reordering buffer resided in the TLP Completer apart from Non-posted credits before sending any memory read request to PCIe host. If a TLP type is blocked due to a lack of the corresponding RX buffer space from the PCIe host, other TLP types may bypass it per the PCIe transaction ordering rules.
- Performs Packing according to the Header Packing scheme defined in the GTS AXI Streaming Intel® FPGA IP for PCI Express. The SSGDMA supports simple packing scheme where the header always start from Byte Index 0. This rule constraints only one packet can be sent per cycle.
- Generates dummy completion TLP(for posted/MEMWR TLP) to TLP Completer which eventually routes to the agents upon transfer completion to PCIe Host. This is to ensure the agents only initiate write-back response to PCIe Host after all data are successfully transferred to Host memory.
The table below shows the mapping of the header and data for a 256-bit wide Tdata defined in the PCIe* IP.
Tdata [255:0] | |
---|---|
16B | 16B |
Header Upper 16 bytes | Header Lower 16 bytes |
Data | Data |