More complex applications require external memory and at the processing rates available today need the highest possible random access rate to that memory. Traditional memory interfaces are a burden to performance because they are plagued by slow speeds, lengthy latency, and high pin counts. As a result, conventional design approaches to implementing external memory have already reached the point of diminishing returns.
Serial protocols & standards break the I/O bottleneck
Consider any modern System-on-Chip (SoC) available today and you will see nearly all the interfaces are serial, except for that to traditional memory ICs. Going forward, the transition to serial memory has already begun and decisions need to be made regarding which serial interface protocols to support. Any interface can be delineated into its physical layer or PHY, transport protocol or PCS, and transaction layer or the command set. Standardisation can take place on each level, independently.
Regarding the serial PHY; the industry standards group, the Optical Internetworking Forum (OIF), published the Common Electrical Interface I/O (CEI) standards including CEI-11 in September 2011.[Ref. 1] Standards development groups such as OIF require three to five years to develop channel models, set clocking and jitter budgets, determine electrical signal coding, and encourage the development of the ecosystem. As a result, these standards are [now] being adopted for a broad range of applications.
In fact, three serial memory interface protocols have adopted the CEI-11 physical definition: the GigaChip Interface (GCI) [Ref. 2], the Interlaken Look-Aside (ILA) [Ref. 3], and the Hybrid Memory Cube Interface (HMC) [Ref. 4] as indicated in Figure 1. Design teams can expect these protocols to also conform to the CEI-25 5 standard in the future. Each of these protocols targets different applications and markets as outlined in Table 1.
Designers therefore do not need to develop three different interface solutions to meet multiple use cases. Instead, host processors can incorporate two or more protocols running on