First boards, brought up and measured
New boards rarely work on the first try, and the hard part is knowing whether a fault is in the board or the code. We bring them up one layer at a time and write down what we measured.
Key characteristics
- You provide
- Boards, schematics, layout and hardware engineer time
- You receive
- Bring-up log, board support package, issue list
- Per revision
- Each board revision gets its own log
- Checked
- Rails, clocks, debug, buses, radio and flash
The first boards back from assembly are where your hardware and firmware meet for the first time. Some will have a rotated part, a missing pull-up resistor, a crystal that never starts or a regulator that runs hot. Some faults will look like hardware and turn out to be firmware, and the reverse. Board bring-up is the disciplined work of finding out which, one layer at a time, and leaving a record your hardware engineer can act on.
We work alongside your hardware engineer, not instead of them. They know the design intent; we bring the firmware side, the measurements and the habit of writing everything down.
The order we work in
Each step depends on the one before it, so we do not skip ahead, even when the radio demo is the exciting part.
- Before power. Confirm the schematic, layout and bill of materials match the board revision in hand. Inspect for missing, rotated or bridged parts. Measure resistance from each supply rail to ground, and set a current-limited bench supply below the expected draw.
- First power. Measure each rail at its test point, record idle current against the estimate, check that nothing runs hot, and confirm the reset and power-good signals behave as designed.
- Debug and clocks. Connect a debug probe over SWD or JTAG and read the chip ID. Run a minimal program from flash that toggles a pin. Measure the main and low-frequency clocks rather than assuming them, and get log output working.
- Peripherals. Every I2C and SPI device answers at its expected address. ADC readings are checked against a known voltage. The radio transmits and receives at short range. Flash is erased, written and read across the whole part. Each GPIO on the schematic is exercised once.
- Record and hand back. Write the bring-up log with measurements and board serial numbers, list hardware issues with evidence, write rework instructions, and check the pin map and clock tree into the firmware repository.
These are the five sections of our free board bring-up checklist, 21 items in all. Use it on your own boards, with or without us.
Triage with your hardware team
When something does not work, the useful answer is a measurement, not an opinion. We report each issue with what we expected, what we measured, the board serial number and a suggested next test, so your hardware engineer can decide quickly whether it needs a rework, a layout change or nothing at all.
| Symptom | Usual first checks |
|---|---|
| Debugger will not connect | Supply rails, reset line, debug pin assignment, protection settings left by an earlier image |
| A clock does not start | Crystal load capacitors, startup time, clock configuration |
| A peripheral does not answer | Bus address, pull-ups, chip select, power to that part |
| Radio range is short | Antenna matching, ground, transmit power setting |
| Idle current is too high | Floating inputs, parts not put to sleep, leakage paths |
Many hardware issues have a firmware workaround that keeps the schedule moving while the next revision is laid out. We write those down as well, with the board revision they apply to, so nobody forgets to remove them when the fix arrives. Silicon errata, part substitutions on the build and a missing or unreachable debug header are common sources of surprises, so we check them early.
The board support package
Once the board works, we capture what we learned as a board support package (BSP): the pin map, clock configuration, memory layout and driver settings that let application firmware run on this exact board. On Zephyr this is a board definition whose devicetree describes the SoC, connectors, sensors, buttons and LEDs, with configuration files beside it. On embedded Linux the kernel reads a devicetree too (see embedded Linux). On FreeRTOS or bare metal it is a set of startup and configuration files. Each board revision gets its own, so Rev C and Rev D boards can run from one code base.
Bring-up with updates in mind
Bring-up is the right moment to confirm three things the update path depends on. First, that the bootloader (often MCUboot) starts and verifies an image on the real part, not only on an evaluation kit. Second, that the flash size and erase sector size match the datasheet and the flash budget. Third, that there is a written plan for when the debug port will be locked on production units, which manufacturing firmware and firmware security carry forward.
Example (fictional). Loamwick brings up its Rev C prototype probes in weeks 1 and 2, overlapping the firmware review in week 1. The bring-up log confirms the Bluetooth LE microcontroller’s 1 MB of internal flash, and the flash map is fixed then: a 48 KB MCUboot partition, two 448 KB image slots, 32 KB of settings and 48 KB of logs. The Rev D trial units get a bring-up log of their own before the field trial. Follow the whole story on the example project page.
What you receive
- A bring-up log for each board revision, with measurements and board serial numbers.
- A board support package in your repository.
- Test firmware that exercises every peripheral, reusable on the next revision and as a starting point for factory test.
- An issue list with evidence, firmware workarounds and rework instructions for your hardware team.
Where to start
A bring-up sprint is a fixed-scope engagement per board revision. Boards can be shipped to our Denver office, or for teams in the Denver area we can work at your site by arrangement. If boards are still in layout, a firmware review is the better first step: we read the schematics before they are built, which is the cheapest time to add a debug header or a test point. Request a firmware review, or read more in the prototype to production section of Field Update.
Send us your board and your plan.
A firmware review reads your schematics, code, flash layout and update plan, and ends with a written plan: what to build first, what could go wrong in the field and how updates will reach your devices.
Or email sales@fumbar.com, or call (720) 675-4202.