English
Debugging hard faults in ARM Cortex-M0 based SoCs
Shashikant Joshi & Hanumanthaiah Shruti (Cypress Semiconductors)
embedded.com (February 08, 2017)
Programmable system-on-chip (PSoC) architectures integrate a wide range of capabilities, including MCU cores like the Cortex-M0, programmable analog blocks (PAB), programmable digital blocks (PDB), programmable interconnect and routing, a wide range of interfaces and peripherals, and advanced capabilities such as capacitive touch sensing. These architectures over many advantages over traditional microcontrollers and can substantially reduce design time and system bill of materials (BOM) cost.
As the complexity of programmable system-on-chip architectures and their MCU increases, so do the issues that can occur at each stage of design. One common issue developers face in Cortex-M0-based embedded systems is the hard fault. In some cases, we might get lucky and be able to quickly locate the source of the hard fault. However, most of the time chasing down a hard fault can be very time consuming. In this article, we will discuss some common errors programmers make and how to debug the hard fault caused by these errors.
|
E-mail This Article | 
|
|
Printer-Friendly Page |
|
||||||
Related Articles
- Designing with ARM Cortex-M based System-On-Chips (SoCs) - Part I: The basics
- Designing with ARM Cortex-M based SoC Achitectures: Part 2 - Some typical applications
- An introduction to ARM Cortex-M0 DesignStart
- Method for Booting ARM Based Multi-Core SoCs
- ADCs in SoCs - Just a placeholder or a vital subsection?
New Articles
- Increase battery life of Consumer Products using architecture simulation
- Area Overhead: GOH Control and Track
- Distorted Waveform Phenomena in 7nm Technology Node and its Impact on Signoff Timing Analysis
- AI Challenges for Next-Gen EDA
- It's Not My Fault! How to Run a Better Fault Campaign Using Formal