??? 12/03/04 11:53 Read: times |
#82456 - Erik Responding to: ???'s previous message |
Hell, I typed a lengthy and detailed reply to your post and by the time I clicked 'Post' the blasted forum had logged me off.
In a nutshell though the position is this: In order to use ISRs of any length, short or long, you need to take into account exactly the same things. You cannot simply say 'they must be short' because you don't know how short unless you have actually worked it out. If you do simply choose some arbitrary execution time limit you are putting yourself in the precise position you advise against - you have code that may work this week, may pass all the tests then fail next week. It is utterly useless to have some sort of general 'ISRs must be short' rule. |
Topic | Author | Date |
soft I2C and interrupts. | 01/01/70 00:00 | |
Interrupt Issue with I2C | 01/01/70 00:00 | |
Interrupts & I2C | 01/01/70 00:00 | |
I2C or SMBus | 01/01/70 00:00 | |
Not SMBus PHILIPS I2C | 01/01/70 00:00 | |
a possible fix | 01/01/70 00:00 | |
Generic answer that is not true | 01/01/70 00:00 | |
ok Michael | 01/01/70 00:00 | |
Easy as pie. | 01/01/70 00:00 | |
Polarised view | 01/01/70 00:00 | |
no, Donald | 01/01/70 00:00 | |
" | 01/01/70 00:00 | |
Burned Fingers | 01/01/70 00:00 | |
Donald, Michael | 01/01/70 00:00 | |
Erik | 01/01/70 00:00 | |
100% Agree | 01/01/70 00:00 | |
Ok![]() | 01/01/70 00:00 | |
Lazy | 01/01/70 00:00 |