Hi there everyone. 
I have a project that I am likely to tinker with over the Christmas break, which involves storing quite a bit of data on an EEPROM running on the I2C bus. This data will be a combination of raw data that the PICAXE can read and write when needed, but 75% of the memory-map will be ASCII text messages which the PICAXE can read out of the chip and show on the LCD when needed for various things - it's a way of saving program space on the PICAXE itself, as lots of text messages can gobble up all your program space.
My main concern at this point is, uploading and downloading the data from the EEPROM to the PC and back.
Reading would be relatively straightforward - setup a routine which when selected(there will be LCD and button control) simply transmits the entire memory map one byte at a time, serially to the computer running some terminal software, then save the terminal session - done.
However, what if I wanted to write back the computer file to the EEPROM?
You might say that you can reverse the above, but you can't as page-errors and overflows have to be controlled when writing large amounts of data to EEPROM.
Does anyone here have any pointers on the best way to get a download from a computer into the EEPROM chip?
I was thinking of making use of CTS and RTS on the serial port, using PICAXE IO pins, which SHOULD control the data flow to the EEPROM via the PICAXE, allowing the PICAXE to control the writing speed to the EEPROM and prevent page-errors - correct?
I might be slightly off track with my understanding of things, so please feel free to offer pointers and suggestions.
I am currently reading my way through the 24LC256 EEPROM chip manual.
This EEPROM supports page writing, with a 64-byte page length, so I have to be able to control writes at no more then 64-byte pages at a time.
...back to the reading...

I have a project that I am likely to tinker with over the Christmas break, which involves storing quite a bit of data on an EEPROM running on the I2C bus. This data will be a combination of raw data that the PICAXE can read and write when needed, but 75% of the memory-map will be ASCII text messages which the PICAXE can read out of the chip and show on the LCD when needed for various things - it's a way of saving program space on the PICAXE itself, as lots of text messages can gobble up all your program space.

My main concern at this point is, uploading and downloading the data from the EEPROM to the PC and back.
Reading would be relatively straightforward - setup a routine which when selected(there will be LCD and button control) simply transmits the entire memory map one byte at a time, serially to the computer running some terminal software, then save the terminal session - done.

However, what if I wanted to write back the computer file to the EEPROM?
You might say that you can reverse the above, but you can't as page-errors and overflows have to be controlled when writing large amounts of data to EEPROM.
Does anyone here have any pointers on the best way to get a download from a computer into the EEPROM chip?
I was thinking of making use of CTS and RTS on the serial port, using PICAXE IO pins, which SHOULD control the data flow to the EEPROM via the PICAXE, allowing the PICAXE to control the writing speed to the EEPROM and prevent page-errors - correct?
I might be slightly off track with my understanding of things, so please feel free to offer pointers and suggestions.
I am currently reading my way through the 24LC256 EEPROM chip manual.
This EEPROM supports page writing, with a 64-byte page length, so I have to be able to control writes at no more then 64-byte pages at a time.
...back to the reading...
Last edited: