BRING-UPMISSION 022 · Bring-up · SWD accessFoundational

The Prototype Cannot Be Programmed

A new STM32 board powers cleanly, but the debugger cannot identify the MCU. Inspect the supplied assembly and continuity reports, then propose a first-contact plan.

Requirements

Target VDD · 3.30 VSense-only VTref · no probe back-poweringRead the target device ID over the routed debug port
  1. 01Plan first attachment
  2. 02Record first contact
Circuit overview

Programming header review

Target MCU and six-pin SWD headerThe target 3.3 volt rail reaches the MCU, while the debug header voltage reference reaches it only when R101 is fitted.U1 · STM32F401CCVDD = 3.30 VJ7 · SWDPA13 · SWDIOSWDIOPA14 · SWCLKSWCLKNRSTNRSTGNDGND+3V3 TARGET RAILR1010 ΩVTREFASSEMBLY · R101 DNPVTref is a target-voltage sense input in this board contract, not a power feed.

The target is powered from the bench supply. J7 uses the supplied sense-only VTref contract; the assembly state is shown in the report.

Circuit and case data
Circuit and case data
Continuity and population report
J7 SWDIO → U1 PA130.3 ΩJ7 SWCLK → U1 PA140.3 ΩJ7 NRST → U1 NRST0.4 ΩJ7 GND → board GND0.2 ΩY1 external HSEDNPR101 VTref linkDNP

Continuity was measured with the board unpowered. The target is a blank device with default debug access.

Evidence notebook 0 saved

No evidence saved yet. Measure, inspect the result, then save useful observations.

Current task
Current task

Step 1 of 2

Plan a safe first attachment

0 evaluated decisions · Draft and evidence saved locally
Technical references

Bring-up boundary

This exercise establishes a safe debug attachment and device identification. It does not prove application clocks, option bytes, flash integrity, reset timing, low-power behavior or production programming reliability.

ST RM0368 · STM32F401 debug support and MCU device ID