Firmware & Drivers
Drivers for SPI, I²C, UART, ADC and DMA, bare-metal or on top of the vendor HAL.
Meplis · Embedded Software Engineering
We build the software side of embedded products end to end: system architecture, board bring-up, RTOS design, connectivity, edge AI and the secure update path that keeps devices maintainable once they ship.
Edge AI
We deploy ML models on microcontrollers and embedded processors, so devices can detect, classify and decide locally: low latency, no dependency on connectivity, and data that does not have to leave the device.
Models that run on the MCU or embedded processor itself, inside a fixed RAM, flash and power budget. No round trip to the cloud.
Quantization, pruning and operator-level tuning, so a model trained on a GPU fits the target and meets its real-time deadline.
Filtering, feature extraction and sensor fusion written as production firmware, not notebook code.
Data capture from devices, validation on hardware in HIL, and versioned model updates shipped over OTA with the firmware.
Drivers for SPI, I²C, UART, ADC and DMA, bare-metal or on top of the vendor HAL.
Zephyr and FreeRTOS: task design, priorities, IPC and memory budgets that hold under load.
Wi-Fi, Ethernet, LoRa, BLE, cellular and CAN. MQTT and TLS on top, with reconnects and buffering for unreliable links.
Signed images, A/B slots and rollback if the new firmware does not come up.
HIL and SIL setups, host-based unit tests with mocked hardware, MISRA-C checks in CI.
SWD debugger, logic analyzer and scope, for bugs that are half hardware.
What it must do, what it runs on, what is fixed.
Clocks, pins and drivers on the real board.
Application code and RTOS tasks.
Unit tests, static analysis, bench tests on hardware.
Signed release over OTA, then watch the telemetry.
Checked from this machine each time you load the page. Some services are firewalled, so “offline” may only mean “not open to the internet”.
Tell us about the hardware, the requirements and the timeline.