Doubling Bandwidth in Under Two Years: PCI Express Base Specification Revision 5.0, Version 0.9 is Now Available to Members
Our PCI-SIG® members have been hard at work. In 2017, we delivered PCI Express® 4.0 with its 16 GT/s, while also diving headfirst into PCI Express 5.0 development – first announced at our annual PCI-SIG DevCon in June 2017. With data-hungry applications like artificial intelligence, machine learning, enterprise servers and more, growing in popularity and capabilities, we knew that it was only a matter of time before the market would demand greater bandwidth.
Thanks to the diligence and dedication of our workgroups, I’m pleased to announce that the feature complete PCIe® 5.0, Version 0.9 has now been published to members. This is a great indicator that PCI-SIG will be able to meet its goal of doubling bandwidth—from 16 GT/S to 32 GT/s—in a record less than two years.
To read the full article, click here
Related Semiconductor IP
- PCIe 5.0 Controller
- Configurable CCIX controllers for CCIX 32G supporting Endpoint, Root Complex, Switch Port, and Dual Mode applications
- Controllers for CCIX 25G supporting Endpoint, Root Complex, Switch Port, and Dual Mode applications targeting automotive
- Configurable CCIX controllers for CCIX 25G supporting Endpoint, Root Complex, Switch Port, and Dual Mode applications
- PCIe 5.0 Controller with AXI
Related Blogs
- Complete Interface Solution for PCI Express 5.0 Launched
- NVM Express: pervasion of PCI Express in SSD based storage
- Rambus Achieves PCI Express® (PCIe®) 5.0 Compliance for PCIe 5.0 Controller IP and Inspector PCIe 5.0 Interposer with Diagnostic IP
- PCI Express takes on Apple/Intel Thunderbolt and 16 Gtransfers/sec at PCI SIG while PCIe Gen 3 starts to power up
Latest Blogs
- Beyond Trusted: What the NSA’s New Guidance Means for Hardware Security
- A scalable, shader-programmable vector graphics GPU core for low-power MCUs
- Navigating ISO 26262 Part 11: A Guide for Semiconductor Architects
- Embedded Security explained: Digital signatures
- Hardware security verification must go beyond functional testing