A bring-up checklist we use on every new board spin
When a client ships rev B while rev A still runs in the field, bring-up discipline prevents subtle regressions from becoming fleet-wide OTA surprises. This is the ordered list we follow in Walmer before application features touch the tree.
1. Visual and continuity
Microscope pass for solder bridges on QFN thermal pads. Meter check from USB input to 3V3 LDO output before applying USB data lines. Note which rails are always on versus switched by the MCU.
2. Current profile
Bench supply with logging: inrush, idle after reset, and deep-sleep target. Compare to rev A at the same firmware tag if possible. A 2 mA delta at idle often precedes a forgotten pull-up on a new GPIO.
3. Clock tree verification
Output a toggling pin synchronised to SYSCLK on the scope. Confirm HSE crystal oscillates across temperature with a heat gun and freeze spray—cheap insurance before you trust UART baud rates.
4. One peripheral per day
UART console first, then SPI flash ID read, then sensors. Commit each milestone with a tag. Parallel driver work invites merge conflicts in interrupt vectors.
5. Structured boot log
Every POST line includes reset reason, brown-out flags, firmware git SHA, and hardware revision GPIO strap if present. Field logs without reset reason waste a week of email.
We keep a template repository for clients who want a neutral starting point—ask during BSP engagements.