V Unit
V Unit
Asst. Professor
MGIT.
ARM-Cortex Processors/controllers
The ARM-Cortex microcontroller is a most popular
microcontroller in the digital embedded system world
and most of the industries prefer only ARM
microcontrollers since it consists of enormous features
to implement products with an advanced appearance.
32-bit cores:
ARM Cortex-A5, A7, A8, A9,A12, A15, A17 ,A32
64-bit cores:
ARM Cortex-A35, A53,A55,A57, A72, A73,75, A76 and A77.
The main distinguishing feature of the ARM-A core
compared to ARM Cortex-R cores and ARM Cortex-M
cores, is
only the ARM-A core includes a memory management
unit (MMU).
ARMv8-A architecture:
The Cortex-A32 /A34 / A35 / A53 / A57 / A72 / A73 cores
implement the ARMv8-A architecture.
ARMv8.2-A architecture:
The Cortex-A55 / A65 / A75 / A76 /A77 cores implement
the ARMv8.2-A architecture.
The Cortex-A5 processor
The Cortex-A5 processor is the smallest ARM multi-
core applications processor.
https://www.arm.com/products/silicon-ip-cpu
ARM-Cortex R-series
ARM-Cortex R4-Processor
ARM-Cortex R4-Processor
ARM-Cortex R-series
The ARM Cortex-R Series is a family of embedded processors for real-time
systems. The Cortex-R family processors support the ARM and Thumb
instruction sets.
The ARM Cortex-M4 processor is a low-power processor that features low gate count, low interrupt
latency, and low-cost debug. The Cortex-M4F is a processor with the same capability as the Cortex-
M4 processor, and includes floating point arithmetic functionality. These processors are intended for
applications requiring digital signal processing functionality.
The ARM Cortex-M3 processor is a low-power processor that features low gate count, low interrupt
latency, and low-cost debug. It is intended for deeply embedded applications that require fast
interrupt response, including microcontrollers and automotive and industrial control systems.
The ARM Cortex-M1 FPGA processor is intended for deeply embedded applications that require a
small processor integrated into an FPGA.
The ARM Cortex-M0+ processor is a very low gate count, highly energy efficient processor that is
intended for microcontroller and deeply embedded applications that require an area and power
consumption optimized processor, with a rich set of configuration options.
The ARM Cortex-M0 processor is a very low gate count, energy efficient processor that is intended
for microcontroller and deeply embedded applications that require an area optimized processor.
ARM Architecture and Processors
Table 2-1 lists the architecture version implemented by a number of older ARM processors.
v5TE - ARM946E-S™
ARM966E-S™
ARM968E-S
v5TEJ ARM926EJ-S™ -
v6K ARM1136J(F)-S™ -
ARM11™ MPCore™
v6T2 - ARM1156T2-S™
Table 2-2 lists the architecture version implemented by the Cortex family of processors.
Cortex-A15 (MP)
Table 2-3 on page 2-9 compares the properties of Cortex-A series processors. For processor
cache information, see Table 8-1 on page 8-11.
ARM DEN0013D Copyright © 2011 – 2013 ARM. All rights reserved. 2-8
ID012214 Non-Confidential
ARM Architecture and Processors
Processor
Release date Dec 2009 Oct 2011 July 2006 March 2008 June 2013 April 2011
Execution order In-order In-order In-order Out of order Out of order Out of order
Cores 1 to 4 1 to 4 1 1 to 4 1 to 4 1 to 4
Return stack 4 8 8 8 8 48
entries
ARM DEN0013D Copyright © 2011 – 2013 ARM. All rights reserved. 2-9
ID012214 Non-Confidential
ARM Architecture and Processors
The Cortex-A5 processor is the smallest ARM multi-core applications processor. Devices based
on this processor are typically low-cost, capable of delivering the internet to the widest possible
range of devices from low-cost entry-level smartphones and smart mobile devices, to
embedded, consumer and industrial devices.
NEON
Data Engine
Cortex-A5 processor
Floating-point
unit
4
3
Instruction
Data Cache 2
Cache
Core 1
SCU ACP
ARM DEN0013D Copyright © 2011 – 2013 ARM. All rights reserved. 2-10
ID012214 Non-Confidential
ARM Architecture and Processors
The ARM Cortex-A7 processor is the most energy efficient application processor developed by
ARM and extends ARM’s low-power leadership in entry level smart phones, tablets and other
advanced mobile devices.
NEON
Data Engine
Cortex-A7 processor
Floating-point
unit
4
3
Instruction
Data Cache 2
Cache
Core 1
• Architecture and feature set identical to the Cortex-A15 processor, enabling big.LITTLE
configuration.
• Floating-point unit.
The ARM Cortex-A8 processor, has the ability to scale in speed from 600MHz to greater than
1GHz. The Cortex-A8 processor can meet the requirements for power-optimized mobile
devices needing operation in less than 300mW; and performance-optimized consumer
applications requiring 2000 Dhrystone MIPS. It is available in a number of different devices,
including the S5PC100 from Samsung, the OMAP3530 from Texas Instruments and the
ARM DEN0013D Copyright © 2011 – 2013 ARM. All rights reserved. 2-11
ID012214 Non-Confidential
ARM Architecture and Processors
i.MX515 from Freescale. From high-end feature phones to netbooks, DTVs, printers and
automotive-infotainment, the Cortex-A8 processor offers a proven high-performance solution
with millions of units shipped annually
NEON
Data Engine
Cortex-A8 processor
Dynamic branch
prediction
L1 Instruction Floating-point
L1 Data Cache unit
Cache
Integrated L2 Cache
The ARM Cortex-A9 processor is a power-efficient and popular high performance choice in low
power or thermally constrained cost-sensitive devices.
It is currently shipping in large volumes for smartphones, digital TV, consumer and enterprise
applications. The Cortex-A9 processor provides an increase in performance of greater than 50%
compared to the Cortex-A8 processor. The Cortex-A9 processor can be configured with up to
four cores delivering peak performance when required. Configurability and flexibility makes
the Cortex-A9 processor suitable for wide variety of markets and applications.
ARM DEN0013D Copyright © 2011 – 2013 ARM. All rights reserved. 2-12
ID012214 Non-Confidential
ARM Architecture and Processors
NEON
Data Engine
Cortex-A9 processor
Floating-point
unit
4
3
L1 Instruction
L1 Data Cache 2
Cache
Core 1
SCU ACP
Devices containing the Cortex-A9 processor include nVidia’s dual-core Tegra-2, the
SPEAr1300 from ST and TI’s OMAP4 platform.
• Floating-point unit.
The high performance and high-end feature set of the Cortex-A12 processor is suitable for many
use cases. Mid-range devices can build on the success of high-end devices and continue driving
the fastest growing market segment in mobile.
Architecturally, the Cortex-A12 processor is based on the latest ARMv7-A architecture and
features extensions that are aligned with processors such as the Cortex-A15 processor.
ARM DEN0013D Copyright © 2011 – 2013 ARM. All rights reserved. 2-13
ID012214 Non-Confidential
ARM Architecture and Processors
NEON
Data Engine
Cortex-A12 processor
Floating-point
unit
4
3
L1 Instruction
L1 Data Cache 2
Cache
Core 1
The ARM Cortex-A15 processor is designed to deliver unprecedented flexibility and processing
capability. This processor is designed with advanced power reduction techniques, and enables
products in a wide range of markets ranging from mobile computing, high-end digital home,
servers and wireless infrastructure.
The Cortex-A15 MPCore processor has full application compatibility with all other Cortex-A
series processors.
ARM DEN0013D Copyright © 2011 – 2013 ARM. All rights reserved. 2-14
ID012214 Non-Confidential
ARM Architecture and Processors
NEON
Data Engine
Cortex-A15 processor
Floating-point
unit
4
3
L1 Instruction
L1 Data Cache 2
Cache
Core 1
• Floating-point unit.
ARM DEN0013D Copyright © 2011 – 2013 ARM. All rights reserved. 2-15
ID012214 Non-Confidential
ARM Architecture and Processors
• 32-bit RISC core, with 16 × 32-bit visible registers with mode-based register banking.
• Load/Store Architecture.
• 4GB of virtual address space and a minimum of 4GB of physical address space.
• Virtual page sizes of 4KB, 64KB, 1MB and 16MB. Cacheability attributes and access
permissions can be set on a per-page basis.
• Physically indexed, physically tagged (PIPT) data caches. See Virtual and physical tags
and indexes on page 8-11.
All of these architectural points are described in the chapters which follow.
ARM DEN0013D Copyright © 2011 – 2013 ARM. All rights reserved. 2-16
ID012214 Non-Confidential
ARMv8-A Architecture and Processors
Processor
Cortex-A53 Cortex-A57
Cores 1 to 4 1 to 4
A. IMPLEMENTATION DEFINED
This section describes each of the processors that implement the ARMv8-A architecture. It only
gives a general description in each case. For more specific information on each processor, see
Table 2-1 on page 2-5.
The Cortex-A53 processor is a mid-range, low-power processor with between one and four
cores in a single cluster, each with an L1 cache subsystem, an optional integrated GICv3/4
interface, and an optional L2 cache controller.
NEON
Data Engine
with crypto ext
Cortex-A53 processor
Floating-point
unit
Level 1 Memory
Level 1 Data
Instruction Management 3
Cache w/ECC
Cache Unit
2
Performance Monitor Data Processing Core 1
Unit Unit
0
• Lower power consumption from the use of hierarchical clock gating, power domains, and
advanced retention modes.
• Power-optimized L2 cache design delivers lower latency and balances performance with
efficiency.
The Cortex-A57 processor features cache coherent interoperability with other processors,
including the ARM Mali™ family of Graphics Processing Units (GPUs) for GPU compute and
provides optional reliability and scalability features for high-performance enterprise
applications. It provides significantly more performance than the ARMv7 Cortex-A15
processor, at a higher level of power efficiency. The inclusion of cryptography extensions
improves performance on cryptography algorithms by 10 times over the previous generation of
processors.
NEON
Data Engine
with crypto ext
Cortex-A57 processor
Floating-point
unit
Level 1
Level 1 Data Memory
Instruction 3
Cache w/ECC Protection Unit
Cache
2
Performance Monitor Unit Core 1
0
The Cortex-A57 processor fully implements the ARMv8-A architecture. It enables multi-core
operation with between one and four cores multi-processing within a single cluster. Multiple
coherent SMP clusters are possible, through AMBA5 CHI or AMBA 4 ACE technology. Debug
and trace are available through CoreSight technology.
2
Hercules™ MCUs RM57L
330 MHz
4MB Flash
Scalable platform for functional safety applications RM48L9
220 MHz
512kB RAM
3MB Flash
256kB RAM
RM48L7 337p BGA
200 MHz
2MB Flash
256kB RAM 144p QFP
RM46L8 337p BGA 570LC43
220 MHz 300 MHz
1.2MB Flash 144p QFP 4MB Flash
512kB RAM
RM44L9 192kB RAM
337p BGA
570LS31
180 MHz
1MB Flash 180 MHz
128kB RAM
144p QFP
3MB Flash
256kB RAM
337p BGA
RM44L5 337p BGA 570LS12
180 MHz 180 MHz
1.2MB Flash
768K Flash
128kB RAM
100p QFP 192kB RAM 144p QFP
144p QFP 570LS09 337p BGA
160 MHz
RM42L4 1MB Flash
100 MHz 144p QFP
100p QFP 128kB RAM
384kB Flash
570LS07 337p BGA
32kB RAM 144p QFP 160 MHz
768kB Flash
128kB RAM
100p QFP
570LS04 144p QFP
RM41L2 100p QFP 80 MHz
80MHz
128kB Flash
384kB Flash 100p QFP
32kB RAM
32kB RAM 144p QFP External certification: ISO 26262, IEC 61508
570LS03
80 MHz 100p QFP
100p QFP 256kB Flash
32kB RAM
Documentation: Safety Manual, FMEDA reports
Production
100p QFP
Cortex-R: Ideal for safety-critical applications
Lockstep implementation
Safety features
Compare
• Supports Lockstep Error
Output + Control
• Memory Protection Unit (MPU)
CCM
• Error-Correcting Code (ECC) Cycle Delay
Self
Test
Higher performance
• 8-stage processor pipeline
• Dual issue – two instructions can
execute in parallel
• Load store unit reduces stalling
• Pre-fetch and Branch Prediction Units
• Cached*
Cycle Delay
Real-time / determinism
• Tightly Coupled Memory (TCM)
• Fast interrupt response Input + Control
64-bit
Floating Point Unit (FPU)
• FPU is compliant to IEEE754
• Supports features:
– Single-precision and double-precision add, subtract, multiply, divide, multiply and accumulate,
and square root operations
– Comparisons
– Underflow
– Exceptions
Processor modes
Mode Description • ARM has 7 basic operating modes.
Supervisor Entered on reset and when a • Modes other than user mode have
(SVC) Software Interrupt instruction privileged access rights.
(SWI) is executed
Undef Used to handle undefined • Usually the initial setup is done in SVC
instructions Privileged mode after reset, then switch to
Abort Used to handle memory modes system or user mode afterwards.
Exception modes
Current Program
Status Register (CPSR) CPSR CPSR CPSR CPSR CPSR CPSR
Saved Program SPSR FIQ SPSR IRQ SPSR SVC SPSR ABORT SPSR UNDEF
Status Register (SPSR)
Current Processor Status Register (CPSR)
31 30 29 28 27 26 25 24 23 20 19 16 15 10 9 8 7 6 5 4 0
• Index interrupts mode (legacy mode): The interrupt dispatching has to be done completely in
software (software dispatcher).
• Register-vectored interrupt mode: This mode allows the interrupt dispatching to be done in
hardware, the software has only to load the interrupt vector of the ISR from the VIM module
and branch to the vector.
• Hardware-vectored interrupt mode (IRQ only): This mode has the advantage that the vector
of the ISR has not been loaded by software. Instead, the vector is directly supplied to the MCU
core via the VIC port, and saves some CPU cycles for lower interrupt latency compared to the
second mode.
Index interrupts mode
1. Events occur within peripherals
2. Peripherals make FIQ/IRQ requests
to the VIM
3. VIM prioritizes the requests &
provides the highest ISR to CPU
4. CPU fetch from 0x18/0x1C.
5. Branch to ISR dispatcher.
6. Load Interrupt offset .(IRQINDEX,
FIQINDEX)
7. Decide which ISR to execute.
8. Branch to ISR
VIM:
Prioritizing and
signaling IRQ/FIQ
to ARM Cortex-R4
Register-vectored interrupts
1. Events occur within peripherals
2. Peripherals make FIQ/IRQ requests
to the VIM
3. VIM prioritizes the requests &
provides the addr of the highest ISR
to CPU
4. CPU fetches from 0x18/0x1C
5. Branch to ISR (LDR PC, [PC, #-
0x1B0]), (IRQVECREG/FIQVECREG.)
6. Branch to ISR
VIM:
Prioritizing and signaling
IRQ/FIQ to ARM Cortex-R4
Hardware-vectored interrupts (only IRQ)
1. Events occur within
peripherals
2. Peripherals make FIQ/IRQ
requests to the VIM
3. VIM prioritizes the requests
4. VIM provides address of
highest pending request
directly to the processors VIC
port.
5. CPU branches directly to ISR.
VIM:
Prioritizing and signaling
IRQ/FIQ to
ARM Cortex-R4/5
Abort: Prefetch and Data
Prefetch Abort (PABT)
• CPU tries to execute an instruction from a protected or faulty memory location, such as:
– The memory location is not implemented in the system.
– The memory region is protected by the MPU.
– An error is detected in the data by the ECC checking logic.
• All prefetch aborts are precise.
Contents
ARM cores
Designed by ARM
Designed by third parties
ARM core timeline
See also
References
Further reading
ARM cores
Designed by ARM
https://en.wikipedia.org/wiki/List_of_ARM_microarchitectures 1/14
15/04/2020 List of ARM microarchitectures - Wikipedia
https://en.wikipedia.org/wiki/List_of_ARM_microarchitectures 2/14
15/04/2020 List of ARM microarchitectures - Wikipedia
ARMv6T2 ARM1156T2(F)- 9-stage pipeline, SIMD, Thumb-2, (VFP), Variable, MPU [10]
S enhanced DSP instructions
965 DMIPS @
ARM1176JZ(F)- Variable, MMU + 772 MHz, up to [11]
ARMv6Z As ARM1136EJ(F)-S
S TrustZone 2,600 DMIPS with
four processors
ARMv6K ARM11MPCore As ARM1136EJ(F)-S, 1–4 core SMP Variable, MMU
ARMv6-M SC000 0.9 DMIPS/MHz
SecurCore ARMv4T SC100
ARMv7-M SC300 1.25 DMIPS/MHz
Microcontroller profile, most Thumb + some
Thumb-2,[13] hardware multiply instruction Optional cache,
Cortex-M0[12] 0.84 DMIPS/MHz
(optional small), optional system timer, no TCM, no MPU
optional bit-banding memory
Microcontroller profile, most Thumb + some Optional cache,
Thumb-2,[13] hardware multiply instruction no TCM, optional
Cortex-M0+[14] 0.93 DMIPS/MHz
ARMv6-M (optional small), optional system timer, MPU with 8
optional bit-banding memory regions
Microcontroller profile, most Thumb + some 136 DMIPS @
Optional cache,
Thumb-2,[13] hardware multiply instruction 0–1024 KB I- 170 MHz,[16]
Cortex-M1[15] (optional small), OS option adds SVC / TCM, 0–1024 KB (0.8 DMIPS/MHz
banked stack pointer, optional system timer, D-TCM, no MPU FPGA-dependent)[17]
no bit-banding memory
Optional cache,
Microcontroller profile, Thumb / Thumb-2,
no TCM, optional
ARMv7-M Cortex-M3[18] hardware multiply and divide instructions, 1.25 DMIPS/MHz
MPU with 8
optional bit-banding memory
regions
Microcontroller profile, Thumb / Thumb-2 / Optional cache,
DSP / optional VFPv4-SP single-precision no TCM, optional 1.25 DMIPS/MHz
Cortex-M4[19]
FPU, hardware multiply and divide MPU with 8 (1.27 w/FPU)
instructions, optional bit-banding memory regions
Cortex-M
0−64 KB I-cache,
ARMv7E-M 0−64 KB D-
Microcontroller profile, Thumb / Thumb-2 / cache, 0–16 MB
DSP / optional VFPv5 single and double I-TCM, 0–16 MB
Cortex-M7[20] 2.14 DMIPS/MHz
precision FPU, hardware multiply and divide D-TCM (all these
instructions w/optional ECC),
optional MPU with
8 or 16 regions
Optional cache,
Microcontroller profile, Thumb-1 (most), no TCM, optional
Cortex-M23[21] 0.99 DMIPS/MHz
Thumb-2 (some), Divide, TrustZone MPU with 16
regions
Optional cache,
Microcontroller profile, Thumb-1, Thumb-2,
no TCM, optional
Cortex-M33[22] Saturated, DSP, Divide, FPU (SP), 1.50 DMIPS/MHz
MPU with 16
ARMv8-M TrustZone, Co-processor
regions
Built-in cache
(with option 2–
Microcontroller profile, Thumb-1, Thumb-2,
Cortex- 16 KB), I-cache,
Saturated, DSP, Divide, FPU (SP), 1.50 DMIPS/MHz
M35P[23] TrustZone, Co-processor
no TCM, optional
MPU with 16
regions
Cortex-R ARMv7-R Real-time profile, Thumb / Thumb-2 / DSP /
0–64 KB / 0–
optional VFPv3 FPU, hardware multiply and
64 KB, 0–2 of 0–
optional divide instructions, optional parity &
Cortex-R4[24] 8 MB TCM, opt. 1.67 DMIPS/MHz[25]
ECC for internal buses / cache / TCM, 8-
MPU with 8/12
stage pipeline dual-core running lockstep
regions
with fault logic
Real-time profile, Thumb / Thumb-2 / DSP /
optional VFPv3 FPU and precision, hardware
multiply and optional divide instructions, 0–64 KB / 0–
optional parity & ECC for internal buses / 64 KB, 0–2 of 0–
Cortex-R5[26] cache / TCM, 8-stage pipeline dual-core 8 MB TCM, opt. 1.67 DMIPS/MHz[25]
running lock-step with fault logic / optional as MPU with 12/16
2 independent cores, low-latency peripheral regions
port (LLPP), accelerator coherency port
(ACP)[27]
https://en.wikipedia.org/wiki/List_of_ARM_microarchitectures 3/14
15/04/2020 List of ARM microarchitectures - Wikipedia
multiply and optional divide instructions, 128 KB TCM, opt.
optional parity & ECC for internal buses / MPU with 16
cache / TCM, 11-stage pipeline dual-core regions
running lock-step with fault logic / out-of-
order execution / dynamic register renaming /
optional as 2 independent cores, low-latency
peripheral port (LLPP), ACP[27]
https://en.wikipedia.org/wiki/List_of_ARM_microarchitectures 4/14
15/04/2020 List of ARM microarchitectures - Wikipedia
Cortex-A35[43] Application profile, AArch32 and AArch64, 1– 8−64 KB w/parity 1.78 DMIPS/MHz
4 SMP cores, TrustZone, NEON advanced / 8−64 KB w/ECC
SIMD, VFPv4, hardware virtualization, 2- L1 per core,
width decode, in-order pipeline 128 KB–1 MB
L2 shared, 40-bit
physical
addresses
8−64 KB w/parity
/ 8−64 KB w/ECC
Application profile, AArch32 and AArch64, 1–
L1 per core,
4 SMP cores, TrustZone, NEON advanced
Cortex-A53[44] SIMD, VFPv4, hardware virtualization, 2-
128 KB–2 MB 2.3 DMIPS/MHz
L2 shared, 40-bit
width decode, in-order pipeline
physical
addresses
48 KB w/DED
parity / 32 KB
Application profile, AArch32 and AArch64, 1–
w/ECC L1 per
4 SMP cores, TrustZone, NEON advanced
core; 512 KB– 4.1–
Cortex-A57[45] SIMD, VFPv4, hardware virtualization, 3-
width decode superscalar, deeply out-of-
2 MB L2 shared 4.5 DMIPS/MHz[46][47]
w/ECC; 44-bit
order pipeline
physical
addresses
48 KB w/DED
parity / 32 KB
Application profile, AArch32 and AArch64, 1–
w/ECC L1 per
4 SMP cores, TrustZone, NEON advanced
core; 512 KB–
Cortex-A72[48] SIMD, VFPv4, hardware virtualization, 3- 4.7 DMIPS/MHz
2 MB L2 shared
width superscalar, deeply out-of-order
w/ECC; 44-bit
pipeline
physical
addresses
64 KB / 32−64 KB
Application profile, AArch32 and AArch64, 1– L1 per core,
4 SMP cores, TrustZone, NEON advanced 256 KB–8 MB
Cortex-A73[49] SIMD, VFPv4, hardware virtualization, 2- L2 shared w/ 4.8 DMIPS/MHz[50]
width superscalar, deeply out-of-order optional ECC, 44-
pipeline bit physical
addresses
ARMv8.2-A Application profile, AArch32 and AArch64, 1– 16−64 KB /
8 SMP cores, TrustZone, NEON advanced 16−64 KB L1,
Cortex-A55[51] SIMD, VFPv4, hardware virtualization, 2- 256 KB L2 per
core, 4 MB L3
width decode, in-order pipeline[52]
shared
Application profile, AArch64, 1–8 SMP cores,
64 / 64 KB L1,
Arm Cortex- TrustZone, NEON advanced SIMD, VFPv4,
256 KB L2 per
hardware virtualization, 2-wide decode
A65AE[53] core, 4 MB L3
superscalar, 3-width issue, out-of-order
shared
pipeline, SMT
Application profile, AArch32 and AArch64, 1–
64 / 64 KB L1,
8 SMP cores, TrustZone, NEON advanced
512 KB L2 per
Cortex-A75[54] SIMD, VFPv4, hardware virtualization, 3-
core, 4 MB L3
width decode superscalar, deeply out-of-
shared
order pipeline[55]
Application profile, AArch32 (non-privileged
64 / 64 KB L1,
level or EL0 only) and AArch64, 1–4 SMP
256−512 KB L2
cores, TrustZone, NEON advanced SIMD,
Cortex-A76[56] VFPv4, hardware virtualization, 4-width
per core,
512 KB−4 MB L3
decode superscalar, 8-way issue, 13 stage
shared
pipeline, deeply out-of-order pipeline[57]
Application profile, AArch32 (non-privileged
1.5K L0 MOPs
level or EL0 only) and AArch64, 1–4 SMP
cache, 64 / 64 KB
cores, TrustZone, NEON advanced SIMD,
L1, 256−512 KB
Cortex-A77[58] VFPv4, hardware virtualization, 4-width
L2 per core,
decode superscalar, 6-width instruction fetch,
512 KB−4 MB L3
12-way issue, 13 stage pipeline, deeply out-
shared
of-order pipeline[57]
Neoverse Application profile, AArch32 (non-privileged 64 / 64 KB L1,
level or EL0 only) and AArch64, 1–4 SMP 512−1024 KB L2
cores, TrustZone, NEON advanced SIMD, per core,
Neoverse N1[59] VFPv4, hardware virtualization, 4-width 2−128 MB L3
decode superscalar, 8-way dispatch/issue, 13 shared, 128 MB
stage pipeline, deeply out-of-order system level
pipeline[57] cache
Neoverse E1 Application profile, AArch64, 1–8 SMP cores, 32−64 KB /
TrustZone, NEON advanced SIMD, VFPv4, 32−64 KB L1,
hardware virtualization, 2-wide decode 256 KB L2 per
https://en.wikipedia.org/wiki/List_of_ARM_microarchitectures 5/14
15/04/2020 List of ARM microarchitectures - Wikipedia
superscalar, 3-width issue, 10 stage pipeline, core, 4 MB L3
out-of-order pipeline, SMT shared
ARM ARM Cache (I / D),
ARM core Feature Typical MIPS @ MHz Reference
family architecture MMU
As Dhrystone is a synthetic benchmark developed in 1980s, it is no longer representative of prevailing workloads – use with caution.
These cores implement the ARM instruction set, and were developed independently by companies with an architectural license from
ARM.
https://en.wikipedia.org/wiki/List_of_ARM_microarchitectures 6/14
15/04/2020 List of ARM microarchitectures - Wikipedia
Instruction
Core Family Microarchitecture Feature Cache (I / D), MMU Typical MIPS @ MHz
set
100–233 MHz
StrongARM SA-110 5-stage pipeline 16 KB / 16 KB, MMU
ARMv4 1.0 DMIPS/MHz
(Digital)
SA-1100 derivative of the SA-110 16 KB / 8 KB, MMU
Up to 32 KB / 32 KB cache, 1.26 DMIPS/MHz
FA510
MPU 100–200 MHz
6-stage pipeline
Up to 32 KB / 32 KB cache, 1.26 MIPS/MHz
ARMv4 FA526
MMU 166–300 MHz
1.35 DMIPS/MHz
FA626 8-stage pipeline 32 KB / 32 KB cache, MMU
500 MHz
Faraday[60]
1.22 DMIPS/MHz
(Faraday FA606TE 5-stage pipeline No cache, no MMU
200 MHz
Technology)
1.43 MIPS/MHz
FA626TE 8-stage pipeline
800 MHz
ARMv5TE
1.43 MIPS/MHz
FMP626TE 8-stage pipeline, SMP 32 KB / 32 KB cache, MMU
500 MHz
2.4 DMIPS/MHz
FA726TE 13 stage pipeline, dual issue
1000 MHz
7-stage pipeline, Thumb, enhanced
XScale 32 KB / 32 KB, MMU 133–400 MHz
DSP instructions
XScale
Wireless MMX, wireless SpeedStep
(Intel / ARMv5TE Bulverde 32 KB / 32 KB, MMU 312–624 MHz
added
Marvell)
32 KB / 32 KB L1, optional
Monahans[61] Wireless MMX2 added Up to 1.25 GHz
L2 cache up to 512 KB, MMU
Feroceon 5–8 stage pipeline, single-issue 16 KB / 16 KB, MMU
600–2000 MHz
Jolteon 5–8 stage pipeline, dual-issue 32 KB / 32 KB, MMU
ARMv5
Sheeva 5–8 stage pipeline, single-issue, 1.46 DMIPS/MHz
(Marvell) PJ1 (Mohawk) 32 KB / 32 KB, MMU
Wireless MMX2 1.06 GHz
ARMv6 / 6–9 stage pipeline, dual-issue, 2.41 DMIPS/MHz
PJ4 32 KB / 32 KB, MMU
ARMv7-A Wireless MMX2, SMP 1.6 GHz
1 or 2 cores. ARM / Thumb / Thumb-
Scorpion[62] 2 / DSP / SIMD / VFPv3 FPU / NEON 256 KB L2 per core 2.1 DMIPS/MHz per core
(128-bit wide)
ARMv7-A
1, 2, or 4 cores. ARM / Thumb /
4 KB / 4 KB L0, 16 KB /
Snapdragon Krait[62] Thumb-2 / DSP / SIMD / VFPv4 FPU
16 KB L1, 512 KB L2 per core
3.3 DMIPS/MHz per core
(Qualcomm) / NEON (128-bit wide)
Up to 2.2 GHz
ARMv8-A Kryo[63] 4 cores. ?
(6.3 DMIPS/MHz)
https://en.wikipedia.org/wiki/List_of_ARM_microarchitectures 7/14
15/04/2020 List of ARM microarchitectures - Wikipedia
X-Gene ARMv8-A X-Gene 64-bit, quad issue, SMP, 64 cores[72] Cache, MMU, virtualization 3 GHz (4.2 DMIPS/MHz
(Applied per core)
Micro)
2 cores. AArch64, 7-wide
superscalar, in-order, dynamic code
Denver 128 KB I-cache / 64 KB D-
(Nvidia)
ARMv8-A Denver[73][74] optimization, 128 MB optimization
cache
Up to 2.5 GHz
cache,
Denver1: 28nm, Denver2:16nm
2 cores. AArch64, 10-wide
superscalar, in-order, dynamic code
Carmel optimization, ? MB optimization
ARMv8(t.b.d.) Carmel[75][76] ? KB I-cache / ? KB D-cache Up to ? GHz
(Nvidia) cache,
functional safety, dual execution,
parity & ECC
ThunderX 64-bit, with two models with 8–16 or
ARMv8-A ThunderX ? Up to 2.2 GHz
(Cavium) 24–48 cores (×2 w/two chips)
K12
ARMv8-A K12[77] ? ? ?
(AMD)
5.1 DMIPS/MHz
64 KB I-cache / 32 KB D-
M1/M2 4 cores. AArch64, 4-wide, quad-
ARMv8-A cache, L2: 16-way shared
("Mongoose")[78] issue, superscalar, out-of-order
2 MB (2.6 GHz)
64 KB I-cache / 32 KB D-
Exynos 4 cores, AArch64, 6-decode, 6-issue, cache, L2: 8-way private
(Samsung) ARMv8-A M3 ("Meerkat")[79] ?
6-wide. superscalar, out-of-order 512 KB, L3: 16-way shared
4 MB
64 KB I-cache / 32 KB D-
2 cores, AArch64, 6-decode, 6-issue, cache, L2: 8-way private
ARMv8.2-A M4 ("Cheetah") ?
6-wide. superscalar, out-of-order 512 KB, L3: 16-way shared
4 MB
https://en.wikipedia.org/wiki/List_of_ARM_microarchitectures 8/14
15/04/2020 List of ARM microarchitectures - Wikipedia
Neoverse
Classic cores Cortex cores
cores
Year
Real- Application Application Application
ARM7 ARM8 ARM9 ARM10 ARM11 Microcontroller
time (32-bit) (64-bit) (64-bit)
1993 ARM700
ARM710
1994 ARM7DI
ARM7TDMI
1995 ARM710a
1996 ARM810
ARM710T
1997 ARM720T
ARM740T
ARM9TDMI
1998
ARM940T
ARM9E-S
1999 ARM966E-
S
ARM920T
ARM922T
2000 ARM1020T
ARM946E-
S
ARM7TDMI- ARM9EJ-S
ARM1020E
2001 S ARM926EJ-
ARM1022E
ARM7EJ-S S
ARM1026EJ-
2002 ARM1136J(F)-S
S
ARM1156T2(F)-
ARM968E- S
2003
S ARM1176JZ(F)-
S
2004 Cortex-M3
2005 ARM11MPCore Cortex-A8
2006 ARM996HS
2007 Cortex-M1 Cortex-A9
2008
2009 Cortex-M0 Cortex-A5
2010 Cortex-M4(F) Cortex-A15
Cortex-
R4
Cortex-
2011 Cortex-A7
R5
Cortex-
R7
Cortex-A53
2012 Cortex-M0+
Cortex-A57
2013 Cortex-A12
2014 Cortex-M7(F) Cortex-A17
Cortex-A35
2015
Cortex-A72
Cortex-
Cortex-M23 R8
2016 Cortex-A32 Cortex-A73
Cortex-M33(F) Cortex-
R52
Cortex-A55
2017
Cortex-A75
Cortex-
A65AE
2018 Cortex-M35P(F) Cortex-A76
Cortex-
A76AE
2019 Cortex-A77 Neoverse
E1
https://en.wikipedia.org/wiki/List_of_ARM_microarchitectures 9/14
15/04/2020 List of ARM microarchitectures - Wikipedia
Neoverse
N1
See also
Comparison of ARMv7-A cores
Comparison of ARMv8-A cores
List of applications of ARM cores
ARM architecture
References
1. "ARM Powered Standard Products" (http://infocenter.arm.com/help/topic/com.arm.doc.faqs/attached/6745/0141_5linecard.pdf)
(PDF). 2005. Archived (https://web.archive.org/web/20171020195635/http://infocenter.arm.com/help/topic/com.arm.doc.faqs/attach
ed/6745/0141_5linecard.pdf) (PDF) from the original on 20 October 2017. Retrieved 23 December 2017.
2. ARM Ltd and ARM Germany GmbH. "Device Database" (http://www.keil.com/dd/parms/arm.htm). Keil. Archived (https://web.archiv
e.org/web/20110110215343/http://www.keil.com/dd/parms/arm.htm) from the original on 10 January 2011. Retrieved 6 January
2011.
3. "Processors" (http://www.arm.com/products/processors/). ARM. 2011. Archived (https://web.archive.org/web/20110117025703/htt
p://www.arm.com/products/processors/) from the original on 17 January 2011. Retrieved 6 January 2011.
4. "ARM610 Datasheet" (http://bitsavers.org/pdf/acorn/ARM_DDI_0004D_ARM610_Data_Sheet_Aug93.pdf) (PDF). ARM Holdings.
August 1993. Retrieved 29 January 2019.
5. "ARM710 Datasheet" (http://bitsavers.org/pdf/acorn/ARM_DDI_0024C_ARM710_Data_Sheet_Jul94.pdf) (PDF). ARM Holdings.
July 1994. Retrieved 29 January 2019.
6. ARM Holdings (7 August 1996). "ARM810 – Dancing to the Beat of a Different Drum" (https://www.hotchips.org/wp-content/upload
s/hc_archives/hc08/2_Mon/HC8.S4/HC8.4.1.pdf) (PDF). Hot Chips. Archived (https://web.archive.org/web/20181224080542/http
s://www.hotchips.org/wp-content/uploads/hc_archives/hc08/2_Mon/HC8.S4/HC8.4.1.pdf) (PDF) from the original on 24 December
2018. Retrieved 14 November 2018.
7. "VLSI Technology Now Shipping ARM810" (http://www.eetimes.com/document.asp?doc_id=1208831). EE Times. 26 August 1996.
Archived (https://web.archive.org/web/20130926155924/http://www.eetimes.com/document.asp?doc_id=1208831) from the original
on 26 September 2013. Retrieved 21 September 2013.
8. Register 13, FCSE PID register (http://infocenter.arm.com/help/topic/com.arm.doc.ddi0151c/I47491.html) Archived (https://web.arc
hive.org/web/20110707164527/http://infocenter.arm.com/help/topic/com.arm.doc.ddi0151c/I47491.html) 7 July 2011 at the
Wayback Machine ARM920T Technical Reference Manual
9. "ARM1136J(F)-S – ARM Processor" (https://web.archive.org/web/20090321200633/http://www.arm.com/products/CPUs/ARM1136
JF-S.html). Arm.com. Archived from the original (http://www.arm.com/products/CPUs/ARM1136JF-S.html) on 21 March 2009.
Retrieved 18 April 2009.
10. "ARM1156 Processor" (https://web.archive.org/web/20100213205149/https://www.arm.com/products/processors/classic/arm11/arm
1156.php). Arm Holdings. Archived from the original (https://www.arm.com/products/processors/classic/arm11/arm1156.php) on 13
February 2010.
11. "ARM11 Processor Family" (http://www.arm.com/products/processors/classic/arm11/). ARM. Archived (https://web.archive.org/web/
20110115045355/http://www.arm.com/products/processors/classic/arm11/) from the original on 15 January 2011. Retrieved
12 December 2010.
12. "Cortex-M0 Specification Summary; ARM Holdings" (http://arm.com/products/processors/cortex-m/cortex-m0.php?tab=Specificatio
ns). Archived (https://web.archive.org/web/20120321175611/http://arm.com/products/processors/cortex-m/cortex-m0.php?tab=Spe
cifications) from the original on 21 March 2012. Retrieved 13 June 2011.
13. "Cortex-M0/M0+/M1 Instruction set; ARM Holding" (https://archive.today/20130418234149/http://archive.electronicdesign.com/files/
29/20719/fig_01.gif). Archived from the original (http://archive.electronicdesign.com/files/29/20719/fig_01.gif) on 18 April 2013.
14. "Cortex-M0+ Specification Summary" (http://www.arm.com/products/processors/cortex-m/cortex-m0plus.php). Arm Holdings.
Archived (https://web.archive.org/web/20120621091855/http://www.arm.com/products/processors/cortex-m/cortex-m0plus.php)
from the original on 21 June 2012. Retrieved 21 July 2012.
15. "Cortex-M1 Specification Summary; ARM Holdings" (http://arm.com/products/processors/cortex-m/cortex-m1.php?tab=Specificatio
ns). Archived (https://web.archive.org/web/20110707165410/http://arm.com/products/processors/cortex-m/cortex-m1.php?tab=Spe
cifications) from the original on 7 July 2011. Retrieved 13 June 2011.
16. "ARM Extends Cortex Family with First Processor Optimized for FPGA" (http://www.arm.com/news/17017.html) (Press release).
ARM Holdings. 19 March 2007. Archived (https://web.archive.org/web/20070505180243/http://www.arm.com/news/17017.html)
from the original on 5 May 2007. Retrieved 11 April 2007.
17. "ARM Cortex-M1" (http://www.arm.com/products/CPUs/ARM_Cortex-M1.html). ARM product website. Archived (https://web.archiv
e.org/web/20070401051142/http://www.arm.com/products/CPUs/ARM_Cortex-M1.html) from the original on 1 April 2007. Retrieved
11 April 2007.
18. "Cortex-M3 Specification Summary; ARM Holdings" (http://arm.com/products/processors/cortex-m/cortex-m3.php?tab=Specificatio
ns). Archived (https://web.archive.org/web/20120829045848/http://www.arm.com/products/processors/cortex-m/cortex-m3.php?tab
=Specifications) from the original on 29 August 2012. Retrieved 13 June 2011.
https://en.wikipedia.org/wiki/List_of_ARM_microarchitectures 10/14
15/04/2020 List of ARM microarchitectures - Wikipedia
https://en.wikipedia.org/wiki/List_of_ARM_microarchitectures 12/14
15/04/2020 List of ARM microarchitectures - Wikipedia
63. "Snapdragon 820 and Kryo CPU: heterogeneous computing and the role of custom compute" (https://www.qualcomm.com/news/sn
apdragon/2015/09/02/snapdragon-820-and-kryo-cpu-heterogeneous-computing-and-role-custom). Qualcomm. 2 September 2015.
Archived (https://web.archive.org/web/20150905203003/https://www.qualcomm.com/news/snapdragon/2015/09/02/snapdragon-82
0-and-kryo-cpu-heterogeneous-computing-and-role-custom) from the original on 5 September 2015. Retrieved 6 September 2015.
64. Lal Shimpi, Anand (15 September 2012). "The iPhone 5's A6 SoC: Not A15 or A9, a Custom Apple Core Instead" (http://www.anan
dtech.com/show/6292/iphone-5-a6-not-a15-custom-core). AnandTech. Archived (https://web.archive.org/web/20120915203513/htt
p://www.anandtech.com/show/6292/iphone-5-a6-not-a15-custom-core) from the original on 15 September 2012. Retrieved
15 September 2012.
65. Smith, Ryan (11 November 2014). "Apple A8X's GPU - GAX6850, Even Better Than I Thought" (http://www.anandtech.com/show/8
716/apple-a8xs-gpu-gxa6850-even-better-than-i-thought). Anandtech. Archived (https://web.archive.org/web/20141130014356/htt
p://www.anandtech.com/show/8716/apple-a8xs-gpu-gxa6850-even-better-than-i-thought) from the original on 30 November 2014.
Retrieved 29 November 2014.
66. Chester, Brandon (15 July 2015). "Apple Refreshes The iPod Touch With A8 SoC And New Cameras" (http://www.anandtech.com/
show/9443/apple-refreshes-the-ipod-touch-with-a8-soc-and-new-camera). Anandtech. Archived (https://web.archive.org/web/2015
0905232041/http://anandtech.com/show/9443/apple-refreshes-the-ipod-touch-with-a8-soc-and-new-camera) from the original on 5
September 2015. Retrieved 11 September 2015.
67. Ho, Joshua (28 September 2015). "iPhone 6s and iPhone 6s Plus Preliminary Results" (http://www.anandtech.com/show/9662/ipho
ne-6s-and-iphone-6s-plus-preliminary-results). Anandtech. Archived (https://web.archive.org/web/20160526001956/http://www.ana
ndtech.com/show/9662/iphone-6s-and-iphone-6s-plus-preliminary-results) from the original on 26 May 2016. Retrieved
18 December 2015.
68. Ho, Joshua (28 September 2015). "The iPhone 7 and iPhone 7 Plus Review" (http://www.anandtech.com/show/10685/the-iphone-7
-and-iphone-7-plus-review). Anandtech. Archived (https://web.archive.org/web/20170914220425/http://www.anandtech.com/show/
10685/the-iphone-7-and-iphone-7-plus-review) from the original on 14 September 2017. Retrieved 14 September 2017.
69. "A11 Bionic - Apple" (https://en.wikichip.org/wiki/apple/ax/a11). WikiChip. Retrieved 1 February 2019.
70. "The iPhone XS & XS Max Review: Unveiling the Silicon Secrets" (https://www.anandtech.com/show/13392/the-iphone-xs-xs-max-r
eview-unveiling-the-silicon-secrets/). Anandtech. Archived (https://web.archive.org/web/20190212070449/https://www.anandtech.c
om/show/13392/the-iphone-xs-xs-max-review-unveiling-the-silicon-secrets/) from the original on 12 February 2019. Retrieved
11 February 2019.
71. Frumusanu, Andrei. "The Apple iPhone 11, 11 Pro & 11 Pro Max Review: Performance, Battery, & Camera Elevated" (https://www.a
nandtech.com/show/14892/the-apple-iphone-11-pro-and-max-review). www.anandtech.com. Retrieved 20 October 2019.
72. "Archived copy" (http://www.pcworld.com/article/2464600/appliedmicros-64core-chip-could-spark-off-arm-core-war.html). Archived
(https://web.archive.org/web/20140821175759/http://www.pcworld.com/article/2464600/appliedmicros-64core-chip-could-spark-off-
arm-core-war.html) from the original on 21 August 2014. Retrieved 21 August 2014.
73. "Archived copy" (http://www.anandtech.com/Gallery/Album/3847). Archived (https://web.archive.org/web/20141205022933/http://w
ww.anandtech.com/Gallery/Album/3847) from the original on 5 December 2014. Retrieved 29 November 2014.
74. "Archived copy" (http://blogs.nvidia.com/blog/2014/08/11/tegra-k1-denver-64-bit-for-android/). Archived (https://web.archive.org/we
b/20140812090907/http://blogs.nvidia.com/blog/2014/08/11/tegra-k1-denver-64-bit-for-android/) from the original on 12 August
2014. Retrieved 29 November 2014.
75. "Archived copy" (https://www.golem.de/news/nvidia-drive-xavier-fuer-autonome-autos-wird-ausgeliefert-1801-132035.html).
Archived (https://web.archive.org/web/20180305202753/https://www.golem.de/news/nvidia-drive-xavier-fuer-autonome-autos-wird-
ausgeliefert-1801-132035.html) from the original on 5 March 2018. Retrieved 5 March 2018.
76. "Archived copy" (https://wccftech.com/nvidia-drive-xavier-soc-detailed/). Archived (https://web.archive.org/web/20180224191519/ht
tps://wccftech.com/nvidia-drive-xavier-soc-detailed/) from the original on 24 February 2018. Retrieved 5 March 2018.
77. "Archived copy" (http://www.anandtech.com/show/7990/amd-announces-k12-core-custom-64bit-arm-design-in-2016). Archived (htt
ps://web.archive.org/web/20150626102331/http://www.anandtech.com/show/7990/amd-announces-k12-core-custom-64bit-arm-des
ign-in-2016) from the original on 26 June 2015. Retrieved 26 June 2015.
78. "Samsung Announces Exynos 8890 with Cat.12/13 Modem and Custom CPU" (http://www.anandtech.com/show/9781/samsung-an
nounces-exynos-8890-with-cat1213-modem-and-custom-cpu). AnandTech. Archived (https://web.archive.org/web/2015112705381
2/http://anandtech.com/show/9781/samsung-announces-exynos-8890-with-cat1213-modem-and-custom-cpu) from the original on
27 November 2015. Retrieved 18 December 2015.
79. "Hot Chips 2018: Samsung's Exynos-M3 CPU Architecture Deep Dive" (https://www.anandtech.com/show/13199/hot-chips-2018-s
amsungs-exynosm3-cpu-architecture-deep-dive). AnandTech. Archived (https://web.archive.org/web/20180820203929/https://ww
w.anandtech.com/show/13199/hot-chips-2018-samsungs-exynosm3-cpu-architecture-deep-dive) from the original on 20 August
2018. Retrieved 20 August 2018.
80. "ARM Company Milestones" (http://www.arm.com/about/company-profile/milestones.php). Archived (https://web.archive.org/web/2
0140328171411/http://www.arm.com/about/company-profile/milestones.php) from the original on 28 March 2014. Retrieved 6 April
2014.
81. "ARM Press Releases" (http://www.arm.com/about/newsroom/index.php). Archived (https://web.archive.org/web/20140409172237/
http://arm.com/about/newsroom/index.php) from the original on 9 April 2014. Retrieved 6 April 2014.
Further reading
https://en.wikipedia.org/wiki/List_of_ARM_microarchitectures 13/14
15/04/2020 List of ARM microarchitectures - Wikipedia
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and
Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.
https://en.wikipedia.org/wiki/List_of_ARM_microarchitectures 14/14
D SUDHAKR
Asst. Professor
MGIT.
Technical White Paper
SWPA001 – December 2000
ABSTRACT
This paper describes how the Open Multimedia Applications Platform™ software and
hardware architecture enables multimedia applications in third-generation (3G) wireless
appliances. It provides an overview of OMAP™ strategy, concepts, main milestones, and
achievements. It also describes OMAP hardware architecture, explains how multimedia
applications can benefit from this advanced architecture, and why a RISC/DSP approach
is superior to RISC-only architecture. This paper outlines OMAP software concepts to
show how an architecture that combines two heterogeneous processors (RISC and DSP),
several operating system (OS) combinations, and applications running on both DSP and
RISC can be made accessible seamlessly to third parties. The final parts of the paper
outline how key multimedia applications such as speech and video can be integrated in an
OMAP solution.
Contents
1 Introduction .........................................................................................................................................2
2 OMAP Hardware Architecture ...........................................................................................................3
2.1 Advantages of a Combined RISC/DSP Architecture.....................................................................3
2.2 How the Architecture Works ..........................................................................................................4
2.3 C55x DSP and Multimedia Extensions .........................................................................................5
3 OMAP Software Architecture ............................................................................................................7
4 OMAP Multimedia Applications.........................................................................................................9
4.1 Video...............................................................................................................................................9
4.2 Speech Applications .....................................................................................................................10
5 Conclusion.........................................................................................................................................11
Figures
Figure 1. OMAP Hardware Architecture ................................................................................................ 4
Figure 2. How the OMAP Architecture Works ...................................................................................... 8
Figure 3. Hierarchical Organization of Speech APIs.......................................................................... 10
Tables
Table 1. Comparative Algorithm Execution......................................................................................... 3
Table 2. Description of the « copr » Opcodes .................................................................................... 5
Table 3. Data Flow Modes ..................................................................................................................... 6
Table 4. Characteristics of Video Hardware Accelerators ................................................................ 6
Table 5. MPEG4 Video Codec Power ................................................................................................... 7
1
SWPA001
1 Introduction
Every wireless handset contains two fundamental components: a modem and an applications
processing and delivery system. The modem communicates with a network to send and receive
data via an air interface. The applications component provides the functions that the user wants
in a multimedia appliance. These may include speech, audio playback, image reproduction and
streaming video, fax transmission and reception, e-mail, Internet connections, games, personal
organizer functions, and a host of other possibilities. The applications component also handles
user interface functions such as speech recognition (voice commands), keyboard, and written
character recognition. Except for user interface functions, all of these applications depend on the
air interface, which provides only limited bandwidth.
Managing the volume of data required for applications involving speech, audio, image, and video
within the available bandwidth requires heavy signal compression before transmission and
decoding or expansion within the receiver, which, for purposes of this paper, is a handheld
wireless appliance. Wireless appliances need additional signal processing capabilities for the
concurrent noise suppression and echo cancellation algorithms essential for even the most basic
functionality, i.e., voice telephony.
In many of today’s second generation (2G) wireless handsets, the modem component employs a
DSP, which provides the air interface and takes care of such essentials as noise suppression
and echo cancellation. The applications component, however, relies on a general purpose
processor (GPP), usually a RISC processor, which attempts to provide the signal processing
needed at the application level, user interfaces, and overall command and control functions.
In 2G appliances, which are, essentially, wireless telephones with extremely limited data
features, this processing dichotomy has generally proved to be satisfactory. However, for 2.5G
and 3G appliances, which offer such capabilities as full-motion video and high-fidelity audio
playback, the currently popular division of tasks between the two processors does not provide
reliably robust performance and still maintain the useful battery life that is acceptable to
consumers.
Next generation appliances, which include numerous applications enabled by high data rates
and real-time signal processing, continue to require both a DSP and a GPP. However, the
functional wall between the two basic appliance components breaks down as the demand for
signal processing within the applications component increases. The DSP, which is optimized for
intensive signal processing in real time with extremely low power consumption, becomes the
primary processor for both the modem and the applications component. The GPP plays a
secondary role, taking care of system management, command, control, and certain user
interface activities. The OMAP architecture provides a means to coordinate dual processors
across the two basic components of the wireless appliance and to seamlessly take advantage of
the unique capabilities of each. Nokia, Ericsson, Sony, Handspring, and others already have
selected the OMAP hardware and software architecture as the development platform for their
wireless appliances. The first samples of an OMAP-based chipset will be available in 4Q00.
In addition to enabling the numerous, media-rich applications made possible by 2.5G and 3G
data rates, the OMAP architecture also provides a new capability—the capability to dynamically
download applications and application upgrades from the web in the same way that PC users
download applications from the Internet today. This dynamic environment requires the
programmability offered by DSPs and the application programming interface (API) features built
into the OMAP architecture.
SRAM
DPLL
Per CLKM
ARM925T Bri
dg
e
I-MMU D-MMU
ARM
Rhea
I-Cache D-Cache
OMAP
The OMAP core contains two external memory interfaces and one internal memory port. The
external memory interfaces support direct connection to synchronous DRAMs at up to 100 MHz
and to standard asynchronous memories, such as SRAM, FLASH, or burst FLASH devices. The
latter interface is typically used for program storage. It can be configured as 16 or 32 bits wide.
The internal memory port allows direct connection to on-chip memory, such as SRAM, and can
be used for frequently-accessed data, such as critical OS routines or the liquid crystal display
(LCD) frame buffer. This reduces the access time and eliminates costly external accesses. All
three interfaces are completely independent and allow concurrent access from either processor
or direct memory access (DMA) unit.
The OMAP core also contains numerous interfaces to connect to peripherals or external devices
from either the DSP or GPP. To improve system efficiency, these interfaces also support DMA
from each respective processor’s DMA unit. The local bus interface is a high-speed,
bidirectional, multimaster bus that can be used to connect to external peripherals or additional
OMAP-based devices in a multicore product. Additionally, a high-speed access bus is available
to allow an external device to share the main OMAP system memory (SDRAM, FLASH, internal
memory). This interface provides an efficient mechanism for data communication and also
allows the designer to reduce system cost by reducing the number of external memories
required in the system.
To support common operating system requirements, the OMAP architecture includes several
peripherals—timers, general purpose input/output interfaces (I/Os), a UART, and watchdog
timers. These are the minimum peripherals required in the system; other peripherals can be
added on the TI peripheral bus (TIPB) interfaces. A color LCD controller is also included to
support a direct connection to the LCD panel. The ARM DMA engine contains a dedicated
channel that is used to transfer data from the frame buffer to the LCD controller, where the frame
buffer can be allocated in the SDRAM or internal SRAM.
Table 3 indicates all data flow modes that can be built using the combination of arithmetic
instructions and the opcodes in Table 2.
One of the first application domains that will extend the functionality of wireless terminals is
video processing. Motion estimation, discrete cosine transform (DCT) and its inverse function
(IDCT), and pixel interpolation require the greatest number of cycles for a pure software
implementation using the C55x DSP processor. Consequently, these three application domains
are the first multimedia programming extensions that the C55x DSP supports. Table 4
summarizes the characteristics of the extensions.
Using the extensions, the overall video-codec application mentioned earlier is twice as fast as a
classic software implementation. By reducing cycle count, the DSP real-time operating
frequency and, thus, the power consumption are also reduced.
Table 5 summarizes current consumption (at maximum and lowest possible supply voltage) of a
C55x DSP video MPEG4 Coder/Decoder using multimedia extensions, for various image rates
and formats.
The most important function of the DSP/BIOS Bridge is providing communications between GPP
applications and DSP tasks. The DSP/BIOS Bridge API is abstracted from the high-level
application developers by a set of DLL and drivers that is provided in the development toolkit for
the platform. This allows application developers to develop on the OMAP platform in the same
manner as if they were developing on a single RISC processor. The environment provided for
development allows the application developer to call the localized functions for video, audio,
speech, etc. and to develop in the traditional manner on platforms such as the PC. The high-
level application developer does not require any awareness of the DSP or DSP/BIOS Bridge
API.
The DLL and driver developers actively use the DSP/BIOS Bridge API to:
Although the design initially targets a limited set of OSs, the underlying architecture facilitates
expansion of this list in the future. Standardization and reuse of existing API and application
software are the main goals for the open platform architecture, thus allowing extensive reuse of
previously developed software and a faster time to market of new software products.
4.1 Video
Video applications include two-way videophone communication and one-way decoding or
encoding, which may be used for entertainment, surveillance, or video messaging. While
second-generation communicators support speech only, coded at 8 to 13 kbps, even low-motion
video on a small display requires at least 20 kbps. 3G wireless standards will make possible the
higher bit rates required for more sophisticated video-related applications.
Compressed video is particularly sensitive to errors that can occur with wireless transmission.
To achieve high compression ratios, variable-length code words are used, and motion is
modeled by copying blocks from one frame to the next. When errors occur, the decoder loses
synchronization, and errors propagate from frame to frame. The new MPEG-4 standard supports
wireless video with special error resilience features, such as added resynchronization markers
and redundant header information. The MPEG-4 data-partitioning tool, originally proposed by TI,
puts the most important data in the first partition of a video packet, which makes partial
reconstruction possible for better error concealment.
TI’s MPEG-4 video software for OMAP architecture is based on reference C software, which is
converted to use ETSI C libraries and then ported to C55x DSP assembly code. The ETSI C
libraries consist of routines representing all common DSP instructions. The ETSI routines
perform the desired function and also evaluate processing cycles and check for saturation, etc.
Thus, the ETSI C, commonly used for testing speech codecs, provides a tool for benchmarking
and facilitates porting the C code to assembly.
As shown in Section 2.2, the video software runs efficiently on the OMAP architecture. The
architecture is able to encode and decode in the same time QCIF (176 ×144 pixels) images at
15 frames per second. The CPU loading for simultaneous encoding and decoding represents
only 15 percent of the total DSP capability. Therefore, 85 percent of the CPU is still available to
other tasks, such as graphic enhancements, audio playback (MP3), or speech recognition.
The assembly encoder is under development and typically requires about three times as much
processing as the decoder. The main processing bottlenecks are motion estimation, DCT, and
IDCT. However, through tight coupling of hardware and software, the OMAP architecture
improves the video encoding execution by a factor of two.
The OMAP architecture provides not only the computational resources, but also the data-
transfer capability needed for video applications. One QCIF frame requires 38016 bytes, for
chrominance components downsampled in 4:2:0 format, when transferring uncompressed data
from a camera or to a display. The video decoder and encoder must access both the current
frame and the previously decoded frame in order to perform the motion compensation and
estimation, respectively. Frame rates of 10- to 15-frames per second must be supported for
wireless applications.
Third-generation standards for wireless communication, along with the new MPEG-4 video
standard, and new low-power platforms like the OMAP architecture will make possible many
new video applications. It is quite probable that video applications will differentiate 2G and 3G
devices, creating new markets and higher demand for wireless communicators.
Speech-enabled
Application
Speech Primitives
[e.g. load_grmrs(), start_rec(),
stop_rec(), get_result(), start_tts(),
tts_speak(), pause_tts(),
ARM
set_spkr()…]
OMAP DIRECT DSP API
DSP
Note that only the unit selection and waveform generation modules of the Text-to-Speech (TTS)
are on the DSP.
For each new recognition context, the grammars and acoustic models are generated
dynamically on the ARM processor and transferred to the recognizer on the DSP. This dynamic
vocabulary capability of the speech recognizer is crucial on resource-constrained wireless
devices. For example, a voice-enabled web browser on the phone can now handle several
different web sites, each with its own different vocabulary, without compiling or storing
vocabularies and speech grammars beforehand. Similarly, for a voice-enabled stock quote
retrieval application, company names can be dynamically added to or removed from the stock
portfolio. At any given time, the size of the active vocabulary is limited by the resource
constraints on the DSP (e.g., size of the RAM available for the recognition search). However,
given that different vocabularies can be swapped in and out depending on the recognition
context, the application can be designed to give the perception of an unlimited speech
recognition vocabulary.
Similarly, the text-to-speech (TTS) system on the wireless device can be split between the ARM
processor and the DSP. The text analysis and linguistic processing modules of the TTS reside
on the ARM processor along with the phonetic databases. The unit selection and waveform
generation modules reside on the DSP. As with the speech recognizer, the interaction between
the ARM processor and DSP modules is minimized and conducted via a hierarchy of APIs.
5 Conclusion
This paper has described how the OMAP hardware and software architecture will enable
multimedia applications in 3G wireless terminals. The OMAP multiprocessor architecture has
been optimized to support heavy multimedia applications, such as video and speech in 3G
terminals. Such a complex architecture, combining two heterogeneous processors (RISC and
DSP), several OS combinations, and applications running on both the DSP and ARM can be
made accessible seamlessly to application developers because of the DSP/BIOS Bridge feature.
Moreover, this dual processor architecture is more cost efficient and power efficient than a single
processor solution.
Open Multimedia Applications Platform, OMAP, TMS320C5510, TMS320C55x, C55x, DSP/BIOS are trademarks of
Texas Instruments.
ARM, StrongARM, ARM9E, ARM10 are trademarks of Advanced RISC Machines, Ltd.
IMPORTANT NOTICE
Texas Instruments and its subsidiaries (TI) reserve the right to make changes to their
products or to discontinue any product or service without notice, and advise customers to
obtain the latest version of relevant information to verify, before placing orders, that
information being relied on is current and complete. All products are sold subject to the
terms and conditions of sale supplied at the time of order acknowledgement, including
those pertaining to warranty, patent infringement, and limitation of liability.
TI warrants performance of its semiconductor products to the specifications applicable at
the time of sale in accordance with TI's standard warranty. Testing and other quality
control techniques are utilized to the extent TI deems necessary to support this warranty.
Specific testing of all parameters of each device is not necessarily performed, except
those mandated by government requirements.
Customers are responsible for their applications using TI components.
In order to minimize risks associated with the customer's applications, adequate design
and operating safeguards must be provided by the customer to minimize inherent or
procedural hazards.
TI assumes no liability for applications assistance or customer product design. TI does
not warrant or represent that any license, either express or implied, is granted under any
patent right, copyright, mask work right, or other intellectual property right of TI covering
or relating to any combination, machine, or process in which such semiconductor
products or services might be or are used. TI's publication of information regarding any
third party's products or services does not constitute TI's approval, warranty or
endorsement thereof.
Copyright 2000 Texas Instruments Incorporated
Product Bulletin
Key Features
As the wireless market continues sumer expects this rich functionali- The OMAP processor is the ideal
to grow, the OMAP™ platform ty while continuing to demand engine for wireless multimedia
from Texas Instruments (TI) will longer battery life and smaller, applications processing. TI DSP
help meet wireless devices sleeker products. The OMAP technology is the key to providing
increasing consumer expectations. architecture features open hard- both the high performance and
Next-generation wireless multime- ware and software that drives the low-power consumption required
dia appliances will include more quick introduction of differentiated in these next generation mobile
than just voice communications. products for next-generation wire- products. In addition, OMAP archi-
As full-motion video, video confer- less appliances. The OMAP archi- tecture is open, providing flexibility
encing, voice recognition, real-time tecture has a high-performance, and a programmable platform for
Internet and high-fidelity audio are ultra-low-power TMS320C55x™ developers. The OMAP processor
integrated into these wireless digital signal processor (DSP) core supports advanced operating sys-
appliances, a general-purpose for efficient execution of real-time tems (OS) such as Microsoft
processor alone will not be able to multimedia applications as well as a Windows® CE and Symbian
handle the processing perform- TI-enhanced ARM™ 925 processor EPOC™ as well as standard multi-
ance needed while meeting bat- to run command and control function media application programming
tery life expectations. The con- and user interface applications. interfaces (APIs). Developers can
leverage a wide range of software decode and encode, MP3 decode OMAP Architecture
developer’s networks, including and encode, JPEG decode and The OMAP1510 processor is
TI DSP third parties, ARM third encode and advanced speech based on the unique dual-core
parties, TI OMAP developers and applications such as text-to- architecture that combines the
OS third parties. The OMAP speech, speech recognition and command and control capabilities
processor enables real-time Adaptive Multi-Rate (AMR). This of the TI-enhanced ARM 925 core
communications with the extended combination of cores and periph- with the benchmark performance/
battery life that consumers demand. erals provides the best-in-class power capabilities of the C55x
The OMAP1510 is the first power and performance ratio for DSP engine. The TI-enhanced
applications processor specifically both standard and custom ARM 925 core is an industry lead-
targeted for 2.5 and 3G wireless processors for wireless devices. As ing implementation of the ARM
devices. The OMAP1510 proces- an example, the OMAP1510 pro- RISC architecture that operates
sor combines a TI-enhanced ARM vides the same processing power up to 175 MHz. The TI-enhanced
925 core with a C55x™ DSP core of a standalone RISC processor ARM 925 includes a memory man-
along with a wide range of gener- but uses just 1/4th the power. agement unit (MMU) for virtual-
al-purpose peripherals and The OMAP1510 is initially to-physical memory translation
dedicated multimedia application targeted at PDA and smart phone and task-to-task memory protec-
peripherals. The OMAP1510 has applications although it is sched- tion as well as a 16KB instruction
been optimized for power efficient uled to be offered for a wider cache, an 8KB data cache and a
execution of the key multimedia range of applications in the sec- 17 word write buffer. There is
applications including MPEG-4 ond half of 2001. 1.5 Mb of internal SRAM provid-
Program
Memory SDRAM
Uart (x3)
1.5 Mb USB Client
I SRAM
USB Host
Microwire™
I Cache
Interface to Applications
GPIO
Peripherals
Management TMS320C55x™
LCD Keyboard
for External Control DSP Core
Modem Controller Camera Interface
Interface SD/MMC
RTC
Clock JTAG/ETM9 Modem Interface
Bluetooth™ Interface
2
ing a large memory space for space as well as between periph- peripherals can occur in the
power efficient on-chip data and erals without Microprocessor Unit background of MPU operation.
code storage for applications such (MPU) intervention.
Camera Interface
as liquid crystal display (LCD)
LCD Controller Video applications will be an
frame buffering. A two level inter-
The LCD controller allows a important part of next-generation
rupt handler provides 32 inter-
direct connection to a black and wireless appliances. A camera
rupt lines including 13 internal
white or color LCD panel, either interface allows the OMAP1510
and 19 external interrupts. Also
super twist nematic (STN) or thin to connect directly with a camera
included in the core is the ARM
film transistor (TFT), reducing module for video conferencing
CP15 coprocessor and protection
the system component count and and other video applications.
module.
power consumption. The frame The interface uses 8-bit parallel
DSP Advantage buffer can be allocated in external image data, pixel clock and
The 200 MHz C55x DSP core sets SDRAM or internal 1.5Mb SRAM horizontal/vertical sync signals for
the DSP industry’s benchmark for improved power efficiency. A the interface. Additionally, a clock
power and performance ratio. dedicated channel on the DMA can be provided to the external
Three key innovations enable unit is used to transfer data from camera at various configurable
this: increased idle domains, the frame buffer to the LCD con- frequencies. The pixel clock can
variable length instructions and troller. The LCD controller can be synchronous or asynchronous
increased parallelism. The C55x support 2/4/8/12/16-bits per pixel depending on the requirements
DSP core has a highly optimized and a 1024x1024 display. of the external camera module.
architecture for multimedia A DMA port allows camera data
Memory Interfaces
applications, including core level to be transferred without the
The OMAP1510 processor con-
extensions that facilitate the need for MPU intervention.
tains three memory interfaces–
demands of the multimedia mar-
two external and one internal. Air Interface
ket for real-time, low-power pro-
The external memory interfaces An external modem device
cessing of streaming video and
support direct connection to can be connected directly to the
audio. The C55x DSP core con-
64MB of addressable SDRAM up OMAP1510 through a modem
tains three multimedia extensions
to 100 MHz and to 32MB of interface, allowing both data and
to further improve the power
addressable Flash (asynchronous voice communications. The inter-
efficiency. These are motion esti-
or burst), random access memory face has been designed to work
mation, discrete cosine transform
(RAM) or read only memory with any air interface standard,
(DCT), inverse discrete cosine
(ROM) devices. Both of these making it easy to use in any
transform (IDCT) and 1/2- pixel
external memory interfaces are system. The data is transferred on
interpolation. The addition of
16-bits data wide and support the TI standard Multi-channel
this hardware accelerator enables
external devices having 2.75-V or Buffered Serial Port (McBSP) at
video applications to run up to
1.8-V (typical) interfaces. The configurable rates up to 6 Mbps
twice as fast while also reducing
internal memory port connects to while the control is done through
the power consumption.
the 1.5 Mb of on-chip SRAM. All a UART along with control signal
The C55x DSP core includes
three memory interfaces are lines for the clock and power. The
32 kwords of internal dual-access
accessible and can be shared by 8-kHz voice data can be trans-
SRAM, 48 kwords of internal
the TI-enhanced ARM 925 MPU, ferred by the Multi-Channel Serial
single access SRAM and a
C55x DSP core and system DMA. Interface (MCSI). The McBSP
12 kword instruction cache. The
The system DMA is included to and universal asynchronous
C55x DSP core also includes an
allow transfers of data between receiver transmitter (UART) have
MMU as well as a dual layer inter-
points in the memory space DMA support, reducing the MPU
rupt handler and a direct memory
without MPU intervention. Data loading.
access (DMA) unit. The DMA
movements to and from internal
allows the transfer of data
memory, external memory and
between points in the memory
3
OMAP1510 2.5 and 3G Wireless System Diagram
5 6 16 5 13
External USB
Host/Client USB LCD SD/MMC Camera
Connector Display
Audio
Codec
48 kHz
Audio
In/Out
Bluetooth™ Interface can be used for 8-kHz voice data serial communication up to
The Bluetooth™ standard will and has a four-wire interface with 115.2 kbps. The three UARTs
allow short distance wireless bi-directional data, a serial clock have 64 word receive and trans-
connectivity so that wireless and frame sync. mit FIFOs with programmable
multimedia appliances can be trigger levels and offer even, odd
Universal Asynchronous
connected with other appliances, or none transmit parity along with
Receiver Transmitter (UART)
a home computer or local area 1, 1.5 or 2 stop bits.
Three 16C750 compatible UARTs
network. A Bluetooth interface,
are included in the OMAP1510. I2C Host
provided by a high-speed UART
All are controllable through a The OMAP1510 includes an I2C
and MCSI serial port on the
software interface or through host port compliant with Philips
OMAP1510 processor allows
hardware flow control signals. I2C standard. The interface is a
developers to easily incorporate
Two of the UARTs, as mentioned single master only, half-duplex
this feature in their next-
above, are intended for modem serial port using two lines (data
generation wireless devices. The
and Bluetooth interfaces but are and clock) for data transmit with
Host Control Interface is done
not limited to those applications. software addressable external
through a standard UART with
The third UART includes optional devices. Both standard 100-kHz
extended baud rate options up to
infrared data adapter (IrDA) 1.0 and fast 400-kHz transmit modes
1.625 Mbps by using an externally
serial infrared (SIR) support for are supported. Burst write, single
supplied baud clock. The MCSI
4
read and combined read modes computer or other master device. Loop (PLL) and power manage-
are all supported. A transmit The OMAP1510 also has a USB ment. The MPU and DSP each
burst buffer of 16 words allows host controller, with up to three have three 32-bit timers and a
for continuous transmission down stream ports, allowing watchdog timer.
of data. connection to high-speed modem
Space Saving Package
devices or USB peripherals such
PWT Generator The OMAP1510 comes in a
as a mouse, keyboard or camera.
A pulse width tone (PWT) space-saving 289-pin MicroStar™
Both the host and client con-
generator generates a modulated ball-grid array (BGA) package
trollers are compliant with the
frequency signal for the external with 0.5-mm ball pitch. The
USB specification version 1.1.
buzzer. The frequency is 12 x 12-mm package is ideal for
programmable between 349 Hz SD/MMC Interface ultra-small, ultra-light designs.
and 5276 Hz with 12 half-tone A Secure Digital (SD)/MultiMedia
Tools and Support
frequencies per octave. In addition, Card Controller (MMC) interface
TI will offer a wide range of sup-
the PWT is volume programma- allows connection of industry
port for OMAP platform products
ble, allowing the user to select standard flash storage cards and
including PC-based application
how loud their phone rings. To I/O peripherals for storage of large
development tools and an evalua-
control the backlight of the LCD multimedia data like digital audio,
tion module (EVM) with a User’s
and keypad, a pseudo-noise pulse digital video, maps and digital still
Guide and Technical Reference
width light (PWL) modulator is photos. The I/O peripheral mode
Manual to help speed designs to
also included. allows for the addition of future
market.
peripherals. The SD/MMC inter-
Serial Ports Application software developers
face is compliant with the MMC
The OMAP1510 processor can use the same PC-based
standard specification version
includes many different types of emulation tools currently provid-
2.2 and the SD Physical Layer
serial ports. Two McBSPs can be ed by the OS manufacturers with
specification version 1.0.
used for interface to an audio added TI OMAP extensions. This
codec for digital audio input and Additional Features allows application developers to
output (using I2S interface The OMAP1510 processor also develop in the same environment
protocol for example) or can be offers support for licensees of they are used to and tap into the
configured to connect to an MemoryStick™ or OpenMG™ OMAP processor capabilities by
external optical audio interface technology. This allows the simply calling into the software
device. A Microwire™ standard consumer to add flash cards to extensions that represent the
compatible interface is included their wireless appliance that extensive base of DSP algorithms.
for connecting external devices contain programs, games, The application developers can
such as a serial EEPROM or LCD. personal information, music or quickly develop software, using
The 14-bit general-purpose other data important to them. available DSP algorithms, without
input/output (GPIO) can be A real-time clock (RTC) having to use either the EVM
dedicated to either the DSP or keeps track of the current time hardware or learn the internal
the microcontroller unit (MCU). in seconds, minutes and hours complexities of the DSP algorithm.
A 5-bit GPIO dedicated to the and allows for devices to include For development of DSP
MCU is also provided. A general alarm clock functionality. algorithms and the DSP gateway
serial port interface (SPI) is Calendar information like day, components on the TI-enhanced
included and can be used as a month, year and day of the week ARM 925, the programmer can
voice communication interface. up to the year 2099 is also use the TI Code Composer
provided. Studio™ Integrated Development
USB Client and Host
Other features of the OMAP1510 Environment (IDE), a component
The OMAP1510 processor
include a keyboard interface that of TI’s award winning eXpressDSP™
includes a universal serial bus
allows a direct connection of Real-Time Software Technology,
(USB) client controller for
a 6x5 or 8x8 matrix keyboard, and EVM. Code Composer Studio
high-speed plug-and-play syn-
a JTAG and emulation interface, is a fully integrated development
chronization with a personal
a clock generator with Phase Lock environment that improves time-
5
OMAP™ Software Architecture
Applications
Protocol
DSP Gateway Video Web Speech Video Audio Speech
Media
Framework
DSP Manager
Host OS DSP Manager Data Streams DSP/OS
Server
(EPOC/ (BIOSII/
Windows® OSE)
CE)
Link Driver Link Driver
to-market and covers all phases of mation are included to get prod- tion developer calls localized DSP
development, from editing and ucts to the market faster. OMAP gateway components to perform
building to debugging, code profil- supports multiple OSs on the DSP different functions like video,
ing and project management. including TI’s DSP/BIOS and audio and speech. Thus, high-
Code Composer Studio includes a OSE™, from Enea OSE systems. level application developers do
full compiler, simulator and not need to be knowledgeable
OMAP1510 Software Applications
debugger for the OMAP1510. The about using the DSP or DSP/BIOS
Platform
Visual Project Management sys- Bridge API to successfully intro-
The OMAP1510 includes an
tem allows visualization, access duce new applications. Once an
open software architecture that
and manipulation of all project application has been developed
supports fast application develop-
files from the same window. Code using this standard API, it will be
ment and provides the ability
Composer Studio also supports compatible with future wireless
to dynamically download applica-
the development of systems appliances based on the OMAP
tions and application upgrades.
with multiple processors using platform.
The DSP/BIOS™ Bridge provides
the Parallel Debug Manager The OMAP platform currently
the communications between the
(PDM). DSP/BIOS™, also part supports Microsoft Windows CE
applications on the TI-enhanced
of eXpressDSP, is a scalable, and Symbian EPOC operating
ARM 925 and algorithms on the
real-time kernel for the C55x DSP systems. Other operating systems
C55x DSP core. The DSP/BIOS
core that provides a standard are planned for the OMAP plat-
Bridge API allows developers to
software base that reduces cost, form in the near future. TI is also
initiate and control tasks on the
risk and development time. investing in technologies, such as
DSP, exchange messages with the
Common run-time objects and JAVA™, which will allow a larger
DSP, stream data to and from the
utilities such as I/O modules, a software developer base.
DSP and perform status queries.
fast preemptive scheduler and
In this environment, the applica-
APIs for capturing real-time infor-
6
OMAP Developers Network The OMAP Developer Network Availability
The OMAP software infrastructure will benefit the wireless device The OMAP1510 processor is ini-
is optimized for use by manufacturer in many different tially targeted at PDAs and smart
software developers. Software ways. The manufacturer can now phone manufacturers. TI is ship-
developed using the standard rely on expert outside developers ping production samples of the
DSP/BIOS will be OMAP proces- to deliver specialized program- OMAP processor today, and the
sor compatible. TI is working with ming specifically for their plat- OMAP1510 is scheduled to be
software developers to develop form. Since the software develop- available in volume production
application software, DSP algo- ers have already invested the quantities in third quarter 2001.
rithms, and gateway components time and resources building
For More Information
for the OMAP platform. expertise in their particular area,
To find out more about how the
There are a number of applica- these applications will add value
OMAP1510 processor is the ideal
tion areas for OMAP developers to any platform. To provide the
engine for 2.5 and 3G wireless
to focus on for 2.5 and 3G wire- highest performance possible, the
devices, call your local sales office
less appliances. Some promising software developer has already
or visit the TI web site. Find out
areas include: optimized their code between
how TI products can help make
the DSP and microprocessor, this
• Multimedia: streaming your next-generation systems
allows faster time-to-market for
audio/video, broadcast, players easier to design with higher
manufacturers.
• Games: 2D, 3D performance and lower power
TI has an existing DSP Third
• Location-based services: GPS, consumption.
Party Program with the most
network-assisted solutions Please visit us at:
extensive collection of DSP devel-
• Security (user interface): www.omap.com
opment support in the industry.
biometrics, user authentication
With access to TI’s DSP Third
• Security (infrastructure):
Party Network, the list of potential
encryption/decryption,
applications leveraging the per-
firewall, user verification,
formance of the DSP is ever-
anti-virus
expanding. Given the wide variety
• Business applications: database
of application software being
management, spreadsheet,
developed, a hardware manufac-
synchronization, application
turer can put together software
navigation via speech
from many different developers
to get the right mix for their
customers.
7
TI Worldwide Technical Support
Internet
TI Semiconductor Product Information Center
Home Page
www.ti.com/sc/support
Japan
Phone International +81-3-3344-5311 Important Notice: The products and services of Texas Instruments and
its subsidiaries described herein are sold subject to TI’s standard terms
Domestic 0120-81-0026 and conditions of sale. Customers are advised to obtain the most current
and complete information about TI products and services before placing
Fax International +81-3-3344-5317 orders. TI assumes no liability for applications assistance, customer’s
Domestic 0120-81-0036 applications or product designs, software performance, or infringement of
patents. The publication of information regarding any other company’s
Internet International www.ti.com/sc/jpic products or services does not constitute TI’s approval, warranty or
endorsement thereof.
Domestic www.tij.co.jp/pic
A030101
The red/black banner, OMAP, TMS320C55x, DSP/BIOS, eXpressDSP and Code Composer Studio are trademarks of Texas Instruments.
Bluetooth is a trademark of Telefonakiebolaget L M Ericsson and licensed to Texas Instruments.
All other trademarks are the property of their respective owners.