Est. MMV
Theme
21 · Electronics · Firmware
STM32 · ESP32 · Arduino · FreeRTOS · Zephyr

Software discipline at the silicon level.

— Definition

Embedded software lives inside the device — it reads sensors, drives relays, runs motors. Every byte counts, every clock cycle matters. The Senkronix embedded team ships production-ready firmware for STM32, ESP32, nRF52, Arduino, and Raspberry Pi. OTA updates, low-power design, BLE/WiFi/LoRa protocols, and security layers are all included.

N° I — Why Custom Firmware?

Prototype ≠ Product.
Both are custom work.

Embedded software is often seen as gluing libraries together. A few sample sketches are copied in the Arduino IDE and the project seems to run. But once it goes to production; simultaneous OTA updates across thousands of devices, sensors running five years on battery in the field, zero-downtime firmware rollback, certification compliance (CE, FCC, UL), and security layers all come into play. Library-pasting does not scale to that level.

The Senkronix embedded team starts with the datasheet. We understand the MCU's internal clock sources, peripheral registers, DMA channels, and interrupt priorities before the design phase. Whether firmware runs bare-metal, on FreeRTOS, or on Zephyr RTOS is decided together based on the project. Even if we start in the Arduino IDE, we finish production with professional toolchains (STM32CubeIDE, PlatformIO, IAR, Keil).

Advantages of custom firmware

  • Optimizes hardware cost — right-sized MCU selection rather than an oversized one
  • Extends battery life up to 10x — sleep modes, wake-up sources, power profiling
  • OTA updates — remotely patch devices running in the field for years
  • Certification compliance — required radio and EMC provisions for CE, FCC, UL, TELEC
  • Security layers — secure boot, encrypted communication, anti-tampering, fuse-bit locking
  • Years of support — firmware lives as long as the hardware is produced
N° II — Capabilities

Eight domains.
All production-grade.

— Firmware Layers / N° II-A
Five layers · From hardware to cloud
DONANIM → ← BULUT N° 01N° 02N° 03N° 04N° 05 HALRTOSUygulamaOTAGüvenlik
● Layer node→ Firmware flow
01
Bare-Metal & RTOS

FreeRTOS, Zephyr, ThreadX; bare-metal scheduler, interrupt-driven design, HAL layer management.

02
OTA Updates

Secure OTA bootloader, dual-bank firmware, rollback, signed package verification, delta updates.

03
Sensor Integration

I²C, SPI, UART, CAN, 1-Wire; IMU (BNO055, MPU), temperature, pressure, humidity, gas, GPS, load cell.

04
Wireless Communication

BLE 5.x, WiFi 6, LoRa, LoRaWAN, Zigbee, Sub-GHz, NB-IoT, LTE-M; protocol stack design.

05
Low-Power Design

Sleep modes, RTC wake-up, power gating, dynamic clock scaling, battery profile analysis.

06
Security & Crypto

Secure boot, AES, ECC, TLS/DTLS, crypto engine, TPM, secure element, anti-tampering circuits.

07
Motor & Control

PID, PWM, brushless motors (BLDC, PMSM), stepper motors, relay control, real-time control.

08
Test & Manufacturing

Unit testing (Ceedling, Unity), HIL test, production line test software, automated calibration, JTAG/SWD.

N° III — Platforms

Which MCU?
Project-driven selection.

— MCU & Sensor Map / N° III-A
Six platforms · Embedded core
Gömülü Çekirdek STM32ESP32NORDIC BLERASPBERRY PISENSÖR PAKETİMOTOR / PWM Cortex-M0/M4/M7HAL · FreeRTOSWiFi + BLEIoT · Düşük güçnRF52 / nRF53BLE 5.x · MeshLinux gatewayPrototip · PoCIMU · SıcaklıkGPS · Yük hücresiBLDC · PMSMStep · Röle
● Core connection□ Platform family

The right microcontroller is different for every project. An 8-bit Atmel Tiny and a 32-bit Cortex-M7 may appear in similar solutions but represent entirely different decisions when weighed against cost, power, performance, and production volume. During Discovery, Senkronix evaluates expected workload, peripheral requirements, power budget, cost target, and chip availability to select the right platform.

MCU families we work on

  • STM32 — F0/F1/F4/F7/H7, L0/L4/L5 (low power), G0/G4 (motor control), U5 (security). Our most common platform
  • ESP32 / ESP32-S3 / C3 — For projects requiring WiFi+BLE; IoT, smart home, industrial gateways
  • nRF52 / nRF53 / nRF91 — Nordic Semiconductor; ultra-low-power BLE, wearables, sensors
  • Arduino (AVR, SAMD) — Education, prototyping, low volume; we migrate to a professional platform when productization requires it
  • Raspberry Pi (RP2040) & Pi Zero/4/5 — Bare-metal for Pico W, Linux-based edge computing for Pi
  • GD32, Renesas RL78/RA, NXP S32, TI MSP430/C2000 — For automotive and industrial-specific needs

Toolchains and languages

  • C / C++ — The standard in embedded; C++17/20 features applied to embedded where appropriate
  • Rust embedded — For memory-safety-critical projects; embedded-hal ecosystem
  • MicroPython / CircuitPython — For rapid prototyping and educational projects
  • IDEs: STM32CubeIDE, PlatformIO, IAR EWARM, Keil μVision, ESP-IDF, Zephyr West
  • CI/CD: Cross-compile, automated test, binary sign & release with GitHub Actions and GitLab CI
N° IV — Who is it for?

Every sector with electronics.

Scenario · 01

IoT Sensor Manufacturers

For companies building field sensors, smart agriculture, smart city, water/gas meters. Low power, long battery life, LoRa/NB-IoT communication.

Scenario · 02

Industrial Devices

For factory-floor device manufacturers. Modbus, CAN, Ethernet/IP protocols, 24V-tolerant I/O, EMC compliance.

Scenario · 03

White Goods & Consumer Electronics

Consumer products; kitchen robots, air purifiers, smart thermostats. UI microcontroller, OTA, certification.

Scenario · 04

Medical Devices

Glucometers, blood pressure monitors, sleep devices. Medical certification (ISO 13485, IEC 62304), BLE-based mobile integration.

Scenario · 05

Automotive & Vehicles

In-vehicle electronics, control units, CAN bus devices. AUTOSAR compliance, ISO 26262 functional safety.

Scenario · 06

R&D & Prototyping

For entrepreneurs who want to validate new ideas quickly. Engineering support across prototype → MVP → production.

N° V — Frequently Asked Questions

Clear questions,
clear answers.

Do you design the hardware as well, or only software?+
Our core expertise is software. For circuit design (schematic, PCB layout) we work with certified hardware engineering partners; we can deliver the full package (hardware + software + manufacturing) or firmware only. If you already have hardware, we can start firmware development immediately.
We started with Arduino — can you productize it?+
Yes, this is very common. We preserve the spirit of the prototype, migrate Arduino code to a professional platform (STM32 or ESP32), rewrite it to meet reliability, power, and certification requirements, and add production-line test software. The journey from Arduino IDE to production typically takes 2-6 months.
How does OTA update work?+
The device periodically checks the server for a new firmware version. If one is available, the signed package is downloaded, verified, and written to the empty half of dual-bank memory. The bootloader activates the new version on restart. On failure it automatically rolls back to the previous version. Delta updates download only changed portions, keeping things fast even over 2G/NB-IoT.
How important is low power consumption? Is 5-year battery life feasible?+
It is feasible — but must be a goal from day one. Five-year battery life on a CR2032 requires microamp-level average consumption. The device spends 99.9% of its time in sleep mode, transmitting for only a few minutes per day. LoRa/NB-IoT radios are more energy-intensive than BLE. On Senkronix projects we measure real battery life with hardware profilers and estimate within 15-30% tolerance.
Is certification (CE, FCC, TELEC) included in the process?+
Certification testing takes place at accredited laboratories (TÜBİTAK MAM, UL Türkiye, EMITEL). We prepare the necessary firmware and hardware adjustments for testing and accompany you at the lab. Test fees are billed separately; typically 5,000-15,000€ for CE radio, similar range for FCC. First-attempt pass rate correlates directly with design quality.
How long does a project take and how much does it cost?+
Simple sensor firmware 4-8 weeks, medium-complexity product 3-6 months, certified full package 6-12 months. Price is set during Discovery based on MCU selection, peripheral count, protocol complexity, security requirements, and certification scope. Project-based pricing, no license fees.
N° VI — Process

Four stages.
Each one documented.

01
Discovery

Use case, power budget, production volume, and certification requirements are clarified.

Output: Spec · BOM · Scope
02
Design

MCU selection, architecture, memory map, peripheral design, power analysis, OTA/security strategy.

Output: HLD · LLD · Power Profile
03
Development

Two-week sprints; module development, unit testing, HIL testing, integration on real hardware.

Output: Firmware · Test Report · Git
04
Manufacturing & Support

Production line test software, serial number registration, flash programming, certification, OTA infrastructure.

Output: Production Software · SLA
— Firmware Proposal Desk

Tell us about your device.
Its inner workings we will write together.

bilgi@senkronix.com · Karatay / Konya