-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
eeprom overflow error with bitlash run command for a user defined function #45
Comments
Update: |
Hello and thanks for your notes. As you have observed, the AVR convention is that 255 is the value for uninitialized EEPROM. The fact that the problem recurs after several reboots from the clean state leads me to believe what you are seeing is likely caused by eeprom fragmentation. Could you send the output of “peep” after the error happens? A possible workaround is to only define the eeprom function if it is not already there. You could possibly use the function src/bitlash-eeprom.c::findKey(char *id) to check if it’s already been defined from your C driver program. -br
|
Hello, Thank you for the reply. When everything is working fine the peep of the eeprom is this.
Then say I program it again with the same code, no issue everything works fine. Same eeprom peep. If I do the programming several times (not a specific number of times), then I get the error of 'unexpected id' when trying to run the saved function using doCommand("run iot;") and at that point the peek looks like the following. (which i think is the cause for the 'unexpected id' since following is all seem jumbled up) Note - Even though in previous cases 'eeprom overflow' was shown in addition to 'unexpected id', I coundn't reproduce that error in order to take a peep.
I think for the time being I would try out the workaround you mentioned. |
Hello, I am using an arduino mega. I have the following code. Which works as expected.
When I try to run it as a function in background using;
even though the first doCommand should return 'saved', it returns 'eeprom overflow'. I checked the eeprom using eeprom read and write and also used eeprom clear. Everything is fine. (Plugged out and connected and all the other programs works fine, so does the arduino doCommands. Error occurs only when I try to run a function in background. I have used "ps;" to check whether there are anyother background functions running. There are none.)
I should also mention that the background run command and saving worked perfectly for few attempts. Then it started giving the 'eeprom overflow' instead of 'saved'.
Am I missing something here ?
Any insight will be much appreciated. Thank You
The text was updated successfully, but these errors were encountered: