upvote
Having done basically that a couple of weeks ago (with a scope to verify timing signals), its actually pretty common, specially when you are implementing protocols with hard timing requirements.

And in my case, I was actually troubleshooting the code that makes leds blink, with a bit-banged implementation on a deterministic processor.

reply
Have you never experienced a bug that goes away from adding/removing a logging statement?

I recently restructure a logging module in a client’s project, and the resulting performance gains exposed all sort of race conditions.

Sometime all you get is an LED.

reply
I had a bug triggered by adding a comment. :-(
reply
Wow, how did that work?
reply
Comments shouldn't affect code which executes at all, right?

So... please tell us more!

reply
> This is a waste of your time.

This is the reality of highly constrained embedded systems. If you don't like that, I'd suggest moving to web dev where you have state of the art debugging.

reply
That's kind of like saying "don't be a farmer--you have to go outside".
reply