ARM Cortex-M0 Overview

By: Daniel Widyanto

September 2010
Contents

Introduction to ARM Cortex-M0

Programmer’s Model : Processor Modes
Programmer’s Model : Stacks
Programmer’s Model : Core Registers
Programmer’s Model : Interrupts and Exceptions
Quizzes

2
Introduction to ARM Cortex-M0

3
Introduction to ARM Cortex-M0

ARM Cortex-M0:
– Entry-level 32-bit ARM Cortex processor designed for a broad range of embedded
applications
Benefits:
– simple, easy-to-use programmers model
– highly efficient ultra-low power operation
– excellent code density
– deterministic, high-performance interrupt handling
– upward compatibility with the rest of the Cortex-M processor family
Cortex-M0 core peripherals
– NVIC:
• An embedded interrupt controller that supports low latency interrupt processing.
– System Control Block:
• Provides system implementation information and system control, including configuration, control,
and reporting of system exceptions.
– Optional system timer (SysTick):
• A 24-bit count-down timer. If implemented, use this as a Real Time Operating System (RTOS) tick
timer or as a simple counter
4
Introduction to ARM Cortex-M0
(cont’d)

5
Programmer’s Model

Processor Modes

6
Programmer’s Model
Processor Modes
Thread mode
– Used to execute application software. The processor enters Thread mode when it
comes out of reset.

Handler mode
– Used to handle exceptions. The processor returns to Thread mode when it has
finished all exception processing.

Note:
Other ARM architectures support the concept of privileged or unprivileged software
execution. This processor does not support different privilege levels. Software execution is
always privileged, meaning software can access all the features of the processor.

7
Programmer’s Model

Stacks

8
Programmer’s Model
Stacks
Full descending: stack pointer indicates the last stacked item on the stack
memory.
Two stacks, two independent stack pointers:
Processor mode Used to execute Stack used
Thread Applications Main stack or process stack
Handler Exception handlers Main stack

– Handler mode always uses the MSP (Main Stack Pointer)

– Thread mode can use MSP (Main Stack Pointer) by default, or PSP (Process Stack
Pointer)
• Controlled by CONTROL register

In an OS environment, ARM recommends that threads running in Thread

mode use the process stack and the kernel and exception handlers use the
main stack.
9
Programmer’s Model

Core Registers

10
Programmer’s Model
Core Registers

11
Programmer’s Model
Core Registers
Program Status Register (PSR) combines:
– Application Program Status Register (APSR)
– Interrupt Program Status Register (IPSR)
– Execution Program Status Register (EPSR)
• Mutually exclusive each other.
• User can access the whole registers as ‘PSR’, or individual blocks as ‘APSR’ / ‘IPSR’ /
‘EPSR’, or combination of two blocks

12
Programmer’s Model

Interrupt and Exceptions

13
Programmer’s Model
Interrupts and Exceptions
The vector table is fixed at address 0x00000000
1st record is stack address for MSP
The rest of the record are addresses for
exception handlers
– Address only. No instruction such as ‘branch
<int_handler>’

Address for exception handlers must be in ‘odd’

value, since ARM Cortex-M0 only supports
Thumb mode
– Bit[0] in address determined whether Thumb
mode is used or not

HardFault exception will be triggered for ‘even’

address.

14
Programmer’s Model
Interrupts and Exceptions
Exception entry
– ARM Cortex-M0 is automatically save the registers into stack (pointed by MSP)
before executing exception handler

– The exception handler address then fetch and executed

Exception return
– Use ‘BX LR’ to return the registers value from stack
– LR defines the mode and stack pointer for the return address:
• LR = 0xFFFFFFF1: Return to Handler mode, use MSP after return
• LR = 0xFFFFFFF9: Return to Thread mode, use MSP after return
• LR = 0xFFFFFFFD: Return to Thread mode, use PSP after return

15
Programmer’s Model
Interrupts and Exceptions
Definition:
– An event that alters the normal sequence of execution

Configurable Priority Unconfigureable Priority

Synchronous SVCall HardFault

Asynchronous PendSV, SysTick, IRQ0- Reset, NMI

IRQ31

Unconfigureable priority exceptions are un-maskable. Configurable priority exceptions

are maskable (using ‘PRIMASK’)
Priority value is 0 (highest) to 192 (lowest)
– Default priority is 0 (highest)
– For IRQ0-IRQ31, priority is handled by IPR0 – IPR7 register
– For SVCall, SysTick, and PendSV, priority is handled by SHPR2 – SHPR3 register

16
Programmer’s Model
Interrupts and Exceptions
Magic words:
– Tail-chaining
• On completion of an exception handler, if there is a pending exception that meets the
requirements for exception entry, the stack pop is skipped and control transfers to the
new exception handler.
• Happens if the later interrupt has same or lower priority

– Late-arriving
• If a higher priority exception occurs during state saving for a previous exception, the
processor switches to handle the higher priority exception and initiates the vector fetch
for that exception. State saving is not affected by late arrival because the state saved
would be the same for both exceptions. On return from the exception handler of the
late-arriving exception, the normal tail-chaining rules apply.
• Happens if the later interrupt has higher priority

17
Programmer’s Model
Interrupts and Exceptions
NVIC: Connecting external peripherals to the core
ICPR IPR0-
ICER ISPR IPR7
ISER
S R S R

IRQ IRQ
IRQ Mask* Prioritize CPU
[31:0] Pending

*) Mask active means interrupt is enabled

18
Quizzes

19
Quizzes

Run ‘LPCXpresso’ and download ‘CMSIS’ example

Open ‘core_cm0.h’ and ‘core_cm0.c’ file
Answer these questions:
– What assembly instruction that is needed to enable interrupts ?
– How to set MSP ? (clue: C function name)
– How to enable specific IRQ ? (clue: C function name)
– How to set the IRQ priority ? (clue: C function name)

20
ARM Cortex-M0 Overview
By: Daniel Widyanto
September 2010

1
Contents

Introduction to ARM Cortex-M0

Programmer’s Model : Processor Modes
Programmer’s Model : Stacks
Programmer’s Model : Core Registers
Programmer’s Model : Interrupts and Exceptions
Quizzes

2
Introduction to ARM Cortex-M0

3
 Introduction to ARM Cortex-M0

ARM Cortex-M0:
– Entry-level 32-bit ARM Cortex processor designed for a broad range of embedded
applications
Benefits:
– simple, easy-to-use programmers model
– highly efficient ultra-low power operation
– excellent code density
– deterministic, high-performance interrupt handling
– upward compatibility with the rest of the Cortex-M processor family
Cortex-M0 core peripherals
– NVIC:
• An embedded interrupt controller that supports low latency interrupt processing.
– System Control Block:
• Provides system implementation information and system control, including configuration, control,
and reporting of system exceptions.
– Optional system timer (SysTick):
• A 24-bit count-down timer. If implemented, use this as a Real Time Operating System (RTOS) tick
timer or as a simple counter
4

ARM Cortex-M0 have extra peripherals, other than its processing unit core:
-NVIC: To control the interrupt
-WIC: Wakeup interrupt controller, to wake the MCU from power saving mode without
any clock
-SysTick: Simple 24-bits timer. This timer can be used as RTOS timer to make the RTOS
portable for all of ARM Cortex-M series (Cortex-M0, Cortex-M1, Cortex-M3, Cortex-M4)
-Serial Wire Debug (SWD): To enable simple external connection to debug and trace
ARM Cortex-M series

4
Introduction to ARM Cortex-M0
(cont’d)

5
Programmer’s Model

Processor Modes

6
 Programmer’s Model
Processor Modes
Thread mode
– Used to execute application software. The processor enters Thread mode when it
comes out of reset.

Handler mode
– Used to handle exceptions. The processor returns to Thread mode when it has
finished all exception processing.

Note:
Other ARM architectures support the concept of privileged or unprivileged software
execution. This processor does not support different privilege levels. Software execution is
always privileged, meaning software can access all the features of the processor.

For other ARM Cortex-M series (except ARM CortexM0), the ‘unprivileged’ mode:
• has limited access to the MSR and MRS instructions, and cannot use the CPS
instruction
• cannot access the system timer, NVIC, or system control block
• might have restricted access to memory or peripherals.

The ‘Handler’ mode is always privileged. The ‘Thread’ mode can be privileged or
unprivileged, depending on the settings at ‘CONTROL’ register.

ARM Cortex-M0 retain the mode for compatibility with other ARM Cortex-M series.

7
Programmer’s Model

Stacks

8
 Programmer’s Model
Stacks
Full descending: stack pointer indicates the last stacked item on the stack
memory.
Two stacks, two independent stack pointers:
Processor mode Used to execute Stack used
Thread Applications Main stack or process stack
Handler Exception handlers Main stack

– Handler mode always uses the MSP (Main Stack Pointer)

– Thread mode can use MSP (Main Stack Pointer) by default, or PSP (Process Stack
Pointer)
• Controlled by CONTROL register

In an OS environment, ARM recommends that threads running in Thread

mode use the process stack and the kernel and exception handlers use the
main stack.
9

• The ’MSP’ and ’PSP’ are usually used in RTOS to differentiate application and kernel
codes.
• To simplify the firmware, in ARM Cortex-M0, the ’PSP’ can be ignored. User can always
use ’MSP’ for all of their interrupt handling or normal codes.
• On reset, the processor loads the ’MSP’ with the value from address 0x00000000.

9
Programmer’s Model

Core Registers

10
 Programmer’s Model
Core Registers

11

Notes:
• Some ARM Cortex-M series instruction only works with ‘low registers’ (R0-R7), specially
the memory access instructions
• The PRIMASK register prevents activation of all exceptions with configurable priority.
The bit assignments are:
Bits Name Function
[31:1] - Reserved
[0] PRIMASK
0 = no effect
1 = prevents the activation of all
exceptions with configurable
priority.

• The CONTROL register controls the stack used when the processor is in Thread mode.
The bit assignments are:
Bits Name Function
[31:2] - Reserved
[1] Active stack Defines the current stack:
pointer 0 = MSP is the current stack pointer
1 = PSP is the current stack pointer.
In Handler mode this bit reads as zero
and ignores writes.
[0] - Reserved.

11
 Programmer’s Model
Core Registers
Program Status Register (PSR) combines:
– Application Program Status Register (APSR)
– Interrupt Program Status Register (IPSR)
– Execution Program Status Register (EPSR)
• Mutually exclusive each other.
• User can access the whole registers as ‘PSR’, or individual blocks as ‘APSR’ / ‘IPSR’ /
‘EPSR’, or combination of two blocks

12

•User can also access combination of the two blocks:

Register Combination
PSR APSR, EPSR, and IPSR
IEPSR EPSR and IPSR
IAPSR APSR and IPSR
EAPSR APSR and EPSR
•APSR bit assignments:
Bits Name Function
[31] N Negative flag
[30] Z Zero flag
[29] C Carry or borrow flag
[28] V Overflow flag
[27:0] - Reserved
•IPSR bit assignments:
Bits Name Function
[31:6] - Reserved
[5:0] Exception number This is the number of the current exception
0 = Thread mode
1 = Reserved
2 = NMI
3 = HardFault
4-10 = Reserved11 = SVCall
12, 13 = Reserved
14 = PendSV
15 = SysTick, if implemented[a]
16 = IRQ0
n+15 = IRQ(n-1)[b]
(n+16) to 63 = Reserved.
[a] If the device does not implement the SysTick timer, exception number 15 is reserved.
[b] The number of interrupts, n, is implementation-defined, in the range 1-32.
•EPSR bit assignments
Bits Name Function
[31:25] - Reserved
[24] T Thumb state bit
[23:0] - Reserved
12
Programmer’s Model

Interrupt and Exceptions

13
 Programmer’s Model
Interrupts and Exceptions
The vector table is fixed at address 0x00000000
1st record is stack address for MSP
The rest of the record are addresses for
exception handlers
– Address only. No instruction such as ‘branch
<int_handler>’

Address for exception handlers must be in ‘odd’

value, since ARM Cortex-M0 only supports
Thumb mode
– Bit[0] in address determined whether Thumb
mode is used or not

HardFault exception will be triggered for ‘even’

address.

14

• Other ARM Cortex-M series supports vector address remapping / relocation. ARM
Cortex-M0 only support address 0x00 as vector table base.

• Bit[0] in address determined whether the CPU should use Thumb mode or not. It’s part
of ARM7TDMI compatibility.

14
Programmer’s Model
Interrupts and Exceptions
Exception entry
– ARM Cortex-M0 is automatically save the registers into stack (pointed by MSP)
before executing exception handler

– The exception handler address then fetch and executed

Exception return
– Use ‘BX LR’ to return the registers value from stack
– LR defines the mode and stack pointer for the return address:
• LR = 0xFFFFFFF1: Return to Handler mode, use MSP after return
• LR = 0xFFFFFFF9: Return to Thread mode, use MSP after return
• LR = 0xFFFFFFFD: Return to Thread mode, use PSP after return

15

15
 Programmer’s Model
Interrupts and Exceptions
Definition:
– An event that alters the normal sequence of execution

Configurable Priority Unconfigureable Priority

Synchronous SVCall HardFault

Asynchronous PendSV, SysTick, IRQ0- Reset, NMI

IRQ31

Unconfigureable priority exceptions are un-maskable. Configurable priority exceptions

are maskable (using ‘PRIMASK’)
Priority value is 0 (highest) to 192 (lowest)
– Default priority is 0 (highest)
– For IRQ0-IRQ31, priority is handled by IPR0 – IPR7 register
– For SVCall, SysTick, and PendSV, priority is handled by SHPR2 – SHPR3 register

16

• Reset
Invoked on power up or a warm reset.
• Non-Maskable Interrupt (NMI)
Asserted if NMI pin is pulled HIGH by external circuitry. Not implemented in LPC111x
• HardFault
Occurs because of an error during normal or exception processing (eg. Un-aligned
memory access)
• SVCall
Exception that is triggered by the ‘SVC’ instruction. In an OS environment, applications
can use SVC instructions to access OS kernel functions and device drivers.
• PendSV
Interrupt-driven request for system-level service. In an OS environment, use PendSV for
context switching when no other exception is active. Invoked by setting ’PENDSVSET’ bit
in ‘ICSR’.
• SysTick
Exception when the system timer reaches zero.
• Interrupt (IRQ)
Exception signaled by a peripheral, or generated by a software request.

16
 Programmer’s Model
Interrupts and Exceptions
Magic words:
– Tail-chaining
• On completion of an exception handler, if there is a pending exception that meets the
requirements for exception entry, the stack pop is skipped and control transfers to the
new exception handler.
• Happens if the later interrupt has same or lower priority

– Late-arriving
• If a higher priority exception occurs during state saving for a previous exception, the
processor switches to handle the higher priority exception and initiates the vector fetch
for that exception. State saving is not affected by late arrival because the state saved
would be the same for both exceptions. On return from the exception handler of the
late-arriving exception, the normal tail-chaining rules apply.
• Happens if the later interrupt has higher priority

17

Question: What it takes to enable the tail chaining / late arriving feature ?
Answer: Nothing. It’s enabled by hardware by default.

Question: How to disable the tail-chaining / late-arriving feature ?

Answer: Disable the ‘configurable exceptions’ through PRIMASK. The Reset, NMI, and
HardFault cannot be disabled.

17
Programmer’s Model
Interrupts and Exceptions
NVIC: Connecting external peripherals to the core
ICPR IPR0-
ICER ISPR IPR7
ISER
S R S R

IRQ IRQ
IRQ Mask* Prioritize CPU
[31:0] Pending

*) Mask active means interrupt is enabled

18
Quizzes

19
Quizzes

Run ‘LPCXpresso’ and download ‘CMSIS’ example

Open ‘core_cm0.h’ and ‘core_cm0.c’ file
Answer these questions:
– What assembly instruction that is needed to enable interrupts ?
– How to set MSP ? (clue: C function name)
– How to enable specific IRQ ? (clue: C function name)
– How to set the IRQ priority ? (clue: C function name)

20