TMS320F2800137: Flash Write and Erase Secure Memory

Hi Liam,

Can you show your linker cmd file? Are the sections mapped to LS RAM or GS RAM for your example?

Thanks and regards,

Charles

Hi Charles,

Thank you for the reply. As far as I understand, this MCU has no GS RAM, so it's mapped to LS RAM. My flash functions are sorted in sections 32-34 in flash memory and loaded into LS1 RAM (which I have spilt into A and B in the linker file evenly) origin = 0x0000B000, length = 0x00000FF8

Hi Liam,

When Fapi_doVerify is performed, what address is passed for the verification? Is it the same as the previous program sequence?

Thanks and regards,

Charles

Hi Charles,

I can't confirm exactly due to the fact that the processor is locked during the flash write failure but when I insert unlock code after the write and verify commands the address is the same.

Many thanks,

Liam

Liam Queally said:

Fapi_issueProgrammingCommand returns a success but Fapi_doVerify return the generic error. If I unlock the zone prior to writing/erasing the flash write and erase functions work as expected.

Do you see code programmed in memory window? Also after programming command did you read the STATCMD register using Fapi_getFsmStatus(); to see any error?

What generic error you get for Fapi_doVerify?

Regards,

Rajeshwary

Hi Rajeshwary,

I can see my program memory when the device is unlocked, and I can see the memory be programmed if I write to flash while it is unlocked. Nothing is programmed if it is locked. The generic error is "Fapi_Error_Fail=500,             /* Generic Function Fail code */"
We do call Fapi_getFsmStatus(); but I have not checked what error it returns, I'll get back to you on that.

Many thanks,

Liam

Hi Liam,

Also, can you please check the content of poFlashStatusWord after it fails to verify, this is one of the argument for Fapi_doVerify()?

Regards,

Rajeshwary

Hi Rajeshwary,

This is the contents of poFlashStatusWord.

Fapi_getFsmStatus returns 81

Many thanks,

Liam

Hi Liam,

Taken from the Flash API User Guide:

Are you calling this function before writing to the sector to set up the write protection mask?

Thanks and regards,

Charles

Hi Liam,

Liam Queally said:

Fapi_getFsmStatus returns 81

This indicates your program command is failing due to Write/Erase protection violation. Please refer to flash API user guide for more details.

Hi Charles,

Yes, I do call those functions.

As I said, the code can write and erase just fine when the MCU is unlocked.

Is there perhaps protections on these functions when the MCU is locked? Or do they need to be called differently?

Many thanks,

Liam

Hi Liam,

Are these protections for the same Zone? Is it writing to another Zone?

Thanks and regards,

Charles

Hi Charles,

Only zones 1 and 2 are protected. I am trying to write to zone 55 with my test function.

Everything is identical when I am trying to write. I just add a line of code that unlocks or locks the processor between my test cases.

Many thanks,

Liam

Could you check the value of FLSEM.SEM before the flash API functions fail?

--Luke