TMS320F28377D: Flash API F021 fails in secure mode

Hi Benjamin,

Can you explain more of what you are seeing? How do you know they example is not running from secure memory?

You need to ensure that the data you are trying to program is either in the same zone or unsecure memory, and the flash API is in the same zone you are trying to erase and program. If this is so, then the code should be able to erase and program the secure flash.

Regards,
sal

Hi Sal

I see that the flash is still on 0xFFFF instead on the test data (0x0001, 0x0002 ..) after unsecuring the device again. For that I uncommented the flash erasing part at the end of the example code.

My test procedure in detail:

1. setting boot mode to "Wait Boot Mode"

1. flashing of the example project

1. securing the device

1. boot mode to "Get Mode"

1. power cycle the board 1-2 to be sure that the example code runs through
2. boot mode to "Wait Boot Mode"
3. unsecuring the device

1. checking the flash via Memory Browser

If I skip step 3 and 7 (no securing and unsecuring of the device) the test data stays in the flash, else not.

As I understand the linker file of the example project the flash API is running in secured RAM (LS0-LS3) so the flashing of the secure flash should work.

Did I forget something else?

Thanks for your support, Benjamin

Hi Sal

I changed nothing at the example regarding the mapping. So far I understood the code everything is running in secured RAM.

The data the example code tries to program is at the beginning of the flash sector B (0x82000) and C (0x84000) which are secured via the Z1-GRABSECT setting.

Regards, Benjamin

Hi Sal,

No, you didn't understood me correctly!:)

I modified the example so that the data remains in sectors B and C. The example works if the device is not secured.

Shall I send you the example code?

BR Benjamin

Hi Vivek

Yes, I grab the Flash semaphore. Please see my first post.

Regards, Benjamin

Hi Sal and Vivek

I added a debug pin toggle at everey step into the code example. To make the example running more than once I activated the erasing of the sectors B and C at the end of the example again. The debug pin shows me that the code is running through until the end in both secured and unsecured mode. Please see the attached figure (be aware that the time resolutions are not the same for secured and unsecured mode!).

In the secured mode the erasing steps are faster than in unsecured mode. I think thats because the data of the whole flash bank is still on 0xFFFF in secured mode.

Have you any ideas why it is different?

Regards, Benjamin

FlashExample.pdf

Benjamin,

As suggested yesterday, can you confirm that the functions in the Fapi_UserDefinedFunctions.c file are assigned to .TI.ramfunc section (to copy to RAM at run time)? RAM should be of the same zone as that of the Flash sectors on which erase/program is targeted.

Thanks and regards,
Vamsi

Flash API wiki: http://processors.wiki.ti.com/index.php/C2000_Flash_FAQ#Flash_API_wiki

Hi Vamsi and Vivek

I'm sorry Vamsi, I haven't noticed your comment. I tested it again with following changes:

- copy API user functions to secure RAM
- read back of SEM field to check if it is on 0x1

The result is that the SEM field was still on 0.

However, although referring the documentation (spruhm8g) that is not needed I disabled the write protection (EALLOW) and that solved the problem!



So many thanks for your support and please correct this in the documentation and add this grabbing of the flash semaphore into the future releases of the flash example!

Best regards, Benjamin