| ??? 09/05/08 15:02 Read: times |
#157977 - this may, some day, bite you in your lagest muscle Responding to: ???'s previous message |
The timer is not been activated (until setb tr0) so enabling interrupts before programming timers is not a cause of worry.
so many things are "not a cause of worry" NOW but may, some day, bite you in your lagest muscle. As a general rule NEVER activate interrupts till ALL initialization is finished. Some day you add some other initailize code where the interrupts enable IS "a cause of worry" and will have a nice debugging session to find out that you activated interrupts before ALL initialization was finished. Erikj |
| 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 |