Hard Fault & Exception Analysis - Debugging & Tracing

Cortex-M Fault Exception Types

Exception	Vector	CFSR Bits	Common Cause in Automotive
HardFault	3	HFSR.FORCED	Escalated fault (any configurable fault with priority disabled)
MemManage	4	CFSR.MMFSR	MPU access violation; stack overflow into guard region
BusFault	5	CFSR.BFSR; BFAR=address	Null/invalid pointer dereference; unaligned access on strict-align peripheral
UsageFault	6	CFSR.UFSR	Undefined instruction (Thumb2 not enabled); divide by zero; unaligned access

Fault Status Registers — Reading and Decoding

Cfault_decoder.c

/* Fault status register decoder — run in HardFault handler */
#include 
#include "Dem.h"

typedef struct {
    uint32_t r0, r1, r2, r3, r12, lr, pc, xpsr;  /* hw-pushed frame */
    uint32_t cfsr, hfsr, dfsr, mmfar, bfar;       /* fault status */
    uint32_t sp_at_fault;
} FaultContext_t;

volatile FaultContext_t g_faultContext;  /* inspectable in TRACE32 */

__attribute__((naked)) void HardFault_Handler(void) {
    __asm volatile (
        "TST    LR, #4          
"  /* bit 2: PSP (1) or MSP (0) used? */
        "ITE    EQ              
"
        "MRSEQ  R0, MSP         
"
        "MRSNE  R0, PSP         
"
        "B      HardFault_C_Handler 
"
    );
}

void HardFault_C_Handler(uint32_t *frame) {
    g_faultContext.r0   = frame[0];
    g_faultContext.pc   = frame[6];  /* PC at time of fault */
    g_faultContext.xpsr = frame[7];
    g_faultContext.cfsr = SCB->CFSR;
    g_faultContext.hfsr = SCB->HFSR;
    g_faultContext.bfar = SCB->BFAR;
    g_faultContext.mmfar= SCB->MMFAR;
    g_faultContext.sp_at_fault = (uint32_t)frame;

    Dem_ReportErrorStatus(DEM_EVENT_HARDFAULT, DEM_EVENT_STATUS_FAILED);
    /* Save to NVM for post-mortem analysis (see post-mortem-debugging lesson) */
    /* Then: safe state reset */
    NVIC_SystemReset();
}

TRACE32 HardFault Analysis Script

CMMhardfault_analysis.cmm

// Automated HardFault diagnosis in TRACE32

// Step 1: catch the fault
Break.Set HardFault_Handler /Program

Go
WAIT !STATE.RUN() 30s

// Step 2: read fault status registers
LOCAL &cfsr &hfsr &bfar &mmfar
&cfsr  = Data.Long(SFR:SCB.CFSR)
&hfsr  = Data.Long(SFR:SCB.HFSR)
&bfar  = Data.Long(SFR:SCB.BFAR)
&mmfar = Data.Long(SFR:SCB.MMFAR)

PRINT "CFSR:  0x" FORMAT.HEX(8.,&cfsr)
PRINT "HFSR:  0x" FORMAT.HEX(8.,&hfsr)
PRINT "BFAR:  0x" FORMAT.HEX(8.,&bfar)

// Decode key bits
IF (&cfsr & 0x8000)!=0.          PRINT "BFAR VALID: fault address = 0x" FORMAT.HEX(8.,&bfar)
IF (&cfsr & 0x0004)!=0.          PRINT "UNSTK ERR: fault on exception return (corrupt stack)"
IF (&cfsr & 0x0002)!=0.          PRINT "DACCVIOL: data access to MPU no-access region"
IF (&cfsr & 0x0100)!=0.          PRINT "IBUSERR: instruction fetch fault (NULL PC?)"
IF (&cfsr & 0x40000000)!=0.      PRINT "DIVBYZERO: divide by zero in UsageFault"

// Step 3: find faulting PC from hw-pushed stack frame
LOCAL &fault_pc
&fault_pc=Data.Long(Register(SP)+24.)   // frame offset 6 (PC)
PRINT "Faulting PC: " FORMAT.ADDRESS(&fault_pc)
List &fault_pc                           // show source at faulting instruction

// Step 4: full context dump
Var.View g_faultContext    // if fault handler saved this struct

Summary

HardFault decoding follows a 4-step sequence: CFSR identifies the fault type; BFAR/MMFAR gives the faulting address; the hardware-pushed PC (at SP+24) identifies the exact instruction; the call stack reconstructs what led there. Implementing a naked HardFault handler that saves the full context to g_faultContext before resetting enables post-mortem analysis even when the device has already reset — the struct is visible in TRACE32 immediately after reconnecting, before the application code has had any chance to overwrite RAM.

🔬 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.