Engineering · 02 / Electronics
Electronics & embedded systems from schematic to prototype.
Circuit design, PCB development and embedded firmware for devices that must be built, tested and explained, from the first schematic to a verified prototype.
- 01Circuit design
- 02PCB development
- 03Embedded firmware
- 04Device interfaces
- 05Prototyping
- 06Verification
- U1 · Microcontroller
- J1 · USB-C
- J3 · Field terminals
- ANT1 · Radio module
/* sensor.c · read U3 over I2C */ int sensor_read(float *temp_c) { uint8_t cmd[2] = { 0x24, 0x00 }; uint8_t rx[6]; if (i2c_write(U3_ADDR, cmd, 2)) return -EIO; delay_ms(15); if (i2c_read(U3_ADDR, rx, 6)) return -EIO; uint16_t raw = (rx[0] << 8) | rx[1]; *temp_c = raw * 175.0f / 65535 - 45; return 0; }
Development path
Each stage ends with something you can review.
A device moves through the same revisions whether it is a new product or a rework of an existing board. The outputs below are what you can expect to see at each step.
- REV 01CONCEPT
Concept
Purpose, constraints and interfaces agreed before circuits are drawn.
- Requirements notes
- Block diagram
- Interface list
- REV 02SCH
Schematic
Power, sensing, processing and communication circuits captured and reviewed.
- Reviewed schematics
- Component choices documented
- REV 03PCB
Layout
Board layout checked against the schematic, interfaces and mechanical limits.
- PCB layout
- Fabrication files
- REV 04PROTO
Prototype
Boards built so the concept can be powered, handled and tested.
- Prototype build
- Bring-up checklist
- REV 05FW
Firmware
Drivers, control logic and communication for the microcontroller.
- Source in version control
- Build notes
- REV 06TEST
Verification
Functional tests that show what works and what is still open.
- Test procedures
- Recorded results
- Open items
DWG EE-02 · Development path
Each stage closes with a review point before the next begins.
Stages repeat when testing shows a change is needed.
Typical technical artifacts
What a project can include.
The exact package is agreed from your context, risk, timeline and responsibilities. Not every project needs every item.
- 01
Circuit design and schematics
Power, sensing, processing and communication circuits captured in reviewed schematics with documented component choices.
- 02
PCB development
Board layout and fabrication files, reviewed against the schematic, interfaces and mechanical constraints.
- 03
Embedded firmware
Microcontroller firmware for drivers, control logic and communication, kept in version control with build notes.
- 04
Device interfaces
Defined connections to sensors, actuators and other systems over the bus, serial or wireless links the product requires.
- 05
Prototyping
Prototype builds that let a concept be powered, handled and tested before further design investment.
- 06
Verification records
Bring-up checklists, functional test procedures and recorded results showing what has been verified and what remains open.
A good fit for
Where this work usually starts.
If your project sits close to one of these, a short conversation is usually enough to scope the first stage.
- 01Connected devices and sensor nodes moving from concept to a first prototype
- 02Products that need embedded control, data capture or communication
- 03Existing boards that need firmware, design review or new device interfaces
- 04Proof-of-concept hardware that must become documented and testable
Notes
- 1.Manufacturing handover and certification support are not offered by default. They are described only when confirmed for a specific engagement.
- 2.Milestones, review points and acceptance criteria remain visible from start to handover.
Start a conversation
Have a device to design or a board to bring up? Talk us through it.
Share what the device must sense, control or communicate. We will come back with the first stage we would scope and the questions to answer before it.
Inquiries are routed to the relevant practice lead.