• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 82 subscribers
  • Views 404 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Flash endurance for f28335

Afshin Poraria
Prodigy 20 points

Other Parts Discussed in Thread: TMS320F28335

HI All;

I am using a tms320f28335.  I have always tried to size my code and data properly such that I use the on board flash and boot loader to transfer the code to the RAM at power up and run it in the after.

Now I may need to expand a bit and may need to run part of a code in the flash. I am planning to make sure all variables are moved to RAM at the boot up, and only program code and constants are in the flash.

Beside the drop in speed, I am not clear on how many times I can access the flash safely.   

In worse case, if I locate a variable in flash, does it mean that every time that variable is taking a new value, I am doing a erase / write (which is my understanding)?

Looking at the data sheet (SPRS439M, section 6.17) under "Flash Timing" I see a 50,000 write/erase cycle, this only cover a few seconds of my code execution.

Hope some of you can shed some light on this.

Cheers

Afshin

  • 0
    Guru 192875 points

    Hi Afshin,

    In worse case, if I locate a variable in flash, does it mean that every time that variable is taking a new value, I am doing a erase / write (which is my understanding)?

    You don't have to worry for that, 50,000 write/erase cycles are for physical write/erase conditions ie programing or erasing the sector and not the real-time running conditions.

    Regards,

    Gautam