A developer's insight into ARM Cortex M debugging
Mark Kraeling, GE Transportation
EETimes (11/3/2010 1:00 PM EDT)
A software developer describes tips and tricks for using the built-in debugging options on the ARM Cortex M microcontroller. (Paper from ARM TechCon 2010.)
This paper focuses on the various hardware debug options that are available on ARM Cortex M microcontrollers. I explain the debug options from a software developer's point of view and demonstrate them using a standard ARM family tool. I also show specific debugging cases such as determining the cause of a reset and how you can find the cause using the different debug options. The paper will provide information that's useful when choosing the right debugging hardware for a project.
The paper provides an overview of the JTAG interface which ARM Cortex M is based, discusses the various interfaces that are available, and provides some tips and tricks to make debugging for the software developer easier.
To read the full article, click here
Related Semiconductor IP
- Chiplet Die-to-Die Interconnect IP Solution
- High speed MACsec Engine 100G/200G/400G/800G/1.6T
- Temperature/Voltage sensors
- AMBA Bus Host to eSPI Controller/Target
- AMBA Bus Host to eSPI Controller
Related Articles
- Debugging hard faults in ARM Cortex-M0 based SoCs
- Cortex M-3 microcontrollers and the RTX real-time kernel
- Why Embedded Software Development Still Matters: Optimizing a Computer Vision Application on the ARM Cortex A8
- ARM intrusive debugging for post-silicon SoC validation
Latest Articles
- ZK-Flex: A Flexible and Scalable Framework for Accelerating Zero-Knowledge Proofs
- ITP-STDP: An Intrinsic-Timing Power-of-Two Learning Engine for On-Chip SNN Training
- OpenEye: A Scalable Open-Source Hardware Accelerator for DNNs
- CHIMERA: A Flexible and Scalable 3.1 TOPS/W AI-MCU with Transformer Accelerator and 563 Gb/s Shared-L2 Memory Subsystem with QoS Guarantees
- CXL-ClusterSim: Modeling CXL-based Disaggregated Memory Cluster for Pooling and Sharing using gem5 and SST