How to review an AI-generated STM32 PCB

Check the complete part identity

Resolve the full orderable part number and package. Verify every supply and ground connection, required external components and the symbol-to-footprint mapping. Keep optional package pins and device-specific domains visible in the review.

Validate clocks, reset and recovery

Confirm the selected clock source and the conditions under which it is used. Review reset, boot behavior, debug access and programming recovery against the matching device documentation. A board that runs one preloaded binary may still be difficult to program or recover in production.

Follow each required peripheral

Check alternate-function assignments, electrical levels and external connections from the MCU to the connector or component. Validate layout-sensitive interfaces using the appropriate device guidance. Do not infer correctness from an autogenerated pin label alone.

Practical checklist

1. Resolve full part and package.
2. Check all supply domains.
3. Review clock and reset assumptions.
4. Preserve programming and debug access.
5. Trace required peripheral signals.

A concrete example

Create a board around an STM32 MCU with USB and a sensor bus.

Evidence to accept

The exact pin mapping, supply requirements and interface configuration are checked against that device.

Evidence that is insufficient

A generic family-level example is accepted without resolving the package-specific pins.

Common questions

Primary references and further reading

Use the matching device documentation and project configuration when applying this checklist. These references explain the underlying tools and evaluation approaches.

• KiCad schematic editor documentation
• KiCad PCB editor documentation