(71B) FORTH questions

[J-F Garnier]

(06-16-2023 03:18 PM)Valentin Albillo Wrote:  "1084-3: Small probability exists for bad timer readings, causing random clock errors."

I vaguely remember that the only solution required reading the clock three consecutive times and checking them, in order to assure a good reading.

Thanks Valentin, I didn't remember that bug.
Actually, the code is already doing up to 3 reads with this algorithm (GETTIM routine):
Read timer -> B
Read timer -> A
If A#B then Read timer -> A

The bug is classified as minor in this document, with these extra details:
"Risk of this bug occurring increases if user runs 2 or 3 ON TIMERs with short intervals."
It may come from an inconsistency between the timer and the target time (the 2 quantities I mentioned above), in case a timer event occurs between the reading of these 2 quantities. Without ON TIMER statements, hardware timer events occur every 4.55 hours, so the risk is very low.

I don't know how to easily reproduce the bug, and I can't check if it was fixed in the latest version 2CDCC.

J-F