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.

TMS320F2812: What is the flash erase time of F2812?

Part Number: TMS320F2812

Hi team,

I am trying to confirm the flash erase time fo F2812.

In datasheet it is rated longer than 10s for each sector, but it does not seems that long in practice.

Just want to make sure I am understanding this parameter correctly. Assuming I am trying to erase 128K flash, it would take ~80s?

Regards,

Brian

 

  • Hi Brian,

    It is possible to have flash sectors take 10-11s, or even longer, which is why the typical parameter is what it is in the datasheet. However, most devices will have sector erase times less than 11s.

    When implementing a flash erase timeout within an application we recommend having it be at least 11s long per sector to accommodate all possible situations.

    You can find more information on F05 flash at the FAQ: https://e2e.ti.com/support/microcontrollers/c2000/f/171/t/757585/

    Best,

    Kevin

  • Hi Kevin,

    Thanks for the reply. According to my understanding, ~10s erase time is a typical parameter that guarantees a reliable flash erase for most devices even after multiple flash erases. But under most conditions, we could see shorter erase time.

    Another thing I would like to know is whether the erase time is related to SYSCLK? Since the 150Mhz specific frequency has been noted in the datasheet, could you please tell what is the relationship between SYSCLK and erase time?

    Regards,

    Brian

  • Hi Brian,

    Brian Wang0 said:
    Another thing I would like to know is whether the erase time is related to SYSCLK? Since the 150Mhz specific frequency has been noted in the datasheet, could you please tell what is the relationship between SYSCLK and erase time?

    Yes it is related. There are several software delays implemented into the Flash API functions that are vital to its operation and dependent on the clock frequency. You can find more information on the delays and CPU clocking in the F281x Flash API guide within the download below:

    http://www.ti.com/tool/SPRC125

    You should execute the Flash API algorithms at the highest CPU frequency possible within the system.

    Best,

    Kevin