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.

EEPROM example Program by DK-TM4C123G EVB

Other Parts Discussed in Thread: EK-TM4C1294XL, TM4C123GH6PGE

Hello

i'm  using  EVB-Kit (DK-TM4C123G)

I need EEPROM Read/Write Example program  created  by  Keil Project

thanks

  • Hello Jame,

    Unfortunately, I don't see such a demo/example code available in TivaWare for either CCS or Keil tools. However, there is some discussion and reference code offered in this thread: e2e.ti.com/.../385512
  • Jame,

    A collegue pointed out that you may also be referring to the internal EEPROM on the TM4C123 device. If this is the case and it isn't the external EEPROM on the DK as I previously assumed, then you can reference the code used for the ek-TM4C1294XL board default project, qs_iot, provided in TivaWare. This code writes data to the on-chip EEPROM when a connection is established with the Exosite Server. This should provide some guidance on how to interface with the on-chip EEPROM.
  • Chuck.

    I want to Use internal EEPROM 2KB(512 x 32bit) Built in TM4C123GH6PGE Device of DK-TM4C123G EVBKIT

    I need EEPROM Read/Write Example program  created  by  Keil Project

    because  Keil scatter File not know the configuration of the environment.

    Thanks

  • Read the errata before using the internal EE

    Robert
  • Please explain what you mean. ?
  • I mean read the errata sheet on the TM4C123. Paying particular attention to the EE errata. There are several quite severe errata.

    Robert
  • Hello Jame,

    As Amit mentions in your other thread on this same topic (e2e.ti.com/.../1876575

    "There is no explicit example in any of the tool chains. I would suggest first importing one of the known projects and then using EEPROMInit, EEPROMProgram and EEPROMRead API calls from the driver file as indicated by Chuck in the other post

    You can first create a basic project file, and I can help guide you through it,"

    Given Amit's extensive knowledge/experience with the device and the tools, I would highly recommend you take him up on his offer.

    And as Robert has mentioned, please do review the device errata for the EEPROM and for the device in it's entirety. This should be a normal part of any development effort as the errata documentation is a critical component of the device documentation and definition of device performance. If, upon review, you have any questions or concerns, please come back to the forum to ask questions so we can help you work through any risks or concerns of risk.