Getting Started

Neoverse reference designs provide useful resources with best practices on how to integrate a Neoverse compute subsystem within a larger SoC. These compute subsystems are targeted at addressing requirements for specific applications in the cloud-to-edge infrastructure markets including servers, edge compute nodes, networking-storage-security offloads, mezzanine cards, 5G stations and access points. 


Neoverse N1 hyperscale reference design

The Neoverse N1 hyperscale reference design details the integration of a high core count server-class SoC subsystem using the Neoverse N1 CPU, CMN-600 coherent mesh interconnect and supporting system IP.

Diagram for the Neoverse N1 hyperscale reference design.

  • 64x Neoverse N1 CPUs, each with 1MB private L2, providing 64 threads of parallel execution
  • 8x8 coherent mesh interconnect (CMN-600) configuration with 64MB of shared system level cache
  • CPUs connected directly to the mesh in dual-core configurations for lowest latency
  • 4x CCIX links for multi-socket, chiplets and accelerator attached configurations
  • 8x memory channels supporting DDR4-3200
  • GIC-600 and CoreSight SoC-400 interfacing over the mesh
  • MMU-600 system MMU and NIC-450 non-coherent interconnect integration with PCIe Gen4 support
  • Fully compliant with Arm ServerReady 1.0 specification

Neoverse N1 edge reference design

The Neoverse N1 edge reference design details the integration of a moderate core count edge server SoC subsystem with the Neoverse N1 CPU and CMN-600 mesh interconnect.

Neoverse N1 Edge Reference Design diagram 

  • 8x Neoverse N1 CPUs, each with 512kB private L2, providing 8 threads of parallel execution
  • 4x2 CMN-600 configuration with 8MB of shared system level cache
  • CPUs are connected to the mesh through quad-core clusters with 2MB shared L3
  • 4x CCIX links to support chiplet and accelerator attached configurations
  • 2x memory channels supporting DDR4-3200
  • GIC-600 generic interrupt controller and CoreSight SoC-400 debug and trace IP interfacing over the mesh
  • MMU-600 system MMU and NIC-450 non-coherent interconnect integration with PCIe Gen4 support
  • Fully compliant with Arm ServerReady 1.0 specification

Neoverse E1 edge reference design

The Neoverse E1 edge reference design details the integration of a moderate core count high data throughput SoC subsystem with the Noeverse E1 CPU and CMN-600 mesh interconnect.

Neoverse E1 Edge Reference Design diagram 

  • 16x Neoverse E1 CPUs, each with 256kB private L2, providing 32 threads of parallel execution
  • 4x2 CMN-600 mesh configuration with 8MB of shared system level cache
  • CPUs are connected to the mesh through octa-core clusters with 2MB shared L3
  • 4x CCIX links to support chiplet and accelerator attached configurations
  • 2x memory channels supporting DDR4-3200
  • GIC-600 generic interrupt controller and CoreSight SoC-400 debug and trace IP interfacing over the mesh
  • MMU-600 system MMU and NIC-450 non-coherent interconnect integration with PCIe Gen4 support
  • Fully compliant with Arm ServerReady 1.0 specification

Request information

Want to know more about system guidance? Contact Arm today.

Contact us

Get support

Community Blogs

Community Forums

Answered Where should I ask my question?
  • ARM Community
0 votes 160 views 1 replies Latest 2 days ago by Oliver Beirne Answer this
Not answered Where do I find presentations and photos from SC'18? 2 votes 4843 views 0 replies Started 1 years ago by John Linford Answer this
Suggested answer problems with timers and i2c
  • Timing
  • Communications Standards
  • STM32 F4
0 votes 118 views 1 replies Latest yesterday by Andy Neil Answer this
Not answered Does Keil MDK5 support any RTOS with Bluenrg-2?
  • Keil MDK Cortex-M Edition
  • Bluetooth LE
  • CMSIS RTOS
0 votes 126 views 0 replies Started yesterday by Cletus87408 Answer this
Suggested answer C library folder structure
  • IDEs and Tool Suites
  • Library
0 votes 176 views 2 replies Latest 2 days ago by Clonimus74 Answer this
Suggested answer converting/ moving from Linux compiler to Keil 0 votes 155 views 1 replies Latest 2 days ago by Andy Neil Answer this
Answered Where should I ask my question? Latest 2 days ago by Oliver Beirne 1 replies 160 views
Not answered Where do I find presentations and photos from SC'18? Started 1 years ago by John Linford 0 replies 4843 views
Suggested answer problems with timers and i2c Latest yesterday by Andy Neil 1 replies 118 views
Not answered Does Keil MDK5 support any RTOS with Bluenrg-2? Started yesterday by Cletus87408 0 replies 126 views
Suggested answer C library folder structure Latest 2 days ago by Clonimus74 2 replies 176 views
Suggested answer converting/ moving from Linux compiler to Keil Latest 2 days ago by Andy Neil 1 replies 155 views