Bulletproofing PCIe-based SoCs with Advanced Reliability, Availability, Serviceability (RAS) Mechanisms
As silicon manufacturing process nodes keep shrinking and transistors get smaller, System-on-Chip (SoC) are increasingly subject to failures due to changing external conditions such as temperature, EMI, power surges, Hot Plug events, etc.
The transition to PCIe 5.0 and 6.0 with increasing PCIe signaling speeds (32GT/s and 64GT/s) also increases the risk of errors due to constricted timing budgets inside the SoC and electrical issues outside the SoC (e.g. crosstalk, line attenuation, jitter, etc.)
In addition, the ever-growing number of PCIe components and systems designed to different revisions of the Specification increases the risk for interoperability issues.
As a result, chip designers who use PCIe as the main communication interface in their SoCs are looking for ways to bulletproof their designs by implementing advanced Reliability, Availability, and Serviceability (RAS) mechanisms that go above and beyond those included in the PCI Express Base Specification.
We start this article by defining “RAS” in the context of PCIe interfacing and looking at the provisions for RAS mechanisms in the PCIe Specification. We then explore some potential PCIe hazards SoC designers can face and the RAS mechanisms that can be implemented to detect, recover, or prevent these hazards. We conclude with recommendations for choosing a PCIe silicon IP solution that helps mitigate these risks.
To read the full article, click here
Related Semiconductor IP
- USB 3.0 and PCIe 2.0 Combo PHY
- PCIe PHY and controller solution
- PCIe Controller
- PCIe 4.0 Controller
- PCIe 6.0 PHY, SS SF2A x4 1.2V, N/S for Automotive, ASIL B Random, AEC-Q100 Grade 2
Related Blogs
- Securing SoC Reliability with Precision Power-On Reset IP for 0.8V Industrial Designs
- Want to see the future of low-power SoC design? Have a look into Gary Smith’s crystal ball
- Jim Hogan's top six SoC trends for 2012. Want to know what they are?
- Will your multicore SoC hit the memory wall? Will the memory wall hit your SoC? Does it matter?
Latest Blogs
- When Your IP Vendor Has Operated 150,000 Base Stations: Introducing Viettel Semiconductor
- Relationship between architecture and validation in system design
- The Post-Quantum Cryptography Mandate: Building Cryptographically Agile Systems for the Quantum Era
- Demystify Address Translation Services (ATS) in PCIe 6.0
- Addressing DV Professionals’ Need to Reduce Verification Errors in Complex Designs