Flash Programming via TRACE32 - Debugging & Tracing

Flash Algorithm Selection

Flash Type	TRACE32 Command	Notes
Aurix TC3xx PFlash	FLASH.ReProgram / FLASH.Program	Uses internal HSM-based flash driver; requires DMU configuration
Aurix TC3xx DFlash	FLASH.Program /DFLASH	4 kB sectors; BCB and UCB erase requires ENDINIT clearance
NXP S32K3 PFlash	FLASH.AUTO	Selects correct algo from T32 flash database automatically
STM32H7 Flash	FLASH.AUTO	Dual-bank; cache flush required after programming
SPI NOR (external)	FLASH.SPI.*	SPI flash via bit-bang or SPI master in target MCU

Programming PFlash on Aurix TC3xx

CMMaurix_pflash.cmm

// Program Aurix TC397 PFlash (16 MB) via TRACE32 FLASH driver
// Requires: SYStem.Up already run; symbols loaded optional

// Step 1: Declare flash geometry to TRACE32
FLASH.RESet
FLASH.Create 1. 0x80000000--0x807FFFFF 0x4000 TARGET Long  // 16 kB sectors, PFlash0
FLASH.Create 2. 0x80800000--0x80FFFFFF 0x4000 TARGET Long  // PFlash1

// Step 2: Select flash programming algorithm
FLASH.TARGET C:0x70000000 C:0x70001000 0x2000 ~~/demo/tricore/flash/tc3xx.bin
// Algorithm binary placed in Core0 DSPR at 0x70000000
// Stack pointer for algorithm: 0x70001000

// Step 3: Erase sectors covering the new image
FLASH.Erase 0x80000000--0x80FFFFFF

// Step 4: Program ELF (code sections only, not debug sections)
FLASH.ReProgram ALL /Erase   // combined erase+program in one pass (faster)
Data.LOAD.Elf build/app.elf  // code sections automatically mapped to flash
FLASH.ReProgram OFF           // commit programming

// Step 5: Verify (CRC comparison)
FLASH.VERIFY 0x80000000 /CRC

PRINT "PFlash programmed and verified OK"
SYStem.Reset                  // reset target to start from new firmware

DFlash / EEPROM Emulation Programming

CMMaurix_dflash.cmm

// Aurix DFlash: UCB (User Configuration Block) and user data programming

// UCB programming: JTAG password protection configuration
// WARNING: incorrect UCB programming can permanently lock the device

// Read current UCB0 (Boot Mode Header + passwords)
Data.dump 0xAF400000--0xAF4000FF /Long  // UCB0 in DFLASH

// Program user EEPROM area (DFlash sector 0)
FLASH.RESet
FLASH.Create 5. 0xAF000000--0xAF007FFF 0x1000 TARGET Long  // DFlash user sector 0
FLASH.TARGET C:0x70000000 C:0x70001000 0x2000 ~~/demo/tricore/flash/tc3xxdf.bin

// Write calibration data to EEPROM emulation region
FLASH.Program 0xAF000000
Data.Set 0xAF000000 %Long 0x12345678   // calibration magic
Data.Set 0xAF000004 %Float 9.81        // gravity constant (example)
FLASH.Program OFF

// Verify
Data.COMPARE 0xAF000000++0x7 0xAF000000 /Long
IF FOUND()
    PRINT "DFlash verify PASS"
ELSE
    PRINT %ERROR "DFlash verify FAIL — read-back mismatch"

Program, Verify and CRC Checking

Verification Method	TRACE32 Command	Notes
CRC32 of flash region	FLASH.VERIFY /CRC	Computes CRC32 over programmed range; fast
Read-back compare	Data.COMPARE	Byte-by-byte comparison; slower but exhaustive
SHA-256 via HSM	HSM_CMAC_verify in CMM	Verify HSM-computed hash matches expected; detects tampering
TRACE32 auto-verify	FLASH.ReProgram ALL /VERIFY	Automatically verifies after programming

Summary

TRACE32 flash programming follows a three-phase sequence: declare geometry (FLASH.Create), load the flash algorithm binary to target RAM, then erase-program-verify. The FLASH.ReProgram ALL /Erase mode combines all three phases for efficiency. DFlash UCB programming requires particular caution — programming the wrong UCB content can permanently disable JTAG access. Always read and archive the current UCB content before any DFlash write, and test UCB changes on engineering samples before applying to production units.

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