I am using STM32 CubeProgrammer and performed the "Full chip erase". after the Full chip erase some garbage value appears at EEPROM address (0x0808 0000 & 0x0808 0010)
Can you share the exact reference of the device you're using so that we can reproduce the issue.
Best regards,
Aziz
In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
Hello Aziz, the problem seems to be related to the 4 byte Eeprom pages using ST-Link-V2 and Cube. Program code in flash is always fine.
1) If we use Seggers Ozone + Jlink to load the same ELF, everything is fine
2) If we force to program Eeprom with initialized data from linker by ELF,
Segger is also fine but Cube reports write error for download
Normally our application does not have initialized data segment in eeprom but it expects either 0 or valid data in Eeprom to start correct. Invalid eeprom shows wrong functions as long as the application wrote first time to eeprom itself. This happens many times after application update using ST-link V2 and thats how we found the matter. Maybe we can reproduce with our STM32 Nucleo what contains a very similar STM32L011. I am sure, the reason is not the chip as everything is fine with Segger Tools.
