TMS320F28388D: Flash API erase times

Hi Michael,

Can you clarify what exactly you're asking? The typical flash sector erase time can be found in the datasheet (7.10.4.1). 

Are you asking what can be done to reduce the time needed to call the Fapi_issueAsyncCommandWithAddress() function?

Kind regards,

Skyler

So according to the data sheet the command is aSync which shouldn't halt my program running and yet i have a disruption the program flow, my question is what's the Fapi_issueAsyncCommandWithAddress actual execution time and how it affects my main program after i run it.

Thanks,

Hi Michael,

Are you waiting for the erase operation to complete? For example, the following line is usually added in our examples after calling Fapi_issueAsyncCommandWithAddress.

//
// Wait until the erase operation is over
//
while (Fapi_checkFsmForReady() != Fapi_Status_FsmReady){}

For a real-time system with a cycle of 50 microseconds, you should not be waiting until the FSM is ready as shown above. When running the command on my setup, it only takes about 1.3 microseconds to complete the Fapi_issueAsyncCommandWithAddress function.

Kind regards,

Skyler

I don't wait at all i run the command "clean" what i mean is i run:
Fapi_issueAsyncCommandWithAddress(Fapi_EraseSector,(uint32_t *)FLASH_BANK_SELECT);

and yet the synchronization with the micro-controller fails for some time as if he's busy for a few milliseconds.

Hi Michael,

How are you performing this synchronization? Can you measure how many clock cycles it takes to run the Fapi command on your setup? You can view the CPU clock cycles in the bottom left corner after connecting CPU1 and selecting Run -> Clock -> Enable in CCS. You can set a break point right before the command, clear the cycle count by double-clicking the cycle count, and then running to the next line of code after the Fapi call. You should see that the command is not running on the ms scale.

Kind regards,

Skyler

Yes i did it before if im not mistaken the erase command took about 400~ clock cycles which is stranger regarding to the cause of my synchronization fault.

Hi Michael,

Okay, so it doesn't seem that the Fapi command is the cause of the timing fault. Is there something occurring after the Fapi command that could be causing this issue? Additionally, are you running the Fapi command from flash or RAM?

Kind regards,

Skyler

From RAM,when i track it i can see its the only command that its execution causes it, maybe its related to the micro controller usage %.

Hi Michael,

Can you confirm that the function calling the flash API function is also running from RAM? There may be some other flash operation (read) occurring in the background.

Kind regards,

Skyler

I will double check it to be sure and i'll write here

Hi Michael,

Okay, please let me know what you find.

-Skyler