Skip to content

Embedded Systems Development

Embedded firmware from bare-metal MCU to RTOS and production IoT devices. Nordic nRF, ESP32, STM32. EU engineering, built to CRA requirements.

Reviewed by:
Vladimír Vician
Last reviewed:
Last Updated:
Nov 2026
Service Definition
Embedded firmware from bare-metal MCU to RTOS and production IoT devices. Nordic nRF, ESP32, STM32. EU engineering, built to CRA requirements.

Embedded Firmware. Engineered for Production.

What is Embedded Systems Development?

Embedded systems development is the design and programming of firmware that runs on microcontrollers — from bare-metal C code on Cortex-M0 to multi-threaded RTOS applications on high-performance MCUs. It encompasses hardware bring-up, driver development, wireless protocol stacks, power optimization, and hardware-level security. For AI-enabled devices, see our Edge AI capabilities.

Your product idea is clear. Your hardware is designed. But firmware is where the product comes alive — and where most embedded projects hit the wall.

Firmware that works on the bench and firmware that survives 5 years in the field are fundamentally different things. We build the second kind.

Inovasense delivers production-grade embedded firmware for companies that need it done right, on time, and compliant — without building an in-house embedded team from scratch.


What We Build

🔧 Complete Products — From Zero

Full embedded product development: requirements → architecture → MCU selection → schematic review → firmware → testing → production. You get a turnkey device ready for manufacturing.

  • • IoT sensor nodes & actuators
  • • Industrial controllers & gateways
  • • Wearables & health monitors
  • • Smart city & building devices

💻 Firmware for Existing Hardware

You have the hardware — we write the firmware. BSP development, driver porting, protocol stack integration, and performance optimization for your existing boards.

  • • Board support packages (BSP)
  • • RTOS migration & optimization
  • • Wireless stack integration
  • • Legacy firmware modernization

Platforms We Specialize In

We focus on three MCU families widely used in IoT and embedded products — each chosen for specific strengths:

PlatformKey ChipsBest ForConnectivity
Nordic SemiconductornRF52840, nRF5340, nRF9160, nRF9161BLE devices, wearables, ultra-low-power sensors, cellular IoTBluetooth LE (5.4 or later), Thread, Zigbee, LTE-M/NB-IoT
Espressif ESP32ESP32-S3, ESP32-C6, ESP32-H2Wi-Fi connected devices, cost-optimized IoT, edge AIWi-Fi 4 (ESP32-S3) / Wi-Fi 6 (ESP32-C6), BLE 5, Thread/Zigbee (ESP32-C6, ESP32-H2), Matter
STMicroelectronicsSTM32L4, STM32F4, STM32H7, STM32U5Industrial control, motor drives, medical, high-performance DSPFlexible — paired with external radio modules

How we choose: Nordic when battery life is everything and BLE/cellular is the primary link. ESP32 when Wi-Fi is required and cost pressure is high. STM32 when raw processing power, peripheral richness, or functional-safety support (ST safety manuals and certified self-test libraries for IEC 61508) drive the decision. We help you pick the right platform during assessment — not every project needs the most expensive chip.

Not sure whether to pick an MCU, Crossover, or a powerful Linux MPU?

Try AI Architectural Advisor →

Core Capabilities

Firmware Architecture & RTOS

  • Bare-metal state-machine-driven firmware for ultra-low-power sensors
  • FreeRTOS and Zephyr RTOS for multi-task devices with deterministic scheduling
  • nRF Connect SDK (based on Zephyr) for Nordic platforms
  • ESP-IDF framework for Espressif devices
  • STM32CubeMX + HAL/LL for STMicroelectronics platforms
  • MISRA C/C++ compliant code for safety-critical applications

Wireless Protocol Stacks

ProtocolRangePowerUse Case
Bluetooth Low Energy (5.4 or later)~100 mUltra-lowWearables, beacons, asset tracking
Thread / MatterMesh; tens of metres per hop indoorsLowSmart home, building automation
LoRaWAN2–5 km urban, up to 15 km ruralUltra-lowRemote sensors, agriculture, utilities
LTE-M / NB-IoTCellularMediumAsset tracking, smart metering, remote monitoring
Wi-Fi 6~50 mMedium-HighCameras, gateways, high-bandwidth devices

Power Optimization

Battery-powered devices are our specialty. On Nordic and STM32 platforms we target an average current of units to tens of µA, verified by measurement, through:

  • Deep sleep mode engineering with RTC wake-up
  • Peripheral power gating and clock management
  • RF duty cycling and adaptive transmission scheduling
  • µA-resolution power profiling with Nordic PPK2 / Otii Arc
  • Production-validated battery life predictions (not just datasheet estimates)

Bluetooth Low Energy Products

Bluetooth Low Energy is a common choice for battery-powered devices; we work with it on Nordic nRF52/nRF53 and ESP32. In a BLE project we take care of:

  • GATT design — services and characteristics that a phone app or a gateway can use without workarounds
  • Pairing and bonding with LE Secure Connections, with keys protected in a secure element where the product needs it
  • Power budget for coin cells and small Li-Po batteries: connection intervals and advertising strategy, measured on the real board
  • Firmware updates over BLE with a signed image and the MCUboot bootloader
  • BLE together with NFC and USB in one device
  • Preparation for radio testing to EN 300 328 under the RED, and for Bluetooth SIG qualification of the end product

Experience: our team has worked on the development of battery-powered hardware security devices — FIDO2 authenticators that combine Bluetooth Low Energy, NFC and USB with a fingerprint sensor, a low-power display and a Common Criteria EAL5+ certified secure element.

Secure Firmware — Built to CRA Requirements

Conformity with the EU Cyber Resilience Act is declared by the manufacturer for the whole product. Every firmware project includes security measures that support it:

🔐 Boot & Update Security

  • • Hardware-verified secure boot chain
  • • Signed & encrypted OTA firmware updates
  • • Rollback protection with monotonic counters
  • • MCUboot bootloader integration

🔑 Identity & Crypto

  • • Hardware secure element integration (ATECC608C, OPTIGA)
  • • Per-device unique identity provisioning
  • • TLS 1.3 / DTLS mutual authentication
  • • Hardware-accelerated AES, SHA, ECC

For full security architecture details, see our Embedded Security & IoT practice.

Testing & Quality

  • Hardware-in-the-loop CI/CD — Automated tests running on real target hardware, not just simulators
  • Static analysis — MISRA C compliance checking, Coverity, PC-lint Plus
  • Unit testing — Ceedling with Unity and CMock for embedded C
  • Power regression testing — Automated current measurement to catch power regressions before release
  • EMC pre-compliance — Near-field scanning and conducted emissions testing before formal compliance testing

From our projects: the Collection Box Sensor for postal operators and the Universal Letterbox Sensor for households are battery-powered NB-IoT sensors verified in pilot operation.


How We Work

We follow a structured delivery process designed for enterprise clients who need predictability and transparency:

01

Assessment & Architecture

We analyze your requirements, recommend the optimal MCU platform, define the firmware architecture, and estimate the project timeline. Deliverable: Technical Specification Document.

02

Development & Integration

Firmware development in 2-week sprints with hardware-in-the-loop testing. Regular demos on real hardware. Full Git history and documentation. Deliverable: Working firmware on target board.

03

Validation & Production

Environmental testing, power validation, EMC pre-compliance, and manufacturing test development. Deliverable: Production-ready firmware package with programming tools and OTA infrastructure.

Typical timelines:

  • Simple sensor node (BLE/LoRa, bare-metal): 6–10 weeks
  • Multi-protocol IoT device (BLE + cellular, RTOS): 3–4 months
  • Complex industrial product (multi-sensor, edge AI, OTA, certification): 4–6 months

Indicative figures: for a complete product including hardware, the first working prototype is typically ready 8–16 weeks after the requirements are signed off, and the development cost (NRE) of a moderately complex connected product is typically 40–120 thousand €. Every project gets its own estimate after the assessment — the full process is described under Product Management.


Why Companies Choose Inovasense

Challenge Our Answer
"We can't hire embedded engineers fast enough"An embedded team without recruitment lead time
"Our prototype works on the bench but fails in the field"We build for production — power profiling, EMC, environmental testing
"We need CRA compliance but don't know where to start"Security built in from day one — secure boot, OTA, SBOM included
"Our previous vendor delivered code we can't maintain"Clean, documented, MISRA-compliant code with full Git history
"We need EU-based development for IP protection"100% EU engineering — full IP ownership, GDPR compliant

Our embedded systems development integrates seamlessly with:

  • Embedded Security & IoT — Hardware root of trust, secure elements, Java Card applets
  • FPGA Design Services — When MCUs aren’t fast enough — custom digital logic in FPGA fabric
  • Edge AI — On-device ML inference for anomaly detection, vision, and predictive maintenance
  • Industrial Design — Enclosures, thermal management, and DFM for your embedded product
  • EU Compliance — CRA, CE marking, RED, and full EU market access

Ready to Build?

From concept to production-ready firmware — tell us about your embedded project and we'll provide a detailed technical assessment and project plan within one week.

Start Your Project →

Sources & Official References

Guides in this area

Frequently Asked Questions

What embedded platforms does Inovasense work with?

We specialize in Nordic Semiconductor (nRF52, nRF53, nRF91 series), Espressif (ESP32, ESP32-S3, ESP32-C6), and STMicroelectronics (STM32L4, STM32F4, STM32H7). We select the optimal platform based on your application's power, performance, connectivity, and certification requirements.

Can you develop firmware for hardware we already have?

Yes. We provide firmware development for existing hardware designs — including BSP development, driver porting, protocol stack integration, RTOS migration, and performance optimization. We work with your schematics and documentation to deliver production-quality firmware.

How does Inovasense ensure firmware security and CRA compliance?

Every firmware project includes secure boot, signed and encrypted OTA updates, and hardware-backed key storage by default. We follow the EU Cyber Resilience Act requirements from the architecture stage — including vulnerability management, SBOM generation, and secure development lifecycle documentation.

What is your typical project timeline for a custom embedded product?

A typical embedded product — from concept to production-ready firmware — takes 3–6 months depending on complexity. Simple sensor nodes: 6–10 weeks. Complex multi-protocol devices with BLE + LoRaWAN + edge AI: 4–6 months. We provide detailed project plans with clear milestones.

Do you develop Bluetooth Low Energy devices?

Yes. We work with BLE on Nordic nRF52/nRF53 and ESP32: GATT profile, secure pairing, power budget and firmware updates over BLE, plus preparation for radio testing to EN 300 328 and for Bluetooth SIG qualification. Our team has worked on battery-powered FIDO2 security devices with BLE, NFC, USB, a fingerprint sensor and an EAL5+ certified secure element.

Regulatory References (Authority Source)