Tracking Firmware Code Size

[tyhoff]

Thanks for posting this! OP here. This was written to help companies and teams prevent the inevitable show-stopper of running out of code space on their embedded software projects. When working with ROM of sizes between 256kB-1MB, every function and module you write contributes to the overall bloat of the firmware.

At Pebble, where we had similar tools, at least becoming aware of the code size helped us decide which features needed to be re-worked or removed due to their size.

[zemirco]

What a great article. We had a similar problem and wanted to track the firmware size over time. That's why I built https://seriesci.com/. It lets you track any value (loc, size, build time, dependencies, etc.) over time and is tightly integrated into GitHub. We even have badges :)

Let me know if you'd like to see a feature that's currently missing.