| ??? 09/26/07 18:59 Read: times |
#145014 - very condensed but clear Responding to: ???'s previous message |
But from my experiences teaching 8051 assembly to ungraduate students as a tutor, I think this is all information needed for anyone getting it going.
Maybe one issue: most newcomers seem to have problems enabling the proper interrupt at all (at least that happened in 8/10 cases in the course I tutored) so maybe that is another issue to be addressed in the FAQ? Beside, a nice and readable short article on the DOs and DONOTs of interrupts :) Esp. the "keep it short and only set a flag" rule should recieve double attention. I have seen people doing everything in the interrupts and stoping all work because they couldn't debug it anymore... cheers, Matthias PS: As I use the same technique in my own diploma thesis, is there am official term for those flags? They are not exactly semaphores but somehow a "schedule flag" which schedules a task to be run asap in the main loop. |
| Topic | Author | Date |
| New FAQ III. | 01/01/70 00:00 | |
| Similarly for 'C' | 01/01/70 00:00 | |
| floating point | 01/01/70 00:00 | |
| "fixed point" FAQ by Erik Malund | 01/01/70 00:00 | |
| corrected FAQ | 01/01/70 00:00 | |
| on 3V3 and 5V | 01/01/70 00:00 | |
| when a RC "debouncing" circuit goes wrong | 01/01/70 00:00 | |
| basic interrupt hints | 01/01/70 00:00 | |
| the C hater | 01/01/70 00:00 | |
| better? | 01/01/70 00:00 | |
| very condensed but clear | 01/01/70 00:00 | |
| it's good sometimes to violate the rules | 01/01/70 00:00 | |
| Rule breaking | 01/01/70 00:00 | |
| The idea of keeping the ISR routine short... | 01/01/70 00:00 | |
| epanded | 01/01/70 00:00 | |
Exactly | 01/01/70 00:00 | |
| flags | 01/01/70 00:00 |