hi All ,
I am planning to use TM4C123GH6PZ in my project.
I want to know ,TM4C123GH6PZ is having 256kb of flash ,so can we share this flash as Data flash.
if yes ,please let me know the proccedure.
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
hi All ,
I am planning to use TM4C123GH6PZ in my project.
I want to know ,TM4C123GH6PZ is having 256kb of flash ,so can we share this flash as Data flash.
if yes ,please let me know the proccedure.
utpal kumar said:TM4C123GH6PZ is having 256kb of flash
See for yourself, from the link below.
http://www.ti.com/product/TM4C123GH6PZ
-kel
While 256KB seems large - is that fact alone sufficient to overcome predictable weaknesses?
a) rather restricted SRAM - in which to "capture" data bound for such flash storage - might this derail this effort?
b) added complexity to implement & manage this fairly involved process
c) execution time - to transfer from limited SRAM into "always relatively slow flash writes"
May prove instructive to review how "pro products/firms" so attack. MCU as, "kitchen sink" may prove less than, "stellar."
cb1_mobile said:While 256KB seems large - is that fact alone sufficient to overcome predictable weaknesses?
a) rather restricted SRAM - in which to "capture" data bound for such flash storage - might this derail this effort?
b) added complexity to implement & manage this fairly involved process
c) execution time - to transfer from limited SRAM into "always relatively slow flash writes"
May prove instructive to review how "pro products/firms" so attack. MCU as, "kitchen sink" may prove less than, "stellar."
Only one thing to add: use an external SPI EEPROM/FRAM for data storage; much faster than using the internal flash. If you only have a few sets of data which will not change that often during on-time you can store them in the internal EEPROM.
aBUGSworstnightmare
Yes. Subject to the limitations of (a) total amount of Flash, (b) time takes to erasing and writing to Flash, (c) the Flash retension time, (d) the Flash durability, (e) the Flash reliability, ...
The procedure is:
1. Allocate part of Flash to code and part of Flash to data. The boundary must be at integer multiple of 1KB (for erasing). But 2KB is preferred (for protection).
2. You can protect code & data separatly if the boundary is 2KB aligned.TivaWare has a procedure to do so.
3. The smallest block of Flash you can erase is 1KB at integer KB boundary. TivaWare has a procedure to do so.
4. You can write to already erased Flash, TivaWare has a procedure to do so.
I agree with the other responses, but then 256 KB may not be enough without shareing with data. TM4C may not be fast enogh without erasing/writing to Flash. Everything has its limitations.
@Bug, OCY, CB1 - we three in overall agreement! Each supplying (hopefully) key puzzle piece/consideration.
Can world peace be far behind?