Less Common Errors!

Error: bizarre changes in memory after a function call

• This problem first arose when noticing writes to a EEPROM weren't sticking, and later we drilled it down to an issue where the 3-byte address array we'd pass into the EEPROM read function was inexplicably getting changed during the function, even though we weren't modifying the address in the function. What was suspect was that this problem was not occuring in Skanda's machine (Ubuntu 14.04, arm-non-eabi-gcc version 6.2) but exhibited itself on Rango's and Eric's machines (OSX, arm-non-eabi-gcc version 5.1).

This may have either been a problem associated with stack overflow on the chip (which we don't suspect, because the function call depth and local variable allocation is small), or a compiler bug. Either way, this was solved on OSX by bumping up the version of arm-non-eabi-gcc to 6.2. Contact Eric for details on how to do this.