| ??? 06/12/05 15:35 Read: times |
#94729 - The code doesn't seem to do much Responding to: ???'s previous message |
The lack of comments in your code doesn't help with solving your problem. Besides, I can't see what useful work the code does apart from initialising things and having the two external interrupts enable and disable the timer. Where do you read any results? Also, your main code runs into isr_timer1: - this is not good. Anyway, I gather you want to measure the time between the two inputs - if this is the case, why do you start and stop the timer? Why not store its current value into some memory and do some calculations? Better still, use a processor with a CCA timer - that will do most of the work for you. What processor are you using? |
| Topic | Author | Date |
| interrupt problem | 01/01/70 00:00 | |
| The code doesn't seem to do much | 01/01/70 00:00 | |
| Reti? | 01/01/70 00:00 | |
| are you ok | 01/01/70 00:00 | |
| RETI & CALL | 01/01/70 00:00 | |
| The CPU performs an implicit call | 01/01/70 00:00 | |
| SORRY! i was wrong. | 01/01/70 00:00 | |
| No loop or no jump around isr_timer1 | 01/01/70 00:00 | |
| Is it need to set P3.2 if v use ext,intr | 01/01/70 00:00 | |
| read all about it | 01/01/70 00:00 | |
| No "main loop" | 01/01/70 00:00 | |
| re:code | 01/01/70 00:00 | |
| re: code | 01/01/70 00:00 | |
| Yes, and what have we gained? | 01/01/70 00:00 | |
Superman | 01/01/70 00:00 |