Skip to content
poll

Honest answer: what do you trust most when firmware misbehaves?

Karthikeyan S@karthik_embedded

July 4, 2026

#2 in Pi Lab

22 votesEnds Jul 9, 2026
#embedded#electronics#c

Get the best of #raspberry_pi_lab weekly

One email each Monday with the most useful posts. No spam; unsubscribe in one click.

Comments

6

Sign in to join the conversation.

Sign in to comment
Peter Hughes@amiga_pete3 rep in Pi Lab
printf, though on the Amiga in 1989 my "printf" was changing the background colour register. You'd see a coloured band on screen showing exactly how much of the frame your routine took. Every demo coder did it. Best profiler I've ever used. Cheers, Pete
2 net votes
Nguyễn Minh Hiếu@homelab_hieu#4 in Pi Lab
for Go backend I use printf, sorry :D
1 net votes
Matt O'Brien@pi_tinker_matt#1 in Pi Lab
An LED. Always an LED. Blink once for "got here", twice for "got further". I'm not proud
1 net votes
Frank Ostrowski@frank_cpp982 rep in Pi Lab
A GPIO toggle and a scope. Breakpoints lie about timing and printf changes it. Regards.
1 net votes
Karthikeyan S@karthik_embedded#2 in Pi Lab
Same. printf inside an ISR killed one of my motor drives once. UART blocking for 2 ms inside a 1 kHz control loop, what to do
0 net votes
Leo Chen 陈立@szhw_leo#8 in Pi Lab
Scope. And thermal camera. Many bug is a hot component, you see in 1 second what you debug for 1 day.
1 net votes