bfd-rtt-logger

Capture STM32 RTT output via J-Link into structured debugging logs.

27|1|Updated Mar 9, 2026

Search Tags:#debugging #logging #profiling #stm32 #rtt #jlink

Ready to run

npx skills add https://github.com/Sonder4/STM32-BFD-Kit --skill bfd-rtt-logger

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bfd-rtt-logger
Source: https://github.com/Sonder4/STM32-BFD-Kit/tree/main/skills/claude/bfd-rtt-logger
Command: npx skills add https://github.com/Sonder4/STM32-BFD-Kit --skill bfd-rtt-logger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires JLinkExe, arm-none-eabi-nm, grep, awk, sed, JLinkRTTViewer, and includes scripts (resource) components.

What problem does it solve?

This RTT logger solves the challenge of capturing and structuring Segger RTT output from STM32 devices to enable rapid debugging after flash or reset, and to collect concise runtime evidence for verification.

Core Features & Use Cases

Capture real-time RTT logs from STM32 via J-Link RTT to create evidence for post-flash debugging.
Provide Windows and Linux/macOS tooling (PS1, bash, and shell scripts) and helper utilities to resolve RTT addresses and parse logs.
Archive logs in project folders and support quick mode or dual-mode capture for robust runtime verification.

Quick Start

Bootstrap your profile, then run the RTT logger to capture and save channel logs for analysis.

Frequently Asked Questions about bfd-rtt-logger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I capture STM32 RTT output for debugging after a flash or reset?▼

Capture STM32 RTT output using this logger to produce structured debugging evidence after flash or reset. It leverages J-Link RTT tooling and helper scripts to resolve addresses and parse logs.

What is the best way to log Segger RTT data from an STM32 device?▼

Log Segger RTT data by capturing real-time logs via J-Link RTT to create post-flash debugging evidence. This tool archives logs in project folders and supports quick or dual-mode capture.

Do I need JLinkExe to capture RTT channel logs from STM32?▼

Yes, you need JLinkExe and JLinkRTTViewer to capture RTT channel logs from STM32. The logger requires J-Link RTT tooling and arm-none-eabi-nm for address resolution during runtime verification.

Can I use this RTT logger on both Windows and Linux for STM32 profiling?▼

Yes, you can use this RTT logger on Windows and Linux for STM32 profiling. It provides cross-platform tooling including PS1, bash, and shell scripts to capture and structure RTT output.

How do I bootstrap my profile to start capturing STM32 RTT logs?▼

To start capturing STM32 RTT logs, bootstrap your profile first, then run the RTT logger to capture and save channel logs for analysis. This requires the included helper scripts.

Why does my RTT logger require arm-none-eabi-nm and grep for log parsing?▼

The RTT logger requires arm-none-eabi-nm and grep for log parsing to resolve RTT addresses and structure runtime evidence. These dependencies handle address resolution and text processing during capture.