- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am a newbie to management of Em_EEPROM/Flash and trying to get a handle on how best to store/retrieve data. I have the processes for read/write figured out, but management is the question.
I understand that the PSoC6 Em_EEPROM is byte-addressable. I have a data set that I need to manage, about 800 records of 10 bytes each that I also need to be able to search and update where required. Just wondering how best to store the data, whether I should have a 3D array of 80 Rows, each row containing 10 x 10-byte records.
Does anyone have examples of 2D/3D EEPROM data management? Is there such method for the above example of having eeArray
When searching through the data, do I need to figure out the physical addresses, or is this done by reference to my array configuration? eg eeArray[7][6] sufficient to retrieve the data?
Solved! Go to Solution.
- Labels:
-
PSoC Creator Software
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
In PSOC 6 EEPROM is byte-addressable and Em_EEPROM/Flash is row wise addressable i.e. if you want to change a byte you have to erase the entire row and do the same. You can refer the component datasheet for more information.
I have attached a example project with 2D/3D array implementation.
You can look at it and let us know if that is helpful.
Regards
Alakananda
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
In PSOC 6 EEPROM is byte-addressable and Em_EEPROM/Flash is row wise addressable i.e. if you want to change a byte you have to erase the entire row and do the same. You can refer the component datasheet for more information.
I have attached a example project with 2D/3D array implementation.
You can look at it and let us know if that is helpful.
Regards
Alakananda
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for your help. That is precisely what I was after, but I was under the impression that Em_EEPROM was also byte addressable. I guess I can read it byte-wise though.
I will have a close look at it in the next day or so and see if this gets me to where I need to go. Thanks for your prompt response.