• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 82 subscribers
  • Views 279 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.

TMS320F28377S: Question about FLASH API

Julia Li
Expert 4755 points

Part Number: TMS320F28377S

Tool/software:

Hi Champs,

Could you please help to answer questions? Thanks!

1. Do we have the benchmark of the execution time of these below functions?

Fapi_InitializeAPI (); Fapi_setActiveFlashBank()； Fapi_issueAsyncCommandWithAddress()； Fapi_checkFsmForReady() ； Fapi_getFsmStatus()

2. If meet "DUT fails Erase" in the process, do it need to start over from Start? Or is it starting from somewhere else?

Best regards,

Julia

  • 0
    TI__Expert 6000 points

    Hi Julia,

    We don't have standard benchmark of the execution time of these functions. However all this functions are non-blocking, it just issues command or read/write data to the flash registers and return status.

    The user application must wait for the FMC to complete the Erase/Program operation. Also time may vary depend upon number write/erase cycles. You can refer datasheet for this timings.

    Thanks & Regards,

    Rajeshwary

  • +1 in reply to Rajeshwary Nitin Bongirwar
    TI__Expert 6000 points

    Hi Julia,

     If meet "DUT fails Erase" in the process, do it need to start over from Start?

    -> Also, for F2837xS devices, since there are two FMCs for a single core, Fapi_InitializeAPI (); Fapi_setActiveFlashBank() functions must also be called whenever the target bank (Bank0 or Bank1) is changed. Otherwise you can flow from Fapi_issueAsyncCommandWithAddress(), if it meets "DUT fails erase".

    Regards,

    Rajeshwary