EEPROM suggestion
CannibalRobotics
Posts: 535
For my volume control, I'm needing a way to store configurations through power cycles.
I'm pretty sure Brandon's http://obex.parallax.com/objects/493/·or something similar is the answer for accessing the EEPROM.
Now the question is this, these configuration·strings are really tiny in terms of data. There are 5 to 10 16 byte chains. I know that the Parallax documentation says·32K is loaded from the EEPROM on boot but is is reeeeallly all 32K if the code is small? Is there a terminator in the machine code?
Would I be risking late nights if I hung 160 bytes of data at the very end of the EEPROM?
Pending an answer of yes, is there an optimum choice for the next EEPROM up?
Thanks,
Jim-
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Signature space for rent!
Send $1 to CannibalRobotics.com.
I'm pretty sure Brandon's http://obex.parallax.com/objects/493/·or something similar is the answer for accessing the EEPROM.
Now the question is this, these configuration·strings are really tiny in terms of data. There are 5 to 10 16 byte chains. I know that the Parallax documentation says·32K is loaded from the EEPROM on boot but is is reeeeallly all 32K if the code is small? Is there a terminator in the machine code?
Would I be risking late nights if I hung 160 bytes of data at the very end of the EEPROM?
Pending an answer of yes, is there an optimum choice for the next EEPROM up?
Thanks,
Jim-
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Signature space for rent!
Send $1 to CannibalRobotics.com.
Comments
Mike had an explanation in this post:
·http://forums.parallax.com/showthread.php?p=894581
Jim
J-
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Signature space for rent!
Send $1 to CannibalRobotics.com.