??? 09/05/08 15:25 Read: times |
#157978 - Remember the update Responding to: ???'s previous message |
Lynn Reed said:
The timer is not been activated (until setb tr0) so enabling interrupts before programming timers is not a cause of worry. You mention that you don't start the timer until fully initialized. But you imply that you want to regularly change the timeout value (your code has a label "Update:" and the comment "routine to change the value of r0 and r1") and don't understand why you should stop the timer while reloading it. How does that go with your original question: "Is it necessary to use the instructions clr TR0 and setb TR0 to resart the timer with new timer values"? |
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 |