AI App Development

If you use AI to write embedded firmware—specifically bootloader hooks, flashing routines, and signature verification—and then discover that your device behaves completely incorrectly, host tests pass while the real device fails, or the online deployment is still running an old version, this post is for you. Over the last six days, I analyzed the thirteen detours we took during meta-pass v1.0 development. Most were not core technical failures, but rather the same root cause resurfacing in different forms: the task description did not specify what “done” means. ...

meta-pass is a multi-firmware launcher I wrote for AI Passport. A persistent launcher sits on the device, firmware images are installed into Flash slots and you select which one to boot from a startup list instead of reflashing the whole device every time. The two-day MVP process is documented in the previous post. Not useful. This thing takes up 3MB, leaving only two 2MB slots. Anything slightly practical won’t fit. The comment was mostly right. Over the next six days, I submitted 90 commits, working through eight comments one by one and iterated meta-pass from MVP to v1.0: three slots, signature badges, backup and restore, single-file firmware, data-safe upgrades, bootloader hardening and a USB speedup. Most of the v1.0 changes were directly driven by those comments. ...