Firmware engineering at Hoomanely: bootloaders that can't brick a device, RTOS scheduling patterns, and the flash storage strategies that keep a collar or bowl reliable after thousands of power cycles in the field.
The hub board inside our feeding station reports air quality, light and motion to the rest of the device over a CAN bus. The firmware queued a frame. The controller accepted it. And nothing — nothing at all — appeared on the wire. There was no error code to chase, no exception,
Every over-the-air update hides a bootstrapping problem: the software that applies updates is itself software, and can be broken by an update. When a bad image lands on a sensor module inside a pet feeding station — a device with no screen, no buttons, no port anyone will plug into — nobody
A smart pet bowl runs real neural networks. It segments the animal in a camera frame, reads a temperature at the right point on its body, and classifies the sounds of eating and barking. That means a full deep-learning runtime has to live on the device — not a toy inference
Rebooting a device sounds harmless until you remember what it's for. When a pet-monitoring station restarts, it isn't watching anything — no weight readings, no captures, no heartbeat. A safe operating-system update costs a reboot, and a reboot costs a small hole in a pet's
Every radio on a pet tracker has a horizon. Bluetooth reaches across a room, maybe a house on a good day. The moment a dog slips through a gate and trots down the street, that link is gone — and that is precisely the moment a pet parent most needs to
A camera is the obvious way to know whether a pet is in the room — and often the wrong one. It fails in the dark, it's blocked by a blanket or the side of a bed, and it puts a lens in the most private corners of someone&
When a device misbehaves on your bench, you attach a debugger, tail a log, poke at it. When that same device is a smart pet bowl in a stranger's kitchen — one of thousands, behind a home router, with no screen and no one to read a terminal — none
At 3 a.m., a smart pet bowl in a customer's kitchen notices it hasn't captured anything in half an hour. The sensor path has quietly wedged — the kind of stall that, on a normal device, would sit there dead until someone noticed the app had
The first minute a customer spends with a connected device decides how they feel about it forever. Unbox a smart pet bowl, open the app, and within about a minute it should just be online — quietly uploading, ready to watch over their pet. But that minute hides a genuine chicken-and-egg
Replacing the operating system on a computer usually means having your hands on it: a cable, a USB stick, a recovery button, someone in the room. Now imagine that computer is inside a pet's feeding bowl, in a stranger's kitchen, behind their home router, three time
Firmware is the layer where hardware promises meet reality — the code that has to boot reliably, survive a dying battery, and recover from its own mistakes without a human nearby to help. This hub covers the discipline of embedded software engineering at Hoomanely: bootloaders that can't brick a device, real-time operating system patterns that keep sensor timing deterministic, and the flash storage strategies that make a collar or bowl trustworthy after thousands of power cycles.
We work on this because our devices live in kitchens, on collars, and in yards — not in a lab with a debugger attached. A watchdog that doesn't fire, a filesystem that corrupts on power loss, or an OTA update that bricks a fleet isn't a bug report, it's a product returned. So we write publicly about the failure patterns we've actually hit and the fixes that held up.
Start with The Brick-Proof Bootloader: Designing an A/B Swap Partition for how we make updates recoverable by construction, then The Recovery Bootloader That Cannot Be Overwritten for the layer beneath that. Watchdogs and Livelock: Real Failure Patterns and Fixes and CM4 Bring-Up Checklist: eMMC Boot, USB Boot, and Recovery cover the boot and hang failures we see most in the field. For storage, When Flash Isn't Just Flash: FATFS vs LittleFS in IoT walks through choosing a filesystem for embedded flash. On the RTOS side, One Firmware Platform Across Bare-Metal and FreeRTOS and Queue vs. Direct Task Notify: FreeRTOS ITC Trade-offs cover the scheduling and inter-task communication patterns we lean on daily.
If you're building firmware that has to survive real users rather than a bench test, this is where we put what we've learned.