3 ms·
The number that stuck out was 200K lines of code. Can you expand on why so much code had to be written and which parts were the longest (time and/or code) and
by rwmj 3mo ago
The number that stuck out was 200K lines of code. Can you expand on why so much code had to be written and which parts were the longest (time and/or code) and hardest bits?
- chipweinberger 3mo agoThe app is about 85K lines: device connectivity, first-time setup, syncing, MIDI playback and visualization, library management, audio/video export, and OTA workflows. The firmware is about 110K lines: MIDI recording + streaming, USB, Bluetooth, Wi-Fi, web APIs, storage, OTA updates, diagnostics, security, peripherals, provisioning, and an embedded web interface. There’s a lot required to make a full-featured product.
- lukeweston1234 3mo agoThis seems like an incredibly large codebase. Did you use an existing RTOS or something similar for this product, or was this all hand rolled?
- junon 3mo agoYeesh, please tell me you didn't write all of that yourself. Which uC is it targeting, and which language?
- cazum 3mo agoFrom the photo in the link it looks like he's using an esp32-s3. I suspect that 110k number might include the ESP-IDF libraries as well as his own code. I've written a fairly feature-complete handheld device based on the esp32-s2 and the codebase is about 9k sloc of the C I've written, but that number explodes to almost 40k sloc if I include the esp-idf's imported libraries.
- chipweinberger 3mo agoThese numbers do not include ESP-IDF :)
- bonzini 3mo agoWhat is the manufacturing tooling that you mention?
- chipweinberger 3mo ago3 main components: flashing, provisioning keys, hardware testing. Nearly every component gets tested: sdcard, clock, battery, anti-counterfeit IC, led, buzzer, the tactile-switch!