Embedded Starter Kits
Production-ready BSP and RTOS boilerplate for common MCU and MPU families.
Every embedded programme starts with the same three weeks: get the board to boot, get the toolchain reproducible, get one peripheral talking. The work is necessary, it is nobody’s differentiator, and we have done it enough times to have kept the result.
The starter kits are production BSPs and RTOS skeletons pulled out of delivered projects, cleaned of client specifics and documented. They are a starting commit, not a framework: no abstraction layer to learn and nothing to rip out later. You get a board that boots, a build that is the same on every machine, and drivers that have already survived a production run.
ARM Cortex-M FreeRTOS base
Boot, scheduler, task layout and a driver skeleton ready to extend.
Yocto BSP template
Layer structure for a new board, from bootloader to rootfs.
STM32 driver library
Peripheral drivers already exercised in shipped hardware.
Reproducible toolchain
Containerised build so a new engineer compiles on day one.
Bring-up test suite
The checks that tell you the board is healthy before you write features.
Power and boot profiling
Measurement hooks for consumption and boot time from the start.
Pick the base
Cortex-M with FreeRTOS, or an MPU with embedded Linux.
Map your board
Pin map and clock tree adapted to the hardware in front of you.
Bring up
Run the test suite until the board passes every check.
Build your product
Everything after this point is the part only you can write.
Industrial IoT
New sensor or controller hardware that has to reach a demo in weeks.
Defense & Aerospace
Programmes where the build has to be reproducible and auditable from day one.
Medical & HealthTech
Devices where bring-up evidence becomes part of the documentation trail.
