| ??? 06/22/09 10:14 Read: times |
#166340 - You destroy succeding putchar()'s Responding to: ???'s previous message |
You set a global flag to indicate that the TX can receive a character.
(1) You either write to SBUF and wait till it has finished transmitting. (pretty wasteful) (2) Or you wait for the TX to be free before writing the next char into SBUF. You originally had method (1) and have commented it out so you can have some opti_fooler gobbledygook. Your method will lose all the putchar() calls as fast as you can send them. David. |
| Topic | Author | Date |
| UART code porting to SDCC | 01/01/70 00:00 | |
| doesn't SDCC warn about line 36? | 01/01/70 00:00 | |
| that's it | 01/01/70 00:00 | |
| ah ha | 01/01/70 00:00 | |
| Don't blame the optimiser! | 01/01/70 00:00 | |
| doesn't SDCC warn about line 36 | 01/01/70 00:00 | |
| hmmm | 01/01/70 00:00 | |
modified dog | 01/01/70 00:00 | |
| I cannot remember now | 01/01/70 00:00 | |
| xmt_flag., why "int"? | 01/01/70 00:00 | |
| if you want to use it as "int" / "char" | 01/01/70 00:00 | |
| You destroy succeding putchar()'s | 01/01/70 00:00 | |
| "Volatile" Helps | 01/01/70 00:00 | |
| "bit" is more useful | 01/01/70 00:00 | |
| buzzzzz | 01/01/70 00:00 | |
| family | 01/01/70 00:00 | |
| stdbool | 01/01/70 00:00 |