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

Arm support

Arm training courses and on-site system-design advisory services enable licensees to realize maximum system performance with lowest risk and fastest time-to-market.

Arm training courses Open a support case

Community Blogs

Community Forums

Answered Where do I find presentations and photos from SC'18? 2 votes 1082 views 0 replies Started 7 months ago by John Linford Answer this
Suggested answer 32-bit encoding hex values for Arm instructions 0 votes 72 views 1 replies Latest 9 hours ago by Andy Neil Answer this
Not answered Help regarding AT32UC3C1512C debugging tool 0 votes 34 views 0 replies Started 10 hours ago by iosman123 Answer this
Suggested answer Monitor Mode Debug 0 votes 387 views 4 replies Latest yesterday by Andy Neil Answer this
Suggested answer Memory Protection Unit - Complexity in usage 0 votes 355 views 5 replies Latest yesterday by 42Bastian Schick Answer this
Suggested answer GNU ARM Embedded Toolchain takes more time to compile on Windows 10 than Windows 7 0 votes 330 views 3 replies Latest yesterday by Andy Neil Answer this
Answered Where do I find presentations and photos from SC'18? Started 7 months ago by John Linford 0 replies 1082 views
Suggested answer 32-bit encoding hex values for Arm instructions Latest 9 hours ago by Andy Neil 1 replies 72 views
Not answered Help regarding AT32UC3C1512C debugging tool Started 10 hours ago by iosman123 0 replies 34 views
Suggested answer Monitor Mode Debug Latest yesterday by Andy Neil 4 replies 387 views
Suggested answer Memory Protection Unit - Complexity in usage Latest yesterday by 42Bastian Schick 5 replies 355 views
Suggested answer GNU ARM Embedded Toolchain takes more time to compile on Windows 10 than Windows 7 Latest yesterday by Andy Neil 3 replies 330 views