I built UartX, a cross-platform UART terminal and debugging tool for embedded and firmware developers.
When multiple firmware tasks are printing logs at the same time, debugging can quickly turn into a wall of text. The usual solution is to disable logs, reduce the log level, or modify the firmware — but that can also remove useful information or change timing and make a bug harder to reproduce.
UartX is built around a simple idea:
"Don't filter the data. Filter the way you look at it."
UartX keeps the complete raw UART stream while giving you tools to focus on what matters:
Color Rules to highlight important messages
Multiple live Filter Windows for different tasks, errors, or states
Raw session logging without adding timestamps or other formatting
Search through captured output
TX command history
Configurable display options
Windows and Linux support
Free and open source under the MIT License
The goal is to make firmware debugging easier without requiring changes to the existing logging in your firmware.
I've tested it with my own embedded projects, but I want to see how it performs with different hardware, firmware architectures, and real-world debugging workflows.
If you work with STM32, ESP32, Nordic, Zephyr, RTOS, or other embedded systems, I'd really appreciate you trying it.
If you find a bug, something that behaves unexpectedly, or have a feature idea, please share it on GitHub.
GitHub: https://github.com/Shamanthpoojary/UartX
I'd also like to hear what you currently use for UART debugging and what you wish your terminal could do better.
Main Window: Too many logs?
Color Rules: Define keywords and highlight important messages with custom colors.
Filter Window: See only the messages you need without changing your firmware or deleting logs.
