Hi all,
Sorry but I am unable to find information on the maximum times for erasing and programming sectors on the Concerto using F021 Flash API. Should be somewhere in the data sheet or TRM I suppose. Please help...
Best regards,
Christian
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,
Sorry but I am unable to find information on the maximum times for erasing and programming sectors on the Concerto using F021 Flash API. Should be somewhere in the data sheet or TRM I suppose. Please help...
Best regards,
Christian
Maybe the sector erase and programming (maximum) times have not been characterized and published by TI yet?
Hi Christian,
Christian L said:Maybe the sector erase and programming (maximum) times have not been characterized and published by TI yet?
Sector as such is not mentioned but flash in whole is as follows for your device:
Regards,
Gautam
Hi Gautam,
I might have been unclear but I wasn't asking about endurance, that is, how many erase cycles etc the device can tolerate before bit-flips may occur.
I am interested in knowing what the maximum time it will ever take me to erase- and then program one of the 64kB sectors using the F021 Flash API. From the FAQ you pointed me to, it seems that maybe the erase-time maximum is not really predictable and TI will not give you any upper bound. If so, then I would still at least like to know the max programming time.
Best regards,
Christian
Christian,
This is being worked on. Expect it to be published early next week.
Hareesh
Christian,
Out of the below options, let me know the operating frequency of the M3/C28x at which you want the erase/program times data.
1) 75MHz/150MHz
2) 100MHz/100MHz
3) 75MHz/75MHz
4) 60MHz/60MHz
Thanks and regards,
Vamsi
Hi Christian,
Below are the program and erase times for M3/C28x at 75MHz/150MHz.
Program time includes overhead of the Flash state machine but does not include the data transfer time (to load the code that uses Flash API to program the Flash, Flash API and the Flash data in to device RAM). Program time assumes programming 144-bits at a time at the specified operating frequency. Program time includes program verify by the CPU. Note that the program time does not degrade with cycling.
Erase time does not include the data transfer time. Erase time includes Erase verify by the CPU.
Please let us know if you have any questions.
Master Subsystem Flash parameters at 75MHz | ||||
Parameter | Flash size | Typ | Max | Unit |
Program time | 16 kB | 145 | 290 | ms |
64 kB | 580 | 1160 | ms | |
128 data bits + 16 ECC bits |
40 | 300 | us | |
Parameter | Flash size | Typ | Max | Unit |
Erase time, for first 25 cycles | 16 kB | 25 | 50 | ms |
64 kB | 30 | 55 | ms | |
Parameter | Flash size | Typ | Max | Unit |
Erase time, at 50K cycles |
16 kB | 110 | 4000 | ms |
64 kB | 120 | 4000 | ms | |
Control Subsystem Flash parameters at 150MHz | ||||
Parameter | Flash size | Typ | Max | Unit |
Program time | 16 kB | 95 | 190 | ms |
64 kB | 380 | 760 | ms | |
128 data bits + 16 ECC bits |
40 | 300 | us | |
Parameter | Flash size | Typ | Max | Unit |
Erase time, for first 25 cycles | 16 kB | 25 | 50 | ms |
64 kB | 30 | 55 | ms | |
Parameter | Flash size | Typ | Max | Unit |
Erase time, at 50K cycles |
16 kB | 105 | 4000 | ms |
64 kB | 110 | 4000 | ms |
Thanks and regards,
Vamsi/Adam H