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.

TMS320F280049: Device actions when re-programming OPT memory in F280049

Part Number: TMS320F280049


Hi expert,

We'd like to determine if there are any risk when reprogramming OPT memory in F280049.

Question one: If I program some OTP sector which already being programmed, will the successive erase or program action been neglected? Any harm to the device?

Question two: When designing bootloader, should we avoid programming OPT twice or just let it go? Any suggestions?

Thanks

Sheldon

  • Hi expert,

    Any update on this?

    Thanks

  • Sheldon,

    The Flash API will block any erase attempt based on the address range given.  I'm not sure if the API would return an error if it was passed an OTP address to erase.

    For programming, the API will read the location to be programmed and if the bits are already programmed it will not attempt to "re-program" them.  This is true for both the main array and OTP array.  So there is no risk in doing what you have mentioned.

    Let me know if this addresses all your concerns.

    Best,

    Matthew

  • Hi Matthew,

     Could you help me check if the API would return an error if it was passed an OTP address to erase? This may related to design a customer bootloader program.

    Thanks

    Sheldon

  • Sheldon,

    Regarding erase: F280049 Flash API does not return an error when the OTP address is passed for erase.

    Regarding program: Adding to what Matt mentioned, please note that F280049 OTP also has ECC (every aligned 64-bits have 8-bit ECC). Once you program ECC, you can not re-program the corresponding 64-bit OTP locations again (since OTP can not be erased). Only OTP locations that do not have ECC are link-pointers.

    Thanks and regards,
    Vamsi