PHASE 04 ยท HARDWARE

Hardware design.
Built for production from the first sketch.

You arrive with an architecture, a block diagram or a proof of concept on a development board. You leave with a complete, reviewed hardware design: ready for prototypes, for EMC testing and for production.

Henrik Andersen development loop: enter anywhere, stay as long as you need, exit anytime

At a glance.

You bring
  • An architecture or block diagram
  • Requirements (SRD) or a clear feature list
  • A proof of concept on a development board
  • Or an existing design that needs a review
I do
  • Schematic and component selection
  • PCB layout to DFM rules
  • Design for EMC and for test
  • Independent hardware review
You get
  • Schematic and PCB design files
  • Production BOM with alternates
  • Gerber and assembly data
  • A written review report

What is included.

Ten building blocks. Take them all, or just the ones you need.

HOW COMPLIANCE IS DESIGNED IN

Compliance engineering.

Applicable EMC, radio, safety and environmental requirements are built into the design from the start, checked early with pre-compliance tests, and documented for your conformity assessment and CE marking.

Compliance engineering. Left: four requirement areas with example directives and standards: EMC (EMC Directive, EN 55032 and EN 55035), radio (Radio Equipment Directive, EN 300 328, EN 301 489 and EN 18031), safety (Low Voltage Directive, EN 62368-1) and environmental (RoHS, REACH and WEEE, material declarations). Each leads to design measures: layout, grounding and filtering; antenna and RF layout; creepage, clearance and insulation; compliant parts and materials. Right: an example radiated emissions pre-compliance scan from 30 MHz to 1 GHz below the limit line, with the margin marked. Below: the route to CE marking, compliance plan, pre-compliance, formal tests, technical file, then the EU declaration of conformity and CE marking by the manufacturer. Formal tests and a notified body only where required. Principles: plan from day one, design don't patch, measure early, your conformity. Right: the typical outputs, compliance plan, pre-compliance results and technical documentation.

HOW QUALITY IS BUILT IN

Implementation quality assurance.

Coding and design rules, peer reviews, static analysis and automated checks are applied to every change in hardware and firmware. Routine errors are caught by tools, so reviews can focus on the design itself.

Implementation quality assurance. Four checks are applied to every change: rules, peer review, static analysis and automated checks. For hardware: design and DFM rules, schematic and layout review, net, footprint and BOM checks, and ERC and DRC on every revision. For firmware: MISRA C and a coding standard, code review on every merge, static analysis on every build, and a CI build with unit tests. A band shows the defects remaining getting smaller after each check. Principles: written rules, a second pair of eyes, automated first, evidence kept. Right: the typical outputs, review evidence, analysis results and controlled design files.

What you get.

Schematic PDF + native files
PCB layout Native files, Gerber or ODB++
Bill of materials MPNs + alternates
Assembly data Drawings, pick-and-place
Review report Findings ranked by priority
Firmware handover Pinout + peripheral notes
Duration

Agreed in your proposal

Enter with

An architecture or block diagram

Exit with

A complete design

Payment

After your approval

Where to next.

Continue with me through the next phases to start of production, or leave with what you came for.

Previous phase03 ArchitectureHW / SW partitioning and the choice of key components. Next phase05 FirmwareArm Cortex-M, RISC-V and MCS-51 firmware, tested and documented.

CONTACT

Ready to start at phase 04?
Or hand over the complete development? Just ask.

A new product to develop from scratch, a design that needs a second look, or a prototype that does not work yet: a few lines are enough to start.

  • A personal reply within one working day
  • No cost and no commitment up front: you only pay for work you approve
  • Your idea stays confidential, NDA on request (how I keep your project confidential)

Write to me

info@siliconmeetscode.com
Write an email

Helpful to mention: what the product does, where it is today, and your timeline. The email opens with these questions ready to fill in.

Working from Belgium and Germany with clients across Europe and Asia