Printf debugging vs SWO/ITM trace — what are the tradeoffs?

Printf debugging routes formatted text through a UART peripheral to a serial terminal. It is universally available, requires no special hardware beyond a USB-to-serial adapter, and works on any MCU architecture. The fundamental problem is intrusion: printf calls are slow (formatting a single integer takes thousands of CPU cycles), they block on UART transmission unless you implement DMA-backed buffering, and they change the timing of your application. A printf that takes 500 microseconds can mask a race condition or shift an ISR deadline, making the bug disappear when instrumented and reappear when the printf is removed — the classic Heisenbug.

SWO (Serial Wire Output) with ITM (Instrumentation Trace Macrocell) is an ARM CoreSight feature that provides a dedicated trace output channel on the SWO pin (shared with the JTAG TDO pin). ITM has 32 stimulus ports, each of which can emit 1-4 bytes with a single 32-bit write to a memory-mapped register. The write takes only a few cycles (the ITM has a small FIFO), and the data is clocked out asynchronously on the SWO pin at a configurable baud rate (up to several MHz). The debug probe (J-Link, ST-Link) captures and displays the trace data on the host PC.

The tradeoffs are clear: SWO/ITM is orders of magnitude less intrusive — a 4-byte ITM write takes roughly 10 cycles versus thousands for printf. It does not require a UART peripheral, leaving all UARTs available for application use. It supports timestamped trace (the DWT can stamp each ITM packet with a cycle counter), enabling precise profiling of event timing. The downsides: SWO requires a debug probe that supports trace capture, it is ARM-specific (not available on RISC-V, MSP430, AVR, or PIC), and the SWO pin bandwidth is finite — at 2 MHz SWO clock, you get about 200 KB/s of trace data, which is insufficient if you try to dump large buffers. For production logging (field diagnostics), printf over UART is still the practical choice because you cannot ship a JTAG probe with every device. The ideal workflow is SWO/ITM during development for timing-sensitive debugging, and a lightweight ring-buffer logger for production diagnostics.