hardware-integration-check

To prevent STM32 peripheral conflicts, verify GPIO, DMA, IRQ, and timer configurations against canonical documentation before generating HAL or LL code, ensuring safe and correct initialization without resource overlaps.

Checking DMA channel conflicts and NVIC priorities involves validating your DMAMUX assignments and interrupt settings against module requirements and hardware IO maps to ensure safe peripheral initialization.

Validate STM32 pinmux by cross-referencing your pin and mode configurations with the owner documentation in docs/HW_IO_MAP.md and snapshots in the docs/hsi directory to guarantee consistency.

You need an .ioc file and generated snapshots to verify STM32 peripheral setup because the check enforces alignment with these configurations to ensure your hardware integration does not diverge from reference designs.

You should run an STM32 hardware integration check before generating or editing peripheral initialization code to identify resource conflicts early and ensure configuration consistency with canonical hardware maps.

STM32 peripheral initialization diverges when manual pinmux, DMA, or IRQ settings are not aligned with the .ioc file and hardware IO maps, requiring a consistency check to identify and resolve conflicts.