Embedded Firmware Development
Microcontroller firmware for products where the hardware and the firmware are the same project.
Firmware for a custom board is easier when whoever writes it can read the schematic, and easier still when they drew it. That is the case here: the firmware, the board, and where relevant the FPGA all come off the same bench.
Work spans bare-metal and RTOS targets across STM32, ESP32, and PIC, from initial bring-up on an unpopulated board through a shipping application.
Targets
- STM32, across the Cortex-M families
- ESP32, including the Arduino framework and ESP-IDF
- PIC microcontrollers
- Bare-metal and RTOS-based architectures
Peripherals and connectivity
- SPI, I2C, UART, CAN, and timer or PWM subsystems
- Sensor and actuator integration, including servo control
- WiFi-connected devices and local network control interfaces
- Smart-home integration: Alexa, Google Home, and Home Assistant
Product work
- Board bring-up: clocks, power, and first signs of life
- Bootloaders and field update paths
- Low-power design and sleep-mode budgeting
- Production test firmware and provisioning
Built, shipped, and debugged on real hardware
Connected consumer devices
ESP32-based products with WiFi control and smart-home integration, designed as complete units rather than firmware handed over a wall.
Board bring-up
First-power firmware for custom boards, establishing clocks, rails, and communication before the application layer exists.
Scope that fits the problem
- Firmware for a board you have already designed
- Hardware and firmware together, as a single deliverable
- Bring-up only: get a new board talking, then hand off
- Rescue work on firmware whose original author is gone
Related work on this site
These are shipping products from the same bench. They are the clearest evidence of what the service delivers.
Discuss a project