You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While performing some code examination I found a bug in calls to the "copy_STM8_bytes_to_I2C_EEPROM()" function. Those calls were intended to perform I2C EEPROM "fill with 0" or fill with some other constant as part of initialization of those I2C EEPROM areas. Instead the calls were filling the first byte with the constant, and the remaining were writes had random data. I wrote a new function "init_I2C_EEPROM()" to implement the intended outcome. I may combine these later if it results in code space savings.
I'm not sure this was causing any user issues. The fix will be included in the next major release.
The text was updated successfully, but these errors were encountered:
While performing some code examination I found a bug in calls to the "copy_STM8_bytes_to_I2C_EEPROM()" function. Those calls were intended to perform I2C EEPROM "fill with 0" or fill with some other constant as part of initialization of those I2C EEPROM areas. Instead the calls were filling the first byte with the constant, and the remaining were writes had random data. I wrote a new function "init_I2C_EEPROM()" to implement the intended outcome. I may combine these later if it results in code space savings.
I'm not sure this was causing any user issues. The fix will be included in the next major release.
The text was updated successfully, but these errors were encountered: