??? 12/30/08 00:26 Read: times |
#161215 - Not solved? Responding to: ???'s previous message |
K. Paulsen said:
Problem was solved (sic?) by shifting baudrate generation from T1 to T2. Are you sure that actually solved the problem, rather than just masking the symptoms? New problem - fitting to the headline : when using simple putchar
in the main loop there is no problem but when using fprint (sic?) instead the mentioned I/O interrupt is slowed down significantly. Does rather suggest that you have just reduced the symptoms without actually fixing the underlying cause. Is printf disabling interrupts during runtime ? As far as I have
read printf is also just using putchar so there should be no such problem, right ? Again, are you using a polled or interrupt-driven putchar? main things happen in the interrupt. What do you mean by that? Sounds potentially problematic... |
Topic | Author | Date |
Keil printf disables output ? | 01/01/70 00:00 | |
Cross post | 01/01/70 00:00 | |
Keil printf disables output ? | 01/01/70 00:00 | |
Keil printf disables output ? | 01/01/70 00:00 | |
Not solved? | 01/01/70 00:00 | |
printf slows I/O interrupt | 01/01/70 00:00 | |
unlikely to disable IRQs | 01/01/70 00:00 | |
you can use your own putchar() function with Keil | 01/01/70 00:00 | |
you can use your own putchar() function with Keil![]() | 01/01/70 00:00 |