메뉴
Use when sampling STM32 peripheral registers, tracking register changes over time, or exporting register snapshots to CSV for hardware-state analysis.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | bfd-register-capture |
| description | Use when sampling STM32 peripheral registers, tracking register changes over time, or exporting register snapshots to CSV for hardware-state analysis. |
BFD-Kit/.learnings/ERRORS.md and/or BFD-Kit/.learnings/LEARNINGS.md; unresolved capability gaps go to BFD-Kit/.learnings/FEATURE_REQUESTS.md.SKILL.md, script, wrapper, or resource so the next run benefits by default.BFD-Kit/.learnings/CHANGELOG.md and mention the improvement in the task close-out.Use this skill to capture register evidence with repeatable scripts.
# 0) Bootstrap profile (required)
python3 ./.codex/skills/bfd-project-init/scripts/bootstrap.py --project-root . --mode check
# USART1, 1 second
./.codex/skills/bfd-register-capture/scripts/capture_registers.sh -p USART1 -d 1 -o logs/debug/usart1_1s.csv
# CAN1 key status registers (STM32F427 bxCAN)
./.codex/skills/bfd-register-capture/scripts/capture_registers.sh -p CAN1 -r MCR,MSR,TSR,RF0R,RF1R,ESR,BTR -d 5 -o logs/debug/can1_status.csv
# Fast status check
./.codex/skills/bfd-register-capture/scripts/capture_registers.sh -p CAN1 -s
# High-frequency batch capture
./.codex/skills/bfd-register-capture/scripts/jlink_batch_capture.sh USART1 10 logs/debug/usart1_batch.csv
logs/debug/..codex/skills/bfd-register-capture/scripts/capture_registers.sh.codex/skills/bfd-register-capture/scripts/capture_registers.ps1.codex/skills/bfd-register-capture/scripts/jlink_batch_capture.sh.codex/skills/bfd-register-capture/scripts/jlink_fast_capture.pybfd-project-initbfd-debug-executorbfd-rtt-loggerbfd-data-acquisitionUse 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.