First boards assembled, powered up and tested, on your bench or ours.

How this works

First power-on is where a design meets reality. A shorted rail, reversed part or wrong power-up order is cheap to find before a second board spin or a line stoppage; the checklist puts those checks first.

Before anything is powered, the checklist has your team measure each rail for shorts, check the orientation of polarised parts and set a current limit on the bench supply. Bring-up then goes one block at a time: power, clocks, the debug connection, then each interface.

Test steps say what to measure, where, and what reading counts as a pass, so the person at the bench doesn't need to have sat in the design reviews. If you plan to build a test fixture, the notes cover the test points and what it should check.

Project checkpoints
CheckpointWhat your team can expect
Scope and stageThe next defined stage is written before larger work begins, so you can decide what to fund next.
HandoverSource files, tests and decision notes are part of the handover, so your team can continue from a known version.
Procurement and buildWhen hardware is involved, you can buy the parts directly or have us source them at itemised cost; alternates and first checks are recorded before any order.

Start with a technical review

Frequently asked questions

What equipment does our bench need?

A current-limited bench supply, a decent multimeter and an oscilloscope cover most bring-up work. The procedure lists anything beyond that, such as a programmer for the microcontroller or a specific load, so you can have it ready before you start.

Can you help when a board won't come up?

We'll debug it with you, usually remotely while your engineer is at the bench. The measurements the procedure asks for are the best place to start.

Can our contract manufacturer use these files?

They can. The assembly notes and test steps are written so a contract manufacturer can follow them as easily as your own team. Most CMs will also want the data in their own formats, and we can answer their questions during the build.

What gets written down when something goes wrong?

Every problem found during bring-up goes into an issue log with what was seen, the cause and the fix. Anything that needs a board change becomes a recommendation for the next revision.