I checked and I actually using version 1.8.0 updated.fpiSTM wrote: Mon May 11, 2020 5:13 am Th next release of the core will include several I2C bug fixes.
You can try with the master repo to see if this fixes your issue.
The strange thing, that lead me to think that there is something wrong with memory allocation, is that if I change, for example, print content, it change systematically the output, even if truncated to int, so it is not a problem with float management, but maybe some register or ram that is overwrited or bad instantiated?