| ??? 09/06/08 10:42 Read: times |
#158000 - Re:problem with updating a 16-bit counter Responding to: ???'s previous message |
Per Westermark said:
The problem with updating a 16-bit counter with two 8-bit writes while the counter is ticking, is that if the low-order byte performs a turn-around before both bytes are written, then you can get a compiletely different total count than expected.
That is why I opted to stop the timer using CLR TR0 and than reload timer and start it again.So I get the required time delay. |
| Topic | Author | Date |
| Auto reload | 01/01/70 00:00 | |
| See any potential problems? | 01/01/70 00:00 | |
| Enable interrupts last | 01/01/70 00:00 | |
| RE: | 01/01/70 00:00 | |
| this may, some day, bite you in your lagest muscle | 01/01/70 00:00 | |
| also may, some day, bite you in your lagest muscle | 01/01/70 00:00 | |
| CALL or JMP | 01/01/70 00:00 | |
| good catch | 01/01/70 00:00 | |
| RE: | 01/01/70 00:00 | |
find out | 01/01/70 00:00 | |
| Remember the update | 01/01/70 00:00 | |
| So, what the final answer ? | 01/01/70 00:00 | |
| diplomatic answer - OK and the direct too | 01/01/70 00:00 | |
| care with multi-read/multi-write of running timers | 01/01/70 00:00 | |
| Re:problem with updating a 16-bit counter | 01/01/70 00:00 | |
| If you knew that.................. | 01/01/70 00:00 | |
| RE:If you knew that.................. | 01/01/70 00:00 |