Cortex-M3 - Generic User Guide

Cortex -M3 Devices
Generic User Guide
Copyright 2010 ARM. All rights reserved. ARM DUI 0552A (ID121610)
Cortex-M3 Devices
Generic User Guide Copyright 2010 ARM. All rights reserved.
Release Information The following changes have been made to this book.
Change history Date 16 December 2010 Issue A Confidentiality Non-Confidential Change First release
Proprietary Notice Words and logos marked with or are registered trademarks or trademarks of ARM in the EU and other countries, except as otherwise stated below in this proprietary notice. Other brands and names mentioned herein may be the trademarks of their respective owners. Neither the whole nor any part of the information contained in, or the product described in, this document may be adapted or reproduced in any material form except with the prior written permission of the copyright holder. The product described in this document is subject to continuous developments and improvements. All particulars of the product and its use contained in this document are given by ARM in good faith. However, all warranties implied or expressed, including but not limited to implied warranties of merchantability, or fitness for purpose, are excluded. This document is intended only to assist the reader in the use of the product. ARM shall not be liable for any loss or damage arising from the use of any information in this document, or any error or omission in such information, or any incorrect use of the product. Where the term ARM is used it means ARM or any of its subsidiaries as appropriate. Confidentiality Status This document is Non-Confidential. The right to use, copy and disclose this document may be subject to license restrictions in accordance with the terms of the agreement entered into by ARM and the party that ARM delivered this document to. Product Status The information in this document is final, that is for a developed product. Web Address
http://www.arm.com
ARM DUI 0552A ID121610
Copyright 2010 ARM. All rights reserved. Non-Confidential
ii
Contents Cortex-M3 Devices Generic User Guide
Preface
About this book ........................................................................................................... vi Feedback .................................................................................................................... ix
Chapter 1
1.1
Introduction
About the Cortex-M3 processor and core peripherals ............................................. 1-2
Chapter 2
2.1 2.2 2.3 2.4 2.5
The Cortex-M3 Processor

Programmers model ................................................................................................ 2-2 Memory model ....................................................................................................... 2-12 Exception model .................................................................................................... 2-21 Fault handling ........................................................................................................ 2-28 Power management ............................................................................................... 2-31
Chapter 3
The Cortex-M3 Instruction Set

3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 Instruction set summary ........................................................................................... 3-2 CMSIS functions ...................................................................................................... 3-6 About the instruction descriptions ............................................................................ 3-8 Memory access instructions .................................................................................. 3-17 General data processing instructions .................................................................... 3-34 Multiply and divide instructions .............................................................................. 3-49 Saturating instructions ........................................................................................... 3-54 Bitfield instructions ................................................................................................. 3-56 Branch and control instructions ............................................................................. 3-60 Miscellaneous instructions ..................................................................................... 3-68
Chapter 4
4.1
Cortex-M3 Peripherals
About the Cortex-M3 peripherals ............................................................................. 4-2
iii
4.2 4.3 4.4 4.5
Nested Vectored Interrupt Controller ....................................................................... 4-3 System control block .............................................................................................. 4-11 System timer, SysTick ........................................................................................... 4-33 Optional Memory Protection Unit ........................................................................... 4-37
Appendix A
Cortex-M3 Options
A.1 Cortex-M3 implementation options .......................................................................... A-2
Glossary
iv
Preface
This preface introduces the Cortex-M3 Devices Generic User Guide. It contains the following sections: About this book on page vi Feedback on page ix.
Preface
About this book

This book is a generic user guide for devices that implement the ARM Cortex-M3 processor. Implementers of Cortex-M3 designs make a number of implementation choices, that can affect the functionality of the device. This means that, in this book: some information is described as implementation-defined some features are described as optional. In this book, unless the context indicates otherwise: Processor Device Refers to the Cortex-M3 processor, as supplied by ARM. Refers to an implemented device, supplied by an ARM partner, that incorporates a Cortex-M3 processor. In particular, your device refers to the particular implementation of the Cortex-M3 that you are using. Some features of your device depend on the implementation choices made by the ARM partner that made the device.
Product revision status The rnpn identifier indicates the revision status of the product described in this book, where: rn Identifies the major revision of the product. pn Identifies the minor revision or modification status of the product. Intended audience This book is written for application and system-level software developers, familiar with programming, who want to program a device that includes the Cortex-M3 processor. Using this book This book is organized into the following chapters: Chapter 1 Introduction Read this for an introduction to the Cortex-M3 processor and its features. Chapter 2 The Cortex-M3 Processor Read this for information about how to program the processor, the processor memory model, exception and fault handling, and power management. Chapter 3 The Cortex-M3 Instruction Set Read this for information about the processor instruction set. Chapter 4 Cortex-M3 Peripherals Read this for information about Cortex-M3 peripherals. Appendix A Cortex-M3 Options Read this for information about the processor implementation and configuration options. Glossary Read this for definitions of terms used in this book.
vi
Preface
Typographical conventions The typographical conventions are: italic bold

monospace
Highlights important notes, introduces special terminology, denotes internal cross-references, and citations. Highlights interface elements, such as menu names. Denotes signal names. Also used for terms in descriptive lists, where appropriate. Denotes text that you can enter at the keyboard, such as commands, file and program names, and source code. Denotes a permitted abbreviation for a command or option. You can enter the underlined text instead of the full command or option name. Denotes arguments to monospace text where the argument is to be replaced by a specific value. Enclose replaceable terms for assembler syntax where they appear in code or code fragments. For example:
CMP Rn, <Rm|#imm>
monospace
monospace italic
< and >
vii
Preface
Additional reading This section lists publications by ARM and by third parties. See Infocenter, http://infocenter.arm.com, for access to ARM documentation. See onARM, http://onarm.com, for embedded software development resources including the Cortex Microcontroller Software Interface Standard (CMSIS). ARM publications This book contains information that is specific to this product. See the following documents for other relevant information: Cortex-M3 Technical Reference Manual (ARM DDI 0439) ARMv7-M Architecture Reference Manual (ARM DDI 0403). Other publications This guide only provides generic information for devices that implement the ARM Cortex-M3 processor. For information about your device see the documentation published by the device manufacturer.
viii
Preface
Feedback
ARM welcomes feedback on this product and its documentation. Feedback on content If you have comments on content then send an e-mail to errata@arm.com. Give: the title the number, ARM DUI 0552A the page numbers to which your comments apply a concise explanation of your comments. ARM also welcomes general suggestions for additions and improvements.
ix
Chapter 1 Introduction
This chapter introduces the Cortex-M3 processor and its features. It contains the following section: About the Cortex-M3 processor and core peripherals on page 1-2.
1-1
Introduction
1.1
About the Cortex-M3 processor and core peripherals

The Cortex-M3 processor is a high performance 32-bit processor designed for the microcontroller market. It offers significant benefits to developers, including: outstanding processing performance combined with fast interrupt handling enhanced system debug with extensive breakpoint and trace capabilities efficient processor core, system and memories ultra-low power consumption with integrated sleep mode and an optional deep sleep mode platform security robustness, with an optional integrated Memory Protection Unit (MPU).
Cortex-M3 processor Optional WIC NVIC Processor core Optional Embedded Trace Macrocell
Optional Debug Access Port
Optional Memory protection unit
Optional Serial Wire viewer
Optional Flash patch
Optional Data watchpoints
Bus matrix Code interface SRAM and peripheral interface
Figure 1-1 Cortex-M3 implementation
The Cortex-M3 processor is built on a high-performance processor core, with a 3-stage pipeline Harvard architecture, making it ideal for demanding embedded applications. The processor delivers exceptional power efficiency through an efficient instruction set and extensively optimized design, providing high-end processing hardware including optional IEEE754-compliant single-precision floating-point computation, a range of single-cycle and SIMD multiplication and multiply-with-accumulate capabilities, saturating arithmetic and dedicated hardware division. To facilitate the design of cost-sensitive devices, the Cortex-M3 processor implements tightly-coupled system components that reduce processor area while significantly improving interrupt handling and system debug capabilities. The Cortex-M3 processor implements a version of the Thumb instruction set based on Thumb-2 technology, ensuring high code density and reduced program memory requirements. The Cortex-M3 instruction set provides the exceptional performance expected of a modern 32-bit architecture, with the high code density of 8-bit and 16-bit microcontrollers. The Cortex-M3 processor closely integrates a configurable NVIC, to deliver industry-leading interrupt performance. The NVIC includes a Non-Maskable Interrupt (NMI) that can provide up to 256 interrupt priority levels. The tight integration of the processor core and NVIC provides fast execution of Interrupt Service Routines (ISRs), dramatically reducing the interrupt latency.
1-2
Introduction
This is achieved through the hardware stacking of registers, and the ability to suspend load-multiple and store-multiple operations. Interrupt handlers do not require wrapping in assembler code, removing any code overhead from the ISRs. A tail-chain optimization also significantly reduces the overhead when switching from one ISR to another. To optimize low-power designs, the NVIC integrates with the sleep modes, which can include an optional deep sleep function. This enables the entire device to be rapidly powered down while still retaining program state. 1.1.1 System-level interface The Cortex-M3 processor provides multiple interfaces using AMBA technology to provide high speed, low latency memory accesses. It supports unaligned data accesses and implements atomic bit manipulation that enables faster peripheral controls, system spinlocks and thread-safe Boolean data handling. The Cortex-M3 processor has an optional Memory Protection Unit (MPU) that permits control of individual regions in memory, enabling applications to utilize multiple privilege levels, separating and protecting code, data and stack on a task-by-task basis. Such requirements are becoming critical in many embedded applications such as automotive. 1.1.2 Optional integrated configurable debug The Cortex-M3 processor can implement a complete hardware debug solution. This provides high system visibility of the processor and memory through either a traditional JTAG port or a 2-pin Serial Wire Debug (SWD) port that is ideal for microcontrollers and other small package devices. For system trace the processor integrates an Instrumentation Trace Macrocell (ITM) alongside data watchpoints and a profiling unit. To enable simple and cost-effective profiling of the system events these generate, a Serial Wire Viewer (SWV) can export a stream of software-generated messages, data trace, and profiling information through a single pin. The optional Embedded Trace Macrocell (ETM) delivers unrivalled instruction trace capture in an area far smaller than traditional trace units, enabling many low cost MCUs to implement full instruction trace for the first time. The optional Flash Patch and Breakpoint Unit (FPB) provides up to eight hardware breakpoint comparators that debuggers can use. The comparators in the FPB also provide remap functions of up to eight words in the program code in the CODE memory region. This enables applications stored on a non-erasable, ROM-based microcontroller to be patched if a small programmable memory, for example flash, is available in the device. During initialization, the application in ROM detects, from the programmable memory, whether a patch is required. If a patch is required, the application programs the FPB to remap a number of addresses. When those addresses are accessed, the accesses are redirected to a remap table specified in the FPB configuration, which means the program in the non-modifiable ROM can be patched. 1.1.3 Cortex-M3 processor features and benefits summary tight integration of system peripherals reduces area and development costs Thumb instruction set combines high code density with 32-bit performance code-patch ability for ROM system updates power control optimization of system components integrated sleep modes for low power consumption fast code execution permits slower processor clock or increases sleep mode time hardware division and fast digital-signal-processing orientated multiply accumulate
1-3
Introduction
deterministic, high-performance interrupt handling for time-critical applications optional MPU for safety-critical applications extensive implementation-defined debug and trace capabilities: Serial Wire Debug and Serial Wire Trace reduce the number of pins required for debugging, tracing, and code profiling.
1.1.4
Cortex-M3 core peripherals These are: Nested Vectored Interrupt Controller The NVIC is an embedded interrupt controller that supports low latency interrupt processing. System Control Block The System Control Block (SCB) is the programmers model interface to the processor. It provides system implementation information and system control, including configuration, control, and reporting of system exceptions. System timer The system timer, SysTick, is a 24-bit count-down timer. Use this as a Real Time Operating System (RTOS) tick timer or as a simple counter. Memory Protection Unit The MPU improves system reliability by defining the memory attributes for different memory regions. It provides up to eight different regions, and an optional predefined background region.
1-4
Chapter 2 The Cortex-M3 Processor
This Chapter describes the Cortex-M3 processor. It contains the following sections: Programmers model on page 2-2 Memory model on page 2-12 Exception model on page 2-21 Fault handling on page 2-28 Power management on page 2-31.
2-1
2.1
Programmers model
This section describes the Cortex-M3 programmers model. In addition to the individual core register descriptions, it contains information about the processor modes and privilege levels for software execution and stacks.
2.1.1
Processor mode and privilege levels for software execution The processor modes are: Thread mode Handler mode Used to execute application software. The processor enters Thread mode when it comes out of reset. Used to handle exceptions. The processor returns to Thread mode when it has finished all exception processing.
The privilege levels for software execution are: Unprivileged The software: 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.
Unprivileged software executes at the unprivileged level. Privileged The software can use all the instructions and has access to all resources. Privileged software executes at the privileged level. In Thread mode, the CONTROL register controls whether software execution is privileged or unprivileged, see CONTROL register on page 2-9. In Handler mode, software execution is always privileged. Only privileged software can write to the CONTROL register to change the privilege level for software execution in Thread mode. Unprivileged software can use the SVC instruction to make a supervisor call to transfer control to privileged software. 2.1.2 Stacks The processor uses a full descending stack. This means the stack pointer holds the address of the last stacked item in memory. When the processor pushes a new item onto the stack, it decrements the stack pointer and then writes the item to the new memory location. The processor implements two stacks, the main stack and the process stack, with a pointer for each held in independent registers, see Stack Pointer on page 2-4. In Thread mode, the CONTROL register controls whether the processor uses the main stack or the process stack, see CONTROL register on page 2-9. In Handler mode, the processor always uses the main stack. The options for processor operations are:
Table 2-1 Summary of processor mode, execution privilege level, and stack use options Processor mode Thread Handler Used to execute Applications Exception handlers Privilege level for software execution Privileged or unprivileged a Always privileged Stack used Main stack or process stack a Main stack
a. See CONTROL register on page 2-9.
2-2
2.1.3
Core registers The processor core registers are:

R0 R1 R2 Low registers R3 R4 R5 R6 R7 R8 R9 High registers R10 R11 R12 Stack Pointer Link Register Program Counter SP (R13) LR (R14) PC (R15) PSR PRIMASK FAULTMASK BASEPRI CONTROL CONTROL register Exception mask registers Special registers Program status register PSP MSP
General-purpose registers
Banked version of SP
Table 2-2 Core register set summary Name R0-R12 MSP PSP LR PC PSR ASPR IPSR EPSR PRIMASK FAULTMASK BASEPRI CONTROL Type a RW RW RW RW RW RW RW RO RO RW RW RW RW Required privilege b Either Privileged Either Either Either Privileged Either Privileged Privileged Privileged Privileged Privileged Privileged Reset value Unknown See description Unknown
0xFFFFFFFF
Description General-purpose registers on page 2-4 Stack Pointer on page 2-4 Stack Pointer on page 2-4 Link Register on page 2-4 Program Counter on page 2-4 Program Status Register on page 2-4 Application Program Status Register on page 2-5 Interrupt Program Status Register on page 2-6 Execution Program Status Register on page 2-6 Priority Mask Register on page 2-8 Fault Mask Register on page 2-8 Base Priority Mask Register on page 2-9 CONTROL register on page 2-9
See description
0x01000000
Unknown
0x00000000 0x01000000 0x00000000 0x00000000 0x00000000 0x00000000
a. Describes access type during program execution in thread mode and Handler mode. Debug access can differ. b. An entry of Either means privileged and unprivileged software can access the register.
2-3
General-purpose registers R0-R12 are 32-bit general-purpose registers for data operations. Stack Pointer The Stack Pointer (SP) is register R13. In Thread mode, bit[1] of the CONTROL register indicates the stack pointer to use: 0 = Main Stack Pointer (MSP). This is the reset value. 1 = Process Stack Pointer (PSP). On reset, the processor loads the MSP with the value from address 0x00000000. Link Register The Link Register (LR) is register R14. It stores the return information for subroutines, function calls, and exceptions. On reset, the processor sets the LR value to 0xFFFFFFFF. Program Counter The Program Counter (PC) is register R15. It contains the current program address. On reset, the processor loads the PC with the value of the reset vector, which is at address 0x00000004. Bit[0] of the value is loaded into the EPSR T-bit at reset and must be 1. Program Status Register The Program Status Register (PSR) combines: Application Program Status Register (APSR) Interrupt Program Status Register (IPSR) Execution Program Status Register (EPSR). These registers are mutually exclusive bitfields in the 32-bit PSR. The bit assignments are:
31 30 29 28 27 26 25 24 23 APSR N Z C V Q 16 15 Reserved 10 9 8 0
IPSR
Reserved
ISR_NUMBER
EPSR
Reserved
ICI/IT T
Reserved
ICI/IT
Reserved
Access these registers individually or as a combination of any two or all three registers, using the register name as an argument to the MSR or MRS instructions. For example: read all of the registers using PSR with the MRS instruction write to the APSR N, Z, C, V, and Q bits using APSR_nzcvq with the MSR instruction.
2-4
The PSR combinations and attributes are:

Table 2-3 PSR register combinations Register PSR IEPSR IAPSR EAPSR Type RWa, b RO RWa RWb Combination APSR, EPSR, and IPSR EPSR and IPSR APSR and IPSR APSR and EPSR
a. The processor ignores writes to the IPSR bits. b. Reads of the EPSR bits return zero, and the processor ignores writes to the these bits
See the instruction descriptions MRS on page 3-74 and MSR on page 3-75 for more information about how to access the program status registers.
Application Program Status Register
The APSR contains the current state of the condition flags from previous instruction executions. See the register summary in Table 2-2 on page 2-3 for its attributes. The bit assignments are:
Table 2-4 APSR bit assignments Bits [31] [30] [29] [28] [27] [26:0] Name N Z C V Q Function Negative flag Zero flag Carry or borrow flag Overflow flag Saturation flag Reserved
2-5
Interrupt Program Status Register
The IPSR contains the exception type number of the current Interrupt Service Routine (ISR). See the register summary in Table 2-2 on page 2-3 for its attributes. The bit assignments are:
Table 2-5 IPSR bit assignments Bits [31:9] [8:0] Name ISR_NUMBER Function Reserved. This is the number of the current exception: 0 = Thread mode 1 = Reserved 2 = NMI 3 = HardFault 4 = MemManage 5 = BusFault 6 = UsageFault 7-10 = Reserved 11 = SVCall 12 = Reserved for Debug 13 = Reserved 14 = PendSV 15 = SysTick 16 = IRQ0 . . . n+15 = IRQ(n-1)a. See Exception types on page 2-21 for more information.
a. The number of interrupts, n, is implementation-defined, in the range 1-240.
Execution Program Status Register
The EPSR contains the Thumb state bit, and the execution state bits for either the: If-Then (IT) instruction Interruptible-Continuable Instruction (ICI) field for an interrupted load multiple or store multiple instruction.
See the register summary in Table 2-2 on page 2-3 for the EPSR attributes. The bit assignments are:
Table 2-6 EPSR bit assignments Bits [31:27] [26:25], [15:10] Name ICI/IT Function Reserved. Indicates the interrupted position of a continuable instruction, see Interruptible-continuable instructions on page 2-7, or the execution state of an IT instruction, see IT on page 3-64.
2-6
Table 2-6 EPSR bit assignments (continued) Bits [24] [23:16] [9:0] Name T Function Thumb state bit, see Thumb state. Reserved. Reserved.
Attempts to read the EPSR directly through application software using the MSR instruction always return zero. Attempts to write the EPSR using the MSR instruction in application software are ignored.
Interruptible-continuable instructions
When an interrupt occurs during the execution of an LDM, STM, PUSH, or POP instruction, the processor: stops the load multiple or store multiple instruction operation temporarily stores the next register operand in the multiple operation to EPSR bits[15:12]. After servicing the interrupt, the processor: returns to the register pointed to by bits[15:12] resumes execution of the multiple load or store instruction. When the EPSR holds ICI execution state, bits[26:25,11:10] are zero.
If-Then block
The If-Then block contains up to four instructions following an IT instruction. Each instruction in the block is conditional. The conditions for the instructions are either all the same, or some can be the inverse of others. See IT on page 3-64 for more information.
Thumb state
The Cortex-M3 processor only supports execution of instructions in Thumb state. The following can clear the T bit to 0: instructions BLX, BX and POP{PC} restoration from the stacked xPSR value on an exception return bit[0] of the vector value on an exception entry or reset. Attempting to execute instructions when the T bit is 0 results in a fault or lockup. See Lockup on page 2-30 for more information. Exception mask registers The exception mask registers disable the handling of exceptions by the processor. Disable exceptions where they might impact on timing critical tasks. To access the exception mask registers use the MSR and MRS instructions, or the CPS instruction to change the value of PRIMASK or FAULTMASK. See MRS on page 3-74, MSR on page 3-75, and CPS on page 3-70 for more information.
2-7
Priority Mask Register
The PRIMASK register prevents activation of all exceptions with configurable priority. See the register summary in Table 2-2 on page 2-3 for its attributes. The bit assignments are:
31 Reserved PRIMASK 1 0
Table 2-7 PRIMASK register bit assignments Bits [31:1] [0] Name PRIMASK Function Reserved 0 = no effect 1 = prevents the activation of all exceptions with configurable priority.
Fault Mask Register
The FAULTMASK register prevents activation of all exceptions except for Non-Maskable Interrupt (NMI). See the register summary in Table 2-2 on page 2-3 for its attributes. The bit assignments are:
31 Reserved FAULTMASK 1 0
Table 2-8 FAULTMASK register bit assignments Bits [31:1] [0] Name FAULTMASK Function Reserved 0 = no effect 1 = prevents the activation of all exceptions except for NMI.
The processor clears the FAULTMASK bit to 0 on exit from any exception handler except the NMI handler.
2-8
Base Priority Mask Register
The BASEPRI register defines the minimum priority for exception processing. When BASEPRI is set to a nonzero value, it prevents the activation of all exceptions with the same or lower priority level as the BASEPRI value. See the register summary in Table 2-2 on page 2-3 for its attributes. The bit assignments are:
31 Reserved 8 7 BASEPRI 0
Table 2-9 BASEPRI register bit assignments Bits [31:8] [7:0] Name BASEPRI a Function Reserved Priority mask bits: 0x00 = no effect Nonzero = defines the base priority for exception processing. The processor does not process any exception with a priority value greater than or equal to BASEPRI.
a. This field is similar to the priority fields in the interrupt priority registers. Register priority value fields are 8 bits wide, and non-implemented low-order bits read as zero and ignore writes. See Interrupt Priority Registers on page 4-7 for more information. Higher priority field values correspond to lower exception priorities.
CONTROL register The CONTROL register controls the stack used and the privilege level for software execution when the processor is in Thread mode. See the register summary in Table 2-2 on page 2-3 for its attributes. The bit assignments are:
31 Reserved 3 2 1 0
SPSEL nPRIV
Table 2-10 CONTROL register bit assignments Bits [31:2] [1] Name SPSEL Function Reserved. Defines the currently active stack pointer: In Handler mode this bit reads as zero and ignores writes. The Cortex-M3 updates this bit automatically on exception return. 0 = MSP is the current stack pointer 1 = PSP is the current stack pointer. Defines the Thread mode privilege level: 0 = Privileged 1 = Unprivileged.
[0]
nPRIV
Handler mode always uses the MSP, so the processor ignores explicit writes to the active stack pointer bit of the CONTROL register when in Handler mode. The exception entry and return mechanisms automatically update the CONTROL register based on the EXC_RETURN value, see Table 2-17 on page 2-27.
ARM DUI 0552A ID121610 Copyright 2010 ARM. All rights reserved. Non-Confidential 2-9
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. By default, Thread mode uses the MSP. To switch the stack pointer used in Thread mode to the PSP, either: use the MSR instruction to set the Active stack pointer bit to 1, see MSR on page 3-75. perform an exception return to Thread mode with the appropriate EXC_RETURN value, see Table 2-17 on page 2-27.
Note When changing the stack pointer, software must use an ISB instruction immediately after the MSR instruction. This ensures that instructions after the ISB instruction execute using the new stack pointer. See ISB on page 3-73
2.1.4
Exceptions and interrupts The Cortex-M3 processor supports interrupts and system exceptions. The processor and the NVIC prioritize and handle all exceptions. An exception changes the normal flow of software control. The processor uses Handler mode to handle all exceptions except for reset. See Exception entry on page 2-26 and Exception return on page 2-27 for more information. The NVIC registers control interrupt handling. See Nested Vectored Interrupt Controller on page 4-3 for more information.
2.1.5
Data types The processor: supports the following data types: 32-bit words 16-bit halfwords 8-bit bytes. manages all data memory accesses as little-endian or big-endian. Instruction memory and PPB accesses are always performed as little-endian. See Memory regions, types and attributes on page 2-12 for more information.
2.1.6
The Cortex Microcontroller Software Interface Standard For a Cortex-M3 microcontroller system, the Cortex Microcontroller Software Interface Standard (CMSIS) defines: a common way to: access peripheral registers define exception vectors the names of: the registers of the core peripherals the core exception vectors a device-independent interface for RTOS kernels, including a debug channel. The CMSIS includes address definitions and data structures for the core peripherals in the Cortex-M3 processor.
2-10
CMSIS simplifies software development by enabling the reuse of template code and the combination of CMSIS-compliant software components from various middleware vendors. Software vendors can expand the CMSIS to include their peripheral definitions and access functions for those peripherals. This document includes the register names defined by the CMSIS, and gives short descriptions of the CMSIS functions that address the processor core and the core peripherals. Note This document uses the register short names defined by the CMSIS. In a few cases these differ from the architectural short names that might be used in other documents. The following sections give more information about the CMSIS: Power management programming hints on page 2-33 CMSIS functions on page 3-6 Accessing the Cortex-M3 NVIC registers using CMSIS on page 4-4 NVIC programming hints on page 4-9.
2-11
2.2
Memory model
This section describes the processor memory map, the behavior of memory accesses, and the optional bit-banding features. The processor has a fixed default memory map that provides up to 4GB of addressable memory. The memory map is:
0xFFFFFFFF Vendor-specific memory 511MB
0xE0100000 0xE00FFFFF Private peripheral 1.0MB bus 0xE0000000 0xDFFFFFFF
External device
1.0GB
0xA0000000 0x9FFFFFFF
0x43FFFFFF 32MB Bit band alias 0x42000000 0x400FFFFF 1MB Bit band region 0x40000000 0x23FFFFFF 32MB Bit band alias 0x22000000 0x200FFFFF 1MB Bit band region 0x20000000
External RAM
1.0GB
0x60000000 0x5FFFFFFF Peripheral 0.5GB 0x40000000 0x3FFFFFFF SRAM 0.5GB 0x20000000 0x1FFFFFFF Code 0.5GB 0x00000000
The regions for SRAM and peripherals include optional bit-band regions. Bit-banding provides atomic operations to bit data, see Optional bit-banding on page 2-16. The processor reserves regions of the PPB address range for core peripheral registers, see About the Cortex-M3 peripherals on page 4-2. 2.2.1 Memory regions, types and attributes The memory map and the programming of the optional MPU splits the memory map into regions. Each region has a defined memory type, and some regions have additional memory attributes. The memory type and attributes determine the behavior of accesses to the region. The memory types are: Normal The processor can re-order transactions for efficiency, or perform speculative reads.
2-12
Device Strongly-ordered
The processor preserves transaction order relative to other transactions to Device or Strongly-ordered memory. The processor preserves transaction order relative to all other transactions.
The different ordering requirements for Device and Strongly-ordered memory mean that the memory system can buffer a write to Device memory, but must not buffer a write to Strongly-ordered memory. The additional memory attributes include: Shareable For a shareable memory region that is implemented, the memory system provides data synchronization between bus masters in a system with multiple bus masters, for example, a processor with a DMA controller. Strongly-ordered memory is always shareable. If multiple bus masters can access a non-shareable memory region, software must ensure data coherency between the bus masters. Note This attribute is relevant only if the device is likely to be used in systems where memory is shared between multiple processors. Execute Never (XN) Means the processor prevents instruction accesses. A fault exception is generated only on execution of an instruction executed from an XN region. 2.2.2 Memory system ordering of memory accesses For most memory accesses caused by explicit memory access instructions, the memory system does not guarantee that the order in which the accesses complete matches the program order of the instructions, providing this does not affect the behavior of the instruction sequence. Normally, if correct program execution depends on two memory accesses completing in program order, software must insert a memory barrier instruction between the memory access instructions, see Software ordering of memory accesses on page 2-15. However, the memory system does guarantee some ordering of accesses to Device and Strongly-ordered memory. For two memory access instructions A1 and A2, if A1 occurs before A2 in program order, the ordering of the memory accesses caused by two instructions is:
A2 A1 Normal access Device access, non-shareable Device access, shareable Strongly-ordered access Normal access Device access Non-shareable < < Shareable < < Stronglyordered access < < <
Where: < Means that the memory system does not guarantee the ordering of the accesses. Means that accesses are observed in program order, that is, A1 is always observed before A2.
2-13
2.2.3
Behavior of memory accesses Table 2-11 lists the behavior of accesses to each region in the memory map.
Table 2-11 Memory access behavior
Address range
0x000000000x1FFFFFFF 0x200000000x3FFFFFFF
Memory region Code SRAM
Memory typea Normal Normal
XNa -
Description Executable region for program code. You can also put data here. Executable region for data. You can also put code here.This region includes bit band and bit band alias areas, see Table 2-13 on page 2-16. This region includes bit band and bit band alias areas, see Table 2-14 on page 2-16. Executable region for data. External Device memory. This region includes the NVIC, System timer, and system control block. Implementation-specific.
0x400000000x5FFFFFFF 0x600000000x9FFFFFFF 0xA00000000xDFFFFFFF 0xE00000000xE00FFFFF 0xE01000000xFFFFFFFF
Peripheral External RAM External device Private Peripheral Bus Device
Device Normal Device Stronglyordered Device
XN XN XN XN
a. See Memory regions, types and attributes on page 2-12 for more information.
The Code, SRAM, and external RAM regions can hold programs. However, ARM recommends that programs always use the Code region. This is because the processor has separate buses that enable instruction fetches and data accesses to occur simultaneously. The optional MPU can override the default memory access behavior described in this section. For more information, see Optional Memory Protection Unit on page 4-37. Additional memory access constraints for caches and shared memory When a system includes caches or shared memory, some memory regions might have additional access constraints, and some regions are subdivided, as Table 2-12 shows:
Table 2-12 Memory region shareability and cache policies Address range
0x00000000- 0x1FFFFFFF 0x20000000- 0x3FFFFFFF 0x40000000- 0x5FFFFFFF 0x60000000- 0x7FFFFFFF 0x80000000- 0x9FFFFFFF
Memory region Code SRAM Peripheral External RAM
Memory typea Normal Normal Device Normal
Shareability -
Cache policy b WT WBWA WBWA WT
2-14
Table 2-12 Memory region shareability and cache policies (continued) Address range
0xA0000000- 0xBFFFFFFF 0xC0000000- 0xDFFFFFFF 0xE0000000- 0xE00FFFFF 0xE0100000- 0xFFFFFFFF
Memory region External device
Memory typea Device
Shareability Shareable Non-shareable
Cache policy b -
Private Peripheral Bus Device
Strongly- ordered Device
Shareable -
a. See Memory regions, types and attributes on page 2-12 for more information. b. WT = Write through, no write allocate. WBWA = Write back, write allocate. See the Glossary for more information.
Instruction prefetch and branch prediction The Cortex-M3 processor: prefetches instructions ahead of execution speculatively prefetches from branch target addresses. 2.2.4 Software ordering of memory accesses The order of instructions in the program flow does not always guarantee the order of the corresponding memory transactions. This is because: the processor can reorder some memory accesses to improve efficiency, providing this does not affect the behavior of the instruction sequence. the processor has multiple bus interfaces memory or devices in the memory map have different wait states some memory accesses are buffered or speculative.
Memory system ordering of memory accesses on page 2-13 describes the cases where the memory system guarantees the order of memory accesses. Otherwise, if the order of memory accesses is critical, software must include memory barrier instructions to force that ordering. The processor provides the following memory barrier instructions:
DMB
The Data Memory Barrier (DMB) instruction ensures that outstanding memory transactions complete before subsequent memory transactions. See DMB on page 3-71. The Data Synchronization Barrier (DSB) instruction ensures that outstanding memory transactions complete before subsequent instructions execute. See DSB on page 3-72. The Instruction Synchronization Barrier (ISB) ensures that the effect of all completed memory transactions is recognizable by subsequent instructions. See ISB on page 3-73.
DSB
ISB
MPU programming Use a DSB followed by an ISB instruction or exception return to ensure that the new MPU configuration is used by subsequent instructions.
2-15
2.2.5
Optional bit-banding A bit-band region maps each word in a bit-band alias region to a single bit in the bit-band region. The bit-band regions occupy the lowest 1MB of the SRAM and peripheral memory regions. The memory map has two 32MB alias regions that map to two 1MB bit-band regions: accesses to the 32MB SRAM alias region map to the 1MB SRAM bit-band region, as shown in Table 2-13 accesses to the 32MB peripheral alias region map to the 1MB peripheral bit-band region, as shown in Table 2-14.
Table 2-13 SRAM memory bit-banding regions Address range
0x200000000x200FFFFF 0x220000000x23FFFFFF
Memory region SRAM bit-band region SRAM bit-band alias
Instruction and data accesses Direct accesses to this memory range behave as SRAM memory accesses, but this region is also bit addressable through bit-band alias. Data accesses to this region are remapped to bit band region. A write operation is performed as read-modify-write. Instruction accesses are not remapped. Table 2-14 Peripheral memory bit-banding regions
Address range
0x400000000x400FFFFF 0x420000000x43FFFFFF
Memory region Peripheral bit-band alias Peripheral bit-band region
Instruction and data accesses Direct accesses to this memory range behave as peripheral memory accesses, but this region is also bit addressable through bit-band alias. Data accesses to this region are remapped to bit band region. A write operation is performed as read-modify-write. Instruction accesses are not permitted.
Note A word access to the SRAM or peripheral bit-band alias regions maps to a single bit in the SRAM or peripheral bit-band region Bit band accesses can use byte, halfword, or word transfers. The bit band transfer size matches the transfer size of the instruction making the bit band access.
The following formula shows how the alias region maps onto the bit-band region:
bit_word_offset = (byte_offset x 32) + (bit_number x 4) bit_word_addr = bit_band_base + bit_word_offset
where:
Bit_word_offset is the position of the target bit in the bit-band memory region. Bit_word_addr is the address of the word in the alias memory region that maps to the
targeted bit.
Bit_band_base is the starting address of the alias region. Byte_offset is the number of the byte in the bit-band region that contains the targeted bit.
2-16
Bit_number is the bit position, 0-7, of the targeted bit.
Figure 2-1 shows examples of bit-band mapping between the SRAM bit-band alias region and the SRAM bit-band region: The alias word at 0x23FFFFE0 maps to bit[0] of the bit-band byte at 0x200FFFFF: 0x23FFFFE0 = 0x22000000 + (0xFFFFF*32) + (0*4). The alias word at 0x23FFFFFC maps to bit[7] of the bit-band byte at 0x200FFFFF: 0x23FFFFFC = 0x22000000 + (0xFFFFF*32) + (7*4). The alias word at 0x22000000 maps to bit[0] of the bit-band byte at 0x20000000: 0x22000000 = 0x22000000 + (0*32) + (0 *4). The alias word at 0x2200001C maps to bit[7] of the bit-band byte at 0x20000000: 0x2200001C = 0x22000000+ (0*32) + (7*4).
32MB alias region
0x23FFFFFC 0x23FFFFF8 0x23FFFFF4 0x23FFFFF0 0x23FFFFEC 0x23FFFFE8 0x23FFFFE4 0x23FFFFE0
0x2200001C
0x22000018
0x22000014
0x22000010
0x2200000C
0x22000008
0x22000004
0x22000000
1MB SRAM bit-band region

7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
0x200FFFFF
0x200FFFFE
0x200FFFFD
0x200FFFFC
0x20000003
0x20000002
0x20000001
0x20000000
Figure 2-1 Bit-band mapping
Directly accessing an alias region Writing to a word in the alias region updates a single bit in the bit-band region. Bit[0] of the value written to a word in the alias region determines the value written to the targeted bit in the bit-band region. Writing a value with bit[0] set to 1 writes a 1 to the bit-band bit, and writing a value with bit[0] set to 0 writes a 0 to the bit-band bit. Bits[31:1] of the alias word have no effect on the bit-band bit. Writing 0x01 has the same effect as writing 0xFF. Writing 0x00 has the same effect as writing 0x0E. Reading a word in the alias region: 0x00000000 indicates that the targeted bit in the bit-band region is set to zero 0x00000001 indicates that the targeted bit in the bit-band region is set to 1 Directly accessing a bit-band region Behavior of memory accesses on page 2-14 describes the behavior of direct byte, halfword, or word accesses to the bit-band regions.
2-17
2.2.6
Memory endianness The processor views memory as a linear collection of bytes numbered in ascending order from zero. For example, bytes 0-3 hold the first stored word, and bytes 4-7 hold the second stored word. The memory endianness used is implementation-defined, and the following subsections describe the possible implementations: Byte-invariant big-endian format Little-endian format. Read the AIRCR.ENDIANNESS field to find the implemented endianness, see Application Interrupt and Reset Control Register on page 4-16. Byte-invariant big-endian format In byte-invariant big-endian format, the processor stores the most significant byte of a word at the lowest-numbered byte, and the least significant byte at the highest-numbered byte. For example:
Memory 7 0 31 Address A A+1 A+2 A+3 B0 B1 B2 B3 lsbyte msbyte B0 24 23 B1 16 15 B2 8 7 B3 0 Register
Little-endian format In little-endian format, the processor stores the least significant byte of a word at the lowest-numbered byte, and the most significant byte at the highest-numbered byte. For example:
Memory 7 0 31 Address A A+1 A+2 A+3 B0 B1 B2 B3 msbyte lsbyte B3 24 23 B2 16 15 B1 8 7 B0 0 Register
2.2.7
Synchronization primitives The Cortex-M3 instruction set includes pairs of synchronization primitives. These provide a non-blocking mechanism that a thread or process can use to obtain exclusive access to a memory location. Software can use them to perform a guaranteed read-modify-write memory update sequence, or for a semaphore mechanism.
2-18
A pair of synchronization primitives comprises: A Load-Exclusive instruction Used to read the value of a memory location, requesting exclusive access to that location. A Store-Exclusive instruction Used to attempt to write to the same memory location, returning a status bit to a register. If this bit is: 0 1 it indicates that the thread or process gained exclusive access to the memory, and the write succeeds, it indicates that the thread or process did not gain exclusive access to the memory, and no write was performed.
The pairs of Load-Exclusive and Store-Exclusive instructions are: the word instructions LDREX and STREX the halfword instructions LDREXH and STREXH the byte instructions LDREXB and STREXB. Software must use a Load-Exclusive instruction with the corresponding Store-Exclusive instruction. To perform an exclusive read-modify-write of a memory location, software must: 1. 2. 3. 4. Use a Load-Exclusive instruction to read the value of the location. Modify the value, as required. Use a Store-Exclusive instruction to attempt to write the new value back to the memory location. Test the returned status bit. If this bit is: 0 1 The read-modify-write completed successfully. No write was performed. This indicates that the value returned at step 1 might be out of date. The software must retry the entire read-modify-write sequence.
Software can use the synchronization primitives to implement a semaphores as follows: 1. 2. 3. Use a Load-Exclusive instruction to read from the semaphore address to check whether the semaphore is free. If the semaphore is free, use a Store-Exclusive to write the claim value to the semaphore address. If the returned status bit from step 2 indicates that the Store-Exclusive succeeded then the software has claimed the semaphore. However, if the Store-Exclusive failed, another process might have claimed the semaphore after the software performed step 1.
The Cortex-M3 includes an exclusive access monitor, that tags the fact that the processor has executed a Load-Exclusive instruction. If the processor is part of a multiprocessor system, the system also globally tags the memory locations addressed by exclusive accesses by each processor. The processor removes its exclusive access tag if: It executes a CLREX instruction. It executes a Store-Exclusive instruction, regardless of whether the write succeeds.
2-19
An exception occurs. This means the processor can resolve semaphore conflicts between different threads.
In a multiprocessor implementation: executing a CLREX instruction removes only the local exclusive access tag for the processor executing a Store-Exclusive instruction, or an exception. removes the local exclusive access tags, and global exclusive access tags for the processor.
For more information about the synchronization primitive instructions, see LDREX and STREX on page 3-31 and CLREX on page 3-33. 2.2.8 Programming hints for the synchronization primitives ISO/IEC C cannot directly generate the exclusive access instructions. CMSIS provides functions for generation of these instructions:
Table 2-15 CMSIS functions for exclusive access instructions Instruction
LDREX LDREXH LDREXB STREX STREXH STREXB CLREX
CMSIS function
uint32_t __LDREXW (uint32_t *addr) uint16_t __LDREXH (uint16_t *addr) uint8_t __LDREXB (uint8_t *addr) uint32_t __STREXW (uint32_t value, uint32_t *addr) uint32_t __STREXH (uint16_t value, uint16_t *addr) uint32_t __STREXB (uint8_t value, uint8_t *addr) void __CLREX (void)
2-20
2.3
Exception model
This section describes the exception model in: Exception states Exception types Exception handlers on page 2-23 Vector table on page 2-23 Exception priorities on page 2-24 Interrupt priority grouping on page 2-25 Exception entry and return on page 2-25.
2.3.1
Exception states Each exception is in one of the following states: Inactive Pending The exception is not active and not pending. The exception is waiting to be serviced by the processor. An interrupt request from a peripheral or from software can change the state of the corresponding interrupt to pending. Active An exception that is being serviced by the processor but has not completed. Note An exception handler can interrupt the execution of another exception handler. In this case both exceptions are in the active state. Active and pending The exception is being serviced by the processor and there is a pending exception from the same source.
2.3.2
Exception types The exception types are: Reset Reset is invoked on power up or a warm reset. The exception model treats reset as a special form of exception. When reset is asserted, the operation of the processor stops, potentially at any point in an instruction. When reset is deasserted, execution restarts from the address provided by the reset entry in the vector table. Execution restarts as privileged execution in Thread mode. A NonMaskable Interrupt (NMI) can be signalled by a peripheral or triggered by software. This is the highest priority exception other than reset. It is permanently enabled and has a fixed priority of -2. NMIs cannot be: masked or prevented from activation by any other exception preempted by any exception other than Reset. A HardFault is an exception that occurs because of an error during exception processing, or because an exception cannot be managed by any other exception mechanism. HardFaults have a fixed priority of -1, meaning they have higher priority than any exception with configurable priority.
Copyright 2010 ARM. All rights reserved. Non-Confidential 2-21
NMI
HardFault
MemManage A MemManage fault is an exception that occurs because of a memory protection related fault. The MPU or the fixed memory protection constraints determines this fault, for both instruction and data memory transactions. This fault is always used to abort instruction accesses to Execute Never (XN) memory regions. BusFault A BusFault is an exception that occurs because of a memory related fault for an instruction or data memory transaction. This might be from an error detected on a bus in the memory system. A UsageFault is an exception that occurs because of a fault related to instruction execution. This includes: an undefined instruction an illegal unaligned access invalid state on instruction execution an error on exception return. The following can cause a UsageFault when the core is configured to report them: an unaligned address on word and halfword memory access division by zero. SVCall A supervisor call (SVC) is an 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 is an interrupt-driven request for system-level service. In an OS environment, use PendSV for context switching when no other exception is active. A SysTick exception is an exception the system timer generates when it reaches zero. Software can also generate a SysTick exception. In an OS environment, the processor can use this exception as system tick. A interrupt, or IRQ, is an exception signalled by a peripheral, or generated by a software request. All interrupts are asynchronous to instruction execution. In the system, peripherals use interrupts to communicate with the processor.
Table 2-16 Properties of the different exception types Exception number a 1 2 3 4 5 6 7-10 IRQ number a -14 -13 -12 -11 -10 Exception type Reset NMI HardFault MemManage BusFault UsageFault Reserved Priority -3, the highest -2 -1 Configurable c Configurable c Configurable c Vector address or offset b
0x00000004 0x00000008 0x0000000C 0x00000010 0x00000014
UsageFault
PendSV
SysTick
Interrupt (IRQ)
Activation Asynchronous Asynchronous Synchronous Synchronous when precise, asynchronous when imprecise Synchronous -
0x00000018
2-22
Table 2-16 Properties of the different exception types (continued) Exception number a 11 12-13 14 15 16 IRQ number a -5 -2 -1 0 Exception type SVCall Reserved PendSV SysTick Interrupt (IRQ) Priority Configurable c Configurable c Configurable c Configurable d Vector address or offset b
0x0000002C
Activation Synchronous Asynchronous Asynchronous Asynchronous
0x00000038 0x0000003C 0x00000040e
a. To simplify the software layer, the CMSIS only uses IRQ numbers and therefore uses negative values for exceptions other than interrupts. The IPSR returns the Exception number, see Interrupt Program Status Register on page 2-6. b. See Vector table for more information. c. See System Handler Priority Registers on page 4-21. d. See Interrupt Priority Registers on page 4-7. e. Increasing in steps of 4.
For an asynchronous exception, other than reset, the processor can execute another instruction between when the exception is triggered and when the processor enters the exception handler. Privileged software can disable the exceptions that Table 2-16 on page 2-22 shows as having configurable priority, see: System Handler Control and State Register on page 4-23 Interrupt Clear-enable Registers on page 4-5. For more information about HardFaults, MemManage faults, BusFaults, and UsageFaults, see Fault handling on page 2-28. 2.3.3 Exception handlers The processor handles exceptions using: Interrupt Service Routines (ISRs) The IRQ interrupts are the exceptions handled by ISRs. Fault handlers System handlers HardFault, MemManage fault, UsageFault, and BusFault are fault exceptions handled by the fault handlers. NMI, PendSV, SVCall SysTick, and the fault exceptions are all system exceptions that are handled by system handlers.
2.3.4
Vector table The vector table contains the reset value of the stack pointer, and the start addresses, also called exception vectors, for all exception handlers. Figure 2-2 on page 2-24 shows the order of the exception vectors in the vector table. The least-significant bit of each vector must be 1, indicating that the exception handler is Thumb code, see Thumb state on page 2-7.
2-23
Exception number IRQ number 16+n . . . 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 -10 -11 -12 -13 -14 -5 2 1 0 -1 -2 n
Offset
Vector IRQn . . . IRQ2 IRQ1 IRQ0 Systick PendSV Reserved Reserved for Debug
0x0040+4n . . . 0x004C 0x0048 0x0044 0x0040 0x003C 0x0038
0x002C
SVCall
Reserved
0x0018 0x0014 0x0010 0x000C 0x0008 0x0004 0x0000
Usage fault Bus fault Memory management fault Hard fault NMI Reset Initial SP value
Figure 2-2 Vector table
On system reset, the vector table is fixed at address 0x00000000. Privileged software can write to the VTOR to relocate the vector table start address to a different memory location, in the range 0x00000080 to 0x3FFFFF80, see Vector Table Offset Register on page 4-16. 2.3.5 Exception priorities Table 2-16 on page 2-22 shows that all exceptions have an associated priority, with: a lower priority value indicating a higher priority configurable priorities for all exceptions except Reset, HardFault, and NMI. If software does not configure any priorities, then all exceptions with a configurable priority have a priority of 0. For information about configuring exception priorities, see: System Handler Priority Registers on page 4-21 Interrupt Priority Registers on page 4-7. Note Configurable priority values are in the range 0-255. This means that the Reset, HardFault, and NMI exceptions, with fixed negative priority values, always have higher priority than any other exception.
2-24
For example, assigning a higher priority value to IRQ[0] and a lower priority value to IRQ[1] means that IRQ[1] has higher priority than IRQ[0]. If both IRQ[1] and IRQ[0] are asserted, IRQ[1] is processed before IRQ[0]. If multiple pending exceptions have the same priority, the pending exception with the lowest exception number takes precedence. For example, if both IRQ[0] and IRQ[1] are pending and have the same priority, then IRQ[0] is processed before IRQ[1]. When the processor is executing an exception handler, the exception handler is preempted if a higher priority exception occurs. If an exception occurs with the same priority as the exception being handled, the handler is not preempted, irrespective of the exception number. However, the status of the new interrupt changes to pending. 2.3.6 Interrupt priority grouping To increase priority control in systems with interrupts, the NVIC supports priority grouping. This divides each interrupt priority register entry into two fields: an upper field that defines the group priority a lower field that defines a subpriority within the group. Only the group priority determines preemption of interrupt exceptions. When the processor is executing an interrupt exception handler, another interrupt with the same group priority as the interrupt being handled does not preempt the handler, If multiple pending interrupts have the same group priority, the subpriority field determines the order in which they are processed. If multiple pending interrupts have the same group priority and subpriority, the interrupt with the lowest IRQ number is processed first. For information about splitting the interrupt priority fields into group priority and subpriority, see Application Interrupt and Reset Control Register on page 4-16. 2.3.7 Exception entry and return Descriptions of exception handling use the following terms: Preemption When the processor is executing an exception handler, an exception can preempt the exception handler if its priority is higher than the priority of the exception being handled. See Interrupt priority grouping for more information about preemption by an interrupt. When one exception preempts another, the exceptions are called nested exceptions. See Exception entry on page 2-26 more information. Return This occurs when the exception handler is completed, and: there is no pending exception with sufficient priority to be serviced the completed exception handler was not handling a late-arriving exception.
The processor pops the stack and restores the processor state to the state it had before the interrupt occurred. See Exception return on page 2-27 for more information. Tail-chaining This mechanism speeds up exception servicing. 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.
2-25
Late-arriving
This mechanism speeds up preemption. 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 is the same for both exceptions. Therefore the state saving continues uninterrupted. The processor can accept a late arriving exception until the first instruction of the exception handler of the original exception enters the execute stage of the processor. On return from the exception handler of the late-arriving exception, the normal tail-chaining rules apply.
Exception entry Exception entry occurs when there is a pending exception with sufficient priority and either: the processor is in Thread mode the new exception is of higher priority than the exception being handled, in which case the new exception preempts the exception being handled.
When one exception preempts another, the exceptions are nested. Sufficient priority means the exception has has greater priority than any limits set by the mask registers, see Exception mask registers on page 2-7. An exception with less priority than this is pending but is not handled by the processor. When the processor takes an exception, unless the exception is a tail-chained or a late-arriving exception, the processor pushes information onto the current stack. This operation is referred to as stacking and the structure of eight data words is referred as the stack frame. The stack frame contains the following information:
SP SP SP SP SP SP SP SP + + + + + + + + 0x1C 0x18 0x14 0x10 0x0C 0x08 0x04 0x00 <previous> xPSR PC LR R12 R3 R2 R1 R0 SP points here before interrupt
Decreasing memory address
SP points here after interrupt
Immediately after stacking, the stack pointer indicates the lowest address in the stack frame. The alignment of the stack frame is controlled via the STKALIGN bit of the Configuration Control Register (CCR). The stack frame includes the return address. This is the address of the next instruction in the interrupted program. This value is restored to the PC at exception return so that the interrupted program resumes. The processor performs a vector fetch that reads the exception handler start address from the vector table. When stacking is complete, the processor starts executing the exception handler. At the same time, the processor writes an EXC_RETURN value to the LR. This indicates which stack pointer corresponds to the stack frame and what operation mode the processor was in before the entry occurred. If no higher priority exception occurs during exception entry, the processor starts executing the exception handler and automatically changes the status of the corresponding pending interrupt to active.
2-26
If another higher priority exception occurs during exception entry, the processor starts executing the exception handler for this exception and does not change the pending status of the earlier exception. This is the late arrival case. Exception return Exception return occurs when the processor is in Handler mode and executes one of the following instructions attempts to set the PC to an EXC_RETURN value: an LDM or POP instruction that loads the PC an LDR instruction with PC as the destination a BX instruction using any register. The processor saves an EXC_RETURN value to the LR on exception entry. The exception mechanism relies on this value to detect when the processor has completed an exception handler. Bits[31:4] of an EXC_RETURN value are 0xFFFFFFF. When the processor loads a value matching this pattern to the PC it detects that the operation is a not a normal branch operation and, instead, that the exception is complete. Therefore, it starts the exception return sequence. Bits[3:0] of the EXC_RETURN value indicate the required return stack and processor mode, as Table 2-17 shows.
Table 2-17 Exception return behavior EXC_RETURN
0xFFFFFFF1
Description Return to Handler mode. Exception return gets state from the main stack. Execution uses MSP after return. Return to Thread mode. Exception Return get state from the main stack. Execution uses MSP after return. Return to Thread mode. Exception return gets state from the process stack. Execution uses PSP after return. Reserved.
0xFFFFFFF9
0xFFFFFFFD
All other values
2-27
2.4
Fault handling
Faults are a subset of the exceptions, see Exception model on page 2-21. Faults are generated by: a bus error on: an instruction fetch or vector table load a data access. an internally-detected error such as an Undefined instruction. attempting to execute an instruction from a memory region marked as Non-Executable (XN). attempting to execute an instruction while the EPSR T-bit is clear. For example, as the result of an erroneous BX instruction, or a vector fetch from a vector table entry with bit[0] clear. If your device contains an MPU, a privilege violation or an attempt to access an unmanaged region causing an MPU fault.
2.4.1
Fault types Table 2-18 shows the types of fault, the handler used for the fault, the corresponding fault status register, and the register bit that indicates that the fault has occurred. See Configurable Fault Status Register on page 4-24 for more information about the fault status registers.
Table 2-18 Faults
Fault Bus error on a vector read Fault escalated to a hard fault MPU or default memory map mismatch: on instruction access on data access during exception stacking during exception unstacking Bus error: during exception stacking during exception unstacking during instruction prefetch Precise data bus error Imprecise data bus error Attempt to access a coprocessor Undefined instruction Attempt to enter an invalid instruction set state b
Handler HardFault
Bit name VECTTBL FORCED
Fault status register HardFault Status Register on page 4-30
MemManage
IACCVIOL a DACCVIOL MSTKERR MUNSKERR
MemManage Fault Address Register on page 4-30
BusFault
STKERR UNSTKERR IBUSERR PRECISERR IMPRECISERR
BusFault Status Register on page 4-26
UsageFault
NOCP UNDEFINSTR INVSTATE
UsageFault Status Register on page 4-28
2-28
Table 2-18 Faults (continued) Fault Invalid EXC_RETURN value Illegal unaligned load or store Divide By 0 Handler UsageFault Bit name INVPC UNALIGNED DIVBYZERO Fault status register UsageFault Status Register on page 4-28
a. Occurs on an access to an XN region even if the processor does not include an MPU or if the MPU is disabled. b. Attempting to use an instruction set other than the Thumb instruction set or returns to a non load/store-multiple instruction with ICI continuation.
2.4.2
Fault escalation and hard faults All faults exceptions except for HardFault have configurable exception priority, see System Handler Priority Registers on page 4-21. Software can disable execution of the handlers for these faults, see System Handler Control and State Register on page 4-23. Usually, the exception priority, together with the values of the exception mask registers, determines whether the processor enters the fault handler, and whether a fault handler can preempt another fault handler. as described in Exception model on page 2-21. In some situations, a fault with configurable priority is treated as a HardFault. This is called priority escalation, and the fault is described as escalated to HardFault. Escalation to HardFault occurs when: A fault handler causes the same kind of fault as the one it is servicing. This escalation to HardFault occurs because a fault handler cannot preempt itself because it must have the same priority as the current priority level. A fault handler causes a fault with the same or lower priority as the fault it is servicing. This is because the handler for the new fault cannot preempt the currently executing fault handler. An exception handler causes a fault for which the priority is the same as or lower than the currently executing exception. A fault occurs and the handler for that fault is not enabled. If a BusFault occurs during a stack push when entering a BusFault handler, the BusFault does not escalate to a HardFault. This means that if a corrupted stack causes a fault, the fault handler executes even though the stack push for the handler failed. The fault handler operates but the stack contents are corrupted. Note Only Reset and NMI can preempt the fixed priority HardFault. A HardFault can preempt any exception other than Reset, NMI, or another HardFault.
2-29
2.4.3
Fault status registers and fault address registers The fault status registers indicate the cause of a fault. For BusFaults and MemManage faults, the fault address register indicates the address accessed by the operation that caused the fault, as shown in Table 2-19.
Table 2-19 Fault status and fault address registers Handler HardFault MemManage BusFault UsageFault Status register name HFSR MMFSR BFSR UFSR Address register name MMFAR BFAR Register description HardFault Status Register on page 4-30 MemManage Fault Status Register on page 4-25 MemManage Fault Address Register on page 4-30 BusFault Status Register on page 4-26 BusFault Address Register on page 4-31 UsageFault Status Register on page 4-28
2.4.4
Lockup The processor enters a lockup state if a fault occurs when executing the NMI or HardFault handlers. When the processor is in lockup state it does not execute any instructions. The processor remains in lockup state until either: it is reset an NMI occurs it is halted by a debugger. Note If lockup state occurs from the NMI handler a subsequent NMI does not cause the processor to leave lockup state.
2-30
2.5
Power management
The Cortex-M3 processor sleep modes reduce power consumption. The sleep modes your device implements are implementation-defined, but they might be one or all of the following: sleep mode stops the processor clock deep sleep mode stops the system clock and switches off the PLL and flash memory. If your device implements two sleep modes providing different levels of power saving, the SLEEPDEEP bit of the SCR selects which sleep mode is used, see System Control Register on page 4-19. For more information about the behavior of the sleep modes see the documentation supplied by your device vendor. This section describes the mechanisms for entering sleep mode, and the conditions for waking up from sleep mode.
2.5.1
Entering sleep mode This section describes the mechanisms software can use to put the processor into sleep mode. The system can generate spurious wakeup events, for example a debug operation wakes up the processor. Therefore software must be able to put the processor back into sleep mode after such an event. A program might have an idle loop to put the processor back to sleep mode. Wait For Interrupt The Wait For Interrupt instruction, WFI, causes immediate entry to sleep mode unless the wake-up condition is true, see Wakeup from WFI or sleep-on-exit on page 2-32. When the processor executes a WFI instruction it stops executing instructions and enters sleep mode. See WFI on page 3-80 for more information. Wait For Event The Wait For Event instruction, WFE, causes entry to sleep mode depending on the value of a one-bit event register. When the processor executes a WFE instruction, it checks the value of the event register: 0 1 The processor stops executing instructions and enters sleep mode. The processor clears the register to 0 and continues executing instructions without entering sleep mode.
See WFE on page 3-79 for more information. If the event register is 1, this indicates that the processor must not enter sleep mode on execution of a WFE instruction. Typically, this is because an external event signal is asserted, or a processor in the system has executed an SEV instruction, see SEV on page 3-77. Software cannot access this register directly. Sleep-on-exit If the SLEEPONEXIT bit of the SCR is set to 1, when the processor completes the execution of all exception handlers it returns to Thread mode and immediately enters sleep mode. Use this mechanism in applications that only require the processor to run when an exception occurs.
2-31
2.5.2
Wakeup from sleep mode The conditions for the processor to wakeup depend on the mechanism that cause it to enter sleep mode. Wakeup from WFI or sleep-on-exit Normally, the processor wakes up only when it detects an exception with sufficient priority to cause exception entry. Some embedded systems might have to execute system restore tasks after the processor wakes up, and before it executes an interrupt handler. To achieve this set the PRIMASK bit to 1 and the FAULTMASK bit to 0. If an interrupt arrives that is enabled and has a higher priority than current exception priority, the processor wakes up but does not execute the interrupt handler until the processor sets PRIMASK to zero. For more information about PRIMASK and FAULTMASK see Exception mask registers on page 2-7. Wakeup from WFE The processor wakes up if: it detects an exception with sufficient priority to cause exception entry it detects an external event signal, see The external event input in a multiprocessor system, another processor in the system executes an SEV instruction. In addition, if the SEVONPEND bit in the SCR is set to 1, any new pending interrupt triggers an event and wakes up the processor, even if the interrupt is disabled or has insufficient priority to cause exception entry. For more information about the SCR see System Control Register on page 4-19.
2.5.3
The optional Wakeup Interrupt Controller Your device might include a Wakeup Interrupt Controller (WIC), an optional peripheral that can detect an interrupt and wake the processor from deep sleep mode. The WIC is enabled only when the DEEPSLEEP bit in the SCR is set to 1, see System Control Register on page 4-19. The WIC is not programmable, and does not have any registers or user interface. It operates entirely from hardware signals. When the WIC is enabled and the processor enters deep sleep mode, the power management unit in the system can power down most of the Cortex-M3 processor. This has the side effect of stopping the SysTick timer. When the WIC receives an interrupt, it takes a number of clock cycles to wakeup the processor and restore its state, before it can process the interrupt. This means interrupt latency is increased in deep sleep mode. Note If the processor detects a connection to a debugger it disables the WIC.
2.5.4
The external event input Your device might include an external event input signal, so that device peripherals can signal the processor, to either: wake the processor from WFE set the internal WFE event register to one to indicate that the processor must not enter sleep mode on a later WFE instruction.
2-32
See Wait For Event on page 2-31 and the documentation supplied by your device vendor for more information about this signal. 2.5.5 Power management programming hints ISO/IEC C cannot directly generate the WFI and WFE instructions. The CMSIS provides the following functions for these instructions:
void __WFE(void) // Wait For Event void __WFI(void) // Wait For Interrupt
2-33
Chapter 3 The Cortex-M3 Instruction Set
This chapter is the reference material for the Cortex-M3 instruction set description in a User Guide. The following sections give general information: Instruction set summary on page 3-2 CMSIS functions on page 3-6 About the instruction descriptions on page 3-8. Each of the following sections describes a functional group of Cortex-M3 instructions. Together they describe all the instructions supported by the Cortex-M3 processor: Memory access instructions on page 3-17 General data processing instructions on page 3-34 Multiply and divide instructions on page 3-49 Saturating instructions on page 3-54 Bitfield instructions on page 3-56 Branch and control instructions on page 3-60 Miscellaneous instructions on page 3-68.
3-1
3.1
Instruction set summary

The processor implements a version of the Thumb instruction set. Table 3-1 lists the supported instructions. Note In Table 3-1: angle brackets, <>, enclose alternative forms of the operand braces, {}, enclose optional operands the Operands column is not exhaustive Op2 is a flexible second operand that can be either a register or a constant most instructions can use an optional condition code suffix. For more information on the instructions and operands, see the instruction descriptions.
Table 3-1 Cortex-M3 instructions Mnemonic

ADC, ADCS ADD, ADDS ADD, ADDW ADR AND, ANDS ASR, ASRS B BFC BFI BIC, BICS BKPT BL BLX BX CBNZ CBZ CLREX CLZ CMN CMP CPSID
Operands
{Rd,} Rn, Op2 {Rd,} Rn, Op2 {Rd,} Rn, #imm12 Rd, label {Rd,} Rn, Op2 Rd, Rm, <Rs|#n> label Rd, #lsb, #width Rd, Rn, #lsb, #width {Rd,} Rn, Op2 #imm label Rm Rm Rn, label Rn, label
Brief description Add with Carry Add Add Load PC-relative Address Logical AND Arithmetic Shift Right Branch Bit Field Clear Bit Field Insert Bit Clear Breakpoint Branch with Link Branch indirect with Link Branch indirect Compare and Branch if Non Zero Compare and Branch if Zero Clear Exclusive Count Leading Zeros Compare Negative Compare Change Processor State, Disable Interrupts
Flags N,Z,C,V N,Z,C,V N,Z,C,V N,Z,C N,Z,C N,Z,C N,Z,C,V N,Z,C,V -
See page 3-35 page 3-35 page 3-35 page 3-18 page 3-38 page 3-40 page 3-61 page 3-57 page 3-57 page 3-38 page 3-69 page 3-61 page 3-61 page 3-61 page 3-63 page 3-63 page 3-33 page 3-42 page 3-43 page 3-43 page 3-70
Rd, Rm Rn, Op2 Rn, Op2 i
3-2
Table 3-1 Cortex-M3 instructions (continued) Mnemonic

CPSIE DMB DSB EOR, EORS ISB IT LDM LDMDB, LDMEA LDMFD, LDMIA LDR LDRB, LDRBT LDRD LDREX LDREXB LDREXH LDRH, LDRHT LDRSB, LDRSBT LDRSH, LDRSHT LDRT LSL, LSLS LSR, LSRS MLA MLS MOV, MOVS MOVT MOVW, MOV MRS MSR MUL, MULS MVN, MVNS NOP ORN, ORNS ORR, ORRS
Operands
i {Rd,} Rn, Op2 -
Brief description Change Processor State, Enable Interrupts Data Memory Barrier Data Synchronization Barrier Exclusive OR Instruction Synchronization Barrier If-Then condition block Load Multiple registers, increment after Load Multiple registers, decrement before Load Multiple registers, increment after Load Register with word Load Register with byte Load Register with two bytes Load Register Exclusive Load Register Exclusive with Byte Load Register Exclusive with Halfword Load Register with Halfword Load Register with Signed Byte Load Register with Signed Halfword Load Register with word Logical Shift Left Logical Shift Right Multiply with Accumulate, 32-bit result Multiply and Subtract, 32-bit result Move Move Top Move 16-bit constant Move from Special Register to general register Move from general register to Special Register Multiply, 32-bit result Move NOT No Operation Logical OR NOT Logical OR
Flags N,Z,C N,Z,C N,Z,C N,Z,C N,Z,C N,Z,C,V N,Z N,Z,C N,Z,C N,Z,C
See page 3-70 page 3-71 page 3-72 page 3-38 page 3-73 page 3-64 page 3-27 page 3-27 page 3-27 page 3-17 page 3-17 page 3-19 page 3-31 page 3-31 page 3-31 page 3-17 page 3-17 page 3-17 page 3-17 page 3-40 page 3-40 page 3-50 page 3-50 page 3-44 page 3-46 page 3-44 page 3-74 page 3-75 page 3-50 page 3-44 page 3-76 page 3-38 page 3-38
Rn{!}, reglist Rn{!}, reglist Rn{!}, reglist Rt, [Rn, #offset] Rt, [Rn, #offset] Rt, Rt2, [Rn, #offset] Rt, [Rn, #offset] Rt, [Rn] Rt, [Rn] Rt, [Rn, #offset] Rt, [Rn, #offset] Rt, [Rn, #offset] Rt, [Rn, #offset] Rd, Rm, <Rs|#n> Rd, Rm, <Rs|#n> Rd, Rn, Rm, Ra Rd, Rn, Rm, Ra Rd, Op2 Rd, #imm16 Rd, #imm16 Rd, spec_reg spec_reg, Rm {Rd,} Rn, Rm Rd, Op2
{Rd,} Rn, Op2 {Rd,} Rn, Op2
3-3

POP PUSH RBIT REV REV16 REVSH
Operands
reglist reglist Rd, Rn Rd, Rn Rd, Rn Rd, Rn
Brief description Pop registers from stack Push registers onto stack Reverse Bits Reverse byte order in a word Reverse byte order in each halfword Reverse byte order in bottom halfword and sign extend Rotate Right Rotate Right with Extend Reverse Subtract Subtract with Carry Signed Bit Field Extract Signed Divide Send Event Signed Multiply with Accumulate (32 x 32 + 64), 64-bit result Signed Multiply (32 x 32), 64-bit result Signed Saturate Store Multiple registers, increment after Store Multiple registers, decrement before Store Multiple registers, increment after Store Register word Store Register byte Store Register two words Store Register Exclusive Store Register Exclusive Byte Store Register Exclusive Halfword Store Register Halfword Store Register word Subtract Subtract Supervisor Call Sign extend a byte
Flags N,Z,C N,Z,C N,Z,C,V N,Z,C,V Q N,Z,C,V N,Z,C,V -
See page 3-29 page 3-29 page 3-47 page 3-47 page 3-47 page 3-47 page 3-40 page 3-40 page 3-35 page 3-35 page 3-58 page 3-53 page 3-77 page 3-52 page 3-52 page 3-54 page 3-27 page 3-27 page 3-27 page 3-17 page 3-17 page 3-19 page 3-31 page 3-31 page 3-31 page 3-17 page 3-17 page 3-35 page 3-35 page 3-78 page 3-59
ROR, RORS RRX, RRXS RSB, RSBS SBC, SBCS SBFX SDIV SEV SMLAL
Rd, Rm, <Rs|#n> Rd, Rm {Rd,} Rn, Op2 {Rd,} Rn, Op2 Rd, Rn, #lsb, #width {Rd,} Rn, Rm
RdLo, RdHi, Rn, Rm
SMULL SSAT STM STMDB, STMEA STMFD, STMIA STR STRB, STRBT STRD STREX STREXB STREXH STRH, STRHT STRT SUB, SUBS SUB, SUBW SVC SXTB
RdLo, RdHi, Rn, Rm Rd, #n, Rm {,shift #s} Rn{!}, reglist Rn{!}, reglist Rn{!}, reglist Rt, [Rn, #offset] Rt, [Rn, #offset] Rt, Rt2, [Rn, #offset] Rd, Rt, [Rn, #offset] Rd, Rt, [Rn] Rd, Rt, [Rn] Rt, [Rn, #offset] Rt, [Rn, #offset] {Rd,} Rn, Op2 {Rd,} Rn, #imm12 #imm {Rd,} Rm {,ROR #n}
3-4

SXTH TBB TBH TEQ TST UBFX UDIV UMLAL
Operands
{Rd,} Rm {,ROR #n} [Rn, Rm] [Rn, Rm, LSL #1] Rn, Op2 Rn, Op2 Rd, Rn, #lsb, #width {Rd,} Rn, Rm RdLo, RdHi, Rn, Rm
Brief description Sign extend a halfword Table Branch Byte Table Branch Halfword Test Equivalence Test Unsigned Bit Field Extract Unsigned Divide Unsigned Multiply with Accumulate (32 x 32 + 64), 64-bit result Unsigned Multiply (32 x 32), 64-bit result Unsigned Saturate Zero extend a Byte Zero extend a Halfword Wait For Event Wait For Interrupt
Flags N,Z,C N,Z,C Q -
See page 3-59 page 3-66 page 3-66 page 3-48 page 3-48 page 3-58 page 3-53 page 3-52 page 3-52 page 3-54 page 3-59 page 3-59 page 3-79 page 3-80
UMULL USAT UXTB UXTH WFE WFI
RdLo, RdHi, Rn, Rm Rd, #n, Rm {,shift #s} {Rd,} Rm {,ROR #n} {Rd,} Rm {,ROR #n}
3-5
3.2
CMSIS functions
ISO/IEC C code cannot directly access some Cortex-M3 instructions. This section describes intrinsic functions that can generate these instructions, provided by the CMSIS and that might be provided by a C compiler. If a C compiler does not support an appropriate intrinsic function, you might have to use inline assembler to access some instructions. The CMSIS provides the following intrinsic functions to generate instructions that ISO/IEC C code cannot directly access:
Table 3-2 CMSIS functions to generate some Cortex-M3 instructions Instruction
CPSIE I CPSID I CPSIE F CPSID F ISB DSB DMB REV REV16 REVSH RBIT SEV WFE WFI
CMSIS function
void __enable_irq(void) void __disable_irq(void) void __enable_fault_irq(void) void __disable_fault_irq(void) void __ISB(void) void __DSB(void) void __DMB(void) uint32_t __REV(uint32_t int value) uint32_t __REV16(uint32_t int value) uint32_t __REVSH(uint32_t int value) uint32_t __RBIT(uint32_t int value) void __SEV(void) void __WFE(void) void __WFI(void)
The CMSIS also provides a number of functions for accessing the special registers using MRS and MSR instructions:
Table 3-3 CMSIS functions to access the special registers Special register PRIMASK Access Read Write FAULTMASK Read Write BASEPRI Read Write CONTROL Read Write CMSIS function
uint32_t __get_PRIMASK (void) void __set_PRIMASK (uint32_t value) uint32_t __get_FAULTMASK (void) void __set_FAULTMASK (uint32_t value) uint32_t __get_BASEPRI (void) void __set_BASEPRI (uint32_t value) uint32_t __get_CONTROL (void) void __set_CONTROL (uint32_t value)
3-6
Table 3-3 CMSIS functions to access the special registers (continued) Special register MSP Access Read Write PSP Read Write CMSIS function
uint32_t __get_MSP (void) void __set_MSP (uint32_t TopOfMainStack) uint32_t __get_PSP (void) void __set_PSP (uint32_t TopOfProcStack)
3-7
3.3
About the instruction descriptions

The following sections give more information about using the instructions: Operands on page 3-9 Restrictions when using PC or SP on page 3-9 Flexible second operand on page 3-9 Shift Operations on page 3-10 Address alignment on page 3-13 PC-relative expressions on page 3-13 Conditional execution on page 3-14 Instruction width selection on page 3-16.
3-8
3.3.1
Operands An instruction operand can be an ARM register, a constant, or another instruction-specific parameter. Instructions act on the operands and often store the result in a destination register. When there is a destination register in the instruction, it is usually specified before the operands. Operands in some instructions are flexible in that they can either be a register or a constant. See Flexible second operand.
3.3.2
Restrictions when using PC or SP Many instructions have restrictions on whether you can use the Program Counter (PC) or Stack Pointer (SP) for the operands or destination register. See instruction descriptions for more information. Note Bit[0] of any address you write to the PC with a BX, BLX, LDM, LDR, or POP instruction must be 1 for correct execution, because this bit indicates the required instruction set, and the Cortex-M3 processor only supports Thumb instructions.
3.3.3
Flexible second operand Many general data processing instructions have a flexible second operand. This is shown as Operand2 in the descriptions of the syntax of each instruction.
Operand2 can be a:
Constant Register with optional shift on page 3-10.
Constant You specify an Operand2 constant in the form:

#constant
where constant can be: any constant that can be produced by shifting an 8-bit value left by any number of bits within a 32-bit word any constant of the form 0x00XY00XY any constant of the form 0xXY00XY00 any constant of the form 0xXYXYXYXY.
Note In the constants shown above, X and Y are hexadecimal digits. In addition, in a small number of instructions, constant can take a wider range of values. These are described in the individual instruction descriptions. When an Operand2 constant is used with the instructions MOVS, MVNS, ANDS, ORRS, ORNS, EORS, BICS, TEQ or TST, the carry flag is updated to bit[31] of the constant, if the constant is greater than 255 and can be produced by shifting an 8-bit value. These instructions do not affect the carry flag if Operand2 is any other constant.
3-9
Instruction substitution
Your assembler might be able to produce an equivalent instruction in cases where you specify a constant that is not permitted. For example, an assembler might assemble the instruction CMP Rd, #0xFFFFFFFE as the equivalent instruction CMN Rd, #0x2. Register with optional shift You specify an Operand2 register in the form:
Rm {, shift}
where:
Rm shift
Specifies the register holding the data for the second operand. Is an optional shift to be applied to Rm. It can be one of:
ASR #n LSL #n LSR #n ROR #n RRX
Arithmetic shift right n bits, 1 n 32. Logical shift left n bits, 1 n 31. Logical shift right n bits, 1 n 32. Rotate right n bits, 1 n 31. Rotate right one bit, with extend. If omitted, no shift occurs, equivalent to LSL #0.
If you omit the shift, or specify LSL #0, the instruction uses the value in Rm. If you specify a shift, the shift is applied to the value in Rm, and the resulting 32-bit value is used by the instruction. However, the contents in the register Rm remains unchanged. Specifying a register with shift also updates the carry flag when used with certain instructions. For Is an optional condition the carry flag, see Shift Operations. 3.3.4 Shift Operations Register shift operations move the bits in a register left or right by a specified number of bits, the shift length. Register shift can be performed: directly by the instructions ASR, LSR, LSL, ROR, and RRX, and the result is written to a destination register during the calculation of Operand2 by the instructions that specify the second operand as a register with shift, see Flexible second operand on page 3-9. The result is used by the instruction.
The permitted shift lengths depend on the shift type and the instruction, see the individual instruction description or Flexible second operand on page 3-9. If the shift length is 0, no shift occurs. Register shift operations update the carry flag except when the specified shift length is 0. The following sub-sections describe the various shift operations and how they affect the carry flag. In these descriptions, Rm is the register containing the value to be shifted, and n is the shift length. ASR Arithmetic shift right by n bits moves the left-hand 32-n bits of the register Rm, to the right by n places, into the right-hand 32-n bits of the result. It also copies the original bit[31] of the register into the left-hand n bits of the result. See Figure 3-1 on page 3-11.
3-10
You can use the ASR #n operation to divide the value in the register Rm by 2n, with the result being rounded towards negative-infinity. When the instruction is ASRS or when ASR #n is used in Operand2 with the instructions MOVS, MVNS, ANDS, ORRS, ORNS, EORS, BICS, TEQ or TST, the carry flag is updated to the last bit shifted out, bit[n-1], of the register Rm. Note If n is 32 or more, then all the bits in the result are set to the value of bit[31] of Rm. If n is 32 or more and the carry flag is updated, it is updated to the value of bit[31] of Rm.
Carry Flag 31 5 4 3 2 1 0
Figure 3-1 ASR #3
LSR Logical shift right by n bits moves the left-hand 32-n bits of the register Rm, to the right by n places, into the right-hand 32-n bits of the result. It also sets the left-hand n bits of the result to 0. See Figure 3-2. You can use the LSR #n operation to divide the value in the register Rm by 2n, if the value is regarded as an unsigned integer. When the instruction is LSRS or when LSR #n is used in Operand2 with the instructions MOVS, MVNS, ANDS, ORRS, ORNS, EORS, BICS, TEQ or TST, the carry flag is updated to the last bit shifted out, bit[n-1], of the register Rm. Note If n is 32 or more, then all the bits in the result are cleared to 0. If n is 33 or more and the carry flag is updated, it is updated to 0.
0 0 0
31 5 4 3 2 1 0
Carry Flag
Figure 3-2 LSR #3
LSL Logical shift left by n bits moves the right-hand 32-n bits of the register Rm, to the left by n places, into the left-hand 32-n bits of the result. And it sets the right-hand n bits of the result to 0. See Figure 3-3 on page 3-12.
ARM DUI 0552A ID121610 Copyright 2010 ARM. All rights reserved. Non-Confidential 3-11
You can use he LSL #n operation to multiply the value in the register Rm by 2n, if the value is regarded as an unsigned integer or a twos complement signed integer. Overflow can occur without warning. When the instruction is LSLS or when LSL #n, with non-zero n, is used in Operand2 with the instructions MOVS, MVNS, ANDS, ORRS, ORNS, EORS, BICS, TEQ or TST, the carry flag is updated to the last bit shifted out, bit[32-n], of the register Rm. These instructions do not affect the carry flag when used with LSL #0. Note If n is 32 or more, then all the bits in the result are cleared to 0. If n is 33 or more and the carry flag is updated, it is updated to 0.
0 0 0
31 Carry Flag 5 4 3 2 1 0
Figure 3-3 LSL #3
ROR Rotate right by n bits moves the left-hand 32-n bits of the register Rm, to the right by n places, into the right-hand 32-n bits of the result. And it moves the right-hand n bits of the register into the left-hand n bits of the result. See Figure 3-4. When the instruction is RORS or when ROR #n is used in Operand2 with the instructions MOVS, MVNS, ANDS, ORRS, ORNS, EORS, BICS, TEQ or TST, the carry flag is updated to the last bit rotation, bit[n-1], of the register Rm. Note If n is 32, then the value of the result is same as the value in Rm, and if the carry flag is updated, it is updated to bit[31] of Rm.
ROR with shift length, n, more than 32 is the same as ROR with shift length n-32.
Carry Flag 31 5 4 3 2 1 0
Figure 3-4 ROR #3
RRX Rotate right with extend moves the bits of the register Rm to the right by one bit. And it copies the carry flag into bit[31] of the result. See Figure 3-5 on page 3-13.
3-12
When the instruction is RRXS or when RRX is used in Operand2 with the instructions MOVS, MVNS, ANDS, ORRS, ORNS, EORS, BICS, TEQ or TST, the carry flag is updated to bit[0] of the register Rm.
Carry Flag 31 30 ... 1 0
Figure 3-5 RRX
3.3.5
Address alignment An aligned access is an operation where a word-aligned address is used for a word, dual word, or multiple word access, or where a halfword-aligned address is used for a halfword access. Byte accesses are always aligned. The Cortex-M3 processor supports unaligned access only for the following instructions: LDR, LDRT LDRH, LDRHT LDRSH, LDRSHT STR, STRT STRH, STRHT. All other load and store instructions generate a UsageFault exception if they perform an unaligned access, and therefore their accesses must be address aligned. For more information about UsageFaults see Fault handling on page 2-28. Unaligned accesses are usually slower than aligned accesses. In addition, some memory regions might not support unaligned accesses. Therefore, ARM recommends that programmers ensure that accesses are aligned. To trap accidental generation of unaligned accesses, use the UNALIGN_TRP bit in the Configuration and Control Register, see Configuration and Control Register on page 4-19.
3.3.6
PC-relative expressions A PC-relative expression or label is a symbol that represents the address of an instruction or literal data. It is represented in the instruction as the PC value plus or minus a numeric offset. The assembler calculates the required offset from the label and the address of the current instruction. If the offset is too big, the assembler produces an error. Note For B, BL, CBNZ, and CBZ instructions, the value of the PC is the address of the current instruction plus 4 bytes. For most other instructions that use labels, the value of the PC is the address of the current instruction plus 4 bytes, with bit[1] of the result cleared to 0 to make it word-aligned. Your assembler might permit other syntaxes for PC-relative expressions, such as a label plus or minus a number, or an expression of the form [PC, #number].
3-13
3.3.7
Conditional execution Most data processing instructions can optionally update the condition flags in the Application Program Status Register (APSR) according to the result of the operation, see Application Program Status Register on page 2-5. Some instructions update all flags, and some only update a subset. If a flag is not updated, the original value is preserved. See the instruction descriptions for the flags they affect. You can execute an instruction conditionally, based on the condition flags set in another instruction, either: immediately after the instruction that updated the flags after any number of intervening instructions that have not updated the flags. Conditional execution is available by using conditional branches or by adding condition code suffixes to instructions. See Table 3-4 on page 3-15 for a list of the suffixes to add to instructions to make them conditional instructions. The condition code suffix enables the processor to test a condition based on the flags. If the condition test of a conditional instruction fails, the instruction: does not execute does not write any value to its destination register does not affect any of the flags does not generate any exception. Conditional instructions, except for conditional branches, must be inside an If-Then instruction block. See IT on page 3-64 for more information and restrictions when using the IT instruction. Depending on the vendor, the assembler might automatically insert an IT instruction if you have conditional instructions outside the IT block. Use the CBZ and CBNZ instructions to compare the value of a register against zero and branch on the result. This section describes: The condition flags Condition code suffixes on page 3-15. The condition flags The APSR contains the following condition flags: N Z C V Set to 1 when the result of the operation was negative, cleared to 0 otherwise. Set to 1 when the result of the operation was zero, cleared to 0 otherwise. Set to 1 when the operation resulted in a carry, cleared to 0 otherwise. Set to 1 when the operation caused overflow, cleared to 0 otherwise.
For more information about the APSR see Program Status Register on page 2-4. A carry occurs: if the result of an addition is greater than or equal to 232 if the result of a subtraction is positive or zero as the result of an inline barrel shifter operation in a move or logical instruction. Overflow occurs when the sign of the result, in bit[31], does not match the sign of the result had the operation been performed at infinite precision, for example: if adding two negative values results in a positive value
3-14
if adding two positive values results in a negative value if subtracting a positive value from a negative value generates a positive value if subtracting a negative value from a positive value generates a negative value.
The Compare operations are identical to subtracting, for CMP, or adding, for CMN, except that the result is discarded. See the instruction descriptions for more information. Note Most instructions update the status flags only if the S suffix is specified. See the instruction descriptions for more information.
Condition code suffixes The instructions that can be conditional have an optional condition code, shown in syntax descriptions as {cond}. Conditional execution requires a preceding IT instruction. An instruction with a condition code is only executed if the condition code flags in the APSR meet the specified condition. Table 3-4 shows the condition codes to use. You can use conditional execution with the IT instruction to reduce the number of branch instructions in code. Table 3-4 also shows the relationship between condition code suffixes and the N, Z, C, and V flags.
Table 3-4 Condition code suffixes Suffix
EQ NE CS or HS CC or LO MI PL VS VC HI LS GE LT GT LE AL
Flags Z=1 Z=0 C=1 C=0 N=1 N=0 V=1 V=0 C = 1 and Z = 0 C = 0 or Z = 1 N=V N != V Z = 0 and N = V Z = 1 and N != V Can have any value
Meaning Equal Not equal Higher or same, unsigned Lower, unsigned Negative Positive or zero Overflow No overflow Higher, unsigned Lower or same, unsigned Greater than or equal, signed Less than, signed Greater than, signed Less than or equal, signed Always. This is the default when no suffix is specified.
Example 3-1 on page 3-16 shows the use of a conditional instruction to find the absolute value of a number. R0 = abs(R1).
3-15
Example 3-1 Absolute value
MOVS IT RSBMI
R0, R1 MI R0, R0, #0
; R0 = R1, setting flags ; skipping next instruction if value 0 or positive ; If negative, R0 = -R0
Example 3-2 shows the use of conditional instructions to update the value of R4 if the signed values R0 is greater than R1 and R2 is greater than R3.
Example 3-2 Compare and update value
CMP ITT CMPGT MOVGT
R0, R1 GT R2, R3 R4, R5
; ; ; ;
Compare R0 and R1, setting flags Skip next two instructions unless GT condition holds If 'greater than', compare R2 and R3, setting flags If still 'greater than', do R4 = R5
3.3.8
Instruction width selection There are many instructions that can generate either a 16-bit encoding or a 32-bit encoding depending on the operands and destination register specified. For some of these instructions, you can force a specific instruction size by using an instruction width suffix. The .W suffix forces a 32-bit instruction encoding. The .N suffix forces a 16-bit instruction encoding. If you specify an instruction width suffix and the assembler cannot generate an instruction encoding of the requested width, it generates an error. Note In some cases it might be necessary to specify the .W suffix, for example if the operand is the label of an instruction or literal data, as in the case of branch instructions. This is because the assembler might not automatically generate the right size encoding. To use an instruction width suffix, place it immediately after the instruction mnemonic and condition code, if any. Example 3-3 shows instructions with the instruction width suffix.
Example 3-3 Instruction width selection
BCS.W
label
; creates a 32-bit instruction even for a short branch
ADDS.W R0, R0, R1 ; creates a 32-bit instruction even though the same ; operation can be done by a 16-bit instruction
3-16
3.4
Memory access instructions

Table 3-5 shows the memory access instructions.
Table 3-5 Memory access instructions Mnemonic
ADR CLREX LDM{mode} LDR{type} LDR{type} LDR{type}T LDR LDREX{type} POP PUSH STM{mode} STR{type} STR{type} STR{type}T STREX{type}
Brief description Generate PC-relative address Clear Exclusive Load Multiple registers Load Register using immediate offset Load Register using register offset Load Register with unprivileged access Load Register using PC-relative address Load Register Exclusive Pop registers from stack Push registers onto stack Store Multiple registers Store Register using immediate offset Store Register using register offset Store Register with unprivileged access Store Register Exclusive
See ADR on page 3-18 CLREX on page 3-33 LDM and STM on page 3-27 LDR and STR, immediate offset on page 3-19 LDR and STR, register offset on page 3-22 LDR and STR, unprivileged on page 3-24 LDR, PC-relative on page 3-25 LDREX and STREX on page 3-31 PUSH and POP on page 3-29 PUSH and POP on page 3-29 LDM and STM on page 3-27 LDR and STR, immediate offset on page 3-19 LDR and STR, register offset on page 3-22 LDR and STR, unprivileged on page 3-24 LDREX and STREX on page 3-31
3-17
3.4.1
ADR Generate PC-relative address. Syntax

ADR{cond} Rd, label
where:
cond Rd label
Is an condition code, see Conditional execution on page 3-14. Specifies the destination register. is a PC-relative expression. See PC-relative expressions on page 3-13.
Operation
ADR generates an address by adding an immediate value to the PC, and writes the result to the
destination register.
ADR provides the means by which position-independent code can be generated, because the
address is PC-relative. If you use ADR to generate a target address for a BX or BLX instruction, you must ensure that bit[0] of the address you generate is set to 1 for correct execution. Values of label must be within the range of 4095 to +4095 from the address in the PC. Note You might have to use the .W suffix to get the maximum offset range or to generate addresses that are not word-aligned. See Instruction width selection on page 3-16.
Restrictions
Rd must not be SP and must not be PC.
Condition flags This instruction does not change the flags. Examples
ADR R1, TextMessage ; Write address value of a location labelled as ; TextMessage to R1
3-18
3.4.2
LDR and STR, immediate offset Load and Store with immediate offset, pre-indexed immediate offset, or post-indexed immediate offset. Syntax
op{type}{cond} Rt, [Rn {, #offset}] op{type}{cond} Rt, [Rn, #offset]! op{type}{cond} Rt, [Rn], #offset opD{cond} Rt, Rt2, [Rn {, #offset}] opD{cond} Rt, Rt2, [Rn, #offset]! opD{cond} Rt, Rt2, [Rn], #offset ; immediate offset ; pre-indexed ; post-indexed ; immediate offset, two words ; pre-indexed, two words ; post-indexed, two words
where:
op
Is one of:
LDR STR
Load Register. Store Register. unsigned byte, zero extend to 32 bits on loads. signed byte, sign extend to 32 bits (LDR only). unsigned halfword, zero extend to 32 bits on loads. signed halfword, sign extend to 32 bits (LDR only). omit, for word.
type
Is one of:
B SB H SH -
cond Rt Rn offset Rt2
Is an optional condition code, see Conditional execution on page 3-14. Specifies the register to load or store. Specifies the register on which the memory address is based. Specifies an offset from Rn. If offset is omitted, the address is the contents of Rn. Specifies the additional register to load or store for two-word operations.
3-19
Operation
LDR instructions load one or two registers with a value from memory. STR instructions store one or two register values to memory.
Load and store instructions with immediate offset can use the following addressing modes: Offset addressing The offset value is added to or subtracted from the address obtained from the register Rn. The result is used as the address for the memory access. The register Rn is unaltered. The assembly language syntax for this mode is:
[Rn, #offset]
Pre-indexed addressing The offset value is added to or subtracted from the address obtained from the register Rn. The result is used as the address for the memory access and written back into the register Rn. The assembly language syntax for this mode is:
[Rn, #offset]!
Post-indexed addressing The address obtained from the register Rn is used as the address for the memory access. The offset value is added to or subtracted from the address, and written back into the register Rn. The assembly language syntax for this mode is:
[Rn], #offset
The value to load or store can be a byte, halfword, word, or two words. Bytes and halfwords can either be signed or unsigned. See Address alignment on page 3-13. Table 3-6 shows the ranges of offset for immediate, pre-indexed and post-indexed forms.
Table 3-6 Offset ranges Instruction type Word, halfword, signed halfword, byte, or signed byte Two words Immediate offset 255 to 4095 multiple of 4 in the range 1020 to 1020 Pre-indexed 255 to 255 multiple of 4 in the range 1020 to 1020 Post-indexed 255 to 255 multiple of 4 in the range 1020 to 1020
3-20
Restrictions For load instructions: Rt can be SP or PC for word loads only Rt must be different from Rt2 for two-word loads Rn must be different from Rt and Rt2 in the pre-indexed or post-indexed forms. When Rt is PC in a word load instruction: bit[0] of the loaded value must be 1 for correct execution a branch occurs to the address created by changing bit[0] of the loaded value to 0 if the instruction is conditional, it must be the last instruction in the IT block. For store instructions: Rt can be SP for word stores only Rt must not be PC Rn must not be PC Rn must be different from Rt and Rt2 in the pre-indexed or post-indexed forms. Condition flags These instructions do not change the flags. Examples
LDR LDRNE R8, [R10] R2, [R5, #960]! ; ; ; ; ; ; ; ; ; ; ; ; ; ; Loads R8 from the address in R10. Loads (conditionally) R2 from a word 960 bytes above the address in R5, and increments R5 by 960 const-struc is an expression evaluating to a constant in the range 0-4095. Store R3 as halfword data into address in R4, then increment R4 by 4 Load R8 from a word 8 bytes above the address in R3, and load R9 from a word 9 bytes above the address in R3 Store R0 to address in R8, and store R1 to a word 4 bytes above the address in R8, and then decrement R8 by 16.
STR STRH LDRD
R2, [R9,#const-struc] R3, [R4], #4 R8, R9, [R3, #0x20]
STRD
R0, R1, [R8], #-16
3-21
3.4.3
LDR and STR, register offset Load and Store with register offset. Syntax
op{type}{cond} Rt, [Rn, Rm {, LSL #n}]
where:
op
Is one of:
LDR STR
type
Is one of:
B SB H SH -
cond Rt Rn Rm LSL #n
Is an optional condition code, see Conditional execution on page 3-14. Specifies the register to load or store. Specifies the register on which the memory address is based. Specifies the register containing a value to be used as the offset. Is an optional shift, with n in the range 0 to 3.
Operation
LDR instructions load a register with a value from memory. STR instructions store a register value into memory.
The memory address to load from or store to is at an offset from the register Rn. The offset is specified by the register Rm and can be shifted left by up to 3 bits using LSL. The value to load or store can be a byte, halfword, or word. For load instructions, bytes and halfwords can either be signed or unsigned. See Address alignment on page 3-13. Restrictions In these instructions: Rn must not be PC Rm must not be SP and must not be PC Rt can be SP only for word loads and word stores Rt can be PC only for word loads. When Rt is PC in a word load instruction: bit[0] of the loaded value must be 1 for correct execution, and a branch occurs to this halfword-aligned address if the instruction is conditional, it must be the last instruction in the IT block.
3-22
Condition flags These instructions do not change the flags. Examples

STR LDRSB R0, [R5, R1] ; ; R0, [R5, R1, LSL #1] ; ; ; R0, [R1, R2, LSL #2] ; ; Store value of R0 into an address equal to sum of R5 and R1 Read byte value from an address equal to sum of R5 and two times R1, sign extended it to a word value and put it in R0 Stores R0 to an address equal to sum of R1 and four times R2.
STR
3-23
3.4.4
LDR and STR, unprivileged Load and Store with unprivileged access. Syntax
op{type}T{cond} Rt, [Rn {, #offset}] ; immediate offset
where:
op
Is one of:
LDR STR
type
Is one of:
B SB H SH -
cond Rt Rn offset
Is an optional condition code, see Conditional execution on page 3-14. Specifies the register to load or store. Specifies the register on which the memory address is based. Is an offset from Rn and can be 0 to 255. If offset is omitted, the address is the value in Rn.
Operation These load and store instructions perform the same function as the memory access instructions with immediate offset, see LDR and STR, immediate offset on page 3-19. The difference is that these instructions have only unprivileged access even when used in privileged software. When used in unprivileged software, these instructions behave in exactly the same way as normal memory access instructions with immediate offset. Restrictions In these instructions: Rn must not be PC Rt must not be SP and must not be PC. Condition flags These instructions do not change the flags. Examples
STRBTEQ LDRHT R4, [R7] R2, [R2, #8] ; ; ; ; Conditionally store least significant byte in R4 to an address in R7, with unprivileged access Load halfword value from an address equal to sum of R2 and 8 into R2, with unprivileged access.
3-24
3.4.5
LDR, PC-relative Load register from memory. Syntax

LDR{type}{cond} Rt, label LDRD{cond} Rt, Rt2, label ; Load two words
where:
type
Is one of:
B SB H SH -
unsigned byte, zero extend to 32 bits. signed byte, sign extend to 32 bits. unsigned halfword, zero extend to 32 bits. signed halfword, sign extend to 32 bits. omit, for word.
cond Rt Rt2 label
Is an optional condition code, see Conditional execution on page 3-14. Specifies the register to load or store. Specifies the second register to load or store. Is a PC-relative expression. See PC-relative expressions on page 3-13.
Operation
LDR loads a register with a value from a PC-relative memory address. The memory address is
specified by a label or by an offset from the PC. The value to load or store can be a byte, halfword, or word. For load instructions, bytes and halfwords can either be signed or unsigned. See Address alignment on page 3-13.
label must be within a limited range of the current instruction. Table 3-7 shows the possible offsets between label and the PC.
Table 3-7 Offset ranges Instruction type Word, halfword, signed halfword, byte, signed byte Two words Offset range 4095 to 4095 1020 to 1020
Note You might have to use the .W suffix to get the maximum offset range. See Instruction width selection on page 3-16.
Restrictions In these instructions: Rt can be SP or PC only for word loads Rt2 must not be SP and must not be PC Rt must be different from Rt2.
3-25
When Rt is PC in a word load instruction: bit[0] of the loaded value must be 1 for correct execution, and a branch occurs to this halfword-aligned address if the instruction is conditional, it must be the last instruction in the IT block. Condition flags These instructions do not change the flags. Examples
LDR LDRSB R0, LookUpTable R7, localdata ; ; ; ; ; Load R0 with a word of data from an address labelled as LookUpTable Load a byte value from an address labelled as localdata, sign extend it to a word value, and put it in R7.
3-26
3.4.6
LDM and STM Load and Store Multiple registers. Syntax

op{addr_mode}{cond} Rn{!}, reglist
where:
op
Is one of:
LDM STM
Load Multiple registers. Store Multiple registers.
addr_mode
This is any one of the following: IA Increment address After each access. This is the default. DB Decrement address Before each access. Is an optional condition code, see Conditional execution on page 3-14. Specifies the register on which the memory addresses are based. Is an optional writeback suffix. If ! is present the final address, that is loaded from or stored to, is written back into Rn. Is a list of one or more registers to be loaded or stored, enclosed in braces. It can contain register ranges. It must be comma separated if it contains more than one register or register range, see Examples on page 3-28.
cond Rn !
reglist
LDM and LDMFD are synonyms for LDMIA. LDMFD refers to its use for popping data from Full Descending stacks. LDMEA is a synonym for LDMDB, and refers to its use for popping data from Empty Ascending
stacks.
STM and STMEA are synonyms for STMIA. STMEA refers to its use for pushing data onto Empty Ascending stacks. STMFD is s synonym for STMDB, and refers to its use for pushing data onto Full Descending stacks.
Operation
LDM instructions load the registers in reglist with word values from memory addresses based on Rn. STM instructions store the word values in the registers in reglist to memory addresses based on Rn.
For LDM, LDMIA, LDMFD, STM, STMIA, and STMEA the memory addresses used for the accesses are at 4-byte intervals ranging from Rn to Rn + 4 * (n-1), where n is the number of registers in reglist. The accesses happens in order of increasing register numbers, with the lowest numbered register using the lowest memory address and the highest number register using the highest memory address. If the writeback suffix is specified, the value of Rn + 4 * (n-1) is written back to Rn. For LDMDB, LDMEA, STMDB, and STMFD the memory addresses used for the accesses are at 4-byte intervals ranging from Rn to Rn - 4 * (n-1), where n is the number of registers in reglist. The accesses happen in order of decreasing register numbers, with the highest numbered register using the highest memory address and the lowest number register using the lowest memory address. If the writeback suffix is specified, the value of Rn - 4 * (n-1) is written back to Rn.
3-27
The PUSH and POP instructions can be expressed in this form. See PUSH and POP on page 3-29 for details. Restrictions In these instructions: Rn must not be PC reglist must not contain SP in any STM instruction, reglist must not contain PC in any LDM instruction, reglist must not contain PC if it contains LR reglist must not contain Rn if you specify the writeback suffix. When PC is in reglist in an LDM instruction: bit[0] of the value loaded to the PC must be 1 for correct execution, and a branch occurs to this halfword-aligned address if the instruction is conditional, it must be the last instruction in the IT block.

LDM STMDB R8,{R0,R2,R9} ; LDMIA is a synonym for LDM R1!,{R3-R6,R11,R12}
Incorrect examples
STM LDM R5!,{R5,R4,R9} ; Value stored for R5 is unpredictable R2, {} ; There must be at least one register in the list.
3-28
3.4.7
PUSH and POP Push registers onto, and pop registers off a full-descending stack. Syntax
PUSH{cond} reglist POP{cond} reglist
where:
cond reglist
Is an optional condition code, see Conditional execution on page 3-14. Is a non-empty list of registers, enclosed in braces. It can contain register ranges. It must be comma separated if it contains more than one register or register range.
PUSH and POP are synonyms for STMDB and LDM (or LDMIA) with the memory addresses for the access based on SP, and with the final address for the access written back to the SP. PUSH and POP are
the preferred mnemonics in these cases. Operation

PUSH stores registers on the stack, with the lowest numbered register using the lowest memory
address and the highest numbered register using the highest memory address.
POP loads registers from the stack, with the lowest numbered register using the lowest memory
address and the highest numbered register using the highest memory address.
PUSH uses the value in the SP register minus four as the highest memory address, POP uses the value in the SP register as the lowest memory address, implementing a full-descending stack. On completion, PUSH updates the SP register to point to the location of the lowest stored value, POP updates the SP register to point to the location immediately above the highest location loaded.
If a POP instruction includes PC in its reglist, a branch to this location is performed when the POP instruction has completed. Bit[0] of the value read for the PC is used to update the APSR T-bit. This bit must be 1 to ensure correct operation. See LDM and STM on page 3-27 for more information. Restrictions In these instructions: reglist must not contain SP for the PUSH instruction, reglist must not contain PC for the POP instruction, reglist must not contain PC if it contains LR. When PC is in reglist in a POP instruction: bit[0] of the value loaded for PC must be 1 for correct execution if the instruction is conditional, it must be the last instruction in the IT block. Condition flags These instructions do not change the flags.
3-29
Examples
PUSH {R0,R4-R7} ; Push R0,R4,R5,R6,R7 onto the stack PUSH {R2,LR} ; Push R2 and the link-register onto the stack POP {R0,R6,PC} ; Pop r0,r6 and PC from the stack, then branch to the new PC.
3-30
3.4.8
LDREX and STREX Load and Store Register Exclusive. Syntax

LDREX{cond} Rt, [Rn {, #offset}] STREX{cond} Rd, Rt, [Rn {, #offset}] LDREXB{cond} Rt, [Rn] STREXB{cond} Rd, Rt, [Rn] LDREXH{cond} Rt, [Rn] STREXH{cond} Rd, Rt, [Rn]
where:
cond Rd Rt Rn offset
Is an optional condition code, see Conditional execution on page 3-14. Specifies the destination register for the returned status. Specifies the register to load or store. Specifies the register on which the memory address is based. Is an optional offset applied to the value in Rn. If offset is omitted, the address is the value in Rn.
Operation
LDREX, LDREXB, and LDREXH load a word, byte, and halfword respectively from a memory address. STREX, STREXB, and STREXH attempt to store a word, byte, and halfword respectively to a memory address. The address used in any Store-Exclusive instruction must be the same as the address in the most recently executed Load-exclusive instruction. The value stored by the Store-Exclusive instruction must also have the same data size as the value loaded by the preceding Load-exclusive instruction. This means software must always use a Load-exclusive instruction and a matching Store-Exclusive instruction to perform a synchronization operation, see Synchronization primitives on page 2-18.
If an Store-Exclusive instruction performs the store, it writes 0 to its destination register. If it does not perform the store, it writes 1 to its destination register. If the Store-Exclusive instruction writes 0 to the destination register, it is guaranteed that no other process in the system has accessed the memory location between the Load-exclusive and Store-Exclusive instructions. For reasons of performance, keep the number of instructions between corresponding Load-Exclusive and Store-Exclusive instruction to a minimum. Note The result of executing a Store-Exclusive instruction to an address that is different from that used in the preceding Load-Exclusive instruction is unpredictable.
3-31
Restrictions In these instructions: do not use PC do not use SP for Rd and Rt for STREX, Rd must be different from both Rt and Rn the value of offset must be a multiple of four in the range 0-1020. Condition flags These instructions do not change the flags. Examples
MOV try LDREX CMP ITT STREXEQ CMPEQ BNE .... R0, R0, EQ R0, R0, try [LockAddr] #0 R1, [LockAddr] #0 ; ; ; ; ; ; ; Load the lock value Is the lock free? IT instruction for STREXEQ and CMPEQ Try and claim the lock Did this succeed? No try again Yes we have the lock. R1, #0x1 ; Initialize the lock taken value
3-32
3.4.9
CLREX Clear Exclusive. Syntax

CLREX{cond}
where:
cond
Is an optional condition code, see Conditional execution on page 3-14.
Operation Use CLREX to make the next STREX, STREXB, or STREXH instruction write 1 to its destination register and fail to perform the store. It is useful in exception handler code to force the failure of the store exclusive if the exception occurs between a load exclusive instruction and the matching store exclusive instruction in a synchronization operation. See Synchronization primitives on page 2-18 for more information. Condition flags These instructions do not change the flags. Examples
CLREX
3-33
3.5
General data processing instructions

Table 3-8 shows the data processing instructions.
Table 3-8 Data processing instructions Mnemonic
ADC ADD ADDW AND ASR BIC CLZ CMN CMP EOR LSL LSR MOV MOVT MOVW MVN ORN ORR RBIT REV REV16 REVSH ROR RRX RSB SBC SUB SUBW TEQ TST
Brief description Add with Carry Add Add Logical AND Arithmetic Shift Right Bit Clear Count leading zeros Compare Negative Compare Exclusive OR Logical Shift Left Logical Shift Right Move Move Top Move 16-bit constant Move NOT Logical OR NOT Logical OR Reverse Bits Reverse byte order in a word Reverse byte order in each halfword Reverse byte order in bottom halfword and sign extend Rotate Right Rotate Right with Extend Reverse Subtract Subtract with Carry Subtract Subtract Test Equivalence Test
See ADD, ADC, SUB, SBC, and RSB on page 3-35 ADD, ADC, SUB, SBC, and RSB on page 3-35 ADD, ADC, SUB, SBC, and RSB on page 3-35 AND, ORR, EOR, BIC, and ORN on page 3-38 ASR, LSL, LSR, ROR, and RRX on page 3-40 AND, ORR, EOR, BIC, and ORN on page 3-38 CLZ on page 3-42 CMP and CMN on page 3-43 CMP and CMN on page 3-43 AND, ORR, EOR, BIC, and ORN on page 3-38 ASR, LSL, LSR, ROR, and RRX on page 3-40 ASR, LSL, LSR, ROR, and RRX on page 3-40 MOV and MVN on page 3-44 MOVT on page 3-46 MOV and MVN on page 3-44 MOV and MVN on page 3-44 AND, ORR, EOR, BIC, and ORN on page 3-38 AND, ORR, EOR, BIC, and ORN on page 3-38 REV, REV16, REVSH, and RBIT on page 3-47 REV, REV16, REVSH, and RBIT on page 3-47 REV, REV16, REVSH, and RBIT on page 3-47 REV, REV16, REVSH, and RBIT on page 3-47 ASR, LSL, LSR, ROR, and RRX on page 3-40 ASR, LSL, LSR, ROR, and RRX on page 3-40 ADD, ADC, SUB, SBC, and RSB on page 3-35 ADD, ADC, SUB, SBC, and RSB on page 3-35 ADD, ADC, SUB, SBC, and RSB on page 3-35 ADD, ADC, SUB, SBC, and RSB on page 3-35 TST and TEQ on page 3-48 TST and TEQ on page 3-48
3-34
3.5.1
ADD, ADC, SUB, SBC, and RSB Add, Add with carry, Subtract, Subtract with carry, and Reverse Subtract. Syntax
op{S}{cond} {Rd,} Rn, Operand2 op{cond} {Rd,} Rn, #imm12 ; ADD and SUB only
where:
op
Is one of:
ADD ADC SUB SBC RSB
Add. Add with Carry. Subtract. Subtract with Carry. Reverse Subtract.
Is an optional suffix. If S is specified, the condition code flags are updated on the result of the operation, see Conditional execution on page 3-14. Is an optional condition code, see Conditional execution on page 3-14. Specifies the destination register. If Rd is omitted, the destination register is Rn. Specifies the register holding the first operand. Is a flexible second operand. See Flexible second operand on page 3-9 for details of the options. This is any value in the range 0-4095.
cond Rd Rn Operand2
imm12
Operation The ADD instruction adds the value of Operand2 or imm12 to the value in Rn. The ADC instruction adds the values in Rn and Operand2, together with the carry flag. The SUB instruction subtracts the value of Operand2 or imm12 from the value in Rn. The SBC instruction subtracts the value of Operand2 from the value in Rn. If the carry flag is clear, the result is reduced by one. The RSB instruction subtracts the value in Rn from the value of Operand2. This is useful because of the wide range of options for Operand2. Use ADC and SBC to synthesize multiword arithmetic, see Multiword arithmetic examples on page 3-36. See also ADR on page 3-18. Note ADDW is equivalent to the ADD syntax that uses the imm12 operand. SUBW is equivalent to the SUB syntax that uses the imm12 operand.
3-35
Restrictions In these instructions:

Operand2 must not be SP and must not be PC Rd can be SP only in ADD and SUB, and only with the additional restrictions:
Rn must also be SP
any shift in Operand2 must be limited to a maximum of 3 bits using LSL
Rn can be SP only in ADD and SUB Rd can be PC only in the ADD{cond} PC, PC, Rm instruction where:
you must not specify the S suffix Rm must not be PC and must not be SP if the instruction is conditional, it must be the last instruction in the IT block
with the exception of the ADD{cond} PC, PC, Rm instruction, Rn can be PC only in ADD and SUB, and only with the additional restrictions: you must not specify the S suffix the second operand must be a constant in the range 0 to 4095. Note When using the PC for an addition or a subtraction, bits[1:0] of the PC are rounded to b00 before performing the calculation, making the base address for the calculation word-aligned. If you want to generate the address of an instruction, you have to adjust the constant based on the value of the PC. ARM recommends that you use the ADR instruction instead of ADD or SUB with Rn equal to the PC, because your assembler automatically calculates the correct constant for the ADR instruction.
When Rd is PC in the ADD{cond} PC, PC, Rm instruction: bit[0] of the value written to the PC is ignored a branch occurs to the address created by forcing bit[0] of that value to 0. Condition flags If S is specified, these instructions update the N, Z, C and V flags according to the result. Examples
ADD SUBS RSB ADCHI R2, R1, R3 R8, R6, #240 R4, R4, #1280 R11, R0, R3 ; ; ; ; Sets the flags on the result Subtracts contents of R4 from 1280 Only executed if C flag set and Z flag clear.
Multiword arithmetic examples Example 3-4 on page 3-37 shows two instructions that add a 64-bit integer contained in R2 and R3 to another 64-bit integer contained in R0 and R1, and place the result in R4 and R5.
3-36
Example 3-4 64-bit addition
ADDS ADC
R4, R0, R2 R5, R1, R3
; add the least significant words ; add the most significant words with carry
Multiword values do not have to use consecutive registers. Example 3-5 shows instructions that subtract a 96-bit integer contained in R9, R1, and R11 from another contained in R6, R2, and R8. The example stores the result in R6, R9, and R2.
Example 3-5 96-bit subtraction
SUBS SBCS SBC
R6, R6, R9 R9, R2, R1 R2, R8, R11
; subtract the least significant words ; subtract the middle words with carry ; subtract the most significant words with carry
3-37
3.5.2
AND, ORR, EOR, BIC, and ORN Logical AND, OR, Exclusive OR, Bit Clear, and OR NOT. Syntax
op{S}{cond} {Rd,} Rn, Operand2
where:
op
Is one of:
AND ORR EOR BIC ORN
logical AND. logical OR, or bit set. logical Exclusive OR. logical AND NOT, or bit clear. logical OR NOT.
Is an optional suffix. If S is specified, the condition code flags are updated on the result of the operation, see Conditional execution on page 3-14. Is an optional condition code, see Conditional execution on page 3-14. Specifies the destination register. Specifies the register holding the first operand. Is a flexible second operand. See Flexible second operand on page 3-9 for details of the options.
cond Rd Rn Operand2
Operation The AND, EOR, and ORR instructions perform bitwise AND, Exclusive OR, and OR operations on the values in Rn and Operand2. The BIC instruction performs an AND operation on the bits in Rn with the complements of the corresponding bits in the value of Operand2. The ORN instruction performs an OR operation on the bits in Rn with the complements of the corresponding bits in the value of Operand2. Restrictions Do not use SP and do not use PC. Condition flags If S is specified, these instructions: update the N and Z flags according to the result can update the C flag during the calculation of Operand2, see Flexible second operand on page 3-9 do not affect the V flag.
3-38
Examples
AND ORREQ ANDS EORS BIC ORN ORNS R9, R2, R9, R7, R0, R7, R7, R2, #0xFF00 R0, R5 R8, #0x19 R11, #0x18181818 R1, #0xab R11, R14, ROR #4 R11, R14, ASR #32
3-39
3.5.3
ASR, LSL, LSR, ROR, and RRX Arithmetic Shift Right, Logical Shift Left, Logical Shift Right, Rotate Right, and Rotate Right with Extend. Syntax
op{S}{cond} Rd, Rm, Rs op{S}{cond} Rd, Rm, #n RRX{S}{cond} Rd, Rm
where:
op
Is one of:
ASR LSL LSR ROR
Arithmetic Shift Right. Logical Shift Left. Logical Shift Right. Rotate Right.
Is an optional suffix. If S is specified, the condition code flags are updated on the result of the operation, see Conditional execution on page 3-14. Specifies the destination register. Specifies the register holding the value to be shifted. Specifies the register holding the shift length to apply to the value in Rm. Only the least significant byte is used and can be in the range 0 to 255. Specifies the shift length. The range of shift length depends on the instruction: ASR shift length from 1 to 32 LSL shift length from 0 to 31 LSR shift length from 1 to 32 ROR shift length from 1 to 31.
Rd Rm Rs
Note MOVS Rd, Rm is the preferred syntax for LSLS Rd, Rm, #0.
Operation
ASR, LSL, LSR, and ROR move the bits in the register Rm to the left or right by the number of places specified by constant n or register Rs. RRX moves the bits in register Rm to the right by 1.
In all these instructions, the result is written to Rd, but the value in register Rm remains unchanged. For details on what result is generated by the different instructions, see Shift Operations on page 3-10. Restrictions Do not use SP and do not use PC.
3-40
Condition flags If S is specified: these instructions update the N and Z flags according to the result the C flag is updated to the last bit shifted out, except when the shift length is 0, see Shift Operations on page 3-10.
Examples
ASR LSLS LSR ROR RRX R7, R1, R4, R4, R4, R8, R2, R5, R5, R5 #9 #3 #6 R6 ; ; ; ; ; Arithmetic shift right by 9 bits Logical shift left by 3 bits with flag update Logical shift right by 6 bits Rotate right by the value in the bottom byte of R6 Rotate right with extend.
3-41
3.5.4
CLZ Count Leading Zeros. Syntax

CLZ{cond} Rd, Rm
where:
cond Rd Rm
Is an optional condition code, see Conditional execution on page 3-14. Specifies the destination register. Specifies the operand register.
Operation The CLZ instruction counts the number of leading zeros in the value in Rm and returns the result in Rd. The result value is 32 if no bits are set and zero if bit[31] is set. Restrictions Do not use SP and do not use PC. Condition flags This instruction does not change the flags. Examples
CLZ CLZNE R4,R9 R2,R3
3-42
3.5.5
CMP and CMN Compare and Compare Negative. Syntax

CMP{cond} Rn, Operand2 CMN{cond} Rn, Operand2
where:
cond Rn Operand2
Is an optional condition code, see Conditional execution on page 3-14. Specifies the register holding the first operand. Is a flexible second operand. See Flexible second operand on page 3-9 for details of the options.
Operation These instructions compare the value in a register with Operand2. They update the condition flags on the result, but do not write the result to a register. The CMP instruction subtracts the value of Operand2 from the value in Rn. This is the same as a SUBS instruction, except that the result is discarded. The CMN instruction adds the value of Operand2 to the value in Rn. This is the same as an ADDS instruction, except that the result is discarded. Restrictions In these instructions: do not use PC Operand2 must not be SP. Condition flags These instructions update the N, Z, C and V flags according to the result. Examples
CMP CMN CMPGT R2, R9 R0, #6400 SP, R7, LSL #2
3-43
3.5.6
MOV and MVN Move and Move NOT. Syntax

MOV{S}{cond} Rd, Operand2 MOV{cond} Rd, #imm16 MVN{S}{cond} Rd, Operand2
where:
S
Is an optional suffix. If S is specified, the condition code flags are updated on the result of the operation, see Conditional execution on page 3-14. Is an optional condition code, see Conditional execution on page 3-14. Specifies the destination register. Is a flexible second operand. See Flexible second operand on page 3-9 for details of the options. This is any value in the range 0-65535.
cond Rd Operand2
imm16
Operation The MOV instruction copies the value of Operand2 into Rd. When Operand2 in a MOV instruction is a register with a shift other than LSL #0, the preferred syntax is the corresponding shift instruction:
ASR{S}{cond} Rd, Rm, #n is the preferred syntax for MOV{S}{cond} Rd, Rm, ASR #n LSL{S}{cond} Rd, Rm, #n is the preferred syntax for MOV{S}{cond} Rd, Rm, LSL #n if n != 0 LSR{S}{cond} Rd, Rm, #n is the preferred syntax for MOV{S}{cond} Rd, Rm, LSR #n ROR{S}{cond} Rd, Rm, #n is the preferred syntax for MOV{S}{cond} Rd, Rm, ROR #n RRX{S}{cond} Rd, Rm is the preferred syntax for MOV{S}{cond} Rd, Rm, RRX.
Also, the MOV instruction permits additional forms of Operand2 as synonyms for shift instructions: MOV{S}{cond} Rd, Rm, ASR Rs is a synonym for ASR{S}{cond} Rd, Rm, Rs MOV{S}{cond} Rd, Rm, LSL Rs is a synonym for LSL{S}{cond} Rd, Rm, Rs MOV{S}{cond} Rd, Rm, LSR Rs is a synonym for LSR{S}{cond} Rd, Rm, Rs MOV{S}{cond} Rd, Rm, ROR Rs is a synonym for ROR{S}{cond} Rd, Rm, Rs See ASR, LSL, LSR, ROR, and RRX on page 3-40. The MVN instruction takes the value of Operand2, performs a bitwise logical NOT operation on the value, and places the result into Rd. Note The MOVW instruction provides the same function as MOV, but is restricted to using the imm16 operand.
3-44
Restrictions You can use SP and PC only in the MOV instruction, with the following restrictions: the second operand must be a register without shift you must not specify the S suffix. When Rd is PC in a MOV instruction: bit[0] of the value written to the PC is ignored a branch occurs to the address created by forcing bit[0] of that value to 0. Note Though it is possible to use MOV as a branch instruction, ARM strongly recommends the use of a BX or BLX instruction to branch for software portability to the ARM instruction set.
Condition flags If S is specified, these instructions: update the N and Z flags according to the result can update the C flag during the calculation of Operand2, see Flexible second operand on page 3-9 do not affect the V flag.
Example
MOVS MOV MOVS MOV MOV MVNS R11, #0x000B R1, #0xFA05 R10, R12 R3, #23 R8, SP R2, #0xF ; ; ; ; ; ; ; Write value of 0x000B to R11, flags get updated Write value of 0xFA05 to R1, flags are not updated Write value in R12 to R10, flags get updated Write value of 23 to R3 Write value of stack pointer to R8 Write value of 0xFFFFFFF0 (bitwise inverse of 0xF) to the R2 and update flags.
3-45
3.5.7
MOVT Move Top. Syntax

MOVT{cond} Rd, #imm16
where:
cond Rd imm16
Is an optional condition code, see Conditional execution on page 3-14. Specifies the destination register. Is a 16-bit immediate constant.
Operation
MOVT writes a 16-bit immediate value, imm16, to the top halfword, Rd[31:16], of its destination register. The write does not affect Rd[15:0].
The MOV, MOVT instruction pair enables you to generate any 32-bit constant. Restrictions
MOVT R3, #0xF123 ; Write 0xF123 to upper halfword of R3, lower halfword ; and APSR are unchanged.
3-46
3.5.8
REV, REV16, REVSH, and RBIT Reverse bytes and Reverse bits. Syntax
op{cond} Rd, Rn
where:
op
Is any of:
REV REV16 REVSH RBIT
Reverse byte order in a word. Reverse byte order in each halfword independently. Reverse byte order in the bottom halfword, and sign extend to 32 bits. Reverse the bit order in a 32-bit word.
cond Rd Rn
Is an optional condition code, see Conditional execution on page 3-14. Specifies the destination register. Specifies the register holding the operand.
Operation Use these instructions to change endianness of data:

REV
Converts 32-bit big-endian data into little-endian data or 32-bit little-endian data into big-endian data. Converts 16-bit big-endian data into little-endian data or 16-bit little-endian data into big-endian data. Converts either: 16-bit signed big-endian data into 32-bit signed little-endian data 16-bit signed little-endian data into 32-bit signed big-endian data.
REV16
REVSH
Restrictions Do not use SP and do not use PC. Condition flags These instructions do not change the flags. Examples
REV REV16 REVSH REVHS RBIT R3, R0, R0, R3, R7, R7 R0 R5 R7 R8 ; ; ; ; ; Reverse Reverse Reverse Reverse Reverse byte order of value in R7 and write it to R3 byte order of each 16-bit halfword in R0 Signed Halfword with Higher or Same condition bit order of value in R8 and write the result to R7.
3-47
3.5.9
TST and TEQ Test bits and Test Equivalence. Syntax

TST{cond} Rn, Operand2 TEQ{cond} Rn, Operand2
where:
cond Rn Operand2
Is an optional condition code, see Conditional execution on page 3-14. Specifies the register holding the first operand. Is a flexible second operand. See Flexible second operand on page 3-9 for details of the options.
Operation These instructions test the value in a register against Operand2. They update the condition flags based on the result, but do not write the result to a register. The TST instruction performs a bitwise AND operation on the value in Rn and the value of Operand2. This is the same as the ANDS instruction, except that it discards the result. To test whether a bit of Rn is 0 or 1, use the TST instruction with an Operand2 constant that has that bit set to 1 and all other bits cleared to 0. The TEQ instruction performs a bitwise Exclusive OR operation on the value in Rn and the value of Operand2. This is the same as the EORS instruction, except that it discards the result. Use the TEQ instruction to test if two values are equal without affecting the V or C flags.
TEQ is also useful for testing the sign of a value. After the comparison, the N flag is the logical
Exclusive OR of the sign bits of the two operands. Restrictions Do not use SP and do not use PC. Condition flags These instructions: update the N and Z flags according to the result can update the C flag during the calculation of Operand2, see Flexible second operand on page 3-9 do not affect the V flag.
Examples
TST TEQEQ R0, #0x3F8 R10, R9 ; ; ; ; Perform bitwise AND of R0 value to 0x3F8, APSR is updated but result is discarded Conditionally test if value in R10 is equal to value in R9, APSR is updated but result is discarded.
3-48
3.6
Multiply and divide instructions

Table 3-9 shows the multiply and divide instructions.
Table 3-9 Multiply and divide instructions Mnemonic
MLA MLS MUL SDIV SMLAL
Brief description Multiply with Accumulate, 32-bit result Multiply and Subtract, 32-bit result Multiply, 32-bit result Signed Divide Signed Multiply with Accumulate (32x32+64), 64-bit result Signed Multiply (32x32), 64-bit result Unsigned Divide Unsigned Multiply with Accumulate (32x32+64), 64-bit result Unsigned Multiply (32x32), 64-bit result
See MUL, MLA, and MLS on page 3-50 MUL, MLA, and MLS on page 3-50 MUL, MLA, and MLS on page 3-50 SDIV and UDIV on page 3-53 UMULL, UMLAL, SMULL, and SMLAL on page 3-52 UMULL, UMLAL, SMULL, and SMLAL on page 3-52 SDIV and UDIV on page 3-53 UMULL, UMLAL, SMULL, and SMLAL on page 3-52 UMULL, UMLAL, SMULL, and SMLAL on page 3-52
SMULL UDIV UMLAL
UMULL
3-49
3.6.1
MUL, MLA, and MLS Multiply, Multiply with Accumulate, and Multiply with Subtract, using 32-bit operands, and producing a 32-bit result. Syntax
MUL{S}{cond} {Rd,} Rn, Rm ; Multiply MLA{cond} Rd, Rn, Rm, Ra MLS{cond} Rd, Rn, Rm, Ra ; Multiply with accumulate ; Multiply with subtract
where:
cond S
Is an optional condition code, see Conditional execution on page 3-14. Is an optional suffix. If S is specified, the condition code flags are updated on the result of the operation, see Conditional execution on page 3-14. Specifies the destination register. If Rd is omitted, the destination register is Rn. Are registers holding the values to be multiplied. Is a register holding the value to be added or subtracted from.
Rd Rn, Rm Ra
Operation The MUL instruction multiplies the values from Rn and Rm, and places the least significant 32 bits of the result in Rd. The MLA instruction multiplies the values from Rn and Rm, adds the value from Ra, and places the least significant 32 bits of the result in Rd. The MLS instruction multiplies the values from Rn and Rm, subtracts the product from the value from Ra, and places the least significant 32 bits of the result in Rd. The results of these instructions do not depend on whether the operands are signed or unsigned. Restrictions In these instructions, do not use SP and do not use PC. If you use the S suffix with the MUL instruction: Rd, Rn, and Rm must all be in the range R0 to R7 Rd must be the same as Rm you must not use the cond suffix. Condition flags If S is specified, the MUL instruction: updates the N and Z flags according to the result does not affect the C and V flags.
3-50
Examples
MUL MLA MULS MULLT MLS R10, R2, R5 R10, R2, R1, R5 R0, R2, R2 R2, R3, R2 R4, R5, R6, R7 ; ; ; ; ; Multiply, R10 Multiply with Multiply with Conditionally Multiply with = R2 x R5 accumulate, R10 = flag update, R0 = multiply, R2 = R3 subtract, R4 = R7 (R2 x R1) + R5 R2 x R2 x R2 - (R5 x R6).
3-51
3.6.2
UMULL, UMLAL, SMULL, and SMLAL Signed and Unsigned Long Multiply, with optional Accumulate, using 32-bit operands and producing a 64-bit result. Syntax
op{cond} RdLo, RdHi, Rn, Rm
where:
op
Is one of:
UMULL UMLAL SMULL SMLAL
Unsigned Long Multiply. Unsigned Long Multiply, with Accumulate. Signed Long Multiply. Signed Long Multiply, with Accumulate.
cond RdHi, RdLo
Is an optional condition code, see Conditional execution on page 3-14. Are the destination registers. For UMLAL and SMLAL they also hold the accumulating value. Are registers holding the operands.
Rn, Rm
Operation The UMULL instruction interprets the values from Rn and Rm as unsigned integers. It multiplies these integers and places the least significant 32 bits of the result in RdLo, and the most significant 32 bits of the result in RdHi. The UMLAL instruction interprets the values from Rn and Rm as unsigned integers. It multiplies these integers, adds the 64-bit result to the 64-bit unsigned integer contained in RdHi and RdLo, and writes the result back to RdHi and RdLo. The SMULL instruction interprets the values from Rn and Rm as twos complement signed integers. It multiplies these integers and places the least significant 32 bits of the result in RdLo, and the most significant 32 bits of the result in RdHi. The SMLAL instruction interprets the values from Rn and Rm as twos complement signed integers. It multiplies these integers, adds the 64-bit result to the 64-bit signed integer contained in RdHi and RdLo, and writes the result back to RdHi and RdLo. Restrictions In these instructions: do not use SP and do not use PC RdHi and RdLo must be different registers. Condition flags These instructions do not affect the condition code flags. Examples
UMULL SMLAL R0, R4, R5, R6 R4, R5, R3, R8 ; Unsigned (R4,R0) = R5 x R6 ; Signed (R5,R4) = (R5,R4) + R3 x R8
3-52
3.6.3
SDIV and UDIV Signed Divide and Unsigned Divide. Syntax

SDIV{cond} {Rd,} Rn, Rm UDIV{cond} {Rd,} Rn, Rm
where:
cond Rd Rn Rm
Is an optional condition code, see Conditional execution on page 3-14. Specifies the destination register. If Rd is omitted, the destination register is Rn. Specifies the register holding the value to be divided. Is a register holding the divisor.
Operation
SDIV performs a signed integer division of the value in Rn by the value in Rm. UDIV performs an unsigned integer division of the value in Rn by the value in Rm.
For both instructions, if the value in Rn is not divisible by the value in Rm, the result is rounded towards zero. Restrictions Do not use SP and do not use PC. Condition flags These instructions do not change the flags. Examples
SDIV UDIV R0, R2, R4 R8, R8, R1 ; Signed divide, R0 = R2/R4 ; Unsigned divide, R8 = R8/R1.
3-53
3.7
Saturating instructions
This section describes the saturating instructions, SSAT and USAT.
3.7.1
SSAT and USAT Signed Saturate and Unsigned Saturate to any bit position, with optional shift before saturating. Syntax
op{cond} Rd, #n, Rm {, shift #s}
where:
op
Is one of:
SSAT USAT
Saturates a signed value to a signed range. Saturates a signed value to an unsigned range.
cond Rd n
Is an optional condition code, see Conditional execution on page 3-14. Specifies the destination register. specifies the bit position to saturate to: n ranges from 1 to 32 for SSAT n ranges from 0 to 31 for USAT. Specifies the register containing the value to saturate. Is an optional shift applied to Rm before saturating. It must be one of the following: ASR #s where s is in the range 1 to 31 LSL #s where s is in the range 0 to 31.
Rm shift #s
Operation These instructions saturate to a signed or unsigned n-bit value. The SSAT instruction applies the specified shift, then saturates to the signed range 2n1 x 2n11. The USAT instruction applies the specified shift, then saturates to the unsigned range 0 x 2n1. For signed n-bit saturation using SSAT, this means that: if the value to be saturated is less than 2n1, the result returned is 2n-1 if the value to be saturated is greater than 2n11, the result returned is 2n-11 otherwise, the result returned is the same as the value to be saturated. For unsigned n-bit saturation using USAT, this means that: if the value to be saturated is less than 0, the result returned is 0 if the value to be saturated is greater than 2n1, the result returned is 2n1 otherwise, the result returned is the same as the value to be saturated. If the returned result is different from the value to be saturated, it is called saturation. If saturation occurs, the instruction sets the Q flag to 1 in the APSR. Otherwise, it leaves the Q flag unchanged. To clear the Q flag to 0, you must use the MSR instruction, see MSR on page 3-75. To read the state of the Q flag, use the MRS instruction, see MRS on page 3-74.
3-54
Restrictions Do not use SP and do not use PC. Condition flags These instructions do not affect the condition code flags. If saturation occurs, these instructions set the Q flag to 1. Examples
SSAT R7, #16, R7, LSL #4 ; ; ; ; ; Logical shift left value in R7 by 4, then saturate it as a signed 16-bit value and write it back to R7 Conditionally saturate value in R5 as an unsigned 7 bit value and write it to R0.
USATNE
R0, #7, R5
3-55
3.8
Bitfield instructions
Table 3-10 shows the instructions that operate on adjacent sets of bits in registers or bitfields.
Table 3-10 Packing and unpacking instructions Mnemonic
BFC BFI SBFX SXTB SXTH UBFX UXTB UXTH
Brief description Bit Field Clear Bit Field Insert Signed Bit Field Extract Sign extend a byte Sign extend a halfword Unsigned Bit Field Extract Zero extend a byte Zero extend a halfword
See BFC and BFI on page 3-57 BFC and BFI on page 3-57 SBFX and UBFX on page 3-58 SXT and UXT on page 3-59 SXT and UXT on page 3-59 SBFX and UBFX on page 3-58 SXT and UXT on page 3-59 SXT and UXT on page 3-59
3-56
3.8.1
BFC and BFI Bit Field Clear and Bit Field Insert. Syntax
BFC{cond} Rd, #lsb, #width BFI{cond} Rd, Rn, #lsb, #width
where:
cond Rd Rn lsb
Is an optional condition code, see Conditional execution on page 3-14. Specifies the destination register. Specifies the source register. Specifies the position of the least significant bit of the bitfield. lsb must be in the range 0 to 31. Specifies the width of the bitfield and must be in the range 1 to 32lsb.
width
Operation
BFC clears a bitfield in a register. It clears width bits in Rd, starting at the low bit position lsb. Other bits in Rd are unchanged. BFI copies a bitfield into one register from another register. It replaces width bits in Rd starting at the low bit position lsb, with width bits from Rn starting at bit[0]. Other bits in Rd are
unchanged. Restrictions Do not use SP and do not use PC. Condition flags These instructions do not affect the flags. Examples
BFC BFI R4, #8, #12 R9, R2, #8, #12 ; Clear bit 8 to bit 19 (12 bits) of R4 to 0 ; Replace bit 8 to bit 19 (12 bits) of R9 with ; bit 0 to bit 11 from R2.
3-57
3.8.2
SBFX and UBFX Signed Bit Field Extract and Unsigned Bit Field Extract. Syntax
SBFX{cond} Rd, Rn, #lsb, #width UBFX{cond} Rd, Rn, #lsb, #width
where:
cond Rd Rn lsb
Is an optional condition code, see Conditional execution on page 3-14. Specifies the destination register. Specifies the source register. Specifies the position of the least significant bit of the bitfield. lsb must be in the range 0 to 31. Specifies the width of the bitfield and must be in the range 1 to 32lsb.
width
Operation
SBFX extracts a bitfield from one register, sign extends it to 32 bits, and writes the result to the
destination register.
UBFX extracts a bitfield from one register, zero extends it to 32 bits, and writes the result to the
destination register. Restrictions Do not use SP and do not use PC. Condition flags These instructions do not affect the flags. Examples
SBFX UBFX R0, R1, #20, #4 ; ; R8, R11, #9, #10 ; ; Extract bit 20 to bit 23 (4 bits) from R1 and sign extend to 32 bits and then write the result to R0. Extract bit 9 to bit 18 (10 bits) from R11 and zero extend to 32 bits and then write the result to R8.
3-58
3.8.3
SXT and UXT Sign extend and Zero extend. Syntax

SXTextend{cond} {Rd,} Rm {, ROR #n} UXTextend{cond} {Rd}, Rm {, ROR #n}
where:
extend
Is one of:
B H
Extends an 8-bit value to a 32-bit value. Extends a 16-bit value to a 32-bit value.
cond Rd Rm ROR #n
Is an optional condition code, see Conditional execution on page 3-14. Specifies the destination register. Specifies the register holding the value to extend. Is one of:
ROR #8 ROR #16 ROR #24
Value from Rm is rotated right 8 bits. Value from Rm is rotated right 16 bits. Value from Rm is rotated right 24 bits.
If ROR #n is omitted, no rotation is performed. Operation These instructions do the following: 1. 2. Rotate the value from Rm right by 0, 8, 16 or 24 bits. Extract bits from the resulting value: SXTB extracts bits[7:0] and sign extends to 32 bits. UXTB extracts bits[7:0] and zero extends to 32 bits. SXTH extracts bits[15:0] and sign extends to 32 bits. UXTH extracts bits[15:0] and zero extends to 32 bits.
Restrictions Do not use SP and do not use PC. Condition flags These instructions do not affect the flags. Examples
SXTH R4, R6, ROR #16 ; ; ; ; ; Rotate R6 right by 16 bits, then obtain the lower halfword of the result and then sign extend to 32 bits and write the result to R4. Extract lowest byte of the value in R10 and zero extend it, and write the result to R3.
UXTB
R3, R10
3-59
3.9
Branch and control instructions

Table 3-11 shows the branch and control instructions.
Table 3-11 Branch and control instructions Mnemonic
B BL BLX BX CBNZ CBZ IT TBB TBH
Brief description Branch Branch with Link Branch indirect with Link Branch indirect Compare and Branch if Non Zero Compare and Branch if Zero If-Then Table Branch Byte Table Branch Halfword
See B, BL, BX, and BLX on page 3-61 B, BL, BX, and BLX on page 3-61 B, BL, BX, and BLX on page 3-61 B, BL, BX, and BLX on page 3-61 CBZ and CBNZ on page 3-63 CBZ and CBNZ on page 3-63 IT on page 3-64 TBB and TBH on page 3-66 TBB and TBH on page 3-66
3-60
3.9.1
B, BL, BX, and BLX Branch instructions. Syntax

B{cond} label BL{cond} label BX{cond} Rm BLX{cond} Rm
where:
B BL BX BLX cond label Rm
Is a branch (immediate). Is a branch with link (immediate). Is a branch indirect (register). Is a branch indirect with link (register). Is an optional condition code, see Conditional execution on page 3-14. Is a PC-relative expression. See PC-relative expressions on page 3-13. Is a register that indicates an address to branch to. Bit[0] of the value in Rm must be 1, but the address to branch to is created by changing bit[0] to 0.
Operation All these instructions cause a branch to label, or to the address indicated in Rm. In addition: The BL and BLX instructions write the address of the next instruction to LR (the link register, R14). The BX and BLX instructions result in a UsageFault exception if bit[0] of Rm is 0.
Bcond label is the only conditional instruction that can be either inside or outside an IT block. All other branch instructions can only be conditional inside an IT block, and are always unconditional otherwise, see IT on page 3-64.
Table 3-12 shows the ranges for the various branch instructions.
Table 3-12 Branch ranges Instruction
B label Bcond label (outside IT block) Bcond label (inside IT block) BL{cond} label BX{cond} Rm BLX{cond} Rm
Branch range 16 MB to +16 MB 1 MB to +1 MB 16 MB to +16 MB 16 MB to +16 MB Any value in register Any value in register
3-61
Note You might have to use the .W suffix to get the maximum branch range. See Instruction width selection on page 3-16.
Restrictions The restrictions are: do not use PC in the BLX instruction for BX and BLX, bit[0] of Rm must be 1 for correct execution but a branch occurs to the target address created by changing bit[0] to 0 when any of these instructions is inside an IT block, it must be the last instruction of the IT block.
Note Bcond is the only conditional instruction that is not required to be inside an IT block. However, it has a longer branch range when it is inside an IT block.

B BLE B.W BEQ BEQ.W BL BX BXNE BLX loopA ng target target target funC LR R0 R0 ; ; ; ; ; ; ; ; ; ; ; Branch to loopA Conditionally branch to label ng Branch to target within 16MB range Conditionally branch to target Conditionally branch to target within 1MB Branch with link (Call) to function funC, return address stored in LR Return from function call Conditionally branch to address stored in R0 Branch with link and exchange (Call) to a address stored in R0.
3-62
3.9.2
CBZ and CBNZ Compare and Branch on Zero, Compare and Branch on Non-Zero. Syntax
CBZ Rn, label CBNZ Rn, label
where:
Rn label
Specifies the register holding the operand. Specifies the branch destination.
Operation Use the CBZ or CBNZ instructions to avoid changing the condition code flags and to reduce the number of instructions.
CBZ Rn, label does not change condition flags but is otherwise equivalent to: CMP BEQ Rn, #0 label
CBNZ Rn, label does not change condition flags but is otherwise equivalent to: CMP BNE Rn, #0 label
Restrictions The restrictions are: Rn must be in the range of R0 to R7 the branch destination must be within 4 to 130 bytes after the instruction these instructions must not be used inside an IT block. Condition flags These instructions do not change the flags. Examples
CBZ CBNZ R5, target ; Forward branch if R5 is zero R0, target ; Forward branch if R0 is not zero.
3-63
3.9.3
IT If-Then condition instruction. Syntax

IT{x{y{z}}} cond
where:
x y z cond
specifies the condition switch for the second instruction in the IT block. specifies the condition switch for the third instruction in the IT block. specifies the condition switch for the fourth instruction in the IT block. specifies the condition for the first instruction in the IT block.
The condition switch for the second, third and fourth instruction in the IT block can be either: T Then. Applies the condition cond to the instruction. E Else. Applies the inverse condition of cond to the instruction. Note It is possible to use AL (the always condition) for cond in an IT instruction. If this is done, all of the instructions in the IT block must be unconditional, and each of x, y, and z must be T or omitted but not E.
Operation The IT instruction makes up to four following instructions conditional. The conditions can be all the same, or some of them can be the logical inverse of the others. The conditional instructions following the IT instruction form the IT block. The instructions in the IT block, including any branches, must specify the condition in the
{cond} part of their syntax.
Note Your assembler might be able to generate the required IT instructions for conditional instructions automatically, so that you do not need to write them yourself. See your assembler documentation for details. A BKPT instruction in an IT block is always executed, even if its condition fails. Exceptions can be taken between an IT instruction and the corresponding IT block, or within an IT block. Such an exception results in entry to the appropriate exception handler, with suitable return information in LR and stacked PSR. Instructions designed for use for exception returns can be used as normal to return from the exception, and execution of the IT block resumes correctly. This is the only way that a PC-modifying instruction is permitted to branch to an instruction in an IT block. Restrictions The following instructions are not permitted in an IT block: IT CBZ and CBNZ CPSID and CPSIE MOVS.N Rd,Rm.
3-64
Other restrictions when using an IT block are: a branch or any instruction that modifies the PC must either be outside an IT block or must be the last instruction inside the IT block. These are: ADD PC, PC, Rm MOV PC, Rm B, BL, BX, BLX any LDM, LDR, or POP instruction that writes to the PC TBB and TBH do not branch to any instruction inside an IT block, except when returning from an exception handler all conditional instructions except Bcond must be inside an IT block. Bcond can be either outside or inside an IT block but has a larger branch range if it is inside one each instruction inside the IT block must specify a condition code suffix that is either the same or logical inverse as for the other instructions in the block.
Note Your assembler might place extra restrictions on the use of IT blocks, such as prohibiting the use of assembler directives within them.
Condition flags This instruction does not change the flags. Example
ITTE ANDNE ADDSNE MOVEQ NE R0, R0, R1 R2, R2, #1 R2, R3 ; ; ; ; Next 3 instructions are conditional ANDNE does not update condition flags ADDSNE updates condition flags Conditional move
CMP ITE ADDGT ADDLE
R0, #9 GT R1, R0, #55 R1, R0, #48
; ; ; ; ;
Convert R0 hex value (0 to 15) into ASCII ('0'-'9', 'A'-'F') Next 2 instructions are conditional Convert 0xA -> 'A' Convert 0x0 -> '0'
IT ADDGT
GT R1, R1, #1
; IT block with only one conditional instruction ; Increment R1 conditionally
ITTEE MOVEQ ADDEQ ANDNE BNE.W
EQ R0, R1 R2, R2, #10 R3, R3, #1 dloop
; ; ; ; ; ;
Next 4 instructions are conditional Conditional move Conditional add Conditional AND Branch instruction can only be used in the last instruction of an IT block
IT ADD
NE R0, R0, R1
; Next instruction is conditional ; Syntax error: no condition code used in IT block.
3-65
3.9.4
TBB and TBH Table Branch Byte and Table Branch Halfword. Syntax
TBB [Rn, Rm] TBH [Rn, Rm, LSL #1]
where:
Rn
Specifies the register containing the address of the table of branch lengths. If Rn is PC, then the address of the table is the address of the byte immediately following the TBB or TBH instruction.
Rm
Specifies the index register. This contains an index into the table. For halfword tables, LSL #1 doubles the value in Rm to form the right offset into the table.
Operation These instructions cause a PC-relative forward branch using a table of single byte offsets for TBB, or halfword offsets for TBH. Rn provides a pointer to the table, and Rm supplies an index into the table. For TBB the branch offset is twice the unsigned value of the byte returned from the table. and for TBH the branch offset is twice the unsigned value of the halfword returned from the table. The branch occurs to the address at that offset from the address of the byte immediately after the TBB or TBH instruction. Restrictions The restrictions are: Rn must not be SP Rm must not be SP and must not be PC when any of these instructions is used inside an IT block, it must be the last instruction of the IT block. Condition flags These instructions do not change the flags.
3-66
Examples
ADR.W R0, BranchTable_Byte TBB [R0, R1] ; R1 is the index, R0 is the base address of the ; branch table Case1 ; an instruction sequence follows Case2 ; an instruction sequence follows Case3 ; an instruction sequence follows BranchTable_Byte DCB 0 ; Case1 offset calculation DCB ((Case2-Case1)/2) ; Case2 offset calculation DCB ((Case3-Case1)/2) ; Case3 offset calculation
TBH
[PC, R1, LSL #1]
; R1 is the index, PC is used as base of the ; branch table ; CaseA offset calculation ; CaseB offset calculation ; CaseC offset calculation
BranchTable_H DCI ((CaseA - BranchTable_H)/2) DCI ((CaseB - BranchTable_H)/2) DCI ((CaseC - BranchTable_H)/2) CaseA ; an instruction sequence follows CaseB ; an instruction sequence follows CaseC ; an instruction sequence follows
3-67
3.10
Miscellaneous instructions
Table 3-13 shows the remaining Cortex-M3 instructions.
Table 3-13 Miscellaneous instructions Mnemonic
BKPT CPSID CPSIE DMB DSB ISB MRS MSR NOP SEV SVC WFE WFI
Brief description Breakpoint Change Processor State, Disable Interrupts Change Processor State, Enable Interrupts Data Memory Barrier Data Synchronization Barrier Instruction Synchronization Barrier Move from special register to register Move from register to special register No Operation Send Event Supervisor Call Wait For Event Wait For Interrupt
See BKPT on page 3-69 CPS on page 3-70 CPS on page 3-70 DMB on page 3-71 DSB on page 3-72 ISB on page 3-73 MRS on page 3-74 MSR on page 3-75 NOP on page 3-76 SEV on page 3-77 SVC on page 3-78 WFE on page 3-79 WFI on page 3-80
3-68
3.10.1
BKPT Breakpoint. Syntax

BKPT #imm
where:
imm
is an expression evaluating to an integer in the range 0-255 (8-bit value).
Operation The BKPT instruction causes the processor to enter Debug state. Debug tools can use this to investigate system state when the instruction at a particular address is reached.
imm is ignored by the processor. If required, a debugger can use it to store additional information
about the breakpoint. The BKPT instruction can be placed inside an IT block, but it executes unconditionally, unaffected by the condition specified by the IT instruction. Condition flags This instruction does not change the flags. Examples
BKPT #0x3 ; Breakpoint with immediate value set to 0x3 (debugger can ; extract the immediate value by locating it using the PC)
Note ARM does not recommend the use of the BKPT instruction with an immediate value set to 0xAB for any purpose other than Semi-hosting.
3-69
3.10.2
CPS Change Processor State. Syntax

CPSeffect iflags
where:
effect
Is one of:
IE ID
Clears the special purpose register. Sets the special purpose register.
iflags
Is a sequence of one or more flags: i Set or clear PRIMASK. f Set or clear FAULTMASK.
Operation
CPS changes the PRIMASK and FAULTMASK special register values. See Exception mask
registers on page 2-7 for more information about these registers. Restrictions The restrictions are: use CPS only from privileged software, it has no effect if used in unprivileged software CPS cannot be conditional and so must not be used inside an IT block. Condition flags This instruction does not change the condition flags. Examples
CPSID CPSID CPSIE CPSIE i f i f ; ; ; ; Disable interrupts and configurable fault handlers (set PRIMASK) Disable interrupts and all fault handlers (set FAULTMASK) Enable interrupts and configurable fault handlers (clear PRIMASK) Enable interrupts and fault handlers (clear FAULTMASK).
3-70
3.10.3
DMB Data Memory Barrier. Syntax

DMB{cond}
where:
cond
Operation
DMB acts as a data memory barrier. It ensures that all explicit memory accesses that appear, in program order, before the DMB instruction are completed before any explicit memory accesses that appear, in program order, after the DMB instruction. DMB does not affect the ordering or
execution of instructions that do not access memory. Condition flags This instruction does not change the flags. Examples
DMB ; Data Memory Barrier
3-71
3.10.4
DSB Data Synchronization Barrier. Syntax

DSB{cond}
where:
cond
Operation
DSB acts as a special data synchronization memory barrier. Instructions that come after the DSB, in program order, do not execute until the DSB instruction completes. The DSB instruction completes when all explicit memory accesses before it complete.
DSB ; Data Synchronisation Barrier
3-72
3.10.5
ISB Instruction Synchronization Barrier. Syntax

ISB{cond}
where:
cond
Operation
ISB acts as an instruction synchronization barrier. It flushes the pipeline of the processor, so that all instructions following the ISB are fetched from cache or memory again, after the ISB
instruction has been completed. Condition flags This instruction does not change the flags. Examples
ISB ; Instruction Synchronisation Barrier
3-73
3.10.6
MRS Move the contents of a special register to a general-purpose register. Syntax

MRS{cond} Rd, spec_reg
where:
cond Rd spec_reg
Is an optional condition code, see Conditional execution on page 3-14. Specifies the destination register. can be any of: APSR, IPSR, EPSR, IEPSR, IAPSR, EAPSR, PSR, MSP, PSP, PRIMASK, BASEPRI, BASEPRI_MAX, FAULTMASK, or CONTROL. Note All the EPSR and IPSR fields are zero when read by the MRS instruction.
Operation Use MRS in combination with MSR as part of a read-modify-write sequence for updating a PSR, for example to clear the Q flag. Note BASEPRI_MAX is an alias of BASEPRI when used with the MRS instruction. See MSR on page 3-75. Restrictions
MRS R0, PRIMASK ; Read PRIMASK value and write it to R0.
3-74
3.10.7
MSR Move the contents of a general-purpose register into the specified special register. Syntax
MSR{cond} spec_reg, Rn
where:
cond Rn spec_reg
Is an optional condition code, see Conditional execution on page 3-14. Specifies the source register. can be any of: APSR, IPSR, EPSR, IEPSR, IAPSR, EAPSR, PSR, MSP, PSP, PRIMASK, BASEPRI, BASEPRI_MAX, FAULTMASK, or CONTROL. Note The processor ignores MSR writes to the EPSR and IPSR fields.
Operation The register access operation in MSR depends on the privilege level. Unprivileged software can only access the APSR, see Table 2-4 on page 2-5. Privileged software can access all special registers. In unprivileged software writes to unallocated or execution state bits in the PSR are ignored. Note When you write to BASEPRI_MAX, the instruction writes to BASEPRI only if either: Rn is non-zero and the current BASEPRI value is 0 Rn is non-zero and less than the current BASEPRI value. See MRS on page 3-74. Restrictions
Rn must not be SP and must not be PC.
Condition flags This instruction updates the flags explicitly based on the value in Rn. Examples
MSR CONTROL, R1 ; Read R1 value and write it to the CONTROL register.
3-75
3.10.8
NOP No Operation. Syntax

NOP{cond}
where:
cond
Operation
NOP does nothing. NOP is not necessarily a time-consuming NOP. The processor might remove it from the pipeline before it reaches the execution stage.
Use NOP for padding, for example to adjust the alignment of a following instruction. Condition flags This instruction does not change the flags. Examples
NOP ; No operation
3-76
3.10.9
SEV Send Event. Syntax

SEV{cond}
where:
cond
Operation
SEV is a hint instruction that causes an event to be signaled to all processors within a
multiprocessor system. It also sets the local event register to 1, see Power management on page 2-31. Condition flags This instruction does not change the flags. Examples
SEV ; Send Event
3-77
3.10.10 SVC Supervisor Call. Syntax

SVC{cond} #imm
where:
cond imm
Is an optional condition code, see Conditional execution on page 3-14. Is an expression evaluating to an integer in the range 0-255 (8-bit value).
Operation The SVC instruction causes the SVC exception.

imm is ignored by the processor. If required, it can be retrieved by the exception handler to
determine what service is being requested. Condition flags This instruction does not change the flags. Examples
SVC #0x32 ; Supervisor Call (SVCall handler can extract the immediate value ; by locating it via the stacked PC)
3-78
3.10.11 WFE Wait For Event. Syntax

WFE{cond}
where:
cond
Operation
WFE is a hint instruction.
If the event register is 0, WFE suspends execution until one of the following events occurs: an exception, unless masked by the exception mask registers or the current priority level an exception enters the Pending state, if SEVONPEND in the System Control Register is set a Debug Entry request, if Debug is enabled an event signaled by a peripheral or another processor in a multiprocessor system using the SEV instruction.
If the event register is 1, WFE clears it to 0 and returns immediately. For more information see Power management on page 2-31. Condition flags This instruction does not change the flags. Examples
WFE ; Wait For Event
3-79
3.10.12 WFI Wait For Interrupt. Syntax

WFI{cond}
where:
cond
Operation
WFI is a hint instruction that suspends execution until one of the following events occurs:
a non-masked interrupt occurs and is taken an interrupt masked by PRIMASK becomes pending a Debug Entry request.
WFI ; Wait For Interrupt
3-80
Chapter 4 Cortex-M3 Peripherals
This chapter describes the ARM Cortex-M3 core peripherals. It contains the following sections: About the Cortex-M3 peripherals on page 4-2 Nested Vectored Interrupt Controller on page 4-3 System control block on page 4-11 System timer, SysTick on page 4-33. Optional Memory Protection Unit on page 4-37.
4-1
4.1
About the Cortex-M3 peripherals

Table 4-1 shows the address map of the Private Peripheral Bus (PPB).
Table 4-1 Core peripheral register regions Address
0xE000E008-0xE000E00F 0xE000E010-0xE000E01F 0xE000E100-0xE000E4EF 0xE000ED00-0xE000ED3F 0xE000ED90-0xE000ED93 0xE000ED90-0xE000EDB8 0xE000EF00-0xE000EF03
Core peripheral System control block System timer Nested Vectored Interrupt Controller System control block MPU Type Register Memory Protection Unit Nested Vectored Interrupt Controller
Description Table 4-12 on page 4-11 Table 4-32 on page 4-33 Table 4-2 on page 4-3 Table 4-12 on page 4-11 Reads as zero, indicating MPU is not implemented a Table 4-38 on page 4-38 Table 4-2 on page 4-3
a. Software can read the MPU Type Register at 0xE000ED90 to test for the presence of a Memory Protection Unit (MPU)
In register descriptions: the register type is described as follows: RW Read and write. RO Read-only. WO Write-only. the required privilege gives the privilege level required to access the register, as follows: Privileged Only privileged software can access the register. Unprivileged Both unprivileged and privileged software can access the register.
4-2
4.2
Nested Vectored Interrupt Controller

This section describes the NVIC and the registers it uses. The NVIC supports: An implementation-defined number of interrupts, in the range 1-240 interrupts. A programmable priority level of 0-255 for each interrupt. A higher level corresponds to a lower priority, so level 0 is the highest interrupt priority. Level and pulse detection of interrupt signals. Dynamic reprioritization of interrupts. Grouping of priority values into group priority and subpriority fields. Interrupt tail-chaining. An external Non-Maskable Interrupt (NMI) Optional WIC, providing ultra-low power sleep mode support.
The processor automatically stacks its state on exception entry and unstacks this state on exception exit, with no instruction overhead. This provides low latency exception handling. Table 4-2 shows the hardware implementation of the NVIC registers.
Table 4-2 NVIC register summary Address
0xE000E1000xE000E11C 0XE000E1800xE000E19C 0XE000E2000xE000E21C 0XE000E2800xE000E29C 0xE000E3000xE000E31C 0xE000E4000xE000E4EF 0xE000EF00
Name NVIC_ISER0NVIC_ISER7 NVIC_ICER0NVIC_ICER7 NVIC_ISPR0NVIC_ISPR7 NVIC_ICPR0NVIC_ICPR7 NVIC_IABR0NVIC_IABR7 NVIC_IPR0NVIC_IPR59 STIR
Type RW RW RW RW RW RW WO
Required privilege Privileged Privileged Privileged Privileged Privileged Privileged Configurable a
Reset value
0x00000000
Description Interrupt Set-enable Registers on page 4-4 Interrupt Clear-enable Registers on page 4-5 Interrupt Set-pending Registers on page 4-5 Interrupt Clear-pending Registers on page 4-6 Interrupt Active Bit Registers on page 4-7 Interrupt Priority Registers on page 4-7 Software Trigger Interrupt Register on page 4-8
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
a. See the register description for more information.
4-3
4.2.1
Accessing the Cortex-M3 NVIC registers using CMSIS CMSIS functions enable software portability between different Cortex-M profile processors. To access the NVIC registers when using CMSIS, use the following functions:
Table 4-3 CMSIS access NVIC functions CMSIS function
void NVIC_EnableIRQ(IRQn_Type IRQn)a void NVIC_DisableIRQ(IRQn_Type IRQn)a void NVIC_SetPendingIRQ(IRQn_Type IRQn)a void NVIC_ClearPendingIRQ(IRQn_Type IRQn)a uint32_t NVIC_GetPendingIRQ(IRQn_Type IRQn)a
Description Enables an interrupt or exception. Disables an interrupt or exception. Sets the pending status of interrupt or exception to 1. Clears the pending status of interrupt or exception to 0. Reads the pending status of interrupt or exception. This function returns non-zero value if the pending status is set to 1. Sets the priority of an interrupt or exception with configurable priority level to 1. Reads the priority of an interrupt or exception with configurable priority level. This function return the current priority level.
void NVIC_SetPriority(IRQn_Type IRQn, uint32_t priority)a
uint32_t NVIC_GetPriority(IRQn_Type IRQn)a
a. The input parameter IRQn is the IRQ number, see Table 2-16 on page 2-22 for more information.
4.2.2
Interrupt Set-enable Registers The NVIC_ISER0-NVIC_ISER7 registers enable interrupts, and show which interrupts are enabled. See the register summary in Table 4-2 on page 4-3 for the register attributes. The bit assignments are:
31 SETENA bits 0
Table 4-4 ISER bit assignments Bits [31:0] Name SETENA Function Interrupt set-enable bits. Write: 0 = no effect 1 = enable interrupt. Read: 0 = interrupt disabled 1 = interrupt enabled.
If a pending interrupt is enabled, the NVIC activates the interrupt based on its priority. If an interrupt is not enabled, asserting its interrupt signal changes the interrupt state to pending, but the NVIC never activates the interrupt, regardless of its priority.
4-4
4.2.3
Interrupt Clear-enable Registers The NVIC_ICER0-NVIC_ICER7 registers disable interrupts, and show which interrupts are enabled. See the register summary in Table 4-2 on page 4-3 for the register attributes. The bit assignments are:
31 CLRENA bits 0
Table 4-5 ICER bit assignments Bits [31:0] Name CLRENA Function Interrupt clear-enable bits. Write: 0 = no effect 1 = disable interrupt. Read: 0 = interrupt disabled 1 = interrupt enabled.
4.2.4
Interrupt Set-pending Registers The NVIC_ISPR0-NVIC_ISPR7 registers force interrupts into the pending state, and show which interrupts are pending. See the register summary in Table 4-2 on page 4-3 for the register attributes. The bit assignments are:
31 SETPEND bits 0
Table 4-6 ISPR bit assignments Bits [31:0] Name SETPEND Function Interrupt set-pending bits. Write: 0 = no effect 1 = changes interrupt state to pending. Read: 0 = interrupt is not pending 1 = interrupt is pending.
Note Writing 1 to the ISPR bit corresponding to: an interrupt that is pending has no effect a disabled interrupt sets the state of that interrupt to pending.
4-5
4.2.5
Interrupt Clear-pending Registers The NVIC_ICPR0-NCVIC_ICPR7 registers remove the pending state from interrupts, and show which interrupts are pending. See the register summary in Table 4-2 on page 4-3 for the register attributes. The bit assignments are:
31 CLRPEND bits 0
Table 4-7 ICPR bit assignments Bits [31:0] Name CLRPEND Function Interrupt clear-pending bits. Write: 0 = no effect 1 = removes pending state an interrupt. Read: 0 = interrupt is not pending 1 = interrupt is pending.
Note Writing 1 to an ICPR bit does not affect the active state of the corresponding interrupt.
4-6
4.2.6
Interrupt Active Bit Registers The NVIC_IABR0-NVIC_IABR7 registers indicate which interrupts are active. See the register summary in Table 4-2 on page 4-3 for the register attributes. The bit assignments are:
31 ACTIVE bits 0
Table 4-8 IABR bit assignments Bits [31:0] Name ACTIVE Function Interrupt active flags: 0 = interrupt not active 1 = interrupt active.
A bit reads as one if the status of the corresponding interrupt is active or active and pending. 4.2.7 Interrupt Priority Registers The NVIC_IPR0-NVIC_IPR59 registers provide an 8-bit priority field for each interrupt and each register holds four priority fields. These registers are byte-accessible. See the register summary in Table 4-2 on page 4-3 for their attributes. Each register holds four priority fields as shown:
31 IPR59
...
24 23 PRI_239 PRI_238
16 15 PRI_237
...
8 7 PRI_236
IPRn
...
PRI_4n+3
PRI_4n+2
...
PRI_4n+1
PRI_4n
IPR0
PRI_3
PRI_2
PRI_1
PRI_0
Table 4-9 IPR bit assignments Bits [31:24] [23:16] [15:8] [7:0] Name Priority, byte offset 3 Priority, byte offset 2 Priority, byte offset 1 Priority, byte offset 0 Function Each implementation-defined priority field can hold a priority value, 0-255. The lower the value, the greater the priority of the corresponding interrupt. Register priority value fields are 8 bits wide, and un-implemented low-order bits read as zero and ignore writes.
See Accessing the Cortex-M3 NVIC registers using CMSIS on page 4-4 for more information about the access to the interrupt priority array, which provides the software view of the interrupt priorities.
4-7
Find the IPR number and byte offset for interrupt m as follows: the corresponding IPR number, see Table 4-8 on page 4-7 n is given by n = m DIV 4 the byte offset of the required Priority field in this register is m MOD 4, where: byte offset 0 refers to register bits[7:0] byte offset 1 refers to register bits[15:8] byte offset 2 refers to register bits[23:16] byte offset 3 refers to register bits[31:24]. 4.2.8 Software Trigger Interrupt Register Write to the STIR to generate an interrupt from software. See the register summary in Table 4-2 on page 4-3 for the STIR attributes. When the USERSETMPEND bit in the SCR is set to 1, unprivileged software can access the STIR, see System Control Register on page 4-19. Note Only privileged software can enable unprivileged access to the STIR. The bit assignments are:
31 Reserved 9 8 INTID 0
Table 4-10 STIR bit assignments Bits [31:9] [8:0] Field INTID Function Reserved. Interrupt ID of the interrupt to trigger, in the range 0-239. For example, a value of 0x03 specifies interrupt IRQ3.
4.2.9
Level-sensitive and pulse interrupts A Cortex-M3 device can support both level-sensitive and pulse interrupts. Pulse interrupts are also described as edge-triggered interrupts. A level-sensitive interrupt is held asserted until the peripheral deasserts the interrupt signal. Typically this happens because the ISR accesses the peripheral, causing it to clear the interrupt request. A pulse interrupt is an interrupt signal sampled synchronously on the rising edge of the processor clock. To ensure the NVIC detects the interrupt, the peripheral must assert the interrupt signal for at least one clock cycle, during which the NVIC detects the pulse and latches the interrupt. When the processor enters the ISR, it automatically removes the pending state from the interrupt, see Hardware and software control of interrupts on page 4-9. For a level-sensitive interrupt, if the signal is not deasserted before the processor returns from the ISR, the interrupt becomes pending again, and the processor must execute its ISR again. This means that the peripheral can hold the interrupt signal asserted until it no longer requires servicing. See the documentation supplied by your device vendor for details of which interrupts are level-based and which are pulsed.
4-8
Hardware and software control of interrupts The Cortex-M3 latches all interrupts. A peripheral interrupt becomes pending for one of the following reasons: the NVIC detects that the interrupt signal is HIGH and the interrupt is not active the NVIC detects a rising edge on the interrupt signal software writes to the corresponding interrupt set-pending register bit, see Interrupt Set-pending Registers on page 4-5, or to the STIR to make an interrupt pending, see Software Trigger Interrupt Register on page 4-8.
A pending interrupt remains pending until one of the following: The processor enters the ISR for the interrupt. This changes the state of the interrupt from pending to active. Then: For a level-sensitive interrupt, when the processor returns from the ISR, the NVIC samples the interrupt signal. If the signal is asserted, the state of the interrupt changes to pending, which might cause the processor to immediately re-enter the ISR. Otherwise, the state of the interrupt changes to inactive. For a pulse interrupt, the NVIC continues to monitor the interrupt signal, and if this is pulsed the state of the interrupt changes to pending and active. In this case, when the processor returns from the ISR the state of the interrupt changes to pending, which might cause the processor to immediately re-enter the ISR. If the interrupt signal is not pulsed while the processor is in the ISR, when the processor returns from the ISR the state of the interrupt changes to inactive.
Software writes to the corresponding interrupt clear-pending register bit. For a level-sensitive interrupt, if the interrupt signal is still asserted, the state of the interrupt does not change. Otherwise, the state of the interrupt changes to inactive. For a pulse interrupt, state of the interrupt changes to: inactive, if the state was pending active, if the state was active and pending.
4.2.10
NVIC usage hints and tips Ensure software uses correctly aligned register accesses. The processor does not support unaligned accesses to NVIC registers. See the individual register descriptions for the supported access sizes. A interrupt can enter pending state even if it is disabled. Disabling an interrupt only prevents the processor from taking that interrupt. Before programming VTOR to relocate the vector table, ensure the vector table entries of the new vector table are setup for fault handlers, NMI and all enabled exception like interrupts. For more information see Vector Table Offset Register on page 4-16. NVIC programming hints Software uses the CPSIE I and CPSID I instructions to enable and disable interrupts. The CMSIS provides the following intrinsic functions for these instructions:
void __disable_irq(void) // Disable Interrupts void __enable_irq(void) // Enable Interrupts
4-9
In addition, the CMSIS provides a number of functions for NVIC control, including:
Table 4-11 CMSIS functions for NVIC control CMSIS interrupt control function
void NVIC_SetPriorityGrouping(uint32_t priority_grouping) void NVIC_EnableIRQ(IRQn_t IRQn) void NVIC_DisableIRQ(IRQn_t IRQn) uint32_t NVIC_GetPendingIRQ (IRQn_t IRQn) void NVIC_SetPendingIRQ (IRQn_t IRQn) void NVIC_ClearPendingIRQ (IRQn_t IRQn) uint32_t NVIC_GetActive (IRQn_t IRQn) void NVIC_SetPriority (IRQn_t IRQn, uint32_t priority) uint32_t NVIC_GetPriority (IRQn_t IRQn) void NVIC_SystemReset (void)
Description Set the priority grouping Enable IRQn Disable IRQn Return true (IRQ-Number) if IRQn is pending Set IRQn pending Clear IRQn pending status Return the IRQ number of the active interrupt Set priority for IRQn Read priority of IRQn Reset the system
The input parameter IRQn is the IRQ number, see Table 2-16 on page 2-22. For more information about these functions see the CMSIS documentation.
4-10
4.3
System control block

The System control block (SCB) provides system implementation information, and system control. This includes configuration, control, and reporting of the system exceptions. The system control block registers are:
Table 4-12 Summary of the system control block registers
Address
0xE000E008 0xE000ED00 0xE000ED04 0xE000ED08 0xE000ED0C 0xE000ED10 0xE000ED14 0xE000ED18 0xE000ED1C 0xE000ED20 0xE000ED24 0xE000ED28 0xE000ED28 0xE000ED29 0xE000ED2A 0xE000ED2C 0xE000ED34 0xE000ED38 0xE000ED3C
Name ACTLR CPUID ICSR VTOR AIRCR SCR CCR SHPR1 SHPR2 SHPR3 SHCRS CFSR MMSR b BFSR b UFSR b HFSR MMAR BFAR AFSR
Type RW RO RWa RW RW a RW RW RW RW RW RW RW RW RW RW RW RW RW RW
Required privilege Privileged Privileged Privileged Privileged Privileged Privileged Privileged Privileged Privileged Privileged Privileged Privileged Privileged Privileged Privileged Privileged Privileged Privileged Privileged
Reset value
0x00000000 0x412FC230 0x00000000 0x00000000 0xFA050000 0x00000000 0x00000200 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00 0x00 0x0000 0x00000000
Description Auxiliary Control Register CPUID Base Register on page 4-12 Interrupt Control and State Register on page 4-13 Vector Table Offset Register on page 4-16 Application Interrupt and Reset Control Register on page 4-16 System Control Register on page 4-19 Configuration and Control Register on page 4-19 System Handler Priority Register 1 on page 4-21 System Handler Priority Register 2 on page 4-22 System Handler Priority Register 3 on page 4-22 System Handler Control and State Register on page 4-23 Configurable Fault Status Register on page 4-24 MemManage Fault Status Register on page 4-25 BusFault Status Register on page 4-26 UsageFault Status Register on page 4-28 HardFault Status Register on page 4-30 MemManage Fault Address Register on page 4-30 BusFault Address Register on page 4-31 Auxiliary Fault Status Register on page 4-31
Unknown Unknown
0x00000000
a. See the register description for more information. b. A subregister of the CFSR.
4.3.1
Auxiliary Control Register The ACTLR provides disable bits for the following processor functions: IT folding write buffer use for accesses to the default memory map interruption of multi-cycle instructions. By default this register is set to provide optimum performance from the Cortex-M3 processor, and does not normally require modification.
4-11
See the register summary in Table 4-12 on page 4-11 for the ACTLR attributes. The bit assignments are:
31 Reserved 3 2 1 0
DISFOLD DISDEFWBUF DISMCYCINT
Table 4-13 ACTLR bit assignments Bits [31:3] [2] [1] Name DISFOLD DISDEFWBUF Function Reserved When set to 1, disables IT folding. see About IT folding for more information. When set to 1, disables write buffer use during default memory map accesses. This causes all BusFaults to be precise BusFaults but decreases performance because any store to memory must complete before the processor can execute the next instruction.
Note
This bit only affects write buffers implemented in the Cortex-M3 processor. [0] DISMCYCINT When set to 1, disables interruption of load multiple and store multiple instructions. This increases the interrupt latency of the processor because any LDM or STM must complete before the processor can stack the current state and enter the interrupt handler.
About IT folding In some situations, the processor can start executing the first instruction in an IT block while it is still executing the IT instruction. This behavior is called IT folding, and improves performance, However, IT folding can cause jitter in looping. If a task must avoid jitter, set the DISFOLD bit to 1 before executing the task, to disable IT folding. 4.3.2 CPUID Base Register The CPUID register contains the processor part number, version, and implementation information. See the register summary in Table 4-12 on page 4-11 for its attributes. The bit assignments are:
31 Implementer 24 23 20 19 16 15 PartNo 4 3 0
Variant
Constant
Revision
Table 4-14 CPUID register bit assignments Bits [31:24] [23:20] Name Implementer Variant Function Implementer code:
0x41 = ARM
Variant number, the r value in the rnpn product revision identifier: 0x2 = Revision 2
4-12
Table 4-14 CPUID register bit assignments (continued) Bits [19:16] [15:4] [3:0] Name Constant PartNo Revision Function Reads as 0xF Part number of the processor: 0xC23 = Cortex-M3 Revision number, the p value in the rnpn product revision identifier: 0x0 = Patch 0
4.3.3
Interrupt Control and State Register The ICSR: provides: a set-pending bit for the Non-Maskable Interrupt (NMI) exception set-pending and clear-pending bits for the PendSV and SysTick exceptions indicates: the exception number of the exception being processed whether there are preempted active exceptions the exception number of the highest priority pending exception whether any interrupts are pending.
4-13
See the register summary in Table 4-12 on page 4-11, and the Type descriptions in Table 4-15, for the ICSR attributes. The bit assignments are:
31 30 29 28 27 26 25 24 23 22 21 VECTPENDING 12 11 10 9 8 VECTACTIVE 0
ISRPENDING Reserved for Debug Reserved PENDSTCLR PENDSTSET PENDSVCLR PENDSVSET Reserved NMIPENDSET
Reserved RETTOBASE
Table 4-15 ICSR bit assignments Bits [31] Name NMIPENDSET Type RW Function NMI set-pending bit. Write: 0 = no effect1 = changes NMI exception state to pending. Read: 0 = NMI exception is not pending 1 = NMI exception is pending. Because NMI is the highest-priority exception, normally the processor enter the NMI exception handler as soon as it registers a write of 1 to this bit, and entering the handler clears this bit to 0. A read of this bit by the NMI exception handler returns 1 only if the NMI signal is reasserted while the processor is executing that handler. Reserved. PendSV set-pending bit. Write: 0 = no effect 1 = changes PendSV exception state to pending. Read: 0 = PendSV exception is not pending 1 = PendSV exception is pending. Writing 1 to this bit is the only way to set the PendSV exception state to pending. PendSV clear-pending bit. Write: 0 = no effect 1 = removes the pending state from the PendSV exception. SysTick exception set-pending bit. Write: 0 = no effect 1 = changes SysTick exception state to pending. Read: 0 = SysTick exception is not pending 1 = SysTick exception is pending.
[30:29] [28]
PENDSVSET
RW
[27]
PENDSVCLR
WO
[26]
PENDSTSET
RW
4-14
Table 4-15 ICSR bit assignments (continued) Bits [25] Name PENDSTCLR Type WO Function SysTick exception clear-pending bit. Write: 0 = no effect 1 = removes the pending state from the SysTick exception. This bit is WO. On a register read its value is Unknown. Reserved. This bit is reserved for Debug use and reads-as-zero when the processor is not in Debug. Interrupt pending flag, excluding NMI and Faults: 0 = interrupt not pending 1 = interrupt pending. Reserved. Indicates the exception number of the highest priority pending enabled exception: 0 = no pending exceptions Nonzero = the exception number of the highest priority pending enabled exception. The value indicated by this field includes the effect of the BASEPRI and FAULTMASK registers, but not any effect of the PRIMASK register. Indicates whether there are preempted active exceptions: 0 = there are preempted active exceptions to execute 1 = there are no active exceptions, or the currently-executing exception is the only active exception. Reserved. Contains the active exception number: 0 = Thread mode Nonzero = The exception numbera of the currently active exception.
[24] [23] [22]
Reserved for Debug use ISRPENDING
RO RO
[21:18] [17:12]
VECTPENDING
RO
[11]
RETTOBASE
RO
[10:9] [8:0]
VECTACTIVEa
RO
Note
Subtract 16 from this value to obtain the CMSIS IRQ number required to index into the Interrupt Clear-Enable, Set-Enable, Clear-Pending, Set-Pending, or Priority Registers, see Table 2-5 on page 2-6.
a. This is the same value as IPSR bits[8:0], see Interrupt Program Status Register on page 2-6.
When you write to the ICSR, the effect is Unpredictable if you: write 1 to the PENDSVSET bit and write 1 to the PENDSVCLR bit write 1 to the PENDSTSET bit and write 1 to the PENDSTCLR bit.
4-15
4.3.4
Vector Table Offset Register The VTOR indicates the offset of the vector table base address from memory address 0x00000000. See the register summary in Table 4-12 on page 4-11 for its attributes. The bit assignments are:
31 TBLOFF 7 6 Reserved 0
Table 4-16 VTOR bit assignments Bits [31:7] Name TBLOFF Function Vector table base offset field. It contains bits[29:7] of the offset of the table base from the bottom of the memory map.
Note
Bit[29] determines whether the vector table is in the code or SRAM memory region: 0 = code 1 = SRAM. In implementations bit[29] is sometimes called the TBLBASE bit. [6:0] Reserved.
When setting TBLOFF, you must align the offset to the number of exception entries in the vector table. The minimum alignment is 32 words, enough for up to 16 interrupts. For more interrupts, adjust the alignment by rounding up to the next power of two. For example, if you require 21 interrupts, the alignment must be on a 64-word boundary because the required table size is 37 words, and the next power of two is 64. See your vendor documentation for the alignment details for your device. Note Table alignment requirements mean that bits[6:0] of the table offset are always zero.
4.3.5
Application Interrupt and Reset Control Register The AIRCR provides priority grouping control for the exception model, endian status for data accesses, and reset control of the system. See the register summary in Table 4-12 on page 4-11 and Table 4-17 on page 4-17 for its attributes. To write to this register, you must write 0x5FA to the VECTKEY field, otherwise the processor ignores the write.
4-16
The bit assignments are:

31 On read: VECTKEYSTAT On write: VECTKEY ENDIANNESS 16 15 14 11 10 8 7 Reserved 3 2 1 0
Reserved
PRIGROUP
Reserved for Debug use
SYSRESETREQ VECTCLRACTIVE VECTRESET
Table 4-17 AIRCR bit assignments Bits [31:16] Name Write: VECTKEYSTAT Read: VECTKEY ENDIANNESS Type RW Function Register key: Reads as 0xFA05 On writes, write 0x5FA to VECTKEY, otherwise the write is ignored. Data endianness bit is implementation defined: 0 = Little-endian 1 = Big-endian. Reserved Interrupt priority grouping field is implementation defined. This field determines the split of group priority from subpriority, see Binary point on page 4-18. Reserved. System reset request bit is implementation defined: 0 = no system reset request 1 = asserts a signal to the outer system that requests a reset. This is intended to force a large system reset of all major components except for debug. This bit reads as 0. See you vendor documentation for more information about the use of this signal in your implementation. Reserved for Debug use. This bit reads as 0. When writing to the register you must write 0 to this bit, otherwise behavior is Unpredictable. Reserved for Debug use. This bit reads as 0. When writing to the register you must write 0 to this bit, otherwise behavior is Unpredictable.
[15]
RO
[14:11] [10:8]
PRIGROUP
R/W
[7:3] [2]
SYSRESETREQ
WO
[1] [0]
VECTCLRACTIVE VECTRESET
WO WO
4-17
Binary point The PRIGROUP field indicates the position of the binary point that splits the PRI_n fields in the Interrupt Priority Registers into separate group priority and subpriority fields. Table 4-18 shows how the PRIGROUP value controls this split. Implementations having fewer than 8-bits of interrupt priority treat the least significant bits as zero.
Table 4-18 Priority grouping Interrupt priority level value, PRI_N[7:0] PRIGROUP
0b000 0b001 0b010 0b011 0b100 0b101 0b110 0b111
Number of Group priorities 128 64 32 16 8 4 2 1 Subpriorities 2 4 8 16 32 64 128 256
Binary point a bxxxxxxx.y bxxxxxx.yy bxxxxx.yyy bxxxx.yyyy bxxx.yyyyy bxx.yyyyyy bx.yyyyyyy b.yyyyyyyy
Group priority bits [7:1] [7:2] [7:3] [7:4] [7:5] [7:6] [7] None
Subpriority bits [0] [1:0] [2:0] [3:0] [4:0] [5:0] [6:0] [7:0]
a. PRI_n[7:0] field showing the binary point. x denotes a group priority field bit, and y denotes a subpriority field bit.
Note Determining preemption of an exception uses only the group priority field, see Interrupt priority grouping on page 2-25.
4-18
4.3.6
System Control Register The SCR controls features of entry to and exit from low power state. See the register summary in Table 4-12 on page 4-11 for its attributes. The bit assignments are:
31 Reserved 5 4 3 2 1 0
SEVONPEND Reserved SLEEPDEEP SLEEPONEXIT Reserved
Table 4-19 SCR bit assignments Bits [31:5] [4] Name SEVONPEND Function Reserved. Send Event on Pending bit: 0 = only enabled interrupts or events can wakeup the processor, disabled interrupts are excluded 1 = enabled events and all interrupts, including disabled interrupts, can wakeup the processor. When an event or interrupt enters pending state, the event signal wakes up the processor from WFE. If the processor is not waiting for an event, the event is registered and affects the next WFE. The processor also wakes up on execution of an SEV instruction or an external event. Reserved. Controls whether the processor uses sleep or deep sleep as its low power mode: 0 = sleep 1 = deep sleep. Indicates sleep-on-exit when returning from Handler mode to Thread mode: 0 = do not sleep when returning to Thread mode 1 = enter sleep, or deep sleep, on return from an ISR. Setting this bit to 1 enables an interrupt driven application to avoid returning to an empty main application. Reserved.
[3] [2]
SLEEPDEEP
[1]
SLEEPONEXIT
[0]
4.3.7
Configuration and Control Register The CCR controls entry to Thread mode and enables: the handlers for NMI, hard fault and faults escalated by FAULTMASK to ignore BusFaults trapping of divide by zero and unaligned accesses access to the STIR by unprivileged software, see Software Trigger Interrupt Register on page 4-8.
See the register summary in Table 4-12 on page 4-11 for the CCR attributes.
4-19

31 Reserved 10 9 8 7 5 4 3 2 1 0
STKALIGN BFHFNMIGN Reserved DIV_0_TRP UNALIGN_TRP Reserved USERSETMPEND NONBASETHRDENA
Table 4-20 CCR bit assignments Bits [31:10] [9] Name STKALIGN Function Reserved. Indicates stack alignment on exception entry: 0 = 4-byte aligned 1 = 8-byte aligned. On exception entry, the processor uses bit[9] of the stacked PSR to indicate the stack alignment. On return from the exception it uses this stacked bit to restore the correct stack alignment. Enables handlers with priority -1 or -2 to ignore data BusFaults caused by load and store instructions. This applies to the hard fault, NMI, and FAULTMASK escalated handlers: 0 = data bus faults caused by load and store instructions cause a lock-up 1 = handlers running at priority -1 and -2 ignore data bus faults caused by load and store instructions. Set this bit to 1 only when the handler and its data are in absolutely safe memory. The normal use of this bit is to probe system devices and bridges to detect control path problems and fix them. Reserved. Enables faulting or halting when the processor executes an SDIV or UDIV instruction with a divisor of 0: 0 = do not trap divide by 0 1 = trap divide by 0. When this bit is set to 0, a divide by zero returns a quotient of 0. Enables unaligned access traps: 0 = do not trap unaligned halfword and word accesses 1 = trap unaligned halfword and word accesses. If this bit is set to 1, an unaligned access generates a UsageFault. Unaligned LDM, STM, LDRD, and STRD instructions always fault irrespective of whether UNALIGN_TRP is set to 1.
[8]
BFHFNMIGN
[7:5] [4]
DIV_0_TRP
[3]
UNALIGN_TRP
4-20
Table 4-20 CCR bit assignments (continued) Bits [2] [1] Name USERSETMPEND Function Reserved. Enables unprivileged software access to the STIR, see Software Trigger Interrupt Register on page 4-8: 0 = disable 1 = enable. Indicates how the processor enters Thread mode: 0 = processor can enter Thread mode only when no exception is active 1 = processor can enter Thread mode from any level under the control of an EXC_RETURN value, see Exception return on page 2-27.
[0]
NONBASETHRDENA
4.3.8
System Handler Priority Registers The SHPR1-SHPR3 registers set the priority level, 0 to 255, of the exception handlers that have configurable priority. SHPR1-SHPR3 are byte accessible. See the register summary in Table 4-12 on page 4-11 for their attributes. To access to the system exception priority level using CMSIS, use the following CMSIS functions: uint32_t NVIC_GetPriority(IRQn_Type IRQn) void NVIC_SetPriority(IRQn_Type IRQn, uint32_t priority) The input parameter IRQn is the IRQ number, see Table 2-16 on page 2-22 for more information. System Handler Priority Register 1 The bit assignments are:
31 Reserved 24 23 PRI_6 16 15 PRI_5 8 7 PRI_4 0
Table 4-21 SHPR1 register bit assignments Bits [31:24] [23:16] [15:8] [7:0] Name PRI_7 PRI_6 PRI_5 PRI_4 Function Reserved Priority of system handler 6, UsageFault Priority of system handler 5, BusFault Priority of system handler 4, MemManage
4-21
System Handler Priority Register 2 The bit assignments are:

31 PRI_11 24 23 Reserved 0
Table 4-22 SHPR2 register bit assignments Bits [31:24] [23:0] Name PRI_11 Function Priority of system handler 11, SVCall Reserved
System Handler Priority Register 3 The bit assignments are:

31 PRI_15 24 23 PRI_14 16 15 Reserved 0
Table 4-23 SHPR3 register bit assignments Bits [31:24] [23:16] [15:0] Name PRI_15 PRI_14 Function Priority of system handler 15, SysTick exception Priority of system handler 14, PendSV Reserved
4-22
4.3.9
System Handler Control and State Register The SHCSR enables the system handlers, and indicates: the pending status of the BusFault, MemManage fault, and SVC exceptions the active status of the system handlers. See the register summary in Table 4-12 on page 4-11 for the SHCSR attributes. The bit assignments are:
31 Reserved 19 18 17 16 15 14 13 12 11 10 9 8 7 6 4 3 2 1 0
USGFAULTENA BUSFAULTENA MEMFAULTENA SVCALLPENDED BUSFAULTPENDED MEMFAULTPENDED USGFAULTPENDED SYSTICKACT PENDSVACT Reserved MONITORACT SVCALLACT
MEMFAULTACT BUSFAULTACT Reserved USGFAULTACT Reserved
Table 4-24 SHCSR bit assignments Bits [31:19] [18] [17] [16] [15] [14] [13] [12] [11] [10] [9] [8] [7] [6:4] [3] Name USGFAULTENA BUSFAULTENA MEMFAULTENA SVCALLPENDED BUSFAULTPENDED MEMFAULTPENDED USGFAULTPENDED SYSTICKACT PENDSVACT MONITORACT SVCALLACT USGFAULTACT Function Reserved UsageFault enable bit, set to 1 to enable a BusFault enable bit, set to 1 to enable a MemManage enable bit, set to 1 to enable a SVCall pending bit, reads as 1 if exception is pending b BusFault exception pending bit, reads as 1 if exception is pending b MemManage exception pending bit, reads as 1 if exception is pending b UsageFault exception pending bit, reads as 1 if exception is pending b SysTick exception active bit, reads as 1 if exception is active c PendSV exception active bit, reads as 1 if exception is active Reserved Debug monitor active bit, reads as 1 if Debug monitor is active SVCall active bit, reads as 1 if SVC call is active Reserved UsageFault exception active bit, reads as 1 if exception is active
4-23
Table 4-24 SHCSR bit assignments (continued) Bits [2] [1] [0] Name BUSFAULTACT MEMFAULTACT Function Reserved BusFault exception active bit, reads as 1 if exception is active MemManage exception active bit, reads as 1 if exception is active
a. Enable bits, set to 1 to enable the exception, or set to 0 to disable the exception. b. Pending bits, read as 1 if the exception is pending, or as 0 if it is not pending. You can write to these bits to change the pending status of the exceptions. c. Active bits, read as 1 if the exception is active, or as 0 if it is not active. You can write to these bits to change the active status of the exceptions, but see the Caution in this section.
If you disable a system handler and the corresponding fault occurs, the processor treats the fault as a hard fault. You can write to this register to change the pending or active status of system exceptions. An OS kernel can write to the active bits to perform a context switch that changes the current exception type. Caution Software that changes the value of an active bit in this register without correct adjustment to the stacked content can cause the processor to generate a fault exception. Ensure software that writes to this register retains and subsequently restores the current active status. After you have enabled the system handlers, if you have to change the value of a bit in this register you must use a read-modify-write procedure to ensure that you change only the required bit.
4.3.10
Configurable Fault Status Register The CFSR indicates the cause of a MemManage fault, BusFault, or UsageFault. See the register summary in Table 4-12 on page 4-11 for its attributes. The bit assignments are:
31 Usage Fault Status Register 16 15 Bus Fault Status Register 8 7 0
Memory Management Fault Status Register
UFSR
BFSR
MMFSR
The following subsections describe the subregisters that make up the CFSR: MemManage Fault Status Register on page 4-25 BusFault Status Register on page 4-26 UsageFault Status Register on page 4-28. The CFSR is byte accessible. You can access the CFSR or its subregisters as follows: access the complete CFSR with a word access to 0xE000ED28 access the MMFSR with a byte access to 0xE000ED28 access the MMFSR and BFSR with a halfword access to 0xE000ED28 access the BFSR with a byte access to 0xE000ED29 access the UFSR with a halfword access to 0xE000ED2A.
4-24
MemManage Fault Status Register The flags in the MMFSR indicate the cause of memory access faults. The bit assignments are:
7 6 5 4 3 2 1 0
MMARVALID Reserved MSTKERR
IACCVIOL DACCVIOL Reserved MUNSTKERR
Table 4-25 MMFSR bit assignments Bits [7] Name MMARVALID Function MemManage Fault Address Register (MMFAR) valid flag: 0 = value in MMAR is not a valid fault address 1 = MMAR holds a valid fault address. If a MemManage fault occurs and is escalated to a HardFault because of priority, the HardFault handler must set this bit to 0. This prevents problems on return to a stacked active MemManage fault handler whose MMAR value has been overwritten. Reserved. MemManage fault on stacking for exception entry: 0 = no stacking fault 1 = stacking for an exception entry has caused one or more access violations. When this bit is 1, the SP is still adjusted but the values in the context area on the stack might be incorrect. The processor has not written a fault address to the MMAR. MemManage fault on unstacking for a return from exception: 0 = no unstacking fault 1 = unstack for an exception return has caused one or more access violations. This fault is chained to the handler. This means that when this bit is 1, the original return stack is still present. The processor has not adjusted the SP from the failing return, and has not performed a new save. The processor has not written a fault address to the MMAR. Reserved Data access violation flag: 0 = no data access violation fault 1 = the processor attempted a load or store at a location that does not permit the operation. When this bit is 1, the PC value stacked for the exception return points to the faulting instruction. The processor has loaded the MMAR with the address of the attempted access. Instruction access violation flag: 0 = no instruction access violation fault 1 = the processor attempted an instruction fetch from a location that does not permit execution. This fault occurs on any access to an XN region, even when the MPU is disabled or not present. When this bit is 1, the PC value stacked for the exception return points to the faulting instruction. The processor has not written a fault address to the MMAR.
[6:5] [4]
MSTKERR
[3]
MUNSTKERR
[2] [1]
DACCVIOL
[0]
IACCVIOL
4-25
BusFault Status Register The flags in the BFSR indicate the cause of a bus access fault. The bit assignments are:
7 6 5 4 3 2 1 0
BFARVALID Reserved STKERR
IBUSERR PRECISERR IMPRECISERR UNSTKERR
Table 4-26 BFSR bit assignments Bits [7] Name BFARVALID Function BusFault Address Register (BFAR) valid flag: 0 = value in BFAR is not a valid fault address 1 = BFAR holds a valid fault address. The processor sets this bit to 1 after a BusFault where the address is known. Other faults can set this bit to 0, such as a MemManage fault occurring later. If a BusFault occurs and is escalated to a hard fault because of priority, the hard fault handler must set this bit to 0. This prevents problems if returning to a stacked active BusFault handler whose BFAR value has been overwritten. Reserved. BusFault on stacking for exception entry: 0 = no stacking fault 1 = stacking for an exception entry has caused one or more BusFaults. When the processor sets this bit to 1, the SP is still adjusted but the values in the context area on the stack might be incorrect. The processor does not write a fault address to the BFAR. BusFault on unstacking for a return from exception: 0 = no unstacking fault 1 = unstack for an exception return has caused one or more BusFaults. This fault is chained to the handler. This means that when the processor sets this bit to 1, the original return stack is still present. The processor does not adjust the SP from the failing return, does not performed a new save, and does not write a fault address to the BFAR.
[6:5] [4]
STKERR
[3]
UNSTKERR
4-26
Table 4-26 BFSR bit assignments (continued) Bits [2] Name IMPRECISERR Function Imprecise data bus error: 0 = no imprecise data bus error 1 = a data bus error has occurred, but the return address in the stack frame is not related to the instruction that caused the error. When the processor sets this bit to 1, it does not write a fault address to the BFAR. This is an asynchronous fault. Therefore, if it is detected when the priority of the current process is higher than the BusFault priority, the BusFault becomes pending and becomes active only when the processor returns from all higher priority processes. If a precise fault occurs before the processor enters the handler for the imprecise BusFault, the handler detects both IMPRECISERR set to 1 and one of the precise fault status bits set to 1. Precise data bus error: 0 = no precise data bus error 1 = a data bus error has occurred, and the PC value stacked for the exception return points to the instruction that caused the fault. When the processor sets this bit is 1, it writes the faulting address to the BFAR. Instruction bus error: 0 = no instruction bus error 1 = instruction bus error. The processor detects the instruction bus error on prefetching an instruction, but it sets the IBUSERR flag to 1 only if it attempts to issue the faulting instruction. When the processor sets this bit is 1, it does not write a fault address to the BFAR.
[1]
PRECISERR
[0]
IBUSERR
4-27
UsageFault Status Register The UFSR indicates the cause of a UsageFault. The bit assignments are:
15 Reserved 10 9 8 7 4 3 2 1 0
Reserved
DIVBYZERO UNALIGNED
NOCP INVPC INVSTATE UNDEFINSTR
Table 4-27 UFSR bit assignments Bits [15:10] [9] Name DIVBYZERO Function Reserved. Divide by zero UsageFault: 0 = no divide by zero fault, or divide by zero trapping not enabled 1 = the processor has executed an SDIV or UDIV instruction with a divisor of 0. When the processor sets this bit to 1, the PC value stacked for the exception return points to the instruction that performed the divide by zero. Enable trapping of divide by zero by setting the DIV_0_TRP bit in the CCR to 1, see Configuration and Control Register on page 4-19. Unaligned access UsageFault: 0 = no unaligned access fault, or unaligned access trapping not enabled 1 = the processor has made an unaligned memory access. Enable trapping of unaligned accesses by setting the UNALIGN_TRP bit in the CCR to 1, see Configuration and Control Register on page 4-19. Unaligned LDM, STM, LDRD, and STRD instructions always fault irrespective of the setting of UNALIGN_TRP. Reserved. No coprocessor UsageFault. The processor does not support coprocessor instructions: 0 = no UsageFault caused by attempting to access a coprocessor 1 = the processor has attempted to access a coprocessor.
[8]
UNALIGNED
[7:4] [3]
NOCP
4-28
Table 4-27 UFSR bit assignments (continued) Bits [2] Name INVPC Function Invalid PC load UsageFault, caused by an invalid PC load by EXC_RETURN: 0 = no invalid PC load UsageFault 1 = the processor has attempted an illegal load of EXC_RETURN to the PC, as a result of an invalid context, or an invalid EXC_RETURN value. When this bit is set to 1, the PC value stacked for the exception return points to the instruction that tried to perform the illegal load of the PC. Invalid state UsageFault: 0 = no invalid state UsageFault 1 = the processor has attempted to execute an instruction that makes illegal use of the EPSR. When this bit is set to 1, the PC value stacked for the exception return points to the instruction that attempted the illegal use of the EPSR. This bit is not set to 1 if an undefined instruction uses the EPSR. Undefined instruction UsageFault: 0 = no undefined instruction UsageFault 1 = the processor has attempted to execute an undefined instruction. When this bit is set to 1, the PC value stacked for the exception return points to the undefined instruction. An undefined instruction is an instruction that the processor cannot decode.
[1]
INVSTATE
[0]
UNDEFINSTR
Note The UFSR bits are sticky. This means as one or more fault occurs, the associated bits are set to 1. A bit that is set to 1 is cleared to 0 only by writing 1 to that bit, or by a reset.
4-29
4.3.11
HardFault Status Register The HFSR gives information about events that activate the HardFault handler. See the register summary in Table 4-12 on page 4-11 for its attributes. This register is read, write to clear. This means that bits in the register read normally, but writing 1 to any bit clears that bit to 0. The bit assignments are:
31 30 29 Reserved 2 1 0
FORCED DEBUGEVT
VECTTBL Reserved
Table 4-28 HFSR bit assignments Bits [31] [30] Name DEBUGEVT FORCED Function Reserved for Debug use. When writing to the register you must write 0 to this bit, otherwise behavior is Unpredictable. Indicates a forced hard fault, generated by escalation of a fault with configurable priority that cannot be handles, either because of priority or because it is disabled: 0 = no forced HardFault 1 = forced HardFault. When this bit is set to 1, the HardFault handler must read the other fault status registers to find the cause of the fault. Reserved. Indicates a BusFault on a vector table read during exception processing: 0 = no BusFault on vector table read 1 = BusFault on vector table read. This error is always handled by the hard fault handler. When this bit is set to 1, the PC value stacked for the exception return points to the instruction that was preempted by the exception. Reserved.
[29:2] [1]
VECTTBL
[0]
Note The HFSR bits are sticky. This means as one or more fault occurs, the associated bits are set to 1. A bit that is set to 1 is cleared to 0 only by writing 1 to that bit, or by a reset.
4.3.12
MemManage Fault Address Register The MMFAR contains the address of the location that generated a MemManage fault. See the register summary in Table 4-12 on page 4-11 for its attributes. The bit assignments are:
Table 4-29 MMFAR bit assignments Bits [31:0] Name ADDRESS Function When the MMARVALID bit of the MMFSR is set to 1, this field holds the address of the location that generated the MemManage fault
4-30
When an unaligned access faults, the address is the actual address that faulted. Because a single read or write instruction can be split into multiple aligned accesses, the fault address can be any address in the range of the requested access size. Flags in the MMFSR indicate the cause of the fault, and whether the value in the MMFAR is valid. See MemManage Fault Status Register on page 4-25. 4.3.13 BusFault Address Register The BFAR contains the address of the location that generated a BusFault. See the register summary in Table 4-12 on page 4-11 for its attributes. The bit assignments are:
Table 4-30 BFAR bit assignments Bits [31:0] Name ADDRESS Function When the BFARVALID bit of the BFSR is set to 1, this field holds the address of the location that generated the BusFault
When an unaligned access faults the address in the BFAR is the one requested by the instruction, even if it is not the address of the fault. Flags in the BFSR indicate the cause of the fault, and whether the value in the BFAR is valid. See BusFault Status Register on page 4-26. 4.3.14 Auxiliary Fault Status Register The AFSR contains additional system fault information. See the register summary in Table 4-12 on page 4-11 for its attributes. This register is read, write to clear. This means that bits in the register read normally, but writing 1 to any bit clears that bit to 0. The bit assignments are:
Table 4-31 AFSR bit assignments Bits [31:0] Name IMPDEF Function Implementation defined. The bits map to the AUXFAULT input signals.
Each AFSR bit maps directly to an AUXFAULT input of the processor, and a single-cycle HIGH signal on the input sets the corresponding AFSR bit to one. It remains set to 1 until you write 1 to the bit to clear it to zero. See your vendor documentation for more information. When an AFSR bit is latched as one, an exception does not occur. Use an interrupt if an exception is required. 4.3.15 System control block usage hints and tips Ensure software uses aligned accesses of the correct size to access the system control block registers: except for the CFSR and SHPR1-SHPR3, it must use aligned word accesses for the CFSR and SHPR1-SHPR3 it can use byte or aligned halfword or word accesses. The processor does not support unaligned accesses to system control block registers.
4-31
In a fault handler. to determine the true faulting address: 1. 2. Read and save the MMFAR or BFAR value. Read the MMARVALID bit in the MMFSR, or the BFARVALID bit in the BFSR. The MMFAR or BFAR address is valid only if this bit is 1.
Software must follow this sequence because another higher priority exception might change the MMFAR or BFAR value. For example, if a higher priority handler preempts the current fault handler, the other fault might change the MMFAR or BFAR value.
4-32
4.4
System timer, SysTick

The processor has a 24-bit system timer, SysTick, that counts down from the reload value to zero, reloads, that is wraps to, the value in the SYST_RVR register on the next clock edge, then counts down on subsequent clocks. Note When the processor is halted for debugging the counter does not decrement. The system timer registers are:
Table 4-32 System timer registers summary Address
0xE000E010 0xE000E014 0xE000E018 0xE000E01C
Name SYST_CSR SYST_RVR SYST_CVR SYST_CALIB
Type RW RW RW RO
Required privilege Privileged Privileged Privileged Privileged
Reset value
a
Description SysTick Control and Status Register SysTick Reload Value Register on page 4-34 SysTick Current Value Register on page 4-35 SysTick Calibration Value Register on page 4-35
UNKNOWN UNKNOWN
-a
a. See the register description for more information. 4.4.1 SysTick Control and Status Register The SysTick SYST_CSR register enables the SysTick features. The register resets to 0x00000000, or to 0x00000004 if your device does not implement a reference clock. See the register summary in Table 4-32 for its attributes. The bit assignments are:
31 Reserved 17 16 15 Reserved CLKSOURCE TICKINT ENABLE 3 2 1 0 0 0 0
COUNTFLAG
Table 4-33 SysTick SYST_CSR register bit assignments Bits [31:17] [16] [15:3] Name COUNTFLAG Function Reserved. Returns 1 if timer counted to 0 since last time this was read. Reserved.
4-33
Table 4-33 SysTick SYST_CSR register bit assignments (continued) Bits [2] Name CLKSOURCE Function Indicates the clock source: 0 = external clock 1 - processor clock. Enables SysTick exception request: 0 = counting down to zero does not assert the SysTick exception request 1 = counting down to zero asserts the SysTick exception request. Software can use COUNTFLAG to determine if SysTick has ever counted to zero. Enables the counter: 0 = counter disabled 1 = counter enabled.
[1]
TICKINT
[0]
ENABLE
When ENABLE is set to 1, the counter loads the RELOAD value from the SYST_RVR register and then counts down. On reaching 0, it sets the COUNTFLAG to 1 and optionally asserts the SysTick depending on the value of TICKINT. It then loads the RELOAD value again, and begins counting. 4.4.2 SysTick Reload Value Register The SYST_RVR register specifies the start value to load into the SYST_CVR register. See the register summary in Table 4-32 on page 4-33 for its attributes. The bit assignments are:
31 Reserved 24 23 RELOAD 0
Table 4-34 SYST_RVR register bit assignments Bits [31:24] [23:0] Name RELOAD Function Reserved. Value to load into the SYST_CVR register when the counter is enabled and when it reaches 0, see Calculating the RELOAD value.
Calculating the RELOAD value The RELOAD value can be any value in the range 0x00000001-0x00FFFFFF. A start value of 0 is possible, but has no effect because the SysTick exception request and COUNTFLAG are activated when counting from 1 to 0. The RELOAD value is calculated according to its use. For example, to generate a multi-shot timer with a period of N processor clock cycles, use a RELOAD value of N-1. If the SysTick interrupt is required every 100 clock pulses, set RELOAD to 99.
4-34
4.4.3
SysTick Current Value Register The SYST_CVR register contains the current value of the SysTick counter. See the register summary in Table 4-32 on page 4-33 for its attributes. The bit assignments are:
31 Reserved 24 23 CURRENT 0
Table 4-35 SYST_CVR register bit assignments Bits [31:24] [23:0] Name CURRENT Function Reserved. Reads return the current value of the SysTick counter. A write of any value clears the field to 0, and also clears the SYST_CSR COUNTFLAG bit to 0.
4.4.4
SysTick Calibration Value Register The SYST_CALIB register indicates the SysTick calibration properties. See the register summary in Table 4-32 on page 4-33 for its attributes. The reset value of this register is implementation-defined. See the documentation supplied by your device vendor for more information about the meaning of the SYST_CALIB field values. The bit assignments are:
31 30 29 Reserved SKEW NOREF 24 23 TENMS 0
Table 4-36 SYST_CALIB register bit assignments Bits [31] Name NOREF Function Indicates whether the device provides a reference clock to the processor: 0 = reference clock provided 1 = no reference clock provided If your device does not provide a reference clock, the SYST_CSR.CLKSOURCE bit reads-as-one and ignores writes. Indicates whether the TENMS value is exact: 0 = TENMS value is exact 1 = TENMS value is inexact, or not given. An inexact TENMS value can affect the suitability of SysTick as a software real time clock. Reserved. Reload value for 10ms (100Hz) timing, subject to system clock skew errors. If the value reads as zero, the calibration value is not known.
[30]
SKEW
[29:24] [23:0]
TENMS
If calibration information is not known, calculate the calibration value required from the frequency of the processor clock or external clock.
4-35
4.4.5
SysTick usage hints and tips Some implementations stop all the processor clock signals during deep sleep mode. If this happens, the SysTick counter stops. Ensure software uses aligned word accesses to access the SysTick registers. The SysTick counter reload and current value are not initialized by hardware. This means the correct initialization sequence for the SysTick counter is: 1. Program reload value. 2. Clear current value. 3. Program Control and Status register.
4-36
4.5
Optional Memory Protection Unit

This section describes the optional Memory Protection Unit (MPU). The MPU divides the memory map into a number of regions, and defines the location, size, access permissions, and memory attributes of each region. It supports: independent attribute settings for each region overlapping regions export of memory attributes to the system. The memory attributes affect the behavior of memory accesses to the region. The Cortex-M3 MPU defines: eight separate memory regions, 0-7 a background region. When memory regions overlap, a memory access is affected by the attributes of the region with the highest number. For example, the attributes for region 7 take precedence over the attributes of any region that overlaps region 7. The background region has the same memory access attributes as the default memory map, but is accessible from privileged software only. The Cortex-M3 MPU memory map is unified. This means instruction accesses and data accesses have same region settings. If a program accesses a memory location that is prohibited by the MPU, the processor generates a MemManage fault. This causes a fault exception, and might cause termination of the process in an OS environment. In an OS environment, the kernel can update the MPU region setting dynamically based on the process to be executed. Typically, an embedded OS uses the MPU for memory protection. Configuration of MPU regions is based on memory types, see Memory regions, types and attributes on page 2-12. Table 4-37 shows the possible MPU region attributes. These include Shareability and cache behavior attributes are not relevant to most microcontroller implementations. See MPU configuration for a microcontroller on page 4-47 and your vendor documentation for programming guidelines if implemented.
Table 4-37 Memory attributes summary Memory type Strongly- ordered Device Shareability Shared Non-shared Normal Shared Other attributes Non-cacheable Write-through Cacheable Write-back Cacheable Non-cacheable Write-through Cacheable Write-back Cacheable Description All accesses to Strongly-ordered memory occur in program order. All Strongly-ordered regions are assumed to be shared. Memory-mapped peripherals that several processors share. Memory-mapped peripherals that only a single processor uses. Normal memory that is shared between several processors.
Non-shared
Normal memory that only a single processor uses.
4-37
Use the MPU registers to define the MPU regions and their attributes. The MPU registers are:
Table 4-38 MPU registers summary Address
0xE000ED90 0xE000ED94 0xE000ED98 0xE000ED9C 0xE000EDA0 0xE000EDA4
Name MPU_TYPE MPU_CTRL MPU_RNR MPU_RBAR MPU_RASR MPU_RBAR_A1 MPU_RASR_A1 MPU_RBAR_A2 MPU_RASR_A2 MPU_RBAR_A3 MPU_RASR_A3
Type RO RW RW RW RW RW RW RW RW RW RW
Required privilege Privileged Privileged Privileged Privileged Privileged Privileged Privileged Privileged Privileged Privileged Privileged
Reset value
0x00000800 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
Description MPU Type Register MPU Control Register on page 4-39 MPU Region Number Register on page 4-40 MPU Region Base Address Register on page 4-40 MPU Region Attribute and Size Register on page 4-41 Alias of RBAR, see MPU Region Base Address Register on page 4-40 Alias of RASR, see MPU Region Attribute and Size Register on page 4-41 Alias of RBAR, see MPU Region Base Address Register on page 4-40 Alias of RASR, see MPU Region Attribute and Size Register on page 4-41 Alias of RBAR, see MPU Region Base Address Register on page 4-40 Alias of RASR, see MPU Region Attribute and Size Register on page 4-41
0xE000EDA8
0x00000000
0xE000EDAC
0x00000000
0xE000EDB0
0x00000000
0xE000EDB4
0x00000000
0xE000EDB8
0x00000000
4.5.1
MPU Type Register The MPU_TYPE register indicates whether the MPU is present, and if so, how many regions it supports. See the register summary in Table 4-38 for its attributes. The bit assignments are:
31 Reserved 24 23 IREGION 16 15 DREGION 8 7 Reserved 1 0
SEPARATE
Table 4-39 TYPE register bit assignments Bits [31:24] [23:16] [15:8] [7:1] [0] Name IREGION DREGION SEPARATE Function Reserved. Indicates the number of supported MPU instruction regions. Always contains 0x00. The MPU memory map is unified and is described by the DREGION field. Indicates the number of supported MPU data regions: 0x08 = eight MPU regions. Reserved. Indicates support for unified or separate instruction and date memory maps: 0 = unified.
4-38
4.5.2
MPU Control Register The MPU_CTRL register enables: the MPU the default memory map background region the use of the MPU when in the hard fault, Non-maskable Interrupt (NMI), and FAULTMASK escalated handlers.
See the register summary in Table 4-38 on page 4-38 for the MPU_CTRL attributes. The bit assignments are:
31 Reserved 3 2 1 0
PRIVDEFENA HFNMIENA ENABLE
Table 4-40 MPU_CTRL register bit assignments Bits [31:3] [2] Name PRIVDEFENA Function Reserved. Enables privileged software access to the default memory map: 0 = If the MPU is enabled, disables use of the default memory map. Any memory access to a location not covered by any enabled region causes a fault. 1 = If the MPU is enabled, enables use of the default memory map as a background region for privileged software accesses. When enabled, the background region acts as if it is region number -1. Any region that is defined and enabled has priority over this default map. If the MPU is disabled, the processor ignores this bit. Enables the operation of MPU during hard fault, NMI, and FAULTMASK handlers. When the MPU is enabled: 0 = MPU is disabled during hard fault, NMI, and FAULTMASK handlers, regardless of the value of the ENABLE bit 1 = the MPU is enabled during hard fault, NMI, and FAULTMASK handlers. When the MPU is disabled, if this bit is set to 1 the behavior is Unpredictable. Enables the MPU: 0 = MPU disabled 1 = MPU enabled.
[1]
HFNMIENA
[0]
ENABLE
When ENABLE and PRIVDEFENA are both set to 1: For privileged accesses, the default memory map is as described in Memory model on page 2-12. Any access by privileged software that does not address an enabled memory region behaves as defined by the default memory map. Any access by unprivileged software that does not address an enabled memory region causes a MemManage fault.
XN and Strongly-ordered rules always apply to the System Control Space regardless of the value of the ENABLE bit.
4-39
When the ENABLE bit is set to 1, at least one region of the memory map must be enabled for the system to function unless the PRIVDEFENA bit is set to 1. If the PRIVDEFENA bit is set to 1 and no regions are enabled, then only privileged software can operate. When the ENABLE bit is set to 0, the system uses the default memory map. This has the same memory attributes as if the MPU is not implemented, see Table 2-11 on page 2-14. The default memory map applies to accesses from both privileged and unprivileged software. When the MPU is enabled, accesses to the System Control Space and vector table are always permitted. Other areas are accessible based on regions and whether PRIVDEFENA is set to 1. Unless HFNMIENA is set to 1, the MPU is not enabled when the processor is executing the handler for an exception with priority 1 or 2. These priorities are only possible when handling a hard fault or NMI exception, or when FAULTMASK is enabled. Setting the HFNMIENA bit to 1 enables the MPU when operating with these two priorities. 4.5.3 MPU Region Number Register The MPU_RNR selects which memory region is referenced by the MPU_RBAR and MPU_RASR registers. See the register summary in Table 4-38 on page 4-38 for its attributes. The bit assignments are:
31 Reserved 8 7 REGION 0
Table 4-41 MPU_RNR bit assignments Bits [31:8] [7:0] Name REGION Function Reserved. Indicates the MPU region referenced by the MPU_RBAR and MPU_RASR registers. The MPU supports 8 memory regions, so the permitted values of this field are 0-7.
Normally, you write the required region number to this register before accessing the MPU_RBAR or MPU_RASR. However you can change the region number by writing to the MPU RBAR with the VALID bit set to 1, see MPU Region Base Address Register. This write updates the value of the REGION field. 4.5.4 MPU Region Base Address Register The MPU_RBAR defines the base address of the MPU region selected by the MPU_RNR, and can update the value of the MPU_RNR. See the register summary in Table 4-38 on page 4-38 for its attributes.
4-40
Write MPU_RBAR with the VALID bit set to 1 to change the current region number and update the MPU_RNR. The bit assignments are:
31 ADDR N N-1 Reserved 5 4 3 0
REGION
If the region size is 32B, the ADDR field is bits [31:5] and there is no Reserved field
VALID
Table 4-42 MPU_RBAR bit assignments Bits [31:N] [(N-1):5] [4] Name ADDR VALID Function Region base address field. The value of N depends on the region size. For more information see The ADDR field. Reserved. MPU Region Number valid bit: Write: 0 = MPU_RNR not changed, and the processor: updates the base address for the region specified in the MPU_RNR ignores the value of the REGION field 1 = the processor: updates the value of the MPU_RNR to the value of the REGION field updates the base address for the region specified in the REGION field. Always reads as zero. MPU region field: For the behavior on writes, see the description of the VALID field. On reads, returns the current region number, as specified by the RNR.
[3:0]
REGION
The ADDR field The ADDR field is bits[31:N] of the MPU_RBAR. The region size, as specified by the SIZE field in the MPU_RASR, defines the value of N: N = Log2(Region size in bytes), If the region size is configured to 4GB, in the MPU_RASR, there is no valid ADDR field. In this case, the region occupies the complete memory map, and the base address is 0x00000000. The base address is aligned to the size of the region. For example, a 64KB region must be aligned on a multiple of 64KB, for example, at 0x00010000 or 0x00020000. 4.5.5 MPU Region Attribute and Size Register The MPU_RASR defines the region size and memory attributes of the MPU region specified by the MPU_RNR, and enables that region and any subregions. See the register summary in Table 4-38 on page 4-38 for its attributes. MPU_RASR is accessible using word or halfword accesses: the most significant halfword holds the region attributes the least significant halfword holds the region size and the region and subregion enable bits.
4-41

31 29 28 27 26 AP Reserved XN Reserved 24 23 22 21 19 18 17 16 15 S C B SRD Reserved ENABLE 8 7 6 5 SIZE 1 0
TEX Reserved
Table 4-43 MPU_RASR bit assignments Bits [31:29] [28] Name XN Function Reserved. Instruction access disable bit: 0 = instruction fetches enabled 1 = instruction fetches disabled. Reserved. Access permission field, see Table 4-47 on page 4-44. Reserved. Memory access attributes, see Table 4-45 on page 4-43. Shareable bit, see Table 4-45 on page 4-43. Subregion disable bits. For each bit in this field: 0 = corresponding sub-region is enabled 1 = corresponding sub-region is disabled. See Subregions on page 4-46 for more information. Region sizes of 128 bytes and less do not support subregions. When writing the attributes for such a region, write the SRD field as 0x00. Reserved. Specifies the size of the MPU protection region. The minimum permitted value is 3 (0b00010), see See SIZE field values for more information. Region enable bit.
[27] [26:24] [23:22] [21:19, 17, 16] [18] [15:8]
AP TEX, C, B S SRD
[7:6] [5:1] [0]
SIZE ENABLE
For information about access permission, see MPU access permission attributes on page 4-43. SIZE field values The SIZE field defines the size of the MPU memory region specified by the RNR. as follows: (Region size in bytes) = 2(SIZE+1)
4-42
The smallest permitted region size is 32B, corresponding to a SIZE value of 4. Table 4-44 gives example SIZE values, with the corresponding region size and value of N in the MPU_RBAR.
Table 4-44 Example SIZE field values SIZE value
0b00100 (4) 0b01001 (9) 0b10011 (19) 0b11101 (29) 0b11111 (31)
Region size 32B 1KB 1MB 1GB 4GB
Value of N a 5 10 20 30 32
Note Minimum permitted size Maximum possible size
a. In the MPU_RBAR, see MPU Region Base Address Register on page 4-40.
4.5.6
MPU access permission attributes This section describes the MPU access permission attributes. The access permission bits, TEX, C, B, S, AP, and XN, of the RASR, control access to the corresponding memory region. If an access is made to an area of memory without the required permissions, then the MPU generates a permission fault. Table 4-45 shows encodings for the TEX, C, B, and S access permission bits.
Table 4-45 TEX, C, B, and S encoding TEX
0b000
C
0
B
0
S xa xa
0 1
Memory type Strongly-ordered Device Normal
Shareability Shareable Shareable Not shareable Shareable
Other attributes Outer and inner write-through. No write allocate.
1
1 0
Normal
Not shareable Shareable
Outer and inner write-back. No write allocate.
1
0b001 0 0 0
Normal
Not shareable Shareable
Outer and inner noncacheable.
1 1
1 0 1
xa xa
0
Reserved encoding Implementation defined attributes. Normal Not shareable Shareable Device Reserved encoding Reserved encoding Normal Not shareable Shareable Not shareable
Outer and inner write-back. Write and read allocate.
1
0b010 0 0 1 1 0b1BB
xa xa xa
0 1
Nonshared Device. Cached memory, BB = outer policy, AA = inner policy. See Table 4-46 on page 4-44 for the encoding of the AA and BB bits.
xa A
a. The MPU ignores the value of this bit.
4-43
Table 4-46 shows the cache policy for memory attribute encodings with a TEX value is in the range 4-7.
Table 4-46 Cache policy for memory attribute encoding Encoding, AA or BB
0b00 0b01 0b10 0b11
Corresponding cache policy Non-cacheable Write back, write and read allocate Write through, no write allocate Write back, no write allocate
Table 4-47 shows the AP encodings that define the access permissions for privileged and unprivileged software.
Table 4-47 AP encoding AP[2:0] 000 001 010 011 100 101 110 111 Privileged permissions No access RW RW RW Unpredictable RO RO RO Unprivileged permissions No access No access RO RW Unpredictable No access RO RO Description All accesses generate a permission fault Access from privileged software only Writes by unprivileged software generate a permission fault Full access Reserved Reads by privileged software only Read only, by privileged or unprivileged software Read only, by privileged or unprivileged software
4.5.7
MPU mismatch When an access violates the MPU permissions, the processor generates a MemManage fault, see Exceptions and interrupts on page 2-10. The MMFSR indicates the cause of the fault. See MemManage Fault Status Register on page 4-25 for more information.
4.5.8
Updating an MPU region To update the attributes for an MPU region, update the MPU_RNR, MPU_RBAR and MPU_RASR registers. You can program each register separately, or use a multiple-word write to program all of these registers. You can use the MPU_RBAR and MPU_RASR aliases to program up to four regions simultaneously using an STM instruction. Updating an MPU region using separate words Simple code to configure one region:
; R1 = region number ; R2 = size/enable ; R3 = attributes ; R4 = address LDR R0,=MPU_RNR
; 0xE000ED98, MPU region number register
4-44
STR R1, [R0, #0x0] STR R4, [R0, #0x4] STRH R2, [R0, #0x8] STRH R3, [R0, #0xA]
; ; ; ;
Region Region Region Region
Number Base Address Size and Enable Attribute
Disable a region before writing new region settings to the MPU if you have previously enabled the region being changed. For example:
; R1 = region number ; R2 = size/enable ; R3 = attributes ; R4 = address LDR R0,=MPU_RNR STR R1, [R0, #0x0] BIC R2, R2, #1 STRH R2, [R0, #0x8] STR R4, [R0, #0x4] STRH R3, [R0, #0xA] ORR R2, #1 STRH R2, [R0, #0x8]
; ; ; ; ; ; ; ;
0xE000ED98, MPU region number register Region Number Disable Region Size and Enable Region Base Address Region Attribute Enable Region Size and Enable
Software must use memory barrier instructions: before MPU setup if there might be outstanding memory transfers, such as buffered writes, that might be affected by the change in MPU settings after MPU setup if it includes memory transfers that must use the new MPU settings.
However, memory barrier instructions are not required if the MPU setup process starts by entering an exception handler, or is followed by an exception return, because the exception entry and exception return mechanism cause memory barrier behavior. Software does not require any memory barrier instructions during MPU setup, because it accesses the MPU through the PPB, which is a Strongly-Ordered memory region. For example, if you want all of the memory access behavior to take effect immediately after the programming sequence, use a DSB instruction and an ISB instruction. A DSB is required after changing MPU settings, such as at the end of context switch. An ISB is required if the code that programs the MPU region or regions is entered using a branch or call. If the programming sequence is entered using a return from exception, or by taking an exception, then you do not require an ISB. Updating an MPU region using multi-word writes You can program directly using multi-word writes, depending on how the information is divided. Consider the following reprogramming:
; R1 = region number ; R2 = address ; R3 = size, attributes in one LDR R0, =MPU_RNR ; 0xE000ED98, MPU region number register STR R1, [R0, #0x0] ; Region Number STR R2, [R0, #0x4] ; Region Base Address STR R3, [R0, #0x8] ; Region Attribute, Size and Enable
Use an STM instruction to optimize this:

; R1 = region number ; R2 = address ; R3 = size, attributes in one LDR R0, =MPU_RNR ; 0xE000ED98, MPU region number register STM R0, {R1-R3} ; Region Number, address, attribute, size and enable
4-45
You can do this in two words for pre-packed information. This means that the MPU_RBAR contains the required region number and had the VALID bit set to 1, see MPU Region Base Address Register on page 4-40. Use this when the data is statically packed, for example in a boot loader:
; R1 = address and region number in one ; R2 = size and attributes in one LDR R0, =MPU_RBAR ; 0xE000ED9C, MPU Region Base register STR R1, [R0, #0x0] ; Region base address and ; region number combined with VALID (bit 4) set to 1 STR R2, [R0, #0x4] ; Region Attribute, Size and Enable
Subregions Regions of 256 bytes or more are divided into eight equal-sized subregions. Set the corresponding bit in the SRD field of the MPU_RASR to disable a subregion, see MPU Region Attribute and Size Register on page 4-41. The least significant bit of SRD controls the first subregion, and the most significant bit controls the last subregion. Disabling a subregion means another region overlapping the disabled range matches instead. If no other enabled region overlaps the disabled subregion the MPU issues a fault. Regions of 32, 64, and 128 bytes do not support subregions, With regions of these sizes, you must set the SRD field to 0x00, otherwise the MPU behavior is Unpredictable.
Example of SRD use
Two regions with the same base address overlap. Region one is 128KB, and region two is 512KB. To ensure the attributes from region one apply to the first 128KB region, set the SRD field for region two to 0b00000011 to disable the first two subregions, as the figure shows.
Offset from base address 512KB 448KB 384KB 320KB 256KB 192KB 128KB Disabled subregion 64KB Disabled subregion 0 Region 2, with subregions
Region 1
Base address of both regions
4.5.9
MPU usage hints and tips To avoid unexpected behavior, disable the interrupts before updating the attributes of a region that the interrupt handlers might access. Ensure software uses aligned accesses of the correct size to access MPU registers: except for the MPU_RASR, it must use aligned word accesses for the MPU_RASR it can use byte or aligned halfword or word accesses. The processor does not support unaligned accesses to MPU registers. When setting up the MPU, and if the MPU has previously been programmed, disable unused regions to prevent any previous region settings from affecting the new MPU setup.
4-46
MPU configuration for a microcontroller Usually, a microcontroller system has only a single processor and no caches. In such a system, program the MPU as follows:
Table 4-48 Memory region attributes for a microcontroller Memory region Flash memory Internal SRAM External SRAM Peripherals TEX
0b000 0b000 0b000 0b000
C
1 1 1 0
B
0 0 1 1
S
0 1 1 1
Memory type and attributes Normal memory, Non-shareable, write-through Normal memory, Shareable, write-through Normal memory, Shareable, write-back, write-allocate Device memory, Shareable
In most microcontroller implementations, the shareability and cache policy attributes do not affect the system behavior. However, using these settings for the MPU regions can make the application code more portable. The values given are for typical situations. In special systems, such as multiprocessor designs or designs with a separate DMA engine, the shareability attribute might be important. In these cases see the recommendations of the memory device manufacturer.
4-47
Appendix A Cortex-M3 Options
The configuration options for a Cortex-M3 processor implementation are determined by the device manufacturer. This appendix describes what the configuration options are and the affect these have on this book. It contains the following section: Cortex-M3 implementation options on page A-2.
A-1
Cortex-M3 Options
A.1
Cortex-M3 implementation options

Table A-1 shows the Cortex-M3 implementation options.
Table A-1 Effects of the Cortex-M3 implementation options Option Inclusion of MPU Number of interrupts Description, and affected documentation The implementer decides whether to include the MPU. See the Optional Memory Protection Unit on page 4-37. The implementer decides how many interrupts the Cortex-M3 implementation supports Cortex-M3 implementation supports, in the range 1-240. This affects: The range of IRQ values in Table 2-5 on page 2-6. Entries in the last row of Table 2-16 on page 2-22, particularly if only one interrupt is implemented. The maximum interrupt number, and associated information where appropriate, in: Exception handlers on page 2-23 Figure 2-2 on page 2-24 Nested Vectored Interrupt Controller on page 4-3. The number of implemented Nested Vectored Interrupt Controller (NVIC) registers in: Table 4-2 on page 4-3 The appropriate register descriptions in sections Interrupt Set-enable Registers on page 4-4 to Interrupt Priority Registers on page 4-7. Vector Table Offset Register on page 4-16, including the figure and Table 4-16 on page 4-16. See the configuration information in the section for guidance on the required configuration. Number of priority bits Inclusion of the WIC Sleep mode power-saving The implementer decides how many priority bits are implemented in priority value fields, in the range 3-8. This affects The maximum priority level value in Nested Vectored Interrupt Controller on page 4-3. The implementer decides whether to include the Wakeup interrupt Controller (WIC), see The optional Wakeup Interrupt Controller on page 2-32. The implementer decides what sleep modes to implement, and the power-saving measures associated with any implemented mode, See Power management on page 2-31. Sleep mode power saving might also affect the SysTick behavior, see SysTick usage hints and tips on page 4-36. The implementer decides whether all registers in the register bank can be reset. This affects the reset values, see Table 2-2 on page 2-3. The implementer decides whether the memory system is little-endian or big-endian, see Data types on page 2-10 and Memory endianness on page 2-18. Some features of the memory system are implementation-specific. This means that the Memory model on page 2-12 cannot completely describe the memory map for a specific Cortex-M3 implementation. The implementer decides whether bit-banding is implemented., see Optional bit-banding on page 2-16 and Memory model on page 2-12. The SYST_CALIB register is implementation- defined. This can affect: SysTick Calibration Value Register on page 4-35 The entry for SYST_CALIB in Table 4-44 on page 4-43.
Register reset values Endianness Memory features Bit-banding SysTick timer
A-2
Glossary
This glossary describes some of the terms used in technical documents from ARM.
Abort
A mechanism that indicates to a processor that the value associated with a memory access is invalid. An abort can be caused by the external or internal memory system as a result of attempting to access invalid instruction or data memory. A data item stored at an address that is divisible by the number of bytes that defines the data size is said to be aligned. Aligned words and halfwords have addresses that are divisible by four and two respectively. The terms word-aligned and halfword-aligned therefore stipulate addresses that are divisible by four and two respectively. A register that has multiple physical copies, where the state of the processor determines which copy is used. The Stack Pointer, SP (R13) is a banked register. In instruction descriptions, a register specified by a load or store instruction that is used to hold the base value for the address calculation for the instruction. Depending on the instruction and its addressing mode, an offset can be added to or subtracted from the base register value to form the address that is sent to memory. See also Index register.
Aligned
Banked register Base register
Big-endian (BE)
Byte ordering scheme in which bytes of decreasing significance in a data word are stored at increasing addresses in memory. See also Byte-invariant, Endianness, Little-endian (LE).
Big-endian memory
Memory in which: a byte or halfword at a word-aligned address is the most significant byte or halfword within the word at that address
Glossary-1
Glossary
a byte at a halfword-aligned address is the most significant byte within the halfword at that address.
See also Little-endian memory.

Breakpoint
A breakpoint is a mechanism provided by debuggers to identify an instruction at which program execution is to be halted. Breakpoints are inserted by the programmer to enable inspection of register contents, memory locations, variable values at fixed points in the program execution to test that the program is operating correctly. Breakpoints are removed after the program is successfully tested. In a byte-invariant system, the address of each byte of memory remains unchanged when switching between little-endian and big-endian operation. When a data item larger than a byte is loaded from or stored to memory, the bytes making up that data item are arranged into the correct order depending on the endianness of the memory access. An ARM byte-invariant implementation also supports unaligned halfword and word memory accesses. It expects multi-word accesses to be word-aligned. A block of on-chip or off-chip fast access memory locations, situated between the processor and main memory, used for storing and retrieving copies of often used instructions, data, or instructions and data. This is done to greatly increase the average speed of memory accesses and so improve processor performance. A four-bit field in an instruction that specifies a condition under which the instruction can execute. If the condition code flags indicate that the corresponding condition is true when the instruction starts executing, it executes normally. Otherwise, the instruction does nothing.
Byte-invariant
Cache
Condition field Conditional execution
Context
The environment that each process operates in for a multitasking operating system. In ARM processors, this is limited to mean the physical address range that it can access in memory and the associated memory access permissions. A processor that supplements the main processor. The Cortex-M4 processor does not support any coprocessors. A debugging system that includes a program, used to detect, locate, and correct software faults, together with custom hardware that supports software debugging. An operation that accesses main memory directly, without the processor performing any accesses to the data concerned.
Coprocessor Debugger
Direct Memory Access (DMA)
Doubleword Doubleword-aligned
A 64-bit data item. The contents are taken as being an unsigned integer unless otherwise stated. A data item having a memory address that is divisible by eight.
Endianness
Byte ordering. The scheme that determines the order that successive bytes of a data word are stored in memory. An aspect of the systems memory mapping. See also Little-endian and Big-endian
Exception
An event that interrupts program execution. When an exception occurs, the processor suspends the normal program flow and starts execution at the address indicated by the corresponding exception vector. The indicated address contains the first instruction of the handler for the exception.
Glossary-2
Glossary
An exception can be an interrupt request, a fault, or a software-generated system exception. Faults include attempting an invalid memory access, attempting to execute an instruction in an invalid processor state, and attempting to execute an undefined instruction.
Exception service routine
See Interrupt handler.

Exception vector Flat address mapping
See Interrupt vector. A system of organizing memory in which each physical address in the memory space is the same as the corresponding virtual address.
Halfword Illegal instruction Implementation-defined
A 16-bit data item. An instruction that is architecturally Undefined. The behavior is not architecturally defined, but is defined and documented by individual implementations.
Implementation-specific
The behavior is not architecturally defined, and does not have to be documented by individual implementations. Used when there are a number of implementation options available and the option chosen does not affect software compatibility.
Index register
In some load and store instruction descriptions, the value of this register is used as an offset to be added to or subtracted from the base register value to form the address that is sent to memory. Some addressing modes optionally enable the index register value to be shifted prior to the addition or subtraction. See also Base register.
Instruction cycle count
The number of cycles that an instruction occupies the Execute stage of the pipeline.
Interrupt handler Interrupt vector Little-endian (LE)
A program that control of the processor is passed to when an interrupt occurs. One of a number of fixed addresses in low memory, or in high memory if high vectors are configured, that contains the first instruction of the corresponding interrupt handler. Byte ordering scheme in which bytes of increasing significance in a data word are stored at increasing addresses in memory. See also Big-endian (BE), Byte-invariant, Endianness.
Little-endian memory
Memory in which: a byte or halfword at a word-aligned address is the least significant byte or halfword within the word at that address a byte at a halfword-aligned address is the least significant byte within the halfword at that address.
See also Big-endian memory.

Load/store architecture
A processor architecture where data-processing operations only operate on register contents, not directly on memory contents.
Glossary-3
Glossary
Memory Protection Unit (MPU)
Hardware that controls access permissions to blocks of memory. An MPU does not perform any address translation.
Prefetching
In pipelined processors, the process of fetching instructions from memory to fill up the pipeline before the preceding instructions have finished executing. Prefetching an instruction does not mean that the instruction has to be executed. Reads are defined as memory operations that have the semantics of a load. Reads include the Thumb instructions LDM, LDR, LDRSH, LDRH, LDRSB, LDRB, and POP. A partition of memory space. A field in a control register or instruction format is reserved if the field is to be defined by the implementation, or produces Unpredictable results if the contents of the field are not zero. These fields are reserved for use in future extensions of the architecture or are implementation-specific. All reserved bits not used by the implementation must be written as 0 and read as 0. Write as 1, or all 1s for bit fields, by software. Writing as 0 produces Unpredictable results.
Read Region Reserved
Should Be One (SBO) Should Be Zero (SBZ)
Write as 0, or all 0s for bit fields, by software. Writing as 1 produces Unpredictable results.
Should Be Zero or Preserved (SBZP)
Write as 0, or all 0s for bit fields, by software, or preserved by writing the same value back that has been previously read from the same field on the same processor.
Thread-safe
In a multi-tasking environment, thread-safe functions use safeguard mechanisms when accessing shared resources, to ensure correct operation without the risk of shared access conflicts. One or two halfwords that specify an operation for a processor to perform. Thumb instructions must be halfword-aligned. A data item stored at an address that is not divisible by the number of bytes that defines the data size is said to be unaligned. For example, a word stored at an address that is not divisible by four. Indicates an instruction that generates an Undefined instruction exception. You cannot rely on the behavior. Unpredictable behavior must not represent security holes. Unpredictable behavior must not halt or hang the processor, or any parts of the system.
Thumb instruction Unaligned Undefined Unpredictable (UNP)
Warm reset
Also known as a core reset. Initializes the majority of the processor excluding the debug controller and debug logic. This type of reset is useful if you are using the debugging features of a processor. See Write-allocate (WA). See Write-back (WB). A 32-bit data item. Writes are defined as operations that have the semantics of a store. Writes include the Thumb instructions STM, STR, STRH, STRB, and PUSH. In a write-allocate cache, a cache miss on storing data causes a cache line to be allocated into the cache.
WA WB Word Write Write-allocate (WA)
Glossary-4
Glossary
Write-back (WB)
In a write-back cache, data is only written to main memory when it is forced out of the cache on line replacement following a cache miss. Otherwise, writes by the processor only update the cache. This is also known as copyback. A block of high-speed memory, arranged as a FIFO buffer, between the data cache and main memory, whose purpose is to optimize stores to main memory. In a write-through cache, data is written to main memory at the same time as the cache is updated.
Write buffer Write-through (WT)
Glossary-5

Cortex-M3 - Generic User Guide

Uploaded by

Copyright:

Available Formats

Cortex-M3 - Generic User Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cortex-M3 - Generic User Guide

Uploaded by

Copyright:

Available Formats

Cortex -M3 Devices

Generic User Guide

ARM DUI 0552A ID121610

Copyright 2010 ARM. All rights reserved. Non-Confidential

Contents Cortex-M3 Devices Generic User Guide

The Cortex-M3 Processor

The Cortex-M3 Instruction Set

ARM DUI 0552A ID121610

Copyright 2010 ARM. All rights reserved. Non-Confidential

4.2 4.3 4.4 4.5

ARM DUI 0552A ID121610

Copyright 2010 ARM. All rights reserved. Non-Confidential

ARM DUI 0552A ID121610

Copyright 2010 ARM. All rights reserved. Non-Confidential

About this book

ARM DUI 0552A ID121610

Copyright 2010 ARM. All rights reserved. Non-Confidential

Typographical conventions The typographical conventions are: italic bold

< and >

ARM DUI 0552A ID121610

Copyright 2010 ARM. All rights reserved. Non-Confidential

ARM DUI 0552A ID121610

Copyright 2010 ARM. All rights reserved. Non-Confidential

ARM DUI 0552A ID121610

Copyright 2010 ARM. All rights reserved. Non-Confidential

ARM DUI 0552A ID121610

Copyright 2010 ARM. All rights reserved. Non-Confidential

About the Cortex-M3 processor and core peripherals

Optional Debug Access Port

Optional Memory protection unit

Optional Serial Wire viewer

Optional Flash patch

Optional Data watchpoints

Bus matrix Code interface SRAM and peripheral interface

Figure 1-1 Cortex-M3 implementation

ARM DUI 0552A ID121610

Copyright 2010 ARM. All rights reserved. Non-Confidential

ARM DUI 0552A ID121610

Copyright 2010 ARM. All rights reserved. Non-Confidential

ARM DUI 0552A ID121610

Copyright 2010 ARM. All rights reserved. Non-Confidential

Chapter 2 The Cortex-M3 Processor

ARM DUI 0552A ID121610

Copyright 2010 ARM. All rights reserved. Non-Confidential

The Cortex-M3 Processor

a. See CONTROL register on page 2-9.

ARM DUI 0552A ID121610

Copyright 2010 ARM. All rights reserved. Non-Confidential

The Cortex-M3 Processor

Core registers The processor core registers are:

ARM DUI 0552A ID121610

Copyright 2010 ARM. All rights reserved. Non-Confidential

The Cortex-M3 Processor

ARM DUI 0552A ID121610

Copyright 2010 ARM. All rights reserved. Non-Confidential

The Cortex-M3 Processor

The PSR combinations and attributes are:

ARM DUI 0552A ID121610

Copyright 2010 ARM. All rights reserved. Non-Confidential

The Cortex-M3 Processor