메뉴
Use when recording STM32 hardware faults such as HardFault, BusFault, and UsageFault, then exporting structured fault reports.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
| name | bfd-fault-logger |
| description | Use when recording STM32 hardware faults such as HardFault, BusFault, and UsageFault, then exporting structured fault reports. |
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 archive fault evidence in structured formats.
logs/hw_error/.# Record one HardFault example
python3 - <<'PY'
import sys
sys.path.append('.codex/skills/bfd-fault-logger/scripts')
from error_logger import HardwareErrorLogger
logger = HardwareErrorLogger(storage_path='logs/hw_error')
record = logger.record_hard_fault(
registers={"PC":"0x08004567","LR":"0x08002345","SP":"0x2001FFF0"},
cfsr='0x00000200', hfsr='0x40000000',
stack_trace=['0x08004567','0x08002345']
)
print(record.id)
PY
# Classify records
python3 ./.codex/skills/bfd-fault-logger/scripts/error_classifier.py
# Export reports
python3 ./.codex/skills/bfd-fault-logger/scripts/error_exporter.py
mv -f test_report.json logs/hw_error/
mv -f test_report.csv logs/hw_error/
logs/hw_error/.PC/LR/SP, CFSR/HFSR, and stack_trace..codex/skills/bfd-fault-logger/scripts/error_logger.py.codex/skills/bfd-fault-logger/scripts/error_classifier.py.codex/skills/bfd-fault-logger/scripts/error_exporter.py.codex/skills/bfd-fault-logger/scripts/rtt_capture.pybfd-debug-interfacebfd-rtt-loggerbfd-debug-orchestrator