|
|
|
![]() |
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
In order to ensure that the read operation on an timer+interrupt-driven clock counter variable doesn't get messed up, instead of disabling ALL interrupts, I decided to simply shut off the timer, do the read, and then turn it back on. This should keep the clock counter variable safe while allowing other interrupts to jump in and do their thing during the clock read. Is this insane?
|
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| heres the code. y this not working | omega | Programming | 16 | 31-03-2004 15:18 |
| Timer interrupt hic-cupping - HELP | roknjohn | Programming | 9 | 15-03-2004 17:56 |
| Interrupt Handlers and Variable Scope | kaszeta | Programming | 2 | 14-02-2004 18:30 |
| When would I use an interrupt? | Apollo Clark | Programming | 7 | 18-01-2004 13:29 |
| Interrupts Questions | mightywombat | Programming | 0 | 03-01-2004 14:50 |