The original Teenage Engineering OP-1 now has a software-style development loop despite shipping as a closed appliance. The new op1-sdk builds synth engines, effects, sequencers, and interface overlays in C or assembly, tests them in a Blackfin simulator, then patches a user's verified copy of firmware R246 for flashing to real hardware.
The valuable part is the guardrail set around reverse engineering. The SDK checks the firmware SHA-256, original instructions, hook collisions, and every address signature it depends on. Each feature lives in a self-contained folder with sources, tests, a simulator bench, and a manifest. The repository contains none of Teenage Engineering's proprietary firmware, so builders bring their own image and can restore stock by reflashing it. A device that once required edit-flash-pray now has a host-side test loop and a package format.
Embedded product teams should treat this as a warning about closed extension models. If an independent project can build a safer simulator-first workflow around an unsupported product, vendors charging for official SDK access need to ship better tests and faster iteration, not just documentation.