EEPROM Writes - Too many EEPROM.write() can crash board - needs recovery... about opencm9.04 HOT 4 CLOSED

Looking at this, what I find interesting is that:
In drv_eeprom.c lines 126...

#define ADDR_FLASH_PAGE_126 ((uint32_t)0x0801F800) /* Base @ of Page 126, 1 Kbytes /
#define ADDR_FLASH_PAGE_127 ((uint32_t)0x0801FC00) / Base @ of Page 127, 1 Kbytes */

So this page looks correct for PAGE0:
EEVPFWV 0 0 PAGE0 801f800 801fbff HFP 1 801f804 0 HFP 1 801f806 0 status 0

But for Logical Page1, which are first write is showing: EEVPFWV ff ff PAGE1 802f800 802fbff
Which is not Page_127...

The function EE_FindValidPage returns PAGE0 or PAGE1
Which are defined:

#define PAGE0                 ((uint16_t)0x0000)
#define PAGE1                 ((uint16_t)0x0040)

The computation for The pages address is:

 address = (uint32_t)(EEPROM_START_ADDRESS + (uint32_t)(validpage * PAGE_SIZE));
pageendaddress = (uint32_t)((EEPROM_START_ADDRESS - 1) + (uint32_t)((validpage + 1) * PAGE_SIZE));

So wondering why PAGE1 is defined as 0x0040? Wonder what would happen if it was defined as 0x01?

from opencm9.04.

@KurtE ,

So wondering why PAGE1 is defined as 0x0040? Wonder what would happen if it was defined as 0x01?

Oh, sorry and thanks...
The value of PAGE1 is invalid. The value of PAGE1 must be modified to 0x01.
If I make a correction, it will affect your PR.
Do you want to modify and apply PR?

from opencm9.04.

@OpusK
That I can do...

from opencm9.04.

@KurtE,

Thanks again for your contribution!

from opencm9.04.