Pro lesson · Preview
printf Debugging & Logging
Where does printf go on a chip with no console, and what does it cost? Retargeting output to UART/SWO/RTT (vs slow halting semihosting), intrusiveness, and leveled, deferred, compile-gated logging.
22 min read
This lesson is part of Pro
Upgrade to unlock the full lesson and the complete interview Q&A.
Unlock with Pro5 interview questions on this topic
Each one opens a full worked answer.
On an MCU with no console, how does printf produce output?Why shouldn't you call printf in an interrupt handler or hot loop?What's wrong with semihosting for debugging output?How do you make logging suitable for a shipping product rather than ad-hoc prints?When do you use logging versus a debugger like GDB?
This is just the start
Sign up free to track your progress through this course, mark lessons complete, and work through the full interview Q&A.
More in Debugging & Toolchain
The ToolchainThe Build Process & MakefilesLinker Scripts & Memory Sections
Debugging with GDB
On-Chip Debugging: JTAG & SWD
Breakpoints & Watchpoints