ALF-CR-PCIE

PCI Express endpoint & DMA subsystemGen1 to Gen5, x1 to x16, compliant at the full link rate

Production Datasheet

A complete PCI Express endpoint with the data mover built into it, rather than a controller you then have to feed. The transaction layer, the descriptor-driven DMA engine and the host drivers are developed and verified as one thing, which is why it holds the full link rate instead of the fraction of it that a generic bridge reaches. Compliance is not a configuration: every supported lane width and link rate is signed off against the base specification, including link training, error handling and power state transitions.

  • Gen1 to Gen5 at x1, x2, x4, x8 and x16, with automatic rate and width negotiation
  • Descriptor-driven scatter-gather DMA, up to 8 independent channels per direction
  • Sustains the full link rate on both directions at the same time, including 64 B transfers
  • MSI, MSI-X and legacy interrupts; up to 2048 MSI-X vectors
  • Advanced Error Reporting, ECRC, poisoned TLP handling and hot reset recovery
  • SR-IOV with up to 256 virtual functions, and address translation services
  • Up to 6 BARs per function, 32-bit or 64-bit, with prefetchable regions
  • Linux kernel driver, DPDK poll-mode path and a Windows KMDF driver, all supplied as source

Key specifications

Link rates2.5 / 5 / 8 / 16 / 32 GT/s (Gen1–Gen5)
Lane widthsx1, x2, x4, x8, x16
Sustained throughputUp to 55 GB/s aggregate at Gen5 x16
DMA channels1–8 per direction, independently configurable
Max payload128–512 bytes, negotiated
Completion latencyUnder 1 µs typical for a 4 kB read
InterfacesAXI4 and AXI4-Stream, AXI4-Lite control
CompliancePCI-SIG base specification checklist, link training and error injection suites
Gen5 x16 SR-IOV Drivers included
ALF-CR-DMA

AXI4-Stream Scatter-Gather DMASample movement between datapath and memory

Production Datasheet

Descriptor-driven data movement between the streaming datapath and system memory. Sized for radio applications, where sustained bandwidth over a wide datapath matters more than the small-transfer efficiency a general-purpose DMA optimises for. Handles the capture buffers, replay buffers and corner-turn transfers that most signal-processing systems need.

  • Up to 16 independent channels, each bidirectional
  • Descriptor chaining with cyclic buffer mode
  • Datapath width up to 512 bits
  • 2D transfer mode for corner-turn operations
  • Timestamp-triggered start for scheduled capture and replay
  • Per-channel bandwidth statistics and back-pressure reporting

Key specifications

Channels1 – 16, bidirectional
Datapath64 – 512 bits
Throughput> 25 GB/s at 512 bits, 400 MHz
DescriptorsChained, cyclic, 2D modes
TriggeringSoftware or timestamp-based
InterfacesAXI4 memory, AXI4-Stream, AXI4-Lite
Typical FPGA8.4 kLUT for 4 channels @ 400 MHz
512-bit datapath 2D corner turn Silicon-proven

Measuring less than the link should give you?

Send the transfer size distribution and the topology. Most of the time the answer is in the descriptor handling or the memory arbitration, and both are measurable before you commit to anything.