| ??? 12/02/09 15:58 Read: times |
#171405 - Traditional to keep track of timer reloads for slow events Responding to: ???'s previous message |
In a traditional design, I may have a 10ms (or maybe 100ms) interrupt that keeps track of a number of counters. Some are timeout counters that are just decremented to zero and doesn't have any associated action. Some are multiplier to extend the timer for 1s, or 10s or maybe 1h events, and where a count to zero results in the variable being reloaded and some action performed.
A 32-bit processor will normally also have 32-bit timers, but a 16-bit timer works well for handling one-year delays. All it takes is software to keep track of the number of reloads. |
| Topic | Author | Date |
| Maximum Timer interrupt-89S52?? | 01/01/70 00:00 | |
| Use a variable to count number of overflows | 01/01/70 00:00 | |
Yes, the counter works! | 01/01/70 00:00 | |
| Just use a software counter. | 01/01/70 00:00 | |
| Search terms | 01/01/70 00:00 | |
| Traditional to keep track of timer reloads for slow events | 01/01/70 00:00 |