Author: Andrew Irwin

The GNU Arm Embedded Toolchain provides a complete open source toolchain for the Arm Cortex-M family of processors. The GNU compiler for Arm (GCC) offers various levels of optimization that can significantly improve the performance and code size of applications running on Cortex-M0/M1 microcontrollers. Overview of Cortex-M0/M1 Processors The Cortex-M0 and Cortex-M1 processors are Arm’s

The GNU ARM Embedded Toolchain provides a robust set of tools for developing, testing, and debugging ARM Cortex-M0/M1 based applications. One of the key features it offers is the ability to perform comprehensive code safety assessments using the GNU-ARM tools included in the toolchain. Code safety refers to detecting potential bugs, errors or vulnerabilities in

The ARM Cortex-M0 processor implements the PendSV exception handler to allow low priority interrupts to preempt current execution. However, the use of a bootloader can impact how PendSV exceptions are handled. This article provides an in-depth look at PendSV exception handling on the Cortex-M0 and examines how a bootloader can affect it. Overview of PendSV

The Cortex-M0 processor implements a basic exception model with 7 exception types. The PendSV (pendable service request) exception is one of these and allows low priority or background tasks to be run when no other exception is active. Handling the PendSV exception properly is key to implementing an RTOS or multitasking firmware on Cortex-M0 devices.

When developing embedded systems using the ARM Cortex-M0 processor and a bootloader, you may encounter issues with incorrect vector tables causing the system to crash or behave erratically on startup. The root cause is often a mismatch between the vector table defined in the bootloader code and the application code. This article provides a guide

The Cortex-M0 and Cortex-M3 are two popular ARM processor cores used in many embedded and IoT applications. Both support vector table remapping, which allows flexibility in locating the exception/interrupt vector table. However, there are some key differences between the Cortex-M0 and Cortex-M3 implementations of vector table remapping that developers need to be aware of. Overview

When a context switch occurs on a Cortex-M0 processor, the state of the current thread must be saved so that it can be restored when the thread is switched back in. This includes saving the values of all registers that are modified by the thread. The processor must also load the register values for the

The Cortex-M0 is one of ARM’s smallest and simplest microcontroller cores, aimed at low-cost and low-power embedded applications. Like all Cortex-M cores, the M0 starts execution at the reset vector located at address 0x00000000. This reset vector points to the initial stack pointer value and the reset handler function. The vector table on Cortex-M0 contains

Context switching on Cortex-M0 microcontrollers can impact real-time performance if not optimized properly. By following best practices like minimizing the number of context switches, reducing switch latency, and tuning interrupt handling, significant improvements are possible. Understanding Context Switching A context switch occurs when the processor stops what it is currently doing, saves its state to

When developing embedded systems using ARM Cortex-M processors, a common issue that can occur is the bootloader causing an incorrect vector table and problems with the PendSV interrupt. This can lead to hard-to-diagnose faults and system crashes. In this article, we’ll examine the root causes of this issue and provide solutions to resolve it. The