Stm32 Dev

Collect this before making changes:

• .ioc path and target MCU/board (for example STM32F103C8 or STM32H743ZI)
• Existing source tree and whether CubeMX files are regenerated frequently
• Toolchain paths (arm-none-eabi-gcc, cmake, ninja/make, openocd, arm-none-eabi-gdb)
• Debug probe and transport (stlink, swd/jtag)
• Flash layout and linker script (STM32xxxx_FLASH.ld)

Operating Rules

• Keep generated code and user code boundaries clear; avoid editing autogenerated sections.
• Treat .ioc as source of truth for pin/peripheral config.
• Keep CMake targets explicit: include dirs, compile defs, startup file, linker script, and linker flags.
• Build with Debug during bring-up (-Og -g3), then switch profiles intentionally.
• Use OpenOCD board/target config that matches exact MCU family.
• Verify connection and halt state before flashing.

Execution Pattern

1. CubeMX Generation

• Generate code to a stable folder, typically Core/, Drivers/, and startup_*.s.
• Enable options that preserve user code sections.
• Re-run generation after .ioc changes and reconcile CMake source lists.

2. CMake Integration

• Configure a cross-compilation toolchain file for ARM GCC.
• Build an ELF target from CubeMX sources plus user application sources.
• Add post-build steps for .hex and .bin.

For concrete templates and commands, read references/integration-playbook.md.

3. Flash With OpenOCD + ST-Link

• Start OpenOCD with the right interface and target config.
• Flash ELF using program <elf> verify reset exit or GDB load.
• Confirm probe and target voltage if connect fails.

4. GDB Debug Session

• Start OpenOCD server first.
• Attach arm-none-eabi-gdb to localhost:3333.
• Load symbols from ELF, set breakpoints, step/continue, inspect memory/registers.

5. Troubleshooting

• If build fails: validate startup file, linker script, CPU/FPU flags, and HAL include paths.
• If flash fails: validate OpenOCD target cfg, SWD wiring, and target halt state.
• If debug is unstable: reduce SWD speed, check reset strategy, and verify clock/init side effects.

Use the issue-to-fix table in references/integration-playbook.md.

Output Expectations

When executing this skill, produce:

• A reproducible command sequence: configure, build, flash, debug
• Exact file edits (CMake/toolchain/OpenOCD config)
• Minimal, testable troubleshooting steps tied to observed errors
• A short verification checklist (build ok, flash ok, breakpoint hit)