Understanding local compile output

Make Your Binary Smaller By Removing Debug Logging

Locally buliding, I just went from

   text	   data	    bss	    dec	    hex	filename
  90156	   2968	  11484	 104608	  198a0	core-firmware.elf

to

   text	   data	    bss	    dec	    hex	filename
  68272	   2912	  11484	  82668	  142ec	core-firmware.elf

simply by uncommenting line 16 defining USE_ONLY_PANIC in core-common-lib/SPARK_Firmware_Drive/inc/config.h:

There was a discussion last week in a community thread about making this more easily accessible from the command line, leading to this issue in the backlog:

Store Data On External Flash

Check out this thread with functions for reading from the external flash chip the same way we read keys and factory reset firmware:

Additionally in that thread is a discussion of how to use the CC3000 EEPROM.

@mdma was working on a library for :spark: SD/EEPROM access—he has the last post in that thread currently, saying he was taking a break from it a couple weeks ago.

Also, in the libraries category, @mattande posted his NVM library that supports basic wear-leveling and CRC checking:

Lots of ways to read and write over 1.5MB of available flash on the Core!

Cheers!

5 Likes