Firmware & Drivers
Drivers for SPI, I²C, UART, ADC and DMA, bare-metal or on top of the vendor HAL.
Meplis has been developing firmware for more than eight years. We usually join a project at the first prototype board and stay until the devices are in the field and receiving updates.
More of our projects now run a trained model on the device itself. The device reacts within milliseconds, keeps working without a connection, and raw sensor data does not have to leave it.
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.
Typical uses: anomaly detection on motors and pumps, predictive maintenance, power quality analysis, keyword spotting and visual inspection.
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.
We run our own MQTT brokers, OTA update server and LoRaWAN gateway for development and field tests. The console below shows a sample device log.
Tell us about the hardware, the requirements and the timeline.