Motorola 68000 Timing
Clock versus bus timing
The 68000 clock period is not equivalent to instruction latency. Instructions may require multiple internal and external bus phases.
SLeeLa records clock cycle, bus cycle, operation class, address, data, transfer size, read/write, wait/acknowledge, interrupt acknowledge, and bus arbitration.
Timing classes
The model distinguishes byte and word reads/writes and read-modify-write cycles. Interrupt acknowledge and bus arbitration have their own timing paths.
Design principle
Do not collapse all instructions into a fixed cycle count. The effective addressing mode, operand size, memory access, and external bus conditions can alter elapsed time.
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:
lib/cpu/TIMING.md— Voltages, Variable Clocks, and Expert Timings:SLVoltageRail(actual voltages in mV),SLCpuTiming,SLBusTiming,SLRamTiming,SLIOTiming, the Novice/Basic/Advanced/ExpertSLTimingClasstiers, and theSLTimingProfile->SLTimingManifesta compiled.sleelaimage carries so the compiler/VM honor the declared operating point.lib/cpu/components/README.md— running a CPU at spec and overclocking it (SLClockPolicy/setSpecClock/overclock), plus the RAM / storage / optical / system-bus parts bin and the DMA / GPU / native-RAM options.
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.