Internal eeprom - erase block

[Dave]

ruijc, But why are you required to erase all of the data? Why not just keep a couple of pointers? 1 for number of data bytes recorded and 1 for the next data location. The reason for 2 is to verify if either is corrupted. Just update the 2 pointers when writing the data or clear them when you require a memory clear function.

Dave Purola,
N8NTA

[ruijc]

Hello Dave,

Very interesting idea.

It makes perfect sense. It's a completly diferent logic this way.

Thanks

What i thought was:

I can reserve 4 bytes ( using 2 blocks of data...reserve more with more blocks ) of memory such as:

1 will record the starting address for first block
1 will record the ending point for the first block
1 will record the starting point of second block
1 will record the ending address of second block

This way i can have variable size of block with data

These can be stored either in the external or internal eeprom ( i guess it will be safer to store them in the external one )

For reading it will lookup these bytes for it to know where to start colecting data and where to stop.

To erase just simply put these to 0 ( reminding to check for 0 before start recording ).


I think it can work this way, dont you think ?



.

[Dave]

ruijc, Bygolly youv'e got it....... I have used this same method for about 3 years or so using 4 24LC1025's for data storage of depth, temperature, diveplane angle, and status at 1 second intervals for about 18 hours on my TempTracker.

Dave Purola,
N8NTA

[sayzer]

So what Dave is suggesting is like a partition table.

Instead of erasing all data, just erase or clear partition table.

If the partition table is empty, the data is not accessible or is useless.

--------------

[ruijc]

This way i can "erase" alot of blocks of data in a ms and also safely read only what i recorded in the previous session and not mix up data from previous recordings.