Closed brackendawson closed 11 years ago
The second part of this bug (missing 25FPS) is valid. I can fix it by using the second, higher priority TImerA0 interrupt to keep counting timer wraps while the pattern's frame code is running.
Using another clock source isn't really an option, the VLO varies too much from one chip to the next.
Does quoting the commit associate the bug with it?
883135722a1f3c22b8d3639e9a65e3d88d93e1fa
Currently it lights the Red LED if the USI code is still transmitting when we start to calculate the next frame. If it's time for a new frame when the last one is still being processed it probably won't light. Not sure but I might also be missing 25 FPS by not counting some timer ticks.