• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 561 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.

TM4C129 EEPROM Errata Clarification

Matthew Kipper
Intellectual 460 points

Hey guys, I have a quick question regarding the MEM#12 item from the TM4C129 Silicon Errata. The specific item is shown below:

Does this apply to any jump from Flash to ROM execution, or only those where the ROM code is actually interacting with the EEPROM? The wording hints at the former, but I'd just like some confirmation that I'm not misunderstanding this.


Thanks,

  • 0
    TI__Guru**** 244400 points

    Hello Matthew,

    It is the latter, i.e. when a function in ROM is being called while EEPROM is actively writting or reading. This can be the case when doing a EEPROM Write or Read operation and an interrupt handler is called which has ROM_ function being used while the EEPROM operation is ongoing.

    Regards

    Amit

  • 0 in reply to Amit Ashara
    Intellectual 460 points

    Hey Amit,

    Thanks for the quick response!

    I think you might have misunderstood my question. I understand that ROM calls during EEPROM reads/writes might not return, but I wasn't sure if it was ALL ROM_ calls (e.g. ROM_SysCtlDelay()), or just those that actually deal with the EEPROM itself (e.g. ROM_EEPROMRead()). From the wording I feel like it is every single ROM call, but I'd just like to double-check before switching a chunk of my library calls from ROM to Flash in a project.

    Thanks again,

  • 0 in reply to Matthew Kipper
    TI__Guru**** 244400 points

    Hello Matthew

    Any ROM Call can cause the issue. Please do note that it is fixed in the revision-3 of the device

    Regards

    Amit