Ok, usually one can use 127,5 KB (because page 0 can't be accessed). How to get 128 KB?
Maybe upload 2 pages starting at page 255?
THat's a good idea... so page 255 will be 1024 bytes (= 4 EEPROM pages) and all other pages 512 bytes (= 2 EEPROM pages).
Hmm, thinking about why this was necessary in the first place... actually, that problem did only arise because I needed a way to trigger PCM sample playing without halting the firmware (it needs to continue sample playing WHILE accepting new arguments for the next PCMPLAY command, and I couldn't use an interrupt based solution because I need max performance for PCM sample playing). Hence, I figured I will use the "0" as a separator byte (or "clock" byte) for the arguments of the |pcmplay command. Hence, I could not allow the 0 as an argument since it was used as a separator / clock byte. That was the only reason.
However, for the EEPROM as data storage application, this 0-based synchronisation for sending arguments to |pcmplay is not required. We can just use 0 as the start page. Only |PCMPLAY is not allowed to use 0. But |eeprom2ram can use page 0 as an argument / address, why not. Here, it is ok if the firmware waits until the page number argument has been supplied.
So let me change this tonight.
Recent Posts
