Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

Unit 5 Notes

Download as pdf or txt
Download as pdf or txt
You are on page 1of 34

UNIT-5

ARM Architectures and Processors :


ARM Architecture, ARM Processor families, ARM Cortex-M Series family, ARM Cortex-
M3 processor functional description, functions and interfaces.
Programmers Model: Modes of operation, and execution, Instruction set summary, System
address map, write buffer, bit-banding, Processor core register summary, exceptions.
ARM Cortex-M3 programming- Software delay, Programming techniques, Loops, Stack and
Stack pointer, subroutines and parameter passing, parallel I/O, Nested vectored Interrupt
Controller- functional description, and NVIC Programmer’s model.

INTRODUCTION :
ARM was formed in 1990 as Advanced RISC Machines Ltd., a joint venture of Apple
Computer, Acorn Computer Group, and VLSI Technology. In 1991, ARM introduced the
ARM6 processor family, and VLSI became the initial licensee.
The ARM Cortex™-M3 processor, the first of the Cortex generation of processors
released by ARM in 2006, was primarily designed to target the 32-bit microcontroller
market. The Cortex-M3 processor provides excellent performance at low gate count and
comes with many new features previously avail- able only in high-end processors. The
Cortex-M3 addresses the requirements for the 32-bit embedded processor market in the
following ways:
• Greater performance efficiency: allowing more work to be done without
increasing the frequency or power requirements
• Low power consumption: enabling longer battery life, especially critical in
portable products including wireless networking applications
• Enhanced determinism: guaranteeing that critical tasks and interrupts are
serviced as quickly as possible and in a known number of cycles
• Improved code density: ensuring that code fits in even the smallest memory
footprints
• Ease of use: providing easier programmability and debugging for the growing
number of 8-bit and 16-bit users migrating to 32 bits
• Lower cost solutions: reducing 32-bit-based system costs close to those of
legacy 8-bit and 16-bit devices and enabling low-end, 32-bit microcontrollers
to be priced at less than US$1 for the first time
• Wide choice of development tools: from low-cost or free compilers to full-
featured development suites from many development tool vendors
FEATURES OF ARM7 PROCESSOR:

 It is a 32-bit RISC-processor core (32-bit instructions)


 It consists of 37 pieces of 32-bit integer registers. Out of 37 registers 16 registers are
readily available for user.
 ARM consists of Pipelined architecture . Fetch, Decode and Execute are the 3
stages of ARM processor.
 It has Cache memory. Cache memory is a small memory placed between processor
and main memory to store recently accessed transactions (depending on the
implementation).
 Based on memory architecture, ARM processor is a Von Neumann-type bus
structure (ARM7), which has a single memory for both code and data.ARM9 has
Harvard architecture which has separate memory for code and data.
 ARM processor can able to handle 8 / 16 / 32 -bit data types.
 There are 7 modes of operation namely User,FIQ,IRQ,Supervisor mode, Abort
mode, System mode, Undefined mode.
 The architecture is very simple which is reasonably good speed and less power
consumption ratio.
 It implements two instruction set, 32-bit ARM instruction set and 16-bit Thumb
instruction set.

ARM ARCHITECTURE :

Advanced RISC Machine or Acorn RISC Machine is the architecture with different
computing architectures set to be used in different environments. 32-bit and 64-bit can be
used here in different computer processors. It was developed by Arm Holdings and the
architecture is updated in between. This architecture is specified to be used with CPU,
different chips in the system, and in different registers. Reduced Instruction Set Computing
helps in creating instructions for the system to be used for several purposes. Smartphones,
microcomputers, and embedded devices also use ARM architecture for the instruction set in
the registers.
The architecture can be divided into A, R, and M profiles. A profile is mainly for
applications, R profile is for real-time and M profile is for Microcontroller. A profile helps
to maintain high performance and is designed to run the complex system in Linux or
Windows. R profile checks for systems with real-time requirements and is found in
networking equipment or embedded control systems. M profile is used in IOT devices and
can be synchronized with small and high-power devices.

ARM7TDMI architecture is shown in above figure, which has T=Thumb


instruction set, D=Debug Unit, M=MMU(Memory Management Unit) and I=Embedded
Trace Core. It is also called as LOAD and STORE architecture since, the processor can
access only the registers and not the memory. It consists of main blocks like Address
register, Address incrementer, Register Bank, 32x8 multiplier, Barrel shifter, ALU, Data out
and Data in, Instruction decoder and control logic blocks.
1. Instruction Decoder and control logic block is used to decodes the instruction before
it is processed by the ALU.
2. Register Bank is connected to ALU by two data paths, one is through A-bus and the
other through B-bus it passes Barrel shifter before reaching ALU. The data will be
fetched from registers(R0-R15) by ALU for processing which is called LOAD and
the results will be stored in to registers after processing which is called STORE.Let,
The input registers are denoted by Rm and Rn and the output registers are denoted
by Rd.
3. Program counter is used to fetch the address of the next instruction and stored in
address register through PC bus.
4. Barrel shifter is also called as a pre-processor.ie, if the data has to be shift left, right
or to rotate, it will be done by Barrel shifter before sending it to ALU. ALU and
Barrel shifter are called as combinational circuit which will take only one second for
the operations.
5. Address incrementer is used to store the next address from where the instruction has
to be fetched.
CONTROL SIGNALS OF ARM7 PROCESSOR:
1. A[31:0] : This is the 32-bit address bus. ALE, ABE, and APE are used to
Control when the address bus is valid.
2. ABE : Address Bus Enable
3. ALE : Address Latch Enable. Address signals have to be maintained high
Until the complete duration of memory access cycles.
4. ABORT : Memory Abort
5. APE : Address Pipeline Enable. This mode is used for DRAM systems.
6. BL[3:0] : Byte Latch enable. The values on data bus are latched on the falling
Edge, when these are high.
7. Break Point : A conditional request for the processor to enter in to Debug state by
making this signal HIGH.
8. CPA : Coprocessor Absent. If Coprocessor is able to respond the processor, this
signal goes low.
9. CPB : Coprocessor Busy. When the coprocessor is ready to accept the request
From processor, this signal goes low.
10. DBGACK : Debug Acknowledgement. When the processor is in Debug state, this
signal goes high.
11. DBGRQI : Internal Debug Request. This is logical OR of DBGRQ and bit[1] of
Debug control register.
12. ECLK : External Clock output.
13. HIGHZ : HIGH Impedance, when HIGH impedance instruction is loaded into the
Tap Controller.
14. ISYNC : Synchronous Interrupts. Set this signal high if nIRQ and nFIQ are
Synchronous to the processor clock.
15. LOCK : Locked Operation. When the processor is performing a locked memory
access.
16. MAS[1:0] :Memory Access Size. It is used to indicate to the memory system the size
of data transfer required for both read & write control signals.
17. MCLK : Memory Clock Input. This is the main clock for all memory access and
processor operations.
18. nCPI : Not Coprocessor Instruction. When coprocessor instruction are processed,
this signal goes low.
19. nFIQ : Not Fast Interrupt Request.
20. nIRQ : Not Interrupt request.
21. nM[4:0] : Not processor mode. Indicates current processor mode.
22. nMREQ : Not Memory Request.
23. nOPC : Not Opcode Fetch
24. nRESET : Not Reset
25. nRW : Not Read Write
26. nTRANS : Not Memory Translate
27. nWAIT : Not Wait
28. SEQ : Sequential Address. When the address of the next memory is close to the
last memory
ARM PROCESSOR FAMILY:
ARM CORTEX-M SERIES FAMILY:

CORTEX – M0:

The Cortex-M0 core is optimized for small silicon die size and use in the
lowest price chips.It consists of an ARM architecture of ARMV6-M, with Von-
Nuemann memory architecture.It follows 3 stage instruction pipeline.It uses both
Thumb 1(most) and Thumb 2(some) instructions.It takes 16 cycles for Interrupt
including Zero-wait state RAM.
CORTEX – M0+ :

The Cortex-M0+ is an optimized superset of the Cortex-M0. The Cortex-M0+


has complete instruction set compatibility with the Cortex-M0 thus allowing the use of
the same compiler and debug tools. The Cortex-M0+ pipeline was reduced from 3 to 2
stages, which lowers the power usage. In addition to debug features in the existing
Cortex-M0, a silicon option can be added to the Cortex-M0+ called the Micro Trace
Buffer (MTB) which provides a simple instruction trace buffer.

CORTEX M1:

The Cortex-M1 is an optimized core especially designed to be loaded


into FPGA chips. ARMv6-M architecture is the ARM architecture which it is using. It has
3-stage pipeline, Both the thumb instructions,Thumb-1 (most), is used except CBZ, CBNZ,
IT and some of the Thumb-2 are used, only BL, DMB, DSB, ISB, MRS, MSR are used.It
consists of 32-bit hardware integer multiply with 32-bit result.The Tightly-Coupled
Memory (TCM): 0 to 1 MB instruction-TCM, 0 to 1 MB data-TCM, each with optional
ECC(Elliptic Curve Cryptography).

CORTEX M3:

ARMv7-M architecture is used in CORTEX M3. It has 3-stage pipeline with branch
speculation. Thumb-1 and Thumb-2 instructions are used entirely . If 32-bit hardware
integer multiply with 32-bit or 64-bit it results in signed or unsigned, add or subtract after
the multiply. 32-bit multiply is 1 cycle, but 64-bit multiply and MAC instructions require
extra cycles.32-bit hardware integer divided into (2–12 cycles). It has Optional Memory
Protection Unit (MPU): 0 or 8 regions.There are 1 to 241 interrupts including NMI. It
requires 12 cycle interrupt latency.

CORTEX M4:

Conceptually the Cortex-M4 is a Cortex-M3 plus DSP instructions, and optional


floating-point unit (FPU). A core with an FPU is known as Cortex-M4F. It uses ARMv7E-
M architecture, 3-stage pipeline with branch speculation.Thumb-1 and Thumb-2 instructions
used entirely. If 32-bit hardware integer multiply with 32-bit or 64-bit it results in signed or
unsigned, add or subtract after the multiply. For 32-bit Multiply and MAC(Media Access
Control) address are 1 cycle and for 32-bit hardware integer divide it takes 2–12
cycles.Saturation arithmetic support is available in which all operations such as addition and
multiplication are limited to a fixed range between a minimum and maximum value. For
DSP extension: Single cycle 16/32-bit MAC, single cycle dual 16-bit MAC, 8/16-
bit SIMD arithmetic is used.1 to 241 interrupts including NMI is used.It has 12 cycle
interrupt latency. Integrated sleep modes are possible. Optional floating-point unit (FPU):
single-precision only IEEE-754 compliant. It is called the FPv4-SP extension.Optional
memory protection unit (MPU): 0 or 8 regions.
CORTEX M7:

The Cortex-M7 is a high-performance core with almost double the power efficiency
of the older Cortex-M4. It features a 6-stage superscalar pipeline with branch prediction and
an optional floating-point unit capable of single-precision and optionally double-
precision operations. The instruction and data buses have been enlarged to 64-bit wide over
the previous 32-bit buses. If a core contains an FPU, it is known as a Cortex-M7F, otherwise
it is a Cortex-M7. Entire Thumb 1 and Thumb 2 instructions will be used. It follows the
same specifications of CORTEX M4 for multiplication,division, saturated arithmetic,
interrupts and interrupt latency etc.

Optionally it is connected with:

1. Floating-point unit (FPU): (single precision) or (single and double-precision), both


IEEE-754-2008 compliant. It is called the FPv5 extension.
2. CPU cache: 0 to 64 KB instruction-cache, 0 to 64 KB data-cache, each with
optional ECC.
3. Tightly-Coupled Memory (TCM): 0 to 16 MB instruction-TCM, 0 to 16 MB data-
TCM, each with optional ECC.
4. Memory Protection Unit (MPU): 8 or 16 regions.
5. Embedded Trace Macrocell (ETM): instruction-only, or instruction and data.
6. Retention Mode (with Arm Power Management Kit) for Sleep Modes.

CORTEX M23:

The Cortex-M23 core was announced in October 2016 and based on the
newer ARMv8-M architecture that was previously announced in November
2015. Conceptually the Cortex-M23 is similar to a Cortex-M0+ plus integer divide
instructions and Trust Zone security features, and also has a 2-stage instruction pipeline. For
32-bit hardware integer divide it takes 17 or 34 cycles. It is much slower than divide in all
other cores. Stack limit boundaries are available only with SAU option(available in
M23/M33/M35P).

Optionally it is connected with:

1. Memory Protection Unit (MPU): 0, 4, 8, 12, 16 regions.


2. Optional Security Attribution Unit (SAU): 0, 4, 8 regions.
3. Single-cycle I/O port (available in M0+/M23).
4. Micro Trace Buffer (MTB) (available in M0+/M23/M33/M35P).
CORTEX M33:

The Cortex-M33 core was announced in October 2016 and based on the
newer ARMv8-M architecture that was previously announced in November
2015. Conceptually the Cortex-M33 is similar to a cross of Cortex-M4 and Cortex-M23, and
also has a 3-stage instruction pipeline.

Optionally it is connected with:

 Floating-Point Unit (FPU): single-precision only IEEE-754 compliant. It is called the


FPv5 extension.
 Optional Memory Protection Unit (MPU): 0, 4, 8, 12, 16 regions.
 Optional Security Attribution Unit (SAU): 0, 4, 8 regions.
 Micro Trace Buffer (MTB) (available in M0+/M23/M33/M35P).

CORTEX M35P:
The Cortex-M35P core was announced in May 2018. It is conceptually a Cortex-
M33 core with a new instruction cache, plus new tamper-resistant hardware concepts
borrowed from the ARM Secure Core family, and configurable parity and ECC features.

CORTEX M55:

The Cortex-M55 core was announced in February 2020 and is based on the Armv8.1-M
architecture that was previously announced in February 2019. It also has a 4-stage
instruction pipeline. Stack limit boundaries (available only with SAU option).
ARM – CORTEX M3 FUNCTIONAL DESCRIPTION :

The Cortex™-M3 is a 32-bit microprocessor. It has a 32-bit data path, a 32-bit


register bank, and 32-bit memory interfaces. The Cortex-M3 processor is based on ARMv7-
M architecture. It is a high-performance processor that are designed for microcontrollers.
The processor has a Harvard architecture, which means that it has a separate instruction bus
and data bus. This allows instructions and data accesses to take place at the same time, and
as a result of this, the performance of the processor increases because data accesses do not
affect the instruction pipeline. This feature results in multiple bus interfaces on Cortex-M3,
each with optimized usage and the ability to be used simultaneously. However, the
instruction and data buses share the same memory space. It supports 4Gb memory space.

WAKEUP INTERRUPT CONTROLLER :

The Wakeup Interrupt Controller (WIC) is a peripheral that can detect an interrupt
and wake the processor from deep sleep mode. The WIC is enabled only when the system is
in deep sleep mode.
The WIC is not programmable, and does not have any registers or user interface. It
operates entirely from hardware signals.

NESTED VECTORED INTERRUPT CONTROLLER :

Nested vector interrupt control (NVIC) is a method of prioritizing interrupts,


improving the MCU’s performance and reducing interrupt latency.

The term “nested” refers to the fact that in NVIC, a number of interrupts (up to
several hundred in some processors) can be defined, and each interrupt is assigned a
priority, with “0” being the highest priority.

BREAKPOINT UNIT:

A breakpoint enables you to interrupt your application when execution reaches a specific
address. When execution reaches the breakpoint, normal execution stops before any
instruction stored there is executed.

Types of breakpoints:

 Software breakpoints stop your program when execution reaches a specific address.
Software breakpoints are implemented by the debugger replacing the instruction at the
breakpoint address with a special instruction. Software breakpoints can only be set in
RAM.

 Hardware breakpoints use special processor hardware to interrupt application


execution. Hardware breakpoints are a limited resource.

MEMORY PROTECTION UNIT:

The MPU is an optional component for memory protection. The processor supports
the standard ARMv7 Protected Memory System Architecture model. The MPU provides full
support for:

 protection regions
 overlapping protection regions, with ascending region priority:
 7 = highest priority
 0 = lowest priority.
 access permissions
 exporting memory attributes to the system.

FLOATING POINT UNIT :


It is present only for Cortex-M4 Processor to perform several floating point
arithmetic operations.
WATCH POINT UNIT :
A watch point is similar to a breakpoint, but it is the address of a data access that is
monitored rather than an instruction being executed. Watch points are sometimes known as
data breakpoints, emphasizing that they are data dependent. Execution of application stops
when the address being monitored is accessed by your application. It can be set read, write,
or read/write watch points.
PIPELINING:
ARM CORTEX M3 consists of 3 stage instruction pipelining architecture. They are
Fetch, Decode and Execute.

INTERFACES :
There are several bus interfaces on the Cortex-M3 processor. They allow the Cortex-
M3 to carry instruction fetches and data accesses at the same time. The main bus interfaces
are as follows: • Code memory buses • System bus • Private peripheral bus The code
memory region access is carried out on the code memory buses, which physically consist of
two buses, one called I-Code and other called D-Code. These are optimized for instruction
fetches for best instruction execution speed. The system bus is used to access memory and
peripherals. This provides access to the Static Random Access Memory (SRAM),
peripherals, external RAM, external devices, and part of the system level memory regions.
The private peripheral bus provides access to a part of the system-level memory
dedicated to private peripherals, such as debugging components.

MODES OF OPERATION :
The Cortex-M3 processor has two modes and two privilege levels. The operation
modes are given as,
1. Thread Mode
2. Handler Mode
In Thread mode,the processor works in normal mode. In Handler mode, the
processor runs in exception handler like an interrupt handler system.
There are two privilege levels which provide a mechanism for safeguarding
memory accesses to critical regions as well as providing a basic security model. They
are :
1. Privileged Level
2. User Level

When the processor is running a main program (thread mode), it can be either
in a privileged state or a user state, but exception handlers can only be in a
privileged state.

When the processor exits reset, it is in thread mode, with privileged access
rights. In the privileged state, a program has access to all memory ranges (except
when prohibited by MPU settings) and can use all supported instructions.

Software in the privileged access level can switch the program into the user
access level using the control register. When an exception takes place, the processor
will always switch back to the privileged state and return to the previous state when
exiting the exception handler.

A user program cannot change back to the privileged state by writing to the
control register. It has to go through an exception handler that programs the control
register to switch the processor back into the privileged access level when returning
to thread mode.
The support of privileged and user access levels provides a more secure and
robust architecture. For example, when a user program goes wrong, it will not be able to
corrupt control registers in the Nested Vectored Interrupt Controller (NVIC). In
addition, if the Memory Protection Unit (MPU) is present, it is possible to block user
programs from accessing memory regions used by privileged processes.
The user application stack and the kernel stack memory can be separated to
avoid the possibility of crashing a system caused by stack operation errors in user
programs. With this arrangement, the user program (running in thread mode) uses
the PSP, and the exception handlers use the MSP. The switching of SPs is automatic
upon entering or leaving the exception handlers

Privileged User
When running an exception handler Handler mode
When not running an exception handler Thread mode Thread mode
(e.g., main program)
The mode and access level of the processor are defined by the control register. When
the control register bit 0 is 0, the processor mode changes when an exception takes place.

When control register bit 0 is 1 (thread running user application), both processor
mode and access level change when an exception takes place.
Control register bit 0 is programmable only in the privileged level. For a user-
level program to switch to privileged state, it has to raise an interrupt (for example,
supervisor call [SVC]) and write to CONTROL within the handler.

SYSTEM ADDRESS MAP :


The Cortex-M3 processor has a fixed memory map. This makes it easier to port
soft- ware from one Cortex-M3 product to another. The Nested Vectored Interrupt
Controller (NVIC) and Memory Protection Unit (MPU), have the same memory
locations in all Cortex-M3 products. Nevertheless, the memory map definition allows
great flexibility so that manufacturers can differentiate their Cortex-M3-based product
from others.
Some of the memory locations are allocated for private peripherals such as
debugging components. They are located in the private peripheral memory region.
These debugging components include the following:
• Fetch Patch and Breakpoint Unit (FPB)
• Data Watch point and Trace Unit (DWT)
• Instrumentation Trace Macro cell (ITM)
• Embedded Trace Macro cell (ETM)
• Trace Port Interface Unit (TPIU)
• ROM table
The Cortex-M3 processor has a total of 4 GB of address space. Program code can be
located in the code region, the Static Random Access Memory (SRAM) region, or the
external RAM region. However, it is best to put the program code in the code region because
with this arrangement, the instruction fetches and data accesses are carried out simultaneously
on two separate bus interfaces.

The SRAM memory range is for connecting internal SRAM. Access to this region
is carried out via the system interface bus. a 32-MB range is defined as a bit-band alias.
Within the 32-bit-band alias memory range, each word address represents a single bit in
the 1-MB bit-band region. A data write access to this bit-band alias memory range will be
converted to an atomic READ- MODIFY-WRITE operation to the bit-band region so as
to allow a program to set or clear individual data bits in the memory. The bit-band
operation applies only to data accesses not instruction fetches. By putting Boolean
information (single bits) in the bit-band region, it is possible to pack multiple Boolean
data in a single word while still allowing them to be accessible individually via bit-band
alias, thus saving memory space without the need for handling READ-MODIFY-WRITE
in software.
Another 0.5-GB block of address range is allocated to on-chip peripherals. Similar
to the SRAM region, this region supports bit-band alias and is accessed via the system
bus interface. However, instruction execution in this region is not allowed. The bit-band
support in the peripheral region makes it easy to access or change control and status bits
of peripherals, making it easier to program peripheral control.
Two slots of 1-GB memory space are allocated for external RAM and external
devices. The difference between the two is that program execution in the external device
region is not allowed, and there are some differences with the caching behaviors.
The last 0.5-GB memory is for the system-level components, internal peripheral
buses, external peripheral bus, and vendor-specific system peripherals. There are two
segments of the private peripheral bus (PPB):
• Advanced High-Performance Bus (AHB) PPB, for Cortex-M3 internal AHB
peripherals only; this includes NVIC, FPB, DWT, and ITM
• Advance Peripheral Bus (APB) PPB, for Cortex-M3 internal APB devices as well
as external peripherals (external to the Cortex-M3 processor); the Cortex-M3
allows chip vendors to add additional on-chip APB peripherals on this private
peripheral bus via an APB interface
The NVIC is located in a memory region called the system control space (SCS). Besides
providing interrupt control features, this region also provides the control registers for
SYS- TICK, MPU, and code debugging control.
The remaining unused vendor-specific memory range can be accessed via the system bus
interface.
However, instruction execution in this region is not allowed.
The Cortex-M3 processor also comes with an optional MPU. Chip manufacturers can
decide whether to include the MPU in their products.

BIT – BAND OPERATIONS:

Bit-band operation support allows a single load/store operation to access


(read/write) to a single data bit. In the Cortex-M3, this is supported in two predefined
memory regions called bit-band regions. One of them is located in the first 1 MB of the
SRAM region, and the other is located in the first 1 MB of the peripheral region.
These two memory regions can be accessed like normal memory, but they can
also be accessed via a separate memory region called the bit-band alias. When the bit-
band alias address is used, each individual bit can be accessed separately in the least
significant bit (LSB) of each word-aligned address.
For example, to set bit 2 in word data in address 0x20000000, instead of using
three instructions to read the data, set the bit, and then write back the result, this task can
be carried out by a single instruction.

The assembler sequence for these two cases :

Similarly, bit-band support can simplify application code if we need to read a bit in a
memory location. For example, if we need to determine bit 2 of address 0x20000000,
THE BUILT-IN NESTED VECTORED INTERRUPT CONTROLLER:

The Cortex-M3 processor includes an interrupt controller called the Nested Vectored
Interrupt Controller (NVIC). It is closely coupled to the processor core and provides a
number of features as follows:

 Nested interrupt support


 Vectored interrupt support
 Dynamic priority changes support
 Reduction of interrupt latency
 Interrupt masking

Nested Interrupt Support:

The NVIC provides nested interrupt support. All the external interrupts and most of the
system exceptions can be programmed to different priority levels. When an interrupt
occurs, the NVIC compares the priority of this interrupt to the current running priority
level. If the priority of the new interrupt is higher than the current level, the interrupt
handler of the new interrupt will override the current running task.

Vectored Interrupt Support :

The Cortex-M3 processor has vectored interrupt support. When an interrupt is accepted,
the starting address of the interrupt service routine (ISR) is located from a vector table in
memory. There is no need to use software to determine and branch to the starting address
of the ISR. Thus, it takes less time to process the interrupt request.

Dynamic Priority Changes Support:

Priority levels of interrupts can be changed by software during run time. Interrupts that
are being serviced are blocked from further activation until the ISR is completed, so their
priority can be changed without risk of accidental re entry.

Reduction of Interrupt Latency:

The Cortex-M3 processor also includes a number of advanced features to lower the
interrupt latency. These include automatic saving and restoring some register contents,
reducing delay in switching from one ISR to another, and handling of late arrival
interrupts.

Interrupt Masking:

Interrupts and system exceptions can be masked based on their priority level or masked
completely using the interrupt masking registers BASEPRI, PRIMASK, and
FAULTMASK. They can be used to ensure that time-critical tasks can be finished on
time without being interrupted.

EXCEPTIONS :

The Cortex-M3 supports a number of exceptions, including a fixed number of


system exceptions and a number of interrupts, commonly called IRQ. The number of
interrupt inputs on a Cortex-M3 microcontroller depends on the individual design.
Interrupts generated by peripherals, except System Tick Timer, are also connected to the
interrupt input signals. The typical number of interrupt inputs is 16 or 32. However, you
might find some microcontroller designs with more (or fewer) interrupt inputs. Besides
the interrupt inputs, there is also a non maskable interrupt (NMI) input signal. The actual
use of NMI depends on the design of the microcontroller or system-on-chip (SoC)
product you use. In most cases, the NMI could be connected to a watchdog timer or a
voltage-monitoring block that warns the processor when the voltage drops below a
certain level. The NMI exception can be activated any time, even right after the core exits
reset.

The list of exceptions found in the Cortex-M3 is shown:

STACK MEMORY OPERATIONS :

In the Cortex-M3, besides normal software-controlled stack PUSH and POP, the
stack PUSH and POP operations are also carried out automatically when entering or
exiting an exception/interrupt handler.
Basic Operations of the Stack :

The SP is adjusted automatically in PUSH and POP so that multiple data PUSH
will not cause old stacked data to be erased.
The function of the stack is to store register contents in memory so that they can
be restored later, after a processing task is completed. For normal uses, for each store
(PUSH), there must be a corresponding read (POP), and the address of the POP operation
should match that of the PUSH operation. When PUSH/POP instructions are used, the SP
is incremented/decremented automatically.
When program control returns to the main program, the R0–R2 contents are the
same as before. Notice the order of PUSH and POP: The POP order must be the reverse
of PUSH.

Cortex-M3 Stack Implementation:

The Cortex-M3 uses a full-descending stack operation model. The SP points to


the last data pushed to the stack memory, and the SP decrements before a new PUSH
operation.

Cortex-M3 Stack PUSH Implementation

Cortex-M3 Stack POP Implementation

For POP operations, the data is read from the memory location pointer by SP, and
then, the SP is incremented. The contents in the memory location are unchanged but will
be overwritten when the next PUSH operation takes place.
Because each PUSH/POP operation transfers 4 bytes of data (each register
contains 1 word, or 4 bytes), the SP decrements/increments by 4 at a time or a multiple of
4 if more than 1 register is pushed or popped.
The Two-Stack Model in the Cortex-M3 :

The Cortex-M3 has two SPs: 1. SP_main and 2. SP_Process. The SP register to
be used is controlled by the control register bit 1.
When CONTROL[1] is 0, the SP_main is used for both thread mode and handler
mode. In this arrangement, the main program and the exception handlers share the same
stack memory region. This is the default setting after power-up.
When the CONTROL[1] is 1, the SP_Process is used in thread mode. In this
arrangement, the main program and the exception handler can have separate stack
memory regions.

CONTROL[1]=0: Both Thread Level and Handler Use Main Stack.

CONTROL[1]=1: Thread Level Uses Process Stack and Handler Uses Main Stack.

INSTRUCTION SET :

The processor does not support ARM instructions.Thumb-2


instruction set, it is now possible to handle all processing requirements in
one operation state. Even interrupts are now handled with the Thumb state.
Since there is no need to switch between states, the Cortex-M3
processor has a number of advantages over traditional ARM processors,
such as:
 No state switching overhead, saving both execution time and instruction space
 No need to separate ARM code and Thumb code source files, making software
development and maintenance easier
 It’s easier to get the best efficiency and performance, in turn making it easier
to write software, because there is no need to worry about switching code between ARM
and Thumb to try to get the best density/performance.
Instruction are mentioned as follows:
16-BIT THUMB INSTRUCTION SET :

Some of the changes used to reduce the length of the instructions from 32 bits to 16 bits:
 reduce the number of bits used to identify the register o less number of registers can
be used
 reduce the number of bits used for the immediate value o smaller number range
 remove options such as ‘S’ o make it default for some instructions
 remove conditional fields (N, Z, V, C)
 no conditional executions (except branch)
 remove the optional shift (and no barrel shifter operation o introduce dedicated shift
instructions
 remove some of the instructions o more restricted coding
REGISTERS:

The processor has the following 32-bit registers:

 13 general-purpose registers, r0-r12


 stack point alias of banked registers, SP_process and SP_main
 link register, r14
 program counter, r15
 one program status register, xPSR.

ARM CORTEX-M3 has 13 General Purpose Registers which is divided into two
sections.(i) Low Registers (ii) High Registers. These registers are used for data handling
purposes. Low registers are from R0 to R7 and High registers are from R8 to R12.
R13 – This register is called Stack Pointer register. It is also called banked register
since, there are two registers but one register is visible to the user. The two stack registers are
SP_main and SP_Process.
The default stack is SP_main, which will be only used by Handler mode. Both
SP_process and SP_main can be handled by Thread mode based on the programming.
R14 – It is called Link Register. When Interrupt occurs, the return address will be
stored in Link register and the program counter will move to the ISR. Other than interruption,
this register acts as a normal General purpose registers.
R15 – It is called Program Counter. It is used to store the address of the next
instruction that has to be fetched.
Special Registers:
The Cortex-M3 processor also has a number of special registers.
 Program Status registers (PSRs)
 Interrupt Mask registers (PRIMASK, FAULTMASK, and BASEPRI)
 Control register (CONTROL)
These registers have special functions and can be accessed only by special instructions. They
cannot be used for normal data processing.

PROGRAM STATUS REGISTER:


APPLICATION PSR:
The Application PSR (APSR) contains the condition code flags. Before
entering an exception, the processor saves the condition code flags on the stack.
APSR will be access with the MSR(2) and MRS(2) instructions.

FIELD NAME DEFINITION


Negative or less than flag:
[31] N
1 = result negative or less than

0 = result positive or greater than.


Zero flag:
Zero flag:
1 = result of 0
[30] Z Z 1 = result of 0
0 = nonzero result.
0 = nonzero result.

Carry/borrow flag:
Carry/borrow flag: Carry/borrow flag:
1 = carry or borrow
[29] C 1C= carry or borrow 1 = carry or borrow
0 = no carry or borrow.
0 = no carry or borrow.
0 = no carry or borrow.

Overflow flag:
Overflow flag:
1 = overflow
[28] V V 1 = overflow
0 = no overflow.
0 = no overflow.

[27] Q Sticky saturation flag.


Q Sticky saturation flag.

[26:0] -
Reserved.
INTERRUPT PSR:
The Interrupt PSR (IPSR) contains the Interrupt Service Routine (ISR)
number of the current exception activation.

FIELD NAME DEFINITION


- Reserved.
[31:9]

[8:0] ISR NUMBER Number of pre-empted


exception.

Base level = 0

NMI = 2

SVCall = 11

INTISR[0] = 16

INTISR[1] = 17

INTISR[15] = 31

INTISR[239] = 255
EXECUTION PSR:

The Execution PSR (EPSR) contains two overlapping fields:

 the Interruptible-Continuable Instruction (ICI) field for interrupted load multiple


and store multiple instructions
 the execution state field for the If-Then (IT) instruction, and the Thumb state
bit (T-bit).

Interruptible-continuable instruction field:


Load Multiple (LDM) operations and Store Multiple (STM) operations are
interruptible. The ICI field of the EPSR holds the information required to continue the
load or store multiple from the point that the interrupt occurred.
If-then state field:
The IT field of the EPSR contain the execution state bits for the If-Then
instruction.

FIELD NAME DEFINITION

[31:27] - - Reserved.
Reserved

Interruptible-continuable
instruction bits. When an
interrupt occurs during an
LDM or STM operation, the
multiple operation stops
temporarily. The EPSR uses
bits [15:12] to store the
number of the next register
ICI
[26:25], [15:10] operand in the multiple
operation. After servicing the
interrupt, the processor
returns to the register pointed
to by [15:12] and resumes
the multiple operation. If the
ICI field points to a register
that is not in the register list
of the instruction, the
processor continues with the
next register in the list, if any.
If-Then bits. These are the
execution state bits of the If-
[26:25], [15:10] Then instruction. They
IT
contain the number of
instructions in the if-then
block and the conditions for
their execution.
The T-bit can be cleared using
an interworking instruction
where bit [0] of the written PC
is 0. It can also be cleared by
unstacking from an exception
[24] where the stacked T bit is 0.
T

Executing an instruction while


the T bit is clear causes an
INVSTATE exception.

[23:16] - Reserved.
[9:0] - Reserved.

You might also like