| ??? 09/05/08 13:29 Read: times |
#157976 - RE: Responding to: ???'s previous message |
Lynn Reed said:
I note that you are enabling the interrupts before you have finished programming the timer. This can cause a spurious interrupt before you are ready for one to occur.
And this may be a function of your assembler syntax, but are you sure that your code MOV TL0,#R0 MOV TH0,#R1 is correct? It looks like you are loading the timer with the address of the R registers instead of their contents. I have changed it to mov TL0,R0 and mov TH0,R1 . The timer is not been activated (until setb tr0) so enabling interrupts before programming timers is not a cause of worry. |
| 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 |