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.

TM4C123x Errata MEM#14 workaround(s)

Hi,

We need your help on TM4C123x Errata MEM#14, the errata document below
has a workaround but it would be helpful if there is more details.
www.tij.co.jp/.../spmz849f.pdf

I would appreciate it if you could please provide me example code or
the document that explains how to implement it. Especially the option
"Copy the Flash Program/Erase codeto SRAM and CPU executes the code from SRAM."

Best Regards,

  • Hello Matsumoto-san,

    Can you provide more details on the use case? i.e., is the application writing to program flash while also executing from flash? This is the only scenario where this errata would be of concern.
  • Hello Chuck-san,

    Thank you for your quick response.

    Yes. the customer is storing log data to flash memory instead of EEPROM.

    So as a workaround we need to know how to implement,
    "Copy the Flash Program/Erase code to SRAM and CPU executes the code from SRAM."
    Please let us know if there is any sample code on this.

    Best Regards,
  • Hello Matsumoto-san,

    Please review the boot loader example in TivaWare for a guideline on how to do this since it copies the bootloader code into SRAM for execution. The code islocated at C:\ti\TivaWare_C_Series-2.1.3.156\boot_loader if you have TivaWare installed in the default directory. I suspect a modification of the boot loader example would be able to perform the basic write and erase functionalities that they need by replacing the incoming data stream from one of the comm protocols with an internal function interface to the boot loader.