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

TMS570LS1224: Reading OTP with Uniflash v3.4.0

Erik Wolf
Prodigy 60 points
Part Number: TMS570LS1224
Other Parts Discussed in Thread: UNIFLASH

Hi,

For an embedded project I want to use the Customer OTP area to configure some device specific data.

To collect some experiences with usage of Uniflash and OTP I was trying to dump the OTP area and noticed that the content is not 0xFF overall, like expected.

See the dump screenshot (total address offset is 0xF0000000)

I understand the pattern in the address-range 0xF0000000 - 0xF0000010 which contains the AJSM key.

But why are some bits in the following memory read as zero?

I also dumped the memory from different evaluation kits which all give the same pattern (see above). I also tried to flash these memory addresses and it seems that the corresponding bits can be set/reset correctly. But how can I determine if the otp area was not written before when the default value is not 0xFF?

  • 0
    TI__Guru 72500 points
    It appears that the application code in your device has enabled flash ECC. The OTP section (except for the AJSM key) does not have ECC programmed. Therefore you get some addresses that the blank (0xFF) ECC bits decode to a single bit error and invert one of the data bits. Disable ECC and you will see the OTP memory behave as you expect.