Build it.
Measure it. Understand it.

The less visible side of product engineering: bring-up, test jigs, debugging tools and making development repeatable.

CONTEXT

Across product roles

ROLE

Electronics & embedded development

PERIOD

2017 — Present

SCOPE

Engineering practice

Conceptual illustration of a test bench connecting a device to diagnostic tools — Conceptual test-workflow illustration.

01 / OVERVIEW

A working prototype is a starting point. Understanding why it works, how it fails and what is actually running on it is part of the job.

Python / Linux Test jigs Hardware debugging

01Observe02Measure03Change04Verify

Simplified conceptual overview of the work, not an implementation schematic.

02 / THE CHALLENGE

Where the engineering
gets interesting.

Product development can stall when a fault is difficult to reproduce, a hardware revision changes behaviour or the deployed software differs from the intended build. Good tooling makes those gaps visible.

03 / MY CONTRIBUTION

The work I brought
to the system.

Board bring-up and debugging

Use schematics, datasheets and bench measurements to investigate electronic behaviour. Practical tools include oscilloscopes, logic analysers, JTAG, soldering and hardware rework.

Test and configuration tooling

Developed and used Linux / Python tools and test jigs in connected-product work, supporting device configuration and repeatable checks.

Mechanical and enclosure checks

Bring electronics and enclosure considerations together through CAD, prototyping and physical product validation, including ingress-testing work at Horizon.

Source-to-target traceability

Documented an AM62 development workflow covering rapid package iteration, deployment checks and the transition back to source-controlled Yocto image builds.

BENCH ARCHIVE / KASPER GLOBAL

The practical side
of product development.

Examples from my Kasper period: a test jig, a multi-device setup, prototype assembly and printed parts used in physical integration.

Kasper test jig in a carrying case connected to a small circuit board. — TEST JIGA practical test interfaceKasper test-jig assembly with a display, labelled controls and a connected board.

Large panel containing rows of circular and rectangular device assemblies. — ASSEMBLY & TESTWorking across multiple devicesA development panel bringing multiple device assemblies into one setup.

Hand holding a circular translucent assembly with components around its edge. — HARDWARE ASSEMBLYPutting the prototype togetherCircular hardware assembly during bench development.

Hand holding a translucent printed assembly above a cutting mat. — 3D-PRINTED PROTOTYPEAn assembly you can holdPrinted part used to explore the physical assembly and fit.

Populated green PCB mounted in an open gray enclosure. — PRODUCT INTEGRATIONChecking the physical fitPCB positioned in an open enclosure during prototype integration.

An engineer working on a small assembly at an electronics bench. — BENCH ASSEMBLYHands-on prototype workBench assembly during Kasper product development.

04 / VALIDATION

Check the behaviour.

I work from an observable symptom toward measurements and a reproducible check. That may mean checking a signal on the bench, verifying a peripheral address, examining device feedback or confirming which build is present on the target.

Bench-level fault investigation
Repeatable device checks
Clear deployment and verification workflows

05 / OUTCOME & REFLECTION

What the work adds up to.

This is a cross-project engineering practice rather than a single product launch. It supports the connected-device, care-system and embedded Linux work featured elsewhere in this portfolio.

The aim is to make the next investigation easier: keep the test setup understandable, separate assumptions from measurements and leave a clear path from source change to target behaviour.

KEEP EXPLORING