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

CCS/TM4C129ENCPDT: Uniflash and EEPROM

Darren Jenkins
Genius 12471 points
Part Number: TM4C129ENCPDT
Other Parts Discussed in Thread: UNIFLASH

Tool/software: Code Composer Studio

This is a question related to TM4C129 and Uniflash.

We have a customer working with TM4C129, programming their devices using Uniflash.  It looks like there is some different behaviour coming from a small minority of parts.  Those parts were recovered by programming them with LM Flash Programmer and an older image of their code.

There are a few variables here, and they are working on isolating each one, but it would help to understand a couple things about Uniflash.  Does Uniflash modify the EEPROM contents?  What is the default action on the EEPROM?  Do you know if this is handled differently with LM Flash programmer?

The only other memory I can think of is the Battery Backed Hibernate Module. Is this memory written-to by the programmer?

Thanks,
Darren

  • 0
    TI__Guru**** 191296 points

    Hi Darren,

      The Uniflash can not erase the EEprom. The hibernate memory is not a non-volatile memory but rather powered by the presence of the battery or VDD. You will need to call the TivaWare API as part of your application to write/read the EEprom.