On Sun, Nov 8, 2026 at 11:16 PM Daniel <[email protected]> wrote: > "John R. Hogerhuis" <[email protected]> writes: > > > Can anyone explain to me "cycles" versus "states" in regard to the > 8085 > > and the model 100? > > Should I be able to translate clock speed and instruction cycles > > directly to time? > > How accurate are the rtc and cpu crystals in the M100? > > Are there waits when accessing RAM that might change timing? > > I am doing some analysis with timing loops and it seems to indicate > the > > cpu is actually running at 2.3235mhz. But nominalé is 2.4576mhz right > > (after /2)? > > -- John. > > instruct timing is measured in T-states right? each equals a CPU clock > period. You should be able to calculate execution time directly at > 2.4576. Though the m100 generates interrupts at 256Hz for housekeeping, > it might account for the apparent slowdown. Could you try running the > timing > loop with interrupts temporarily disabled? Maaybe youd see the expected > clock speed. > > Running test under disabled interrupts, yes.
Thanks, -- John.
