</>EmbeddedInterview

What tools do you use for board bring-up?

EasyElectronics & Hardware Basics

Short answer: A multimeter (rail voltages, continuity, current), a bench power supply with current limiting (catch shorts before they burn parts), an oscilloscope (analog behaviour: clocks, power ripple, edges, reset timing), a logic analyser (decoding SPI/I2C/UART/CAN over long captures), a debug probe (J-Link, ST-LINK, CMSIS-DAP via SWD/JTAG for flashing and debugging), a USB-UART adapter for the console, and sometimes a thermal camera (hot spots from shorts or wrong components).

Typical bring-up order

  1. Visual inspection (orientation, solder bridges), then check rails for shorts with power off (resistance to ground).
  2. Power up with current limiting; measure every rail and check current draw against expectations.
  3. Check the crystal/oscillator with a scope and reset lines (MCU out of reset?).
  4. Connect the debug probe: read the device ID (JLinkExe, openocd), erase and flash a minimal program.
  5. Blink an LED, then bring up the UART console for logging.
  6. Configure the clock tree to full speed and verify with MCO (clock output pin) on the scope.
  7. Bring up each peripheral one by one: external memory (run a memory test), I2C scan, SPI device ID reads, then higher-level functions.
  8. Measure power in each mode, then run stress and temperature tests.

Useful habits: keep a bring-up log, compare against a known-good board or evaluation kit, write small test firmware for each interface, and verify assumptions with measurements rather than with the schematic alone.