en un clic
STM32-BFD-Kit
STM32-BFD-Kit contient 24 skills collectées depuis Sonder4, avec une couverture métier par dépôt et des pages de détail sur le site.
Skills dans ce dépôt
Use when acquiring STM32 runtime data from global symbols, memory regions, stack-published local slots, or RTT channels and converting captures into structured artifacts for analysis.
Use when debugging STM32 applications with J-Link or ST-Link, including breakpoints, watchpoints, register or memory inspection, HardFault analysis, and automated fault-context capture.
Use when flashing STM32 firmware, verifying flash results, diagnosing download failures, or running repeatable CLI-based flash workflows.
Use when building a closed STM32-to-Matlab workflow for J-Link HSS data capture, system identification, PID/LQR/MPC tuning, Kalman parameter estimation, or Matlab/Simulink code-generation feedback loops.
Use when preparing, auditing, repairing, or launching SEGGER Ozone STM32 debug projects (.jdebug / .jdebug.user). Trigger this skill when Ozone shows stale Windows paths, wrong ELF/SVD/device/interface settings, missing FreeRTOS awareness, duplicated case-variant project files, stale fixed J-Link serial bindings, or when a user wants a ready-to-debug Ozone session opened from the current STM32 project.
Use when capturing STM32 RTT output through the current J-Link mainline, validating runtime behavior after flash/reset, or collecting short runtime evidence from J-Link RTT channels.
Use when acquiring STM32 runtime data from global symbols, memory regions, stack-published local slots, or RTT channels and converting captures into structured artifacts for analysis.
Use when debugging STM32 applications with J-Link or ST-Link, including breakpoints, watchpoints, register or memory inspection, HardFault analysis, and automated fault-context capture.
Use when flashing STM32 firmware, verifying flash results, diagnosing download failures, or running repeatable CLI-based flash workflows.
Use when building a closed STM32-to-Matlab workflow for J-Link HSS data capture, system identification, PID/LQR/MPC tuning, Kalman parameter estimation, or Matlab/Simulink code-generation feedback loops.
Use when capturing STM32 RTT output through the current J-Link mainline, validating runtime behavior after flash/reset, or collecting short runtime evidence from J-Link RTT channels.
Use when flashing, reading memory, writing memory, or starting debug sessions through ST-Link tools such as STM32_Programmer_CLI or ST-LINK_gdbserver, especially when J-Link-specific commands do not apply.
Use when capturing SEGGER RTT over ST-Link via memory polling, or when implementing and diagnosing strtt-style RTT control-block scanning and ring-buffer polling.
Use when a project already has a valid STM32CubeMX .ioc file and the goal is to regenerate CubeMX-managed code in place without changing clock, pin, peripheral, or toolchain configuration.
Use when running direct J-Link command sequences for breakpoints, stepping, register reads, and one-shot debug actions on STM32 targets.
Use when running end-to-end STM32 debug campaigns that coordinate flash, RTT, register capture, HardFault snapshots, and error archival across multiple tools.
Use when recording STM32 hardware faults such as HardFault, BusFault, and UsageFault, then exporting structured fault reports.
Use when parsing STM32CubeMX .ioc files to extract hardware configuration and generate structured JSON outputs for review or downstream analysis.
Use when preparing an STM32 project for debug/flash/RTT workflows by scanning ioc/startup/linker/svd/cfg files, generating a unified profile, and optionally creating missing baseline files.
Use when sampling STM32 peripheral registers, tracking register changes over time, or exporting register snapshots to CSV for hardware-state analysis.
用户反馈与状态监控技能。触发：(1)用户反馈收集请求 (2)运行状态监控 (3)错误日志记录 (4)关键词"收集反馈"、"用户反馈"、"状态监控"、"交互反馈" (5)任务完成需用户确认。禁止跳过用户确认、禁止忽略用户反馈。
Use when running end-to-end STM32 debug campaigns that coordinate flash, RTT, register capture, HardFault snapshots, and error archival across multiple tools.
Use when parsing STM32CubeMX .ioc files to extract hardware configuration and generate structured JSON outputs for review or downstream analysis.
Use when sampling STM32 peripheral registers, tracking register changes over time, or exporting register snapshots to CSV for hardware-state analysis.