Firmware programming and functional testing
Boards that ship programmed, and boards checked against your definition of working. Both are scoped per project: you supply the firmware image and the test procedure or acceptance criteria; the method and any fixture needs are confirmed at file review and quoted as their own lines.
- Part of
- Assembly orders; the verification step of reverse engineering.
- Start with
- The firmware image and target device details; a test procedure, acceptance criteria, or a plain description of what the board must do.
- You receive
- Programmed boards, and test results per board or per lot as agreed in the quotation.
Programming, inspection, and testing
Customer-supplied firmware
Your image loaded into the target device during or after assembly — through a header, test points, or pre-programmed parts — where the device and access method are supported. Confirmed during file review.
Inspection
Visual inspection is part of every build. Further inspection methods are quoted when your project requires them.
Functional testing
A functional check defined with you: power-up and current draw, a built-in self-test, a check in your own equipment, or a measured specification. Fixtures, if needed, are scoped and quoted separately.
Test expectations, in writing
Before the build, the quotation records what "pass" means, how many boards are tested, what is reported, and what happens with a failure.
What to have ready
- The firmware image, its version, and the device it targets.
- How the device is programmed on your board — connector, test points, or protocol.
- A test procedure, or a description of what a good board does when powered.
- Whether every board is tested, or a sample.
Tick "testing" or "programming" on the quote form.
Describe what the boards must do in the requirements field. The file review comes back with the proposed method and the questions that need answering before it can be quoted.