• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 32 subscribers
  • Views 124 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.

TMS570LC4357: FAPI_issueProgrammingCommandForEccAddresses() error causes random subsequent Flash programming errors

Cameron Fruit
Prodigy 55 points
Part Number: TMS570LC4357


Tool/software:

After invoking Fapi_issueProgrammingCommandForEccAddresses with invalid ECC values, the write to Flash fails and when the FSM returns to Ready state the bits 4 (INVDAT) and 5 (CSTAT) of the FMSTAT register are set. I can clear bits 4 and 5 by calling Fapi_issueAsyncCommand(Fapi_ClearStatus) and continue. My problem is that unless I cycle power after the invalid data failure, subsequent writes of valid data (using Fapi_issueProgrammingCommand) succeed only a seemingly random number of times at which the commanded data is not written to Flash. The failure does not seem to relate to the specific address that is written. If I cycle power I have consistent success writing valid data to Flash.

Any idea why this would occur? And is there a step I'm missing to restore consistent Flash programming operations?

Thanks,

Cameron

  • 0
    TI__Guru 74466 points

    Hi Cameron,

    The provided technical documents indicate that the INVDAT (Invalid Data) and CSTAT (Command Status) flags in the Flash Module Status Register (FMSTAT) are set upon specific flash programming failures. Both flags are documented to be cleared by issuing a "Clear Status command". The documents do not explain why subsequent flash programming would be unreliable after these flags are cleared, nor do they specify any additional recovery steps beyond this command.

    Is it possible to share your code for quick debugging of this issue further?

    --
    Thanks & regards,
    Jagadish.