Firmware makes a board part of a working device. I develop embedded software alongside custom electronics, connecting microcontrollers, sensors, actuators, and higher-level applications. You work directly with me, Clemens Elflein, on the behavior your hardware needs.
Start with the device and its interfaces
For a new device, describe its inputs, outputs, operating states, and timing requirements. For existing hardware, a schematic, pin assignment, toolchain details, and a way to reproduce the current behavior help make the work concrete.
The scope can include board bring-up, peripheral interfaces, device control, and communication with other parts of the system. Hardware and firmware often need to be developed together: a pin assignment, power sequence, or interface choice can affect both.
See the system context
xCore pairs a real-time STM32 microcontroller with a Linux-capable Raspberry Pi CM4. It is an example of splitting device control and higher-level robotics software across connected processors.
OpenMower brings electronics, motor control, positioning, and navigation together in a robot. xESC Mini connects motor-control hardware with VESC-based firmware and a ROS driver. The project pages link to documentation and public repositories for a closer look.
Agree on observable behavior
A useful development brief says how the device should behave and how that behavior can be checked. Include the hardware revision, existing source code if available, known issues, and access to a representative device. Build instructions, integration work, and the validation scope can then be agreed for the project.
If the electronics also need development, see hardware and PCB design.
Discuss your firmware project — describe your device, its current stage, the software help you need, and approximate timing.