• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 31 subscribers
  • Views 1038 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.

How to check for ECC Errors using F021 Flash API Fapi_doVerifyByByte

Pashan None
Genius 5660 points

Hello Support,

At the end of Fapi_issueProgrammingCommand() with Fapi_AutoEccGeneration,

I want to perform ECC failure Check along with DATA Verify using Fapi_doVerifyByByte().
I don't see any parameter in Fapi_doVerifyByByte() to select ECC Check along with DATA Verify similar to
Fapi_FlashProgrammingCommandTypeoMode
as used in  Fapi_issueProgrammingCommand().

Please help.
Thank you.
Regards
Pashan

  • 0
    TI__Guru**** 196776 points

    Hi Pashan,

    I have forwarded your question to our F021 API developer. he will contact with you soon.

    Regards,

    QJ

  • 0
    TI__Genius 9015 points

    Hi Pashan,

    There is no switch.  The method for programming in the FMC is based on loading registers with the data and ECC using only the data address and then issuing a programming command.  This allows us to have the capability of programming Data Only, ECC only, or Data and ECC (either supplied or Auto generated).  For reading (or verifying) the data from Flash, however, you must use the correct memory mapped address where data lies in one address range and ECC lives in another.

    To do what you want, you would need to loop over data range using Fapi_CalculateEcc() for each 64bits of data and either saving the results into a temporary buffer or using the single byte result, issuing a Fapi_doVerifyByByte() with the appropriate parameters.

    I can see a valid use case for what you are trying to do and as such, I am entering an enhancement request into our system to implement such a feature (it would be a new function instead of adding to Fapi_doVerify() due to the high amount of overhead needed to implement this) in a future release of the API.