←back to thread

Hacking Coroutines into C

(wiomoc.de)
142 points jmillikin | 2 comments | 13 Jul 25 01:12 UTC | HN request time: 0.801s | source
1. userbinator ◴[13 Jul 25 04:23 UTC] No.44547483[source]▶
Of course, the project didn’t allow us to use an RTOS.

That tends to just make the project eventually implement an approximation of one... as what appears to have happened here.

How I'd solve the given problem is by using the PWM peripheral (or timer interrupts if no PWM peripheral exists) and pin change interrupts, with the CPU halted nearly 100% of the time. I suspect that approach is even simpler than what's shown here.

replies(1): >>44551402 #
2. kevin_thibedeau ◴[13 Jul 25 16:07 UTC] No.44551402[source]▶
You should not use interrupts for button inputs. You will just end up hammering the processor with useless interrupts when the switch bounces. Human interfaces can be polled and still maintain responsiveness. If polling isn't fast enough for machine actuated IO or you need to stay in a low power state then interrupts could be considered but you really need a non-naive solution that disables the interrupt from within the handler for a specified timeout duration.