メニュー
Use when parsing STM32CubeMX .ioc files to extract hardware configuration and generate structured JSON outputs for review or downstream analysis.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | bfd-ioc-parser |
| description | Use when parsing STM32CubeMX .ioc files to extract hardware configuration and generate structured JSON outputs for review or downstream 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 parse .ioc files and produce normalized configuration artifacts.
.ioc file or scan a directory.# Scan current directory
python3 ./.codex/skills/bfd-ioc-parser/scripts/parse_ioc.py --scan .
# Recursive scan
python3 ./.codex/skills/bfd-ioc-parser/scripts/parse_ioc.py --scan ./example_projects --recursive
# Parse a specific ioc file
python3 ./.codex/skills/bfd-ioc-parser/scripts/parse_ioc.py --ioc ./RSCF_A.ioc
# Parse with explicit output directory
python3 ./.codex/skills/bfd-ioc-parser/scripts/parse_ioc.py --ioc RSCF_A.ioc --output ./logs/ioc_json
.ioc file(s).summary.jsonclock_config.jsongpio_config.json.ioc files in this skill..codex/skills/bfd-ioc-parser/scripts/parse_ioc.py.codex/skills/bfd-ioc-parser/scripts/analyze_startup.py.codex/skills/bfd-ioc-parser/references/ioc_format.md.codex/skills/bfd-ioc-parser/references/memory_map_stm32h723.mdUse 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.