Carrier Board Development: A Practical Path from Requirements to Series Production
In parallel, the BIOS or bootloader and the operating system image are adapted to the carrier, including device trees for Arm platforms.
Standard computer on modules give industrial device makers a proven computing core, but the module alone does not make a product. The interfaces, connectors, power supply and mechanical fit that turn a module into a working device all live on the carrier board. Successful carrier board development is therefore where much of a product's value and risk sits. This article walks through the process step by step, compares the main module standards and highlights the decisions that save time and money later.
Why a custom carrier board makes sense
Off the shelf boards cover many applications, but they rarely match a specific device exactly. They may carry interfaces that are never used, lack a fieldbus port the machine needs, or have a shape that does not fit the housing. A custom carrier board solves these problems by including only what the product needs, placed exactly where it is needed.
The modular approach also splits the risk. The processor, memory and fast signal routing are designed and validated by the module supplier. The carrier board holds the application specific functions, which are usually less demanding to design. When a new processor generation becomes available, a compatible module can often be fitted without redesigning the carrier. That is one of the main reasons why carrier board development has become a standard path for industrial products built in small and medium volumes.
Choosing the module standard first
Every carrier board development project starts with the choice of module standard, because the standard defines the connector, the pinout and the mechanical envelope. The table below summarises the most common options in industrial computing.
|
Standard |
Maintained by |
Connection |
Typical application |
|
COM HPC |
PICMG |
Two high density connectors |
High performance edge computing, embedded servers |
|
COM Express |
PICMG |
Two board to board connectors |
Industrial PCs, medical and test equipment |
|
SMARC |
SGET |
314 contact card edge connector |
Low power Arm and x86 devices, HMIs |
|
OSM |
SGET |
Soldered BGA, no connector |
Very compact, cost sensitive IoT devices |
|
Qseven |
SGET |
Card edge connector |
Existing designs and long running products |
PICMG ratified COM Express 3.1 in November 2022, adding support for interfaces such as PCIe Gen 4 and USB4, while Types 6 and 10 remain backward compatible with 3.0 modules and carriers. COM HPC covers higher performance needs with a Client type for display oriented systems and a Server type for headless systems with large memory and high bandwidth I/O. For compact Arm designs, SGET defines SMARC and OSM. Partners such as Advantech, ADLINK, congatec and Kontron offer modules in these standards, so a carrier designed to an open specification is not tied to a single module supplier.
The carrier board development process
A structured process keeps the project predictable. The steps below reflect common practice in industrial embedded projects.
1. Requirements and specification
The first step in carrier board development is a clear requirements document. It should list every interface, the expected performance, the operating temperature range, the power input, the mechanical constraints of the housing, the target certifications and the planned volumes. This is also the moment to decide which module performance levels the carrier must support over the product's life.
2. Module and component selection
With the requirements fixed, the team selects the module family and the key components on the carrier, such as Ethernet PHYs, CAN transceivers, power regulators and connectors. Component lifecycle matters here: parts with long term availability reduce the risk of an unplanned redesign.
3. Schematic design
The schematic implements the interfaces according to the module specification and the supplier's design guide. Standards bodies publish carrier design guides for exactly this purpose. PICMG, for example, released a freely available COM HPC Carrier Board Design Guide in March 2021 for electronics and PCB layout engineers.
4. PCB layout
Layout is where signal integrity, power integrity and EMC are largely decided. High speed interfaces such as PCIe, USB and Ethernet need controlled impedance, careful routing and suitable layer stacks. The mechanical drawing of the housing defines connector positions and mounting holes.
5. Prototyping and bring up
The first prototypes are assembled and brought up step by step: power rails first, then the module boot process, then each interface. In parallel, the BIOS or bootloader and the operating system image are adapted to the carrier, including device trees for Arm platforms.
6. Validation and certification
Validation covers functional tests, temperature tests and, where relevant, shock and vibration. Pre compliance EMC measurements help to find problems before formal testing. For the European market, the final product must meet the applicable CE requirements, such as the EMC Directive 2014/30/EU, and, for products with radio functions, the Radio Equipment Directive 2014/53/EU.
7. Series production and lifecycle management
Once validated, the design moves into series production with defined test procedures. Lifecycle management continues for as long as the product is built: monitoring component availability, handling product change notifications and planning successor modules.
Typical design challenges
|
Challenge |
Why it matters |
How to address it |
|
High speed signal routing |
Errors cause unstable links and EMC failures |
Follow the design guide, use simulation and controlled impedance |
|
Thermal design |
Modules and regulators can overheat in closed housings |
Plan the cooling path between module, heat spreader and enclosure early |
|
Power input |
Industrial supplies vary and see transients |
Design wide input and protection circuits to the target standard |
|
Software integration |
Hardware is useless without stable drivers |
Involve BIOS and BSP work from the first schematic review |
|
Component obsolescence |
Discontinued parts force redesigns |
Choose parts with long term availability and second sources |
Security from the start
Cybersecurity is increasingly part of hardware design. The EU Cyber Resilience Act applies in full from 11 December 2027, with reporting obligations already applying since 11 September 2026. While most of the obligations concern the final product and its software, carrier board development decisions such as secure boot support, a trusted platform module and debug interface protection lay the groundwork for compliance. It is worth addressing these points in the specification rather than adding them late.
What drives effort in carrier board development
The effort in carrier board development rises with the number of high speed interfaces, the number of PCB layers, the mechanical constraints and the certification scope. A board with a few Ethernet ports and serial interfaces is far simpler than one with several PCIe slots, multiple displays and wireless modules. Reusing proven circuit blocks from earlier projects, such as power input stages or fieldbus interfaces, reduces both effort and risk.
Volume also plays a role. For small series, a design that uses standard connectors and readily available components is usually the better choice. For larger volumes, it can pay to optimise the bill of materials and the test strategy more closely. Discussing expected volumes at the start of carrier board development keeps these trade offs transparent and avoids changes late in the project.
Working with a system integrator
Carrier board development touches many disciplines: hardware design, layout, firmware, mechanics, thermal engineering and certification. A system integrator can coordinate these tasks and, when manufacturer independent, recommend the module and component choices that best fit the application rather than a single product catalogue. That neutrality helps to keep second sources open and the lifecycle under control.
FAQ
How long does carrier board development take? That depends on complexity, the number of interfaces and the certification scope. A clear specification and early prototype testing are the biggest factors in keeping the schedule.
Can one carrier board support several modules? Yes, if the modules follow the same standard and type. Many teams design one carrier to support several performance levels.
Do I need to recertify when I change the module? A module change can affect EMC and thermal behaviour. Whether retesting is required depends on the change and on the applicable regulations, so assess each case individually.
Conclusion
A carrier board turns a standard module into a product that fits your application, your housing and your market. With the right module standard, a clear specification and a structured validation process, the risk stays manageable and the design remains upgradeable for years. Aaronn Electronic GmbH supports customers with carrier board development as a manufacturer independent system integrator. Book a free consultation to discuss your project.


