• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 880 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.

RM57L843: F021 Flash API, erase sector or block with ECC

Gunter Schmer
Genius 14212 points
Part Number: RM57L843

Hi,

I had a conceptual question: Using the SPNU501H doc and chapter 5 recommended flows for write and erase, I can see that on the write side usage of Fapi_issueProgrammingCommand() allows the use of a mode argument to make sure ECC is auto generated.

Could you confirm that the same is true for the usage of Fapi_issueAsyncCommandWithAddress() for a sector or bank erase, that the ECC is autogenerated for the erased 0xFF's and written into the ECC range, so that the ESM is happy? i think this is the case. Does the Fapi_enableAutoEccCalculation() need to be enabled for this?

Thanks,

--Gunter

  • 0
    TI__Genius 14212 points
    Hi,

    another side question to this is how to deal with the ESM ECC detection for the flash, whether it needs to be disabled during Flash writes and Flash erase. Again the assumption is that a bootloader using the F021 Flash APIs is in use for writes and erases.


    Regards,
    --Gunter
  • 0
    TI__Guru 72500 points
    ECC is not calculated or programmed during an erase operation. After an erase operation the ECC values are FF.
  • 0 in reply to Gunter Schmer
    TI__Guru 72500 points

    On this R5 based device, ECC is enabled by default. Programming and erasing is done by a state machine and can be done on Flash memory without the ECC being programmed. The two issues that come up are memory holes at the end of cache line fills and trying to do blank checks. To avoid getting an ECC error when the cache controller grabs a line that is only partially full of data or code, in the link command file, use a fill for each section, or replace the "align(32)" with "palign(32)" so that ECC is generated for all 32 bytes in the cache line.

    SECTIONS
{
/* USER CODE BEGIN (5) */
    .intvecs : {} > VECTORS
    .text   palign(32) : {} > FLASH0 | FLASH1
    .const  palign(32) : {} > FLASH0 | FLASH1
    .cinit  palign(32) : {} > FLASH0 | FLASH1
    .pinit  palign(32) : {} > FLASH0 | FLASH1
    .bss     : {} > RAM
    .data    : {} > RAM
    .sysmem  : {} > RAM
#if 0
/* USER CODE END */
    .intvecs : {} > VECTORS
    .text   align(32) : {} > FLASH0 | FLASH1
    .const  align(32) : {} > FLASH0 | FLASH1
    .cinit  align(32) : {} > FLASH0 | FLASH1
    .pinit  align(32) : {} > FLASH0 | FLASH1
    .bss     : {} > RAM
    .data    : {} > RAM
    .sysmem  : {} > RAM
	

/* USER CODE BEGIN (6) */
#endif

    The flash API function for blank check uses a special test mode to verify that the data and ECC bits are all FF.