Quick Answer
DS320PR810 selection begins with the electrical channel and its direction, not only the logical PCIe link width. TI describes an eight-channel linear redriver for interfaces up to 32 Gbps. A PCIe connection carries traffic in both directions, so the design must account for the transmit and receive paths separately when mapping redriver channels. Keep that mapping explicit in the schematic and component count.
This is a family-level application guide. Procurement needs the released complete ordering code, configuration and package details. It does not establish that DS320PR810 is present in any particular H100 or MI300X server.
Key Specifications and Decision Points
TI describes continuous-time linear equalization and a linear data path that preserves transmitter preset characteristics during link training. Configuration can use pin straps, SMBus or EEPROM. The redriver therefore becomes part of a channel that must be evaluated with the endpoint transmitters and receivers; it is not a self-contained guarantee of a passing PCIe link.
The supported signaling rate is a selection criterion, while compliance and margin remain properties of the implemented link. Avoid using a nominal Gen5 description as evidence that an arbitrary riser or cable arrangement has already been qualified.
- Name every high-speed path by source and destination. Associate redriver input, output and control settings with the physical lane direction rather than an ambiguous slot label.
- Record the board, connector and cable configuration used to establish equalization settings. A tuning result belongs to that channel implementation and operating envelope.
- Define who owns configuration at startup. Pin straps, stored settings and later software writes should lead to one documented operating state.
Application and Acceptance Review
Begin channel evaluation with the expected topology and endpoint capabilities confirmed. Then use the manufacturer's tuning guidance and the applicable platform test procedure to assess equalization. Preserve the settings and results together. An unexplained register file that happens to make one prototype train is poor evidence for releasing a production riser.
Avoid assuming that greater equalization always produces a better result. Tune against measurements and the complete channel response. Keep unsuccessful settings in the engineering notes when they explain the selected operating region, but release only the approved configuration to manufacturing.
Test cold startup and management reset separately. If software configures the redriver, establish when that configuration occurs relative to endpoint discovery and training. A board that succeeds after a manual write and reboot may still have a sequencing defect in unattended operation. Make the production boot path part of acceptance rather than a final administrative detail.
- Test the intended lane population and both traffic directions. Include the actual endpoint and host combinations the system supplier supports.
- Record negotiated generation and width, relevant error behavior and measurements required by the qualification plan. A completed boot alone does not demonstrate channel margin.
- Evaluate the permitted cable lengths, board revisions and thermal conditions. Treat a changed connector or stackup as a potential channel change requiring review.
Pricing and Lead Time
An RFQ for the IC should provide its approved ordering suffix, package, carrier format and quantity. An RFQ for a complete riser should also identify board revision, connector population, supported cable assemblies and configuration responsibility. These are different commercial objects and need different evidence before acceptance.
Ask suppliers of assembled hardware whether quoted testing uses the released configuration and representative endpoints. State the reports required, including identities and versions sufficient to reproduce a result. If a supplier proposes a different redriver family, require an engineering comparison before treating it as an equivalent way to meet the original request.
Obtain current price and schedule information for the defined scope. Include configuration development and channel requalification where a change is necessary. A nominally earlier component delivery cannot establish an earlier system deployment if the alternative needs new layout work or tuning. This guide makes no claim about available quantities or delivery dates.
Alternatives and Change Control
A retimer and a linear redriver have different architectures, and the decision belongs to the channel budget and platform design. Evaluate latency, clocking, management, topology and electrical requirements using the relevant manufacturer documents. Do not replace one category with the other simply because both appear in high-speed server interconnect discussions.
Another linear redriver can also differ in channel count, gain behavior, control interface and startup defaults. Map those differences against the actual channel and production process. The need to preserve lane direction remains even if the alternative uses a package with a different arrangement or integrates more paths.
If a link repeatedly trains below the expected capability, first distinguish electrical behavior from host configuration or a limited endpoint. Preserve topology and capability evidence before modifying equalization. That diagnostic order avoids turning a firmware or lane-routing problem into an unnecessary component redesign and gives procurement a clear explanation of which hardware change, if any, is justified.
FAQ
Do eight redriver channels automatically mean one complete x8 PCIe connection?
Map the signal paths explicitly. PCIe traffic travels in both directions, and redriver channels refer to electrical paths. Use the manufacturer diagrams and the board topology to establish the required device count.
Can I reuse one tuning file on every riser design?
Only after qualification establishes that the settings suit each supported channel. Routing, connectors, cables, endpoints and configuration timing can differ. Keep approved settings tied to their tested assembly revision.
Does successful link training prove compliance?
It proves a connection formed under those conditions. Compliance and margin require the relevant qualification procedure and evidence. Include operating conditions, lane population, endpoint identities and configuration in the report.
Discuss your requirements with SENICO and request a quotation
Sources
- TI DS320PR810 product information (checked 2026-10-02)