ARM's Cortex-A15: A big step up for the ARM processor architecture. Targeting 32nm and 28nm technology nodes
Earlier this week Cadence announced that it worked with ARM to develop an implementation methodology for the recently announced, high-end ARM Cortex-A15 processor core, code-named Eagle. The ARM Cortex-A15 processor core has an expanded 40-bit (1Tbyte) memory address space (called Large Physical Address Extensions, LPAE), parity and ECC built into the processor’s cache controllers for both the L1 (32Kbytes of instruction and 32Kbytes of data per processor core) and L2 (maximum size = 4 Mbytes, shared among as many as four processor cores) caches, an AMBA 4 AXI Coherency Extensions (ACE) interface port, and hardware support for multicore designs and virtualization. According to the specification page, the ARM Cortex-A15 processor supports coherent multiprocessing using as many as four closely connected CPUs and supports multiple SMP (symmetric multiprocessing) clusters connected via the AMBA 4 interconnect fabric. The processor core’s virtualization capabilities involve “hardware support for data management and arbitration, whereby multiple software environments and their applications are able to simultaneously access the system capabilities” according to the online specification page. These are truly the specs of an apps-driven processor core.
Related Semiconductor IP
- AES GCM IP Core
- High Speed Ethernet Quad 10G to 100G PCS
- High Speed Ethernet Gen-2 Quad 100G PCS IP
- High Speed Ethernet 4/2/1-Lane 100G PCS
- High Speed Ethernet 2/4/8-Lane 200G/400G PCS
Related Blogs
- TSMC risk production: what does it mean for 28nm?
- Moore's Law and 28nm Yield
- TSMC 28nm Design Advisory
- Fixed logic to give 28nm FPGAs a helping hand
Latest Blogs
- Why Choose Hard IP for Embedded FPGA in Aerospace and Defense Applications
- Migrating the CPU IP Development from MIPS to RISC-V Instruction Set Architecture
- Quintauris: Accelerating RISC-V Innovation for next-gen Hardware
- Say Goodbye to Limits and Hello to Freedom of Scalability in the MIPS P8700
- Why is Hard IP a Better Solution for Embedded FPGA (eFPGA) Technology?