Posted on July 30, 2014 at 07:56
Case 1:
The following image shows the contents of page1 ( page0 now erased). The latest values of 0x5555 & 0x6666 are retained properly from page0. We can see the continuation of variables in page1 of virtual address 0x77
Case 2:
The following image shows the contents of page0 ( page 1 now erased). The latest values of 0x5555 & 0x6666 are retained properly from page1.We can see 2 retained variables 555000A and 66660014, 39th written variable 77770 After them, we should have 40th variable 77770 But it has not been written. I guess there is some coding issue.
I tested Case 1 and Case 2 again once more, I found Case 2 exhibits the same problem described here.Where is it going wrong ?
@clive1: I understand the problems with this emulation stuff, but I desperately need it in my project.
I have created a new IAR project & writing 3 variables with virtual addresses 0x5555, 0x6666 and 0x7777 respectively. The sample code uses 2 pages (page0, page1) in sectors 2 & 3 of FLASH memory ( STM32F4-Discovery board with STM32F407VG mcu).
Here is simple code which writesfirst variable 10 timesat 0x5555, second variable 20 timesat 0x6666 and the third variable 40 times at 0x77
/* Virtual address defined by the user: 0xFFFF value is prohibited */
uint16_t VirtAddVarTab[NB_OF_VAR] = {0x5555, 0x6666, 0x7777};
uint16_t VarDataTab[NB_OF_VAR] = {0, 0, 0};
uint16_t VarValue = 0;
intmain(void)
{
/*!< At this stage the microcontroller clock setting is already configured,
this is done through SystemInit() function which is called from startup
file (startup_stm32f4xx.s) before to branch to application main.
To reconfigure the default setting of SystemInit() function, refer to
system_stm32f4xx.c file
*/
/* Unlock the Flash Program Erase controller */
FLASH_Unlock();
/* EEPROM Init */
EE_Init();
/* --- Store successively many values of the three variables in the EEPROM ---*/
/* Store 10 values of Variable1 in EEPROM */
for(VarValue = 1; VarValue <= 10; VarValue++)
{
EE_WriteVariable(VirtAddVarTab[0], VarValue);
}
/* read the last stored variables data*/
EE_ReadVariable(VirtAddVarTab[0], &VarDataTab[0]);
/* Store 20 values of Variable2 in EEPROM */
for(VarValue = 1; VarValue <= 20; VarValue++)
{
EE_WriteVariable(VirtAddVarTab[1], VarValue);
}
/* read the last stored variables data*/
EE_ReadVariable(VirtAddVarTab[0], &VarDataTab[0]);
EE_ReadVariable(VirtAddVarTab[1], &VarDataTab[1]);
/* Store 40 values of Variable3 in EEPROM */
for(VarValue = 1; VarValue <= 40; VarValue++)
{
EE_WriteVariable(VirtAddVarTab[2], VarValue);
}
/* read the last stored variables data*/
EE_ReadVariable(VirtAddVarTab[0], &VarDataTab[0]);
EE_ReadVariable(VirtAddVarTab[1], &VarDataTab[1]);
EE_ReadVariable(VirtAddVarTab[2], &VarDataTab[2]);
while(1);
}
Posted on July 31, 2014 at 09:13
But WHY there is problem when running stand alone ?Do we need any delay after the sector erase ? too confused !
Replying for myself.
I did step by step debug in IAR, watched flash memory for Case 2. There was no problem, everything works ok.But WHY there is problem when running stand alone ?Do we need any delay after the sector erase ? too confused !
Posted on August 01, 2014 at 04:48
See page1
I found this behavior is repeatable. As we can see the page1 has ERASED page status, when application runs next time, the page will be erased by EE_Init(); functional call at start.I'm updating this forum post with care & hoping that someone will reply and suggest any fix.I'm waiting for EEPROM Emulation application based on STM32Cube package library. Hope that may fix this bug.Please help, our project has tight schedule.
Did little more debugging, actually the loop is not getting terminated. But the values are being written to the erased page ( page1) though the page0 marked as VALID_PAGE and page1 ERASED.
Here is FLASH memory contents of Case 2;See page0See page1I found this behavior is repeatable. As we can see the page1 has ERASED page status, when application runs next time, the page will be erased by EE_Init(); functional call at start.I'm updating this forum post with care & hoping that someone will reply and suggest any fix.I'm waiting for EEPROM Emulation application based on STM32Cube package library. Hope that may fix this bug.Please help, our project has tight schedule.
