??? 05/14/08 05:44 Read: times |
#154752 - Two Program Responding to: ???'s previous message |
In the one I did the "right way" I broke it up into about 70 steps (30 cases with some having sub cases) to insure I could get back to main() in time. Plus I ended up with a lot of static data to keep data I was collecting. It works fine. But I felt it would have been less tedious with a bigger ISR. (just plain for loops)
The other is an SMBus (I2C) slave. To minimize clock stretching the ISR is huge. The main is similar to program one, except it just runs straight through. Of course I then had to disable interrupts for all the data exchanges. For a bigger CPU a preemptive RTOS may have been a candidate. I guess my point is as a beginner follow the rules. But remember they are not laws. |
Topic | Author | Date |
Struct member losing value | 01/01/70 00:00 | |
Please post your code | 01/01/70 00:00 | |
Posted here (along with file descriptions): | 01/01/70 00:00 | |
the can of worms | 01/01/70 00:00 | |
Your program needs to be restructured | 01/01/70 00:00 | |
Can't mod this one up enough. | 01/01/70 00:00 | |
Thanks for the tips | 01/01/70 00:00 | |
You're doing pretty good then. | 01/01/70 00:00 | |
I think that it can be said in a simple way | 01/01/70 00:00 | |
Sorry but.. | 01/01/70 00:00 | |
Agreed | 01/01/70 00:00 | |
the phrase was | 01/01/70 00:00 | |
I agree | 01/01/70 00:00 | |
Don't ignore rules | 01/01/70 00:00 | |
What is "short" in an ISR...? | 01/01/70 00:00 | |
Two Program | 01/01/70 00:00 | |
breaking switch/case![]() | 01/01/70 00:00 | |
Do you understand why? | 01/01/70 00:00 | |
make it a FAQ, please... | 01/01/70 00:00 |