Home /Modules/cpu/TIMING.md

TIMING.md

lib/cpu/cortex-m/TIMING.md · 50 line(s) · markdown

Cortex-M Timing and Exceptions

Timing policy

Timing depends on core variant, instruction mix, memory placement, wait states, bus contention, debug configuration, and optional extensions. The simulator should separate architectural correctness from cycle-accurate timing.

Evidence classes

Sources of variable latency

Interrupt behavior

Priorities and masking rules follow the configured NVIC/profile. Model architectural exception state precisely; model latency only to the evidence level available. Late arrival and tail-chaining are not universal timing constants.

Output

Timing reports must identify profile, variant, clock, memory assumptions, enabled extensions, and evidence level. Do not publish a single family-wide cycles-per-instruction figure.

Expert timing, voltages, and variable clocks (shared across all CPU models)

The per-CPU timing above is the architectural/behavioral view for this part. The adjustable, quality-first timing system is shared by every CPU model in lib/cpu and is documented once, in the package guide:

Every CPU model (this one included) inherits the clock/overclock surface from SLCPURuntime and can be assembled with those shared expert-timing, voltage, and component options; they are a build-layer concern, not re-declared per CPU.