• State
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 93 views
  • Users 0 members are here
Support feedback
Options
Options
Related

MSPM33-SDK: State of emulated EEPROM sector

Sebastien Le Diouris
Prodigy 190 points

Part Number: MSPM33-SDK
Other Parts Discussed in Thread: MSPM33C321A

Hello,

I am working on MSPM33C321A and I use the EEPROM memory (emulated).

The EEPROM memory is composed by 16 sectors of 2KB

I would like to know if it is possible to know if a sector is nok without read or write inside ?

Thanks

 

  • 0
    TI__Prodigy 310 points

    Hi Sebastien Le Diouris,

    Regarding your question about checking if an emulated EEPROM sector on the MSPM33C321A is bad (nok) without performing a read or write operation:
    Strictly speaking, it is not possible to know if a physical Flash sector is bad without any read or write access. A Flash memory failure (such as degradation of the floating gate or endurance exhaustion) can only be detected when the hardware attempts to interact with it—either through an erase/write failure status flag or a read-time ECC error.
    Best Regards,
    Ella Tang
  • 0
    Prodigy 190 points

    Hello Ella,

    thanks for your answer, juste could you tell me how to test the flag of read ECC error ?

    Thanks

  • 0 in reply to Sebastien Le Diouris
    TI__Prodigy 310 points

    Hi Sebastien Le Diouris,

    1. During Erase / Write Phase 
    • If a sector is physically damaged (e.g., endurance limit reached, charge trap failure), the Flash operation will fail or timeout.
    • For example, when use erase / write function, they can return the status of the current command, which can also be got from DL_FlashCTL_getCommandStatus() function.
    • DL_FlashCTL_getFailureStatus() function can return the type of command failure. If it returns DL_FLASHCTL_FAIL_TYPE_VERIFY_ERROR , it means the hardware verification failed right after the write/erase, which strongly indicates a NOK sector.

    2. During Read Phase 

    If the data inside a sector is corrupted due to bit flips, reading it will trigger the hardware ECC DED (Double-Bit Error Detection) and enter NMI_Handler. We have an example in M33 SDK, which can be taken as a reference. 

    examples/nortos/LP_MSPM33C321A/driverlib/flashctl_ecc_error_injection

    Hope this can help you. Thanks!
    Best Regards.
    Ella Tang