Started by eagleeye, December 17, 2012, 12:29:13 pm
Quote from: LubOlimex on December 17, 2012, 01:04:45 pmHey there,We actually don't use any of those functions since they refer to Microchip EEPROM memory on their boards. We mount different memory and never got to use the functions listed.Regards,Lub/OLIMEX
// All parsing complete! Save new settings and force a reboot #ifdef OLIMEXSaveAppConfig(); //<- it should be removed or commented // + Thanks to Allan ("eagleeye" in Olimex forum) for this fix + XEEBeginWrite(0x0000); XEEWrite(0x60); XEEWriteArray((BYTE*)&newAppConfig, sizeof(newAppConfig)); // - Thanks to Allan ("eagleeye" in Olimex forum) for this fix -
Quote from: SHIBBY on February 24, 2014, 04:16:15 pmHi,It looks like line 645 on CustomHTTPApp.c hasn't been updated despite Allan's warning. I've faced the same issue with the latest version of the example code: the NVM reading starts at a wrong adress. It's not a big issue as long as you update every settings on the same web page, otherwise if you just modify some parts of it the unmodified variables will end up having garbage in it and saved in NVM.So, XEEReadArray(sizeof(NVM_VALIDATION_STRUCT), (BYTE*)&newAppConfig, sizeof(newAppConfig)); must be replaced by XEEReadArray(0x0001,(BYTE*)&newAppConfig, sizeof(newAppConfig));.