A serial monitor that
just works.

Things that work the moment you open it.

Recorded in the real app, not mock-ups.

01 — Serial

Plug it in and read the log. The baud rate finds itself.

Ports are rescanned every second and listed with chip name and VID:PID, e.g. COM5 · CH340. A new device is selected for you and reconnected after a replug. Not sure about the baud rate? Click “⚡ Auto”: QCCOM tries 18 common rates, scores the text for readability and connects with the best one. Switch between UTF-8 and GBK at any time; the existing log is re-decoded instantly.

02 — Terminal

U-Boot and Linux shells, right in the window.

Press Ctrl+` for terminal mode: full VT100 / xterm emulation, so vi, top, less and menuconfig render correctly, with scrollback, mouse selection and copy / paste.

03 — Side by side

The log and the code, side by side.

A location like main.c:123 in the log opens next to it with Ctrl+click; HardFaults and asserts show a hint in the status bar. Any two pages (serial, code, compare, circuit) can sit side by side, and pairs you use often open by themselves.

04 — Code

Go to definition and see what a macro expands to.

Open your firmware folder: C / C++ go to definition, find references and macro expansion with the computed value. clangd is used automatically when it is installed and the project has a compile_commands.json.

05 — Plot

Numbers in the log become live plots.

Values are pulled out of the log and plotted as they arrive, together with filters, highlight rules, auto-replies and scripts for tuning sensors and control loops.

06 — Toolbox

Dozens of embedded tools in one window.

TCP / UDP / MQTT / BLE / SSH, Modbus, CRC, number conversion, HEX / ELF / map viewers, firmware size diff, SVD registers, TFTP / HTTP file servers and more. Ctrl+Shift+B opens the searchable toolbox.

What you reach for while debugging, in one place.

Coming from SSCOM or another serial terminal? See where common tasks are in QCCOM.

Download QCCOM

1. Put the file in any folder and double-click it. Nothing to install.
2. Plug in your board or USB-to-TTL adapter. The port appears and is selected; press F5 to connect.
3. Unknown baud rate? Click “⚡ Auto”. Garbled characters? Switch the encoding between UTF-8 and GBK.
4. Create a qccom-data folder next to the exe for portable mode.

The exe is not code-signed yet, so Windows may show “Windows protected your PC” on first run. Click “More info” → “Run anyway”. Use the SHA-256 above to check the file. Code signing policy

1. Windows IME: Enter commits the typed letters instead of starting a new line
2. Terminal commands that use the open serial port (e.g. esptool.py -p COM3) release it first and reopen it afterwards
3. Open / Close button for the serial port on the side page
4. “Open with QCCOM” from Explorer brings the window to the front
5. Community posts and replies can be selected and copied

FAQ

• Why is my serial output garbled?
• How do I find a device’s baud rate?
• USB-to-TTL adapter (CH340 / CP2102) not showing up as a COM port?
• “Access denied” or “port busy” when opening a COM port?
• How do I use a serial console for Linux boards and U-Boot?
• How do I jump from a HardFault or assert in the log to the code?
• Switching from SSCOM to QCCOM

zenghi

Questions and feedback: 309966755@qq.com · GitHub Issues