-
Notifications
You must be signed in to change notification settings - Fork 17
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 persistence #231
Comments
I too need better EEPROM functionality. Gave it 4 votes 👍 |
Thanks @greenveg! What project are you working on? |
Using a Controllino (Arduino framework PLC) for test rig at work. Need power-off recovery and such… |
(This comment is mostly a "bump" - but I also just used a few votes on it!) |
Note: additional discussion in #399 |
newbie here, for my school project IRL I am using |
When you buy a new ATmega328P microcontroller (as used in the Arduino Uno), then the EEPROM is empty. A empty EEPROM means that all the data is 0xFF. Wokwi simulates a fresh new unused Arduino Uno and therefor the EEPROM is empty and is 0xFF. |
How can I store EEPROM contents in browser local storage? |
That is not implemented yet. The EEPROM contents is not stored in the Wokwi project as a file yet and it is not stored on your computer as local browser data. |
Feature request: store the internal EEPROM somewhere to make its data persistent.
My request is a for the internal EEPROM of the AVR family boards. When returning to Wokwi next day, the previous written data should still be there.
No extras
There are many additions that I can think of (download the contents; have a number of binary files which can be choosen or uploaded; also store the simulated EEPROM of the SAMD and ESP processors; and so on), but that it too much over the top.
Writing to EEPROM has no clock-accurate delay. It is slower on a old ATmega8 then on a newer microcontroller. This might have consequences for interrupts. Since this is a very specific situation, I don't mind if the delay for writing data is skipped.
Storage location
It would be nice if the data was stored on the Wokwi server in the project and not on the user's computer. That allows to use an other computer and continue with the same data.
The text was updated successfully, but these errors were encountered: