STM32: A smarter class of microcontroller
The STM32 family didn’t just join the embedded scene—it reframed it with a balance of performance, low power, and scalability across cores and peripherals. That breadth lets teams match the microcontroller to the mission without overengineering, from Cortex-M0 efficiency to Cortex-M7 horsepower. Think of STM32 as a modular toolkit where timers, ADC/DAC, DMA, and robust comms interfaces let firmware stay elegant while hardware grows in capability.
ESP32: Connectivity-first deployments
When the brief demands connectivity out of the box, ESP32 shines with built-in Wi-Fi and Bluetooth, plus strong dual-core compute for edge logic. Real-world deployments span industrial IoT gateways, environmental monitoring, smart home control, HVAC telemetry, and wireless HMIs. It’s the pragmatic path when over-the-air updates, secure pairing, and cloud handshakes are must-haves.
What Andivi builds on STM32
Andivi develops smart sensors and room devices on STM32, integrating advanced sensing, multi-protocol stacks, and power-aware firmware. Our Modbus and BACnet smart sensors show how structured embedded design yields reliable data, stable timing, and predictable network behavior in building automation. The Alledio Room Unit adds a refined user experience on top—tight loops for sensing and control, with firmware that stays responsive under UI load. And with ISO 9001 and ISO 14001 certifications, Andivi’s engineering and operations follow quality and environmental rigor from requirements through release.
Sectors we know best (and beyond)
Andivi is most at home in IoT, HVAC, and Green Energy, where uptime, repeatability, and lifecycle upgrades matter. That said, the firmware practice is stack-agnostic by design: industrial controllers, smart metering, renewables, sensor fusion, gateways, and edge analytics all benefit from the same disciplined approach—clean drivers, resilient state machines, and deterministic I/O.
Languages we use—and why
C: Deterministic control over memory, timing, and peripherals for hard-real-time sections and drivers.
C++: Type safety and modular architectures for larger codebases without sacrificing embedded performance.
C#: Robust tooling for test harnesses, configuration apps, and production support utilities on desktop.
Python: Scripting and automation for CI, calibration flows, data parsing, and rapid algorithm prototyping.
JavaScript: Device-hosted UIs and configuration panels served from the microcontroller or companion gateways.
HTML/CSS: Lightweight web interfaces for setup, diagnostics, and field maintenance with minimal overhead.
Protocols we speak fluently
Low-level: SPI, I2C, UART—clean HALs, DMA-backed drivers, and ISR-safe ring buffers for stability.
Building/industrial: BACnet, KNX, Modbus—solid stacks with robust parsing, rate limiting, and fault recovery.
Wireless and peripherals: Wi-Fi, Bluetooth, NFC, USB—from pairing and provisioning to CDC, HID, and field updates.
Interfaces that feel effortless
Simple, dependable web apps on devices make setup and service faster: HTML, CSS, and JavaScript keep the footprint lean while giving technicians a clear window into status and settings. UI and flows are designed in Figma, so stakeholders can validate interactions before a single line of code lands.
Our development process (firmware-first)
Discovery and Requirements: Clarify constraints, interfaces, timing, and field conditions—the bedrock of predictable firmware.
Architecture and Planning: Define tasks, priorities, and scheduling; isolate peripherals; plan boot, update, and recovery paths.
Driver Bring-up: Stand up clocks, GPIO, DMA, and core peripheral drivers with a focus on ISR brevity and testability.
Application Logic: Implement state machines, supervision, watchdogs, and degradation modes for resilience under stress.
Connectivity and Protocols: Integrate BACnet/KNX/Modbus, or Wi-Fi/BLE stacks with backoff, retries, and QoS-aware flows.
Testing and Verification: Unit, integration, and HIL testing; regression suites; burn-in and environmental edge cases.
Documentation and Handover: Maintain API docs, service guides, bootloader/update instructions, and traceability.
Bonus: Andivi can deliver complete hardware development when a single partner across electronics, firmware, and DFM reduces risk.
Also shipping on ESP32 (in C)
Beyond STM32, Andivi develops ESP32 firmware in C, from sensor nodes to industrial gateways and wireless room controllers. Typical features include secure provisioning, MQTT/REST integrations, OTA updates, low-power modes, and field diagnostics—engineered to be supportable for years, not just functional on day one.
Quick comparison: STM32 vs ESP32 use-cases
| Use-case | Best fit | Why |
|---|---|---|
| Deterministic control loops | STM32 | Tight timing, rich timers/ADC/DAC, scalable cores |
| Wireless-first edge devices | ESP32 | Integrated Wi‑Fi/BLE, proven IoT stacks |
| Multi-protocol building automation | STM32 | Industrial protocol breadth and predictable latency |
| Cost-effective connected sensors | ESP32 | Connectivity on-die with adequate compute |
| Mixed UI + sensing + control | STM32 | Peripheral depth and flexible memory options |
How we think about reliability
Firmware should behave like a well-tuned orchestra, where interrupts, tasks, and I/O all keep tempo—even when a soloist misses a note. That’s why Andivi designs for graceful failure, observability, and maintainability—from watchdog strategies to structured logging and bounded retries. The result is systems that degrade safely, recover quickly, and stay diagnosable in the field.
Ready to collaborate?
If a project would benefit from seasoned STM32 or ESP32 firmware engineers, Andivi is open to a thoughtful conversation about goals, constraints, and timelines. No pushy pitch—just an honest exploration of whether the roadmap aligns, and how to make prototype-to-production smoother with the right engineering partner.
