メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
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.
SOC 職業分類に基づく
| name | bfd-stlink-interface |
| description | 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 this skill for ST-Link-specific probe control. This skill is independent from J-Link and does not describe HSS flows.
python3 ./.codex/skills/bfd-project-init/scripts/bootstrap.py --project-root . --mode check
/opt/st/stm32cubeclt_1.19.0/STM32CubeProgrammer/bin/STM32_Programmer_CLI -l stlink
python3 BFD-Kit/skills/codex/bfd-flash-programmer/scripts/stlink_flash.py --firmware "${STM32_HEX}"
# Connect and identify target
STM32_Programmer_CLI -c port=SWD mode=UR reset=HWrst freq="${STM32_SPEED_KHZ}"
# Read memory
STM32_Programmer_CLI -c port=SWD mode=UR reset=HWrst freq="${STM32_SPEED_KHZ}" -r32 0x20000000 4
# Write memory
STM32_Programmer_CLI -c port=SWD mode=UR reset=HWrst freq="${STM32_SPEED_KHZ}" -w32 0x20000000 0x12345678 -nv
# Start ST-Link GDB server
ST-LINK_gdbserver -p 61234 -m 1
freq=<kHz> for STM32_Programmer_CLI SWD connections; do not use speed=<kHz>.bfd-flash-programmerbfd-debug-interfacebfd-strtt-rtt