Services / 03
$ cat /services/embedded-firmware
Embedded Systems & Custom OS
Bare-metal firmware for devices that must run for years on power budgets near zero.
- px, custom display typeface
- post-quantum secured
- poured per charge, firmware-metered
On a device that has to run for years between charges, every library you did not write is current you cannot account for. We work at the bare-metal level: schedulers sized to the product, drivers written against the datasheet, sleep states measured in microamps and audited line by line.
The furthest we have taken it is a complete operating system for a payment card: a bistable electrochromic display with its own driver stack, a 7×5 pixel typeface designed in-house, a secure element, and post-quantum cryptography, all with zero network dependency at the point of sale. The same discipline runs the pour spout, whose firmware meters ten litres of pouring on a single charge.
Method
-
Budget first
Power, memory, and timing budgets written before code. The coin cell does not negotiate.
-
Bring-up
Board bring-up and drivers from the datasheet, with a logic analyzer as the referee. No vendor blob survives unread.
-
Harden
Secure elements, cryptography, watchdogs, brownout paths. The card assumes the network is absent and hostile.
-
Run the fleet
Provisioning, OTA, and lifecycle tooling, so revision seven ships to devices already in the field.
Deliverables
- Bare-metal & RTOS firmware
- Custom display drivers & UI stacks
- Secure element integration
- Post-quantum cryptography
- OTA & device lifecycle tooling
- Power audits, per instruction if needed
Bench
- ARM Cortex-M, bare metal schedulers written per product
- Bistable & e-paper display stacks drivers plus a 7×5 typeface of our own
- Secure elements · PQC schemes offline-first cryptography
- Sub-µA sleep profiling years-scale battery budgets
- OTA & provisioning tooling fleets, not units