Firmware Development, New Zealand
Bare-metal, RTOS, and Embedded Linux firmware, plus the companion software that connects to it.
Firmware is the layer where hardware either becomes reliable or stays fragile. A board can be perfectly laid out and still fail in the field if the interrupt handling is wrong, the RTOS scheduling doesn't hold under load, or the wireless stack drops connection outside a lab environment.
MicroCore develops embedded firmware across bare-metal, RTOS, and Embedded Linux (Yocto), with deep experience on STM32 ARM Cortex-M platforms. We also bridge the gap between hardware and the people using it, desktop utilities and mobile companion apps for device provisioning, real-time diagnostics, telemetry visualisation, and secure local or cloud connectivity.
Firmware & Software Services
From low-level drivers to the mobile app a technician uses to configure the device in the field.
Bare-Metal & RTOS Firmware
Interrupt-driven, scheduler-based, and callback-based architectures on STM32 ARM Cortex-M (F4/G4 series). Low-level drivers and firmware built for deterministic behaviour, not just a passing bench test.
Embedded Linux (Yocto)
Custom Yocto builds for MPU-class devices that need a full OS, filesystem, networking stack, and application layer tailored to the hardware, not a generic distro image.
Desktop & Mobile Companion Apps
Native utilities and mobile apps for device provisioning, real-time diagnostics, telemetry visualisation, and configuration, the interface between a technician and the hardware in their hands.
Wired & Wireless Stack Integration
CAN bus, Bluetooth dual-mode (SPP + BLE), Wi-Fi, and Ethernet stacks integrated at the firmware level. Scales up to DSP, computer vision, and machine learning workloads on more capable MCU or MPU platforms.
Firmware Written for Unattended Operation
The same firmware base runs client projects and MicroCore's own product development.
Our CAN bus, Bluetooth, and power management firmware base is not theoretical. It has shipped in client hardware across automotive, medical, and agricultural projects, including IP67-rated automotive control modules and a CubeSat payload built to run unattended in Low Earth Orbit for more than six months. We are now building on that base in MicroCore's own IP67 marine MPPT controller and wireless CAN-FD bridge, both currently in design. That is the standard applied to every firmware engagement: code that has to keep running after the engineer who wrote it has gone home.
Start a Firmware Engagement
Bring the hardware, the target, and the constraint that is causing trouble.
The scoping form asks nine questions about the platform, the toolchain, and where the firmware currently sits. Existing code, schematics, and bus captures are all useful. We reply within two working days.
MicroCore is an Auckland firmware practice working remotely with teams in Australia and further afield. Timezone overlap and getting hardware on the bench are usually the real constraints, not distance.