| Aspect | Detail |
|---|---|
| Mechanism | Debugger writes ARM BKPT 0xBE00 (Thumb) or 0xE1200070 (ARM) at breakpoint address; restores original instruction on resume |
| Flash limitation | Cannot use in execute-in-place (XiP) flash without re-erase — destructive; TRACE32 warns 'SWBp not possible in Flash' |
| ROM/flash workaround | Use hardware breakpoint instead, or copy code to RAM and set SW breakpoint in RAM copy |
| Count | Unlimited in RAM; zero in read-only flash |
| TRACE32 command | Break.Set 0x80001234 /Program — sets SW breakpoint at address |
Software Breakpoints: BKPT Instruction
Hardware Breakpoints: FPB (Flash Patch and Breakpoint)
| Core | HW Breakpoints Available | Watchpoints Available |
|---|---|---|
| Cortex-M0/M0+ | 2 (FPB) | 2 (DWT) |
| Cortex-M4/M7 | 6 (FPB) | 4 (DWT) |
| Cortex-M33 | 8 (FPB) | 4 (DWT) |
| Aurix TC3xx (per core) | 8 (OTGS hardware triggers) | 8 (OTGS data triggers) |
CMMhw_breakpoints.cmm
// Hardware breakpoints and conditional breakpoints in TRACE32
// Simple hardware breakpoint at function entry
Break.Set __func_CanReceive /Program /Hardware
// Conditional breakpoint: halt only when CAN ID matches 0x200
Break.Set 0x80001234 /Program /Hardware /CONDition Register(R0)==0x200
// Count breakpoint: halt on 100th execution (useful for loop bugs)
Break.Set 0x80005678 /Program /Hardware /COUNT 100
// Address range breakpoint: halt on any access to a function
Break.Set 0x80001000--0x80001FFF /Program /Range
// List all breakpoints
Break.ListWatchpoints: DWT Data Watchpoints
CMMwatchpoints.cmm
// Watchpoints: halt on read/write of a specific variable or address range
// Halt when g_CanRxBuffer is written
Break.Set g_CanRxBuffer /Write /Hardware
// Halt when a corrupted pointer zone is read
Break.Set 0x20001000--0x200010FF /Read /Hardware
// Halt on read OR write to a register
Break.Set SFR:CAN0.MCR /ReadWrite /Hardware
// Access watchpoint with value condition: halt when speed > 250 km/h
// (R0 holds value at DWT hit — check in condition)
Break.Set g_vehicleSpeed_kmh /Write /Hardware /CONDition Data.Long(g_vehicleSpeed_kmh)>250.
// Watchpoint on stack pointer: detect stack underflow
Break.Set 0x20000000--0x200000FF /Write /Hardware // guard zone at bottom of stack
Break.ListStepping Modes
| Mode | TRACE32 Key / Command | Behaviour |
|---|---|---|
| Step Into | F11 / Step | Executes one instruction; enters called function |
| Step Over | F10 / Step.Over | Executes one source line; treats function calls as single step |
| Step Out | Shift+F11 / Step.Out | Runs until return from current function |
| Run to cursor | F7 / Go | Sets temporary breakpoint at cursor line; runs to it |
| Step by HLL line | Step.HLL | Source-level step: executes all instructions for one C line |
| Reverse step | Step.Back | Requires trace buffer; steps backward through recorded execution |
Summary
SW breakpoints are unlimited in RAM but cannot be set in flash without re-erasing — use hardware breakpoints for flash code. The DWT provides 2–8 hardware watchpoints for data access detection; these catch write corruption bugs without any code modification. Conditional breakpoints filter out irrelevant halt events and are essential when a bug only occurs with a specific register value or after N iterations. Step.HLL is the most productive stepping mode for source-level debugging; Step.Back (with trace) allows root-cause investigation without restarting the debug session.
🔬 Deep Dive — Core Concepts Expanded
This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.
Key principles to reinforce:
- Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
- Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
- Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.
🏭 How This Topic Appears in Production Projects
- Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
- Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
- Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.
⚠️ Common Mistakes and How to Avoid Them
- Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
- Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
- Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
- Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.
📊 Industry Note
Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.