1. 8
  1.  

  2. 2

    There are a bunch of plugins for Jenkins for similar things (link), like tracking warnings or test coverage. There’s nothing for firmware size however. Maybe something could be rigged using some of the tools in the linked article, into a generic firmware size tracking plugin?

    1. 2

      That would be fantastic. CircleCI also has the concept of “Orbs” which we looked into.

    2. 1

      We call the optimization “Memory Tetris”. Since we have different RAMs, it usually means to shift symbols to different regions. For example, use slower global RAM instead of fast core-local one.

      1. 2

        Note that in this post we look at code size rather than RAM footprint. Though if you statically allocate everything you can trivially do the same thing for the data section.