Concept and component selection
Define the electronics architecture, assess microcontroller or processor platforms and select components against system constraints and availability.
Focus topic
PCB Design & Hardware Bring-up
Take embedded electronics from concept to a working prototype, with design decisions that software, test and manufacturing can build on.
Hardware development work can start from a product idea, an existing design that needs changes, or a prototype that does not behave as expected. Design responsibility, tools and access to prototypes are agreed for the assignment.
From concept to verified hardware
Each step produces decisions the next one depends on. Findings from bring-up and verification feed back into the design.
- ConceptArchitecture, platform
- SchematicCircuits, interfaces
- PCBLayout, constraints
- PrototypeManufactured boards
- Bring-upFirst operation, measurement
- VerificationBehaviour against requirements
Findings feed the next design revision
What the work covers
The agreed assignment determines which activities are included and where the responsibility boundary sits.
Schematic development and review
Develop or review schematics, including the low-level interfaces that software and other hardware depend on.
PCB development
Support PCB development and design reviews, with pin allocation and layout constraints coordinated with software and mechanical interfaces.
Prototype bring-up and troubleshooting
Bring first boards into operation, measure and investigate deviations, and connect observed behaviour to design decisions.
Hardware verification and manufacturing documentation
Verify hardware behaviour against requirements and prepare or maintain BOM and manufacturing documentation for the agreed scope.
Typical starting points
A new embedded product needs an electronics concept and a first prototype.
A prototype shows faults and it is unclear whether hardware or software is responsible.
A component is no longer available and the design needs a controlled change.
Example engineering outputs
Outputs are assignment-dependent and agreed for each engagement.
Electronics architecture and component-selection records.
Schematics and PCB development packages within the agreed scope.
Bring-up records and hardware verification results.
BOM and manufacturing-support documentation.
Common questions
Do you manufacture the boards?
Manufacturing is carried out by the customer's manufacturing organisation or a contract manufacturer. The engineering scope can include the documentation they need and technical coordination with them.
Can you work on an existing design?
Yes. Reviews, design changes and troubleshooting on existing hardware are common starting points. Access to the design data and prototypes is needed.
Is software for the board part of the scope?
It can be. Board support and driver development is a separate capability that can be combined with hardware work in one team.
Part of
Electronics & Hardware Engineering
Electronics architecture, schematics, PCB development and prototype bring-up, connected to verification and manufacturing support.
Discuss an electronics design, prototype problem or hardware change.
Describe the current state, the interfaces involved and the result you need. Leave confidential technical files out of the first message.