Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
Jan Waclawek
12/29/11 07:29
Read: 383 times

#185228 - poor tips and no tricks
Responding to: David Prentice's previous message
If I correctly understand your application, Erik's [3] doesn't sound that dramatically bad. You'd use MOVC for reading, won't you - and that's quite fast, isn't it. You can limit the number of needed reads by performing the "garbage collection" either when for a certain variable Nth write is reached, or periodically during "idle" times, if such occur in the application.

There's no trick in B52, the clumsiest possible method is used, employing a sector-sized buffer in RAM, and no provision for sudden powerdown. The BASIC program is stored in FLASH in the same format as in RAM, "linearly", so if lines are added at the end, only those are written into the FLASH, but if a line is modified or inserted or removed from somewhere in the middle, a significant FLASH rewrite is performed - it is quite perceptible as soon as the program reaches a couple dozen of lines. But then I don't think this particular application needs more sophistication than that.


List of 6 messages in thread
Strategy for 'FLASH' eeprom      David Prentice      12/27/11 08:17      
   depends      Jan Waclawek      12/27/11 10:59      
   comments      Erik Malund      12/27/11 11:22      
      Avoid flash if you can - unless having wear-leveling chip      Per Westermark      12/27/11 21:13      
         Thankyou for your input      David Prentice      12/28/11 13:39      
            poor tips and no tricks      Jan Waclawek      12/29/11 07:29      

Back to Subject List