The latest enhancements to the HBM2 standard will clearly be appreciated by developers of memory bandwidth-hungry ASICs, however in order to add support of HBM2E to their designs, they are also going to need an appropriate controller as well as physical interface. For many companies developing of such IP in-house does not make financial sense, so Rambus has designed a highly-integrated HBM2E solution for licensing.
The HBM2E standard supports 12-Hi DRAM stacks as well as memory devices of up to 16 Gbps, thus enabling to build up to 24 GB stacks using a 1024-bit bus. At the same time, the new specification officially supports data rates of up to 3.2 Gbps, which results in 409.6 GB/s bandwidth per stack. Rambus’s HBM2E solution includes a controller that can work with 12-Hi KGSDs (known good stack dies) as well as a verified 1024-bit PHY that supports speeds of up to 3.2 Gbps.
The Rambus HBM2E controller core (originally developed by Northwest Logic) is DFI 3.1 compatible (with appropriate extensions) and supports AXI, OCP or proprietary interfaces to connect to integrator logic. Meanwhile, the controller also supports Look-Ahead command processing (a standard way to trim latencies) as well as channel densities of up to 24 Gb.
Licensees of Rambus’s HBM2E solution will get everything they need to integrate it into their designs, including source code of the controller (in a bid to synthesize it for a particular process technology) as well as fully-characterized hard macros (GDSII) of the interface. Alternatively, engineers from Rambus can help integrate the HBM2E IP support for a fee.
Related Reading:
- JEDEC Updates HBM2 Memory Standard To 3.2 Gbps; Samsung's Flashbolt Memory Nears Production
- GlobalFoundries and SiFive to Design HBM2E Implementation on 12LP/12LP+
- Samsung Develops 12-Layer 3D TSV DRAM: Up to 24 GB HBM2
- SK Hynix Announces 3.6 Gbps HBM2E Memory For 2020: 1.8 TB/sec For Next-Gen Accelerators
- Samsung HBM2E ‘Flashbolt’ Memory for GPUs: 16 GB Per Stack, 3.2 Gbps
Source: Rambus
from AnandTech https://ift.tt/2InabeK
via IFTTT
0 comments:
Post a Comment