Embedded Firmware Development Services
Bare-metal to Zephyr RTOS, OTA updates, sensor integration
Embedded firmware is the software that runs directly on a microcontroller inside a hardware product. Electuni writes firmware for ESP32, STM32 and Nordic nRF devices, from bare-metal code to FreeRTOS and Zephyr RTOS. It includes secure OTA updates and sensor integration, for teams building connected products.
Design → Prototype → Production
Key Facts: Firmware Development
- Platforms
- ESP32, STM32, nRF
- RTOS
- FreeRTOS, Zephyr
- OTA
- Secure Updates
- Protocols
- BLE, Wi-Fi, LoRa
- Sensors
- I2C, SPI, UART
- Testing
- Hardware-in-Loop
What You Get
- Documented, version-controlled firmware repository
- Firmware for the chosen microcontroller platform (ESP32, STM32 or Nordic nRF)
- OTA update system with secure boot, encrypted firmware images and rollback
- Sensor drivers with calibration routines, filtering and data fusion
- Wireless connectivity firmware (BLE, Wi-Fi, LoRa) where the product needs it
How We Approach Firmware Development
From bare-metal register-level programming to full RTOS-based architectures, we write firmware that is reliable, testable, and maintainable.
Our OTA update system includes secure boot, encrypted firmware images, rollback capability, and fleet management integration.
We implement comprehensive sensor integration pipelines with calibration routines, filtering algorithms, and data fusion for multi-sensor systems.
How an Electuni Engagement Works
Step 1
Discovery
Requirements analysis and feasibility study.
Step 2
Architecture
System design, component selection, and risk assessment.
Step 3
Design
Schematic, layout, firmware, and mechanical CAD.
Step 4
Review
DFM/DFT checks and design review with stakeholders.
Step 5
Prototype
Board fabrication, assembly, and firmware bring-up.
Step 6
Handoff
Production files, BOM, and full documentation package.
Tools & Technologies
- VSCode
- PlatformIO
- FreeRTOS
- Zephyr RTOS
- JTAG Debugging
Firmware Development FAQ
How do I choose between ESP32, STM32 and Nordic nRF?
Choose by connectivity, power budget and peripherals. ESP32 integrates Wi-Fi and Bluetooth LE at low cost, which suits Wi-Fi products. STM32 offers a very broad range of ARM Cortex-M parts and rich peripherals. Nordic nRF chips are built for low-power Bluetooth LE, Thread and Zigbee. Supply and toolchain preferences also matter.
Should my product use bare-metal code, FreeRTOS or Zephyr?
Bare-metal fits simple, deterministic devices with few concurrent tasks. FreeRTOS adds a small scheduler with tasks and queues and is the base of ESP32's ESP-IDF. Zephyr is a larger RTOS with a device-tree driver model, a Bluetooth stack and wide board support, and it underlies Nordic's nRF Connect SDK. Pick by complexity and connectivity.
How do secure OTA firmware updates work?
A secure OTA system downloads a new firmware image, and the bootloader verifies its signature before running it. The device keeps the previous image so it can roll back if the new one fails to start. Electuni's OTA systems include secure boot, encrypted images and rollback, and typically use MQTT or CoAP for transport.
Which sensor interfaces do you support: I2C, SPI or UART?
All three. I2C uses two shared wires and device addresses, which is convenient for many slow sensors. SPI is faster and uses a chip-select line per device. UART is a point-to-point serial link, often used for GPS and modems. Raw readings are then calibrated, filtered and, for multi-sensor systems, fused.
How is embedded firmware tested before release?
Firmware is tested at several levels. Hardware-independent logic can be unit-tested on a host computer. Behaviour that depends on real peripherals, timing or radios is tested on target hardware, including hardware-in-the-loop setups. JTAG or SWD debugging is used to inspect problems on the device itself. Electuni lists hardware-in-the-loop among its testing methods.
What do I receive at the end of a firmware project?
You receive a documented, version-controlled firmware repository containing the source code and build instructions for your target microcontroller. Where the scope includes them, the handoff also covers the OTA update setup and the sensor and wireless drivers. The exact deliverables are agreed in the fixed project scope.