| ??? 04/26/07 13:27 Read: times |
#138009 - 1ms vs 1.04ms Responding to: ???'s previous message |
Well, you've just formulated the problem.
If your scheduler ticks once every 1ms and transmission of 1 byte takes just slighly more, then unless you have a hardware FIFO you're going to miss a lot of time slots and your effective transmission rate will go down about to one half of the possible maximum. Now it depends on your application whether this matters or not. On the Rx side this should be just fine. JW PS. Huh, moved to Munich, I see... What, looking for better beer? :-) |
| Topic | Author | Date |
| Serial transmission in scheduller instead of int | 01/01/70 00:00 | |
| danger, maybe, loss of efficiency YES ABSOLUTELY!! | 01/01/70 00:00 | |
| avoiding interrupts means... | 01/01/70 00:00 | |
| Scheduller.... | 01/01/70 00:00 | |
| there is no such thing | 01/01/70 00:00 | |
| Limitation API | 01/01/70 00:00 | |
| API? | 01/01/70 00:00 | |
| Yes ASIC design fixed... | 01/01/70 00:00 | |
| debug possibilities? | 01/01/70 00:00 | |
Monitor is nice idea | 01/01/70 00:00 | |
| 1ms vs 1.04ms | 01/01/70 00:00 | |
| absolutely NOT | 01/01/70 00:00 | |
| ok but 1 byte is transmitted together | 01/01/70 00:00 | |
| if it does, then you need to KISS | 01/01/70 00:00 | |
| I took the 1ms processing tick for granted... | 01/01/70 00:00 | |
| Thanks for the inputs... | 01/01/70 00:00 |