• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 30 subscribers
  • Views 611 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.

Original question:

TMS570LS1114: OTP memory of the Flash Banks 0 and 7

TMS570LS1114: TMS570LS1114 OTP Flash

Bernhard_87
Prodigy 160 points
Part Number: TMS570LS1114

Hello,
the first two questions are not answered. The TMS570LS1114 does not have a flash bank 1. Also I can not use it.
1) Is there any other double usage of the customer OTP memory?

2) Can we use the OTP ranges 0xF000_0010 - 0xF000_0FFF and 0xF000_E000 - 0xF000_E7FF without further restrictions?

3) Is there an overwrite possible? Can a second write access clear further bits of the OTP memory?
I think the answer is no. How is the protection implemented?
3a ) Is every byte protected against further writes?
3b ) Is the protection against further writes for each bank width (144 bit) or flash sector?

  • 0
    TI__Guru**** 197036 points
    Hello,

    The customer OTP is one time program only. Once a bit in the OTP sector is programmed to "0" it cannot be erase anymore . The size of customer OTP on LS1114 is 4k. You should only store data, not your application program. If you write to the customer OTP, make sure you do not unintentionally write to the AJSM locations (0xF0000000-0xF000000F) or you will lock the part. You can write data starting at address 0xF0000010.

    1. You can use the customer OTP to store any kind of data ( permanent data).
    2. The CUSTOM_OTP can only be programmed 1 time.
    3. It is possible to overwrite the existing data in customer OTP. You can flip the bit of "1" to "0", but it is impossible to flip bit of "0" back to "1". For example, if the content of the OTP is 0xFFFF_0000. You can change it to 0xFF00_0000, but you can not change it to 0xFFFF_FFFF.

    No, we don't have protection to block the writing operation to the flash sectors.