EEPROM offset incrementing

Hello Rob,

The procedure you have mentioned is correct. Secondly, the offset register cannot increment by itself.. If you can attach the program for EEPROM Write and Read, we may be able to help better.

Please provide the driverlib version

Regards

Amit

Hello Amit

My main project is in CMSIS but this is the code I am trying to test driver lib with, I get the same result both way. I have tried 3 different boards so I assume that I am missing something in the code.

#include <stdint.h>
#include <stdbool.h>
#include "inc/hw_memmap.h"
#include "inc/hw_types.h"
#include "inc/hw_gpio.h"
#include "inc/hw_ints.h"
#include "driverlib/gpio.h"
#include "driverlib/pin_map.h"
#include "driverlib/sysctl.h"
#include "driverlib/interrupt.h"
#include "driverlib/eeprom.h"
 
 
#define EEPROM_TEST_ADRES 0x0004
 
struct EEPROM
{
    uint8_t value1;
    uint8_t value2;
    uint16_t value3;
    uint8_t value4[12];
};
 
struct EEPROM eeprom_write_value = {5,7,9826, "Hello World"}; /* Write struct */
struct EEPROM eeprom_read_value =  {0,0,0,""}; /* Read struct */
 
int main(void)
{
    uint32_t e2size,e2block,value;
 
    SysCtlClockSet(SYSCTL_SYSDIV_2_5|SYSCTL_USE_PLL|SYSCTL_OSC_MAIN|SYSCTL_XTAL_16MHZ); // 80 Mhz

 
    /* EEPROM SETTINGS */
    SysCtlPeripheralEnable(SYSCTL_PERIPH_EEPROM0); // enable EEPROM
    EEPROMInit(); // EEPROM start
    /*******************************/

    EEPROMProgram((uint32_t *)&eeprom_write_value, EEPROM_TEST_ADRES, sizeof(eeprom_write_value)); //Write struct to EEPROM start from 0x0000
 
    EEPROMRead((uint32_t *)&eeprom_read_value, EEPROM_TEST_ADRES, sizeof(eeprom_read_value)); //Read from struct at EEPROM start from 0x0000

		value = eeprom_read_value.value3;
 
while(1)
 {
 }
 
}

Thanks Amit

You are correct the debugger was incrementing the address.

It makes it hard to debug the EEPROM, nut at least I know what is going on now.

Hello Rob

Glad it helped you

Regards

Amit

Amit Ashara said:

When the register is read in the debugger window it causes...

Quite excellent diagnosis Amit - will help all those (landing) here.

Might there be "other" (mainly peripheral) registers which exhibit similar sensitivity?  (sensitive to either the debugger and/or a simple, MCU "read" of that specific register)

Seems that your excellent "get" here could be expanded - and placed as a proper, "Warning/Signpost" to guide your client-users around - rather than into - this "unwanted/unexpected" pitfall...

Hello SourceTwo,

As far as I know C2000 devices implement a debugger lock as well, where debugger read of the registers does not modify the content, especially like FIFO read registers and auto incrementing registers

Regards

Amit

SourceTwo said:

Coincidentally, within the last week I was reading the data sheet of a competitor's M4

Thou treadest dangerously close to, "Blasphemy" mon ami.  (quelle competition?)

Suspect our identifications - suggested improvements - once again receive (always hallowed) "due notice" - and are then (calmly/quickly) cast to the winds...  (wherefore art thou - "lost, forum template" posts/suggestion?)

Again - key point (bit muddied & escaped): 

"Seems that your excellent "get" here could be expanded - and placed as a proper, "Warning/Signpost" to guide your Tiva client-users (i.e. victims) around - rather than into - this "unwanted/unexpected" (sensitive register/debug) pitfall..." 

(ain't too many C2000 users haunting/slumming - here...)