Home /Modules/cpu/TIMING.md

TIMING.md

lib/cpu/cortex-r/TIMING.md · 48 line(s) · markdown

Cortex-R Timing and Real-Time Analysis

No universal cycle count

Cycle timing depends on the exact core, instruction mix, cache/TCM configuration, memory placement, bus contention, interrupts, and peripheral behavior. A generic Cortex-R profile cannot guarantee worst-case execution time.

Evidence levels

Sources of variability

Analysis report

Every timing report identifies the exact core profile, clock, memory regions, cache and TCM configuration, interrupt assumptions, bus model, and evidence class. Distinguish average latency from a justified upper bound. Never label an estimate as a guaranteed WCET.

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.