| David Prentice 06/22/09 05:14 Read: 190 times Wormshill England |
#166340 - You destroy succeding putchar()'s Responding to: Girish Nikam'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 | Girish Nikam | 06/21/09 13:29 |
| doesn't SDCC warn about line 36? | Frieder Ferlemann | 06/21/09 13:59 |
| that's it | Jan Waclawek | 06/21/09 15:03 |
| ah ha | Jez Smith | 06/21/09 15:08 |
| Don't blame the optimiser! | Andy Neil | 06/22/09 01:36 |
| doesn't SDCC warn about line 36 | Girish Nikam | 06/21/09 22:13 |
| hmmm | Jez Smith | 06/22/09 00:42 |
modified dog | Andy Peters | 06/23/09 14:21 |
| I cannot remember now | Jez Smith | 06/21/09 14:33 |
| xmt_flag., why "int"? | Mahesh Joshi | 06/22/09 01:53 |
| if you want to use it as "int" / "char" | Andy Neil | 06/22/09 02:47 |
| You destroy succeding putchar()'s | David Prentice | 06/22/09 05:14 |
| "Volatile" Helps | Girish Nikam | 06/22/09 07:42 |
| "bit" is more useful | Mahesh Joshi | 06/22/09 08:16 |
| buzzzzz | Erik Malund | 06/22/09 08:37 |
| family | Jan Waclawek | 06/22/09 13:44 |
| stdbool | Oliver Sedlacek | 06/23/09 06:44 |