Saravana Pandian Annamalai
27. August 2015 · Write a comment · Categories: ARM, Embedded Software, Technology · Tags: ,

Continuing our series on interrupts, this blog will capture the ARM interrupt architecture along with the evolution of the same from the early ARMv4 to the latest ARMv8 models. A fair outline of overall flow, including the exception/ registers model, is given to aid the reader understand the principles behind the ARM interrupt architecture design.

ARM Instruction Set

ARM architecture has continuously evolved since its introduction. Beginning with ARMv4, architecture evolution is labeled with incremental values like ARMv5, ARMv6 till the latest ARMv8. There are additions and extensions that are labeled with a suffix like ARMv5TE or ARMv6K.

As with any RISC core, ARM supports very few instructions and is capable of executing them fast at a rate of 1 instruction per clock using techniques such as pipelining, branch prediction, caching etc.

Many RISC architectures define a set of instructions and encoding that will be executed by the processor. But ARM Architecture is an advanced design that supports different instruction sets that can be changed dynamically. Each of these instruction execution modes offer unique advantage like higher code density, support for Java execution etc. Few of the instruction sets supported are

ARM: The default mode that operates with fixed width (32-bit) instructions. Automatically changed to this mode when an interrupt/exception occurs.

Thumb: It is a 16-bit instruction set that can be used for higher code density. It is has limited set of instructions and registers compared to ARM mode, but can be advantageous if limited register manipulations are done.

Thumb2: Introduced in ARMv6T2, this brings the best of both worlds, by supporting mixed 16 bit and 32 bit instructions able to achieve very higher code density and performance. This has become popular that modern OS like Windows Embedded Compact has made this the default execution mode. Even Linux kernel supports compilation to Thumb2 mode.

Jazelle: Optimized for Java code execution.

SIMD: Single Instruction Multiple Data instruction set for better data manipulation.

There are other sets like VFP, Security extension etc that are not explained in this blog. It is interesting to note that these instructions sets can be interchangeably used as switching from one to another is as simple as setting one or more bits is a register, that can be accomplished by a single instruction.

With ARMv8, two higher level Execution States are introduced – AArch32 and AArch64. While the AArch32 is mostly similar to the instructions sets in the earlier architectures, AArch64 supports a single 64 bit instructions set and registers. It is possible to transition between these during exceptions by a process called Interprocessing.

ARM Processor Modes and Exception Levels

While the instruction sets define the type of instructions supported, ARM core supports multiple modes that defines how the access privilege, current exception taken etc. The processor modes supported are

Mode Description
User Mode with minimal access privilege. It is not possible to change to other modes from this mode. In an OS, generally the applications are executed in this mode
FIQ Entered up on an Fast Interrupt being received
IRQ Entered up on an Interrupt being received
Supervisor Same set of register visibility as in User mode but with higher privileges
Monitor Part of security extension that can be used during transition from a Secure Mode to Non-secure mode.
Abort Entered when there is an error accessing data memory(Data Abort) or instruction area (Prefetch abort)
Undefined Entered when a wrong instructions is executed
System Mode that has full privileges that can be used to configure the system. Usually the kernel operates in this mode in an OS.

Of these modes, except User mode, all others are said to be privileged modes. Usually the transition between these modes is done primarily with exceptions and in limited case, with instructions.

AArch64, introduces four Exception levels, represented by ELn, that is used to determine the level of privilege. EL0 is the least privileged while EL3 is the most. The recommended usage model for the same are:

ARMv8 Exception Model

Recommended usage of ARMv8 Exception Levels


It is key to remember that the AArch32 mode processor states are still usable when executing in that.

ARM Register Model

It is generally known that there are 16 general purpose registers (R0 through R12, R13 (Stack Pointer), LR (Link Register) and PC) and two Program Status Registers (CPSR and SPSR). But few of these registers are actually banked and different registers are available for different processor modes. The register bank in AArch32 state as given in ARMv8 TRM is given below:

Registers in ARM

Arm Register Banking

Based on the current processor mode, the registers are visible to software access. i.e. if the processor is in Supervisor mode, reading R13 will return SP_svc where as access to R13 will return SP_irq in IRQ mode. For FIQ mode, lot more registers are banked enabling fewer stack push/pops for faster interrupt processing. Also, since the FIQ vector is at the end of the vector table, the handler (ISR) can be directly placed at the FIQ vector address rather than having a branch to ISR instruction as in case of other exceptions.

In AArch64 mode, there are 31 64-bit general purpose registers labeled XL0 to XL30. XL30 is generally used as Procedure Link Register. None of these are banked. But there are few registers that are banked for each Execution level – Stack Pointer (SP), the Exception Link Register (ELR) and the Saved Process State Register (SPSR). To enable access of AArch32 registers from AArch64 state, the AArch32 registers are mapped to lease significant 32-bits of the AArch64 registers. The mapping of the same as given by ARM is as follows

  X0-X7 X8-X15 X16-X23 X24-X30
0 R0 R8_usr R14_irq R8_fiq
1 R1 R9_usr R13_irq R9_fiq
2 R2 R10_usr R14_svc R10_fiq
3 R3 R11_usr R13_svc R11_fiq
4 R4 R12_usr R14_abt R12_fiq
5 R5 R13_usr R13_abt R13_fiq
6 R6 R14_usr R14_und R14_fiq
7 R7 R13_hyp R13_und No Register

ARM Exceptions Model

In ARM architecture, anything that affects sequential flow of instructions is called an exception. For example, it could be an occurrence of an interrupt, access of wrong memory or even power-cycling the system. These exceptions are clearly defined along with the specific steps taken on an exception – typically involving change in processor mode and jumping to a vector address. Some of the defined exceptions are


Exception Description Entered Mode Vector Offset
Reset Entered on power on reset Supervisor mode 0×00
Undefined Instruction Invalid/Unimplemented instruction Undefined 0×04
Supervisor Call Usually by SWI/SVC instruction. Used for system call implementation Supervisor 0×08
Secure Monitor Call Usually by SMC/SMI instruction. Monitor 0×08
Prefetch Abort Invalid instruction memory access Abort 0x0C
Data Abort Invalid Data memory access Abort 0×10
IRQ Interrupt request to the core IRQ 0×18
FIQ FIQ request to core FIQ 0x1C


When any of these exceptions occurs in an ARM core, following set of sequences happens:

  • CPSR is copied to the SPSR of the mode being entered.
  • Processor mode is set to the new state
  • Whatever the existing instruction set being executed, it is changed to ARM state
  • Return address (of mode being left) is stored to the link register of the mode being entered
  • PC is set to the vector address corresponding to the entered exception

Now that the processor is in the new exception mode, the corresponding registers are banked. The software can choose to handle the exception as desired. Care should be taken that no registers are corrupted or lost, due to multiple or nested exceptions. Registers can be backed up in the stack.

To return back to the interrupted code, following operations can be done:

  • Restore the registers back to the original values (by popping from stack)
  • The above process can be done using a single instruction LDMFD^ if possible.

For AArch64, numerous exception classes are defined that are source of the exceptions like WFI, Illegal execution state, Misaligned PC Exception etc. The cause of exception can be obtained from the Exception Syndrome Register (ESR). The major happenings on an exception entry, as given by ARMv8 TRM,

  • The PE state is saved in the SPSR_ELx at the Exception level the exception is taken to.
  • The preferred return address is saved in the ELR_ELx at the Exception level the exception is taken to.
  • Execution moves to the target Exception level, and starts at the address defined by the exception vector.
  • The stack pointer register selected is the dedicated stack pointer register for the target Exception level.

To return from exception, an ERET instruction can be used. On executing the same:

  • PC is restored with the value held in the ELR_EL of level returning from.
  • PSTATE is restored by using the contents of the SPSR_EL of level returning from.

It is possible to switch from AArch64 to AArch32 states using exceptions.

Thus ARM Architecture is evolving fast to accommodate the growing requirements in computing. Now with basic idea about, the instruction set, register sets and exception model in ARM architecture, we will see about the Interrupt Architecture in specific in the upcoming blog.


Saravana Pandian Annamalai
13. August 2015 · Write a comment · Categories: Industrial, Technology · Tags: , , , ,

Windows Embedded Compact or more commonly referred to as WinCE is a Real Time Operation System offered by Microsoft. WinCE is ideal for many developments including industrial PC’s, medical devices, IoT designs etc. WinCE based HMIs (Human Machine Interface) are quiet common with advantage of popular .NET framework support in embedded devices.

Allwinner is a leading chip manufacturer whose low cost devices are established in very will in Tablet and other CE markets. Allwinner chips are also widely in low cost development platforms which are serious competitors for Raspberry PI. Though Allwinner does not offer industrial grade silicon, nevertheless they are used in allied applications like remote industrial plant systems, remote assistance solutions etc.

With Embien’s WEC2013 BSP offering for Allwinner A20, it becomes possible for using WinCE on the low cost platform for these applications. This blog discusses one such application where our BSP is used to meet a customer requirement for a Windows CE based industrial monitoring system.

Windows CE On New Marsboard

The New Marsboard is an Allwinner A20 based dual core platform. Brief specification of the system is as follows:

  • ARM Cortex-A7 Dual-Core
  • ARM Mali400MP2 Complies with OpenGL ES 2.0/1.1
  • 1GB DRAM, up to 2GB DRAM @ 480Mhz
  • 8GB Flash, SD (Max. 64GB) / MMC card slot, SATA Port
  • 10/100 Ethernet RJ45, USB WIFI(RTL8188EU) with Antenna
  • LCD Connector with Capacitive touch
  • Remote IR
  • USB 2.0 Ports – 4 x USB 2.0 Host, 1 x USB 2.0 OTG

The module is available at an affordable $58 USD price tag. With the expansion ports, it is possible to design custom carrier cards and interface with it. For more details, please visit

Below video demonstrates Embien’s Allwinner A20 based WEC2013 BSP running on the new Marsboard.

Remote industrial plant system

One of our customers uses our WEC2013 BSP to enable WinCE on their Remote industrial plant system. Since the customer has expertise in .NET developments and industrial applications, they were looking for a Windows based HMI. With our BSP, they used Allwinner A20 – New Marsboard platform, and created a WinCE based HMI. This enabled quick .NET based developments for the customer along with very low platform cost and low licensing price. The platform is quickly transformed to a Windows CE Industrial Computer. Some of the features supported are

  • RS485 Interface
  • RS422 Interface
  • Multiple RS232 interfaces
  • Ethernet Interface
  • Remote Assistance System
  • Remote Update
  • USB Host Storage for data transfer
  • Resistive Industrial grade touch panel

The system proved to be robust with intuitive screens. Multiple connectivity options opened up possibilities of data acquisition from multiple devices seamlessly. The Remote update feature enabled the System Integrator to update the application firmware as well as the WinCE OS remotely. FTP and other options like Telnet are provided for remote assistance and management.

As it can be seen, Windows Embedded Compact provides flexibility of running .NET framework on the low cost systems like Allwinner A20 and develop Windows CE Industrial Computer and Wince based HMI. With Embien’s Allwinner A20 WEC2013 BSP, it is possible to realize applications such as Remote industrial plant system etc.

About Embien Technologies: Embien Technologies is a leading provider of embedded design services for the Semi-conductor, Industrial, Consumer and Health Care segments. Our extensive experience in working with industrial technologies like CAN, Profibus, Ethernet, CANOpen, DeviceNet, Ethernet/IP, Modbus etc enables us provide solutions to customer quickly at an unmatched quality at a very low price point. Feel free to contact us for any of your industrial product/prototype development requirements.