From Development Board to Product: What Changes

The demo runs on an evaluation board, a breakout sensor and a USB cable, and it works every time on the bench. Then, in a sequence many hardware teams will recognize, the first custom board fails radiated emissions, resets when someone touches the enclosure, and takes minutes per unit to program and test. Going from development board to product is mostly about constraints that the development board hid: a clean lab supply, no enclosure, no regulator, no factory and no customer. This article walks through what changes, what the regulations and standards actually require, and which decisions are cheap early and expensive late.

Key Takeaways

• In the United States, digital devices are “unintentional radiators” under 47 CFR Part 15 and must be authorized (by Supplier’s Declaration of Conformity or certification) before marketing, even if they have no radio.
• A pre-certified radio module simplifies, but doesn’t remove, compliance work. The FCC’s modular rules require the module to have its own shielding, power regulation and antenna arrangement, and the host must carry a label referring to the module’s FCC ID.
• In the EU, radio equipment falls under the Radio Equipment Directive (2014/53/EU), which covers safety, EMC and efficient use of spectrum together.
• ESD immunity testing under IEC 61000-4-2 commonly applies contact discharges of several kilovolts to anything a user can touch. A development board has none of the protection that requires.
• Boothroyd’s work on design for manufacture and assembly showed that most of a product’s cost is committed in design. Part count, orientation and test access are design decisions, not factory problems.

The problem: the development board solved problems you didn’t know you had

Evaluation boards are designed to make one chip easy to try. They come with generous power supplies, decoupling and ground planes laid out by the chip vendor’s application engineers, a debug probe, and no enclosure or cables longer than a few centimeters. They’re often several times larger than needed, populated with every option, and never sold as a finished product, so they don’t need to pass anything.

The custom board inherits none of that by default. It has to fit an enclosure, run from the power source the product actually has (a battery, a 24 V industrial supply, a cheap wall adapter), connect to cables that act as antennas, and survive being handled. It also has to be built by a contract manufacturer from parts that will still be available in three years, and tested at the end of the line in seconds.

None of this is exotic. It’s just work that doesn’t show up while the prototype is on a bench.

What the rules and research say

Emissions: every digital product is regulated

Under the FCC’s Part 15 rules, a device with digital circuitry that isn’t intended to radiate is an unintentional radiator, and 47 CFR 15.101 requires it to be authorized “prior to the initiation of marketing.” For most digital devices the route is either a Supplier’s Declaration of Conformity (the manufacturer tests, usually at an accredited lab, and declares compliance) or certification. Class A (commercial and industrial) and Class B (residential) have different limits, with Class B stricter.

The common surprise is that the board passes on its own and fails with cables attached, because cables are efficient antennas for common-mode currents. Henry Ott’s Electromagnetic Compatibility Engineering treats this at length: return paths, ground plane continuity, filtering at the connector and controlling the loop area of fast signals do more than any shield added afterward. These are layout decisions.

Radios: modules help but don’t finish the job

Adding a pre-certified radio module is the usual way to avoid certifying an intentional radiator from scratch. Under 47 CFR 15.212, a module qualifies for single modular approval if it has its own shielding for the radio, buffered modulation and data inputs, its own power supply regulation, and a permanently attached or unique antenna connection, and if it’s tested standalone and carries its own FCC ID. When the module’s label isn’t visible in the finished product, the host must carry a label such as “Contains FCC ID: …”.

The host is still a digital device with its own emissions obligations, and using a different antenna or placing the module somewhere its grant didn’t anticipate can void the modular approval. Read the module’s grant conditions and integration guide before laying out the board.

In the EU, Directive 2014/53/EU (the Radio Equipment Directive) governs products with radios and covers safety, EMC and efficient use of the spectrum together, assessed against harmonized standards. A product sold in both markets plans for both from the start.

Immunity: ESD and the user’s finger

IEC 61000-4-2, Electrostatic discharge immunity test, defines how to apply electrostatic discharges to equipment and specifies ranges of test levels related to the environment. In the widely used 2008 edition, contact-discharge levels run from 2 kV to 8 kV and air-discharge levels from 2 kV to 15 kV, and product standards choose which levels apply. Anything a user can touch, including connector shells, buttons, seams in the enclosure and exposed metal, is a test point.

A development board has no transient-voltage suppressors on its connectors, no planned discharge path to chassis or ground and no spacing for a plastic seam. The fixes (TVS diodes close to connectors, a defined return path, firmware that recovers rather than locks up after a glitch) are cheap if planned and difficult to add after tooling.

Manufacturing: cost is committed at design time

Geoffrey Boothroyd’s 1994 paper in Computer-Aided Design summarized two decades of work on design for manufacture and assembly (DFMA). Its central argument is that a large share of a product’s eventual cost is fixed by design decisions, and that systematically reducing part count, simplifying assembly operations and designing parts to be easy to handle and orient cuts that cost. For electronics, the translation is concrete: fewer distinct components, all on one side if possible, no hand-soldered wires, connectors that can only go in one way, and fasteners the enclosure doesn’t actually need removed.

Test is part of the same decision. A board without test points, a programming header the fixture can reach, and firmware that can report its own self-test result will be tested slowly or not at all.

Development board vs product, compared

Area	Development board	Product
Power	Clean USB or bench supply	Real source: battery, industrial 24 V, cheap adapter; brownouts and transients
Emissions	Not tested; short or no cables	Part 15 authorization or equivalent; tested with real cables attached
Radio	Vendor’s antenna and layout	Module grant conditions, antenna keep-out, host labeling, RED in the EU
ESD and immunity	No protection on headers	Test levels per product standard; TVS, return paths, recovery in firmware
Size and enclosure	Oversized, open	Fits the enclosure; thermal and mechanical limits
Bill of materials	Every option populated	Minimum part count, second sources, lifecycle checked
Programming and test	Debug probe on a bench	Fixture access, seconds per unit, logged results
Firmware	Debug build, prints to console	Release build, watchdog, update path, field diagnostics

What to actually do

Write down the target markets and standards first

List the countries and product categories, and from them the emissions, immunity, safety and radio requirements. A short call with a test lab before layout costs much less than a failed scan after it.

Copy the vendor’s layout where it matters

For the processor’s power and decoupling, the radio and its antenna, and any switching regulator, start from the vendor’s reference layout and change it only with a reason.

Design for EMC and ESD at the connectors

Put filtering and transient protection at the point where cables enter, give discharges a defined path, and keep fast signals over a continuous ground plane. Do a pre-compliance scan on the first custom board, not the last.

Treat test as a feature

Add test points and a programming interface the fixture can reach, and firmware that runs a self-test and reports a pass or fail. Estimate the seconds per unit before the factory does.

Reduce and second-source the bill of materials

Cut distinct part numbers, check lifecycle status, and choose footprints that accept alternatives for passives, regulators and memory.

What not to do

Don’t assume a certified module makes the product certified. And don’t let the first custom board be a straight copy of the development board’s schematic with a smaller outline; that’s the board that fails emissions.

How to put it to work

If you have an hour

List every way your product connects to the outside world (power, cables, buttons, radio, enclosure seams) and, next to each, which test or regulation it touches.

If you have a sprint

Book a pre-compliance emissions scan and an ESD test on your current custom board, with real cables attached, and fix the worst finding before the next revision.

If you want it to last the product’s lifetime

Keep a compliance file with test reports, the module grant, the bill of materials and its approved alternates, and re-check it whenever a part, antenna or enclosure changes.

The question to ask yourself: “If this board went to a test lab tomorrow with its real cables and enclosure, which test would it fail first?”

Frequently asked questions

Do I need FCC approval if my product has no radio?

In most cases, yes. A device with digital circuitry is an unintentional radiator under Part 15 and must be authorized before marketing, usually by Supplier’s Declaration of Conformity or certification, unless a specific exemption applies.

Does using a pre-certified radio module mean my product is certified?

No. The module’s approval covers the radio when it’s integrated according to its grant conditions. The host still has its own emissions obligations and labeling requirements, and changes such as a different antenna can affect the module’s approval.

What is ESD immunity testing?

It’s a test in which electrostatic discharges are applied to points a user can touch, following IEC 61000-4-2. The product must keep working, or recover as the product standard allows. Test levels depend on the environment and the applicable product standard.

What is design for manufacture and assembly?

It’s a set of methods, developed by Boothroyd and others, for reducing manufacturing cost through design: fewer parts, simpler assembly steps, and parts that are easy to handle and orient. For electronics it also means designing for automated assembly and fast test.

When should I move off the development board?

As soon as the core function is proven and the requirements are clear enough to choose a power source, enclosure and target markets. The first custom board should already include protection, test access and the vendor’s reference layout for critical circuits.

Related reading: OTA firmware updates, grounding and shielding sensor signals and measuring microcontroller power consumption.

Sources

1. U.S. Federal Communications Commission. 47 CFR § 15.101, “Equipment authorization of unintentional radiators.” https://www.ecfr.gov/current/title-47/chapter-I/subchapter-A/part-15/subpart-B/section-15.101
2. U.S. Federal Communications Commission. 47 CFR § 15.212, “Modular transmitters.” https://www.ecfr.gov/current/title-47/chapter-I/subchapter-A/part-15/subpart-A/section-15.212
3. European Parliament and Council (2014). Directive 2014/53/EU on the harmonisation of the laws of the Member States relating to the making available on the market of radio equipment. https://eur-lex.europa.eu/eli/dir/2014/53/oj/eng
4. IEC 61000-4-2:2008. Electromagnetic compatibility (EMC) – Part 4-2: Testing and measurement techniques – Electrostatic discharge immunity test, Ed. 2.0 (superseded by IEC 61000-4-2:2025). https://webstore.iec.ch/en/publication/4189
5. Boothroyd, G. (1994). “Product Design for Manufacture and Assembly.” Computer-Aided Design, 26(7), 505–520. https://doi.org/10.1016/0010-4485(94)90082-5
6. Ott, H. W. (2009). Electromagnetic Compatibility Engineering. Wiley. https://doi.org/10.1002/9780470508510