Capture STM32 RTT output via J-Link into structured debugging logs.
npx skills add https://github.com/Sonder4/STM32-BFD-Kit --skill bfd-rtt-logger
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
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.
Bootstrap your profile, then run the RTT logger to capture and save channel logs for analysis.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
Sonder4Capture STM32 runtime data from symbols, memory, and RTT channels into JSON/CSV artifacts.
iciakkyDiagnoses root causes of code modifications using a seven-step debugging workflow and generates verified fix plans.
LeoKemp223Parse .map and ELF files to report firmware memory usage and symbol sizes.
Sonder4Flash, read, and write STM32 memory via ST-Link CLI tools.
