??? 01/11/05 16:01 Read: times |
#84761 - Calling printf from an ISR Responding to: ???'s previous message |
Calling printf from an ISR (Interrupt Service Routine) is definitely a Bad Idea! - especially if you call it from elsewhere in your code!!
printf is not reentrant - so calling it from an ISR could well end up with data corruption and all sorts of garbled output! printf it is also a very large function and, therefore, likely to take a long time to execute - not generally Good Things in an ISR. |
Topic | Author | Date |
Multiplication Problems and data types | 01/01/70 00:00 | |
use unsigned int for totcount | 01/01/70 00:00 | |
Wrong printf format specifier? | 01/01/70 00:00 | |
yes i am using printf | 01/01/70 00:00 | |
manual! | 01/01/70 00:00 | |
using %d and %x | 01/01/70 00:00 | |
%u | 01/01/70 00:00 | |
Exactly what it says on the tin! | 01/01/70 00:00 | |
Division problem? | 01/01/70 00:00 | |
division problem in keil evaluation? | 01/01/70 00:00 | |
Which Part? | 01/01/70 00:00 | |
its ok i have sorted it! | 01/01/70 00:00 | |
Still a problem, then... | 01/01/70 00:00 | |
not so strange | 01/01/70 00:00 | |
Not so strange? | 01/01/70 00:00 | |
Need complete code! | 01/01/70 00:00 | |
Like this | 01/01/70 00:00 | |
code | 01/01/70 00:00 | |
Calling printf from an ISR | 01/01/70 00:00 | |
other interrupts wont get in the way | 01/01/70 00:00 | |
ISR | 01/01/70 00:00 | |
yes i see what you mean | 01/01/70 00:00 | |
No No Inside ISR![]() | 01/01/70 00:00 |