• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 21 subscribers
  • Views 103 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

LMK05318: EEPROM Programming

George Volokh
Prodigy 30 points
Part Number: LMK05318

Hi,

I need to program and verify EEPROM using my external equipment (not GUI).

In the GUI I see that I can generate a .txt Sequence EEPROM file (for programming) and Export EEPROM Map file.

But to my surprise the values in the Sequence and EEPROM Map files are different.

So, my questions:

1. Why are the values in the Sequence and EEPROM Map files different?

1. Does TI have EEPROM programming specification for this device where the programming/verification sequence is described?

2. How can I verify the programmed EEPROM memory?

Regards, George Volokh.

  • 0
    TI__Genius 12450 points

    George,

    The team is out of office for the US holiday, please expect a response by tomorrow.

    Thanks,

    Kadeem

  • 0 in reply to Kadeem Samuel
    TI__Genius 10225 points

    Hi George,

    • The sequence outlines the steps to program the register settings (that you configured in TICSPRO) into the device.
    • The .epr file is the EEPROM map that contains the details of how the registers are stored in EEPROM. This file is typically handed over to the contract manufacturer so they can program the EEPROM for you, if that is your use case.
    • Please note , we recommend using the LMK05318B as this is the latest silicon.
    • The EEPROM can be verified a few ways:
      • At every power-up, all of the non-status register settings get loaded from EEPROM. You can check the EEPROM is correct by probing the outputs.
      • When the EEPROM is successfully programmed, the NVMCNT (R156, EEPROM programming count) increments at the next power-up.
      • You can check for CRC failure. R157[5] should be clear as well as the stored and live CRC should be the same (R158 == R155) at the next power-up.
      • You can readback the EEPROM contents through the MEMADDR (R159-R160) and NVMDAT (R161) registers.
    • For additional programming guidelines, please refer to Section 9.5 of the datasheet.

    Regards,

    Jennifer

  • 0 in reply to Jennifer Bernal
    Prodigy 30 points

    Thanks, Jennifer for your explanation.

    But we need to be absolutely sure that the programming is done correctly, so only the last way seems to be okay for us.

    So, if I understood correctly, I need using TICSPRO:

    1. Export EEPROM Instruction for programming and do programing according to these instructions,

    2. Export EEPROM Map and make EEPROM verification according to this map file.

    Am I correct?

    According to this algorithm, the data for programming and reading/verifying should be different in the same addresses, correct?

    Thanks in advance.

    Regards, George.

  • 0 in reply to George Volokh
    TI__Genius 10225 points

    Hi George,

    My recommendation is to follow the steps used on "Step1" which uses the Register Commit method mentioned in Section 9.5.6.1 in the datasheet.

    "Step2" is used only for the SRAM Direct Write Method as seen in Section 9.5.6.2.

    I don't follow this question, can you please elaborate?

    • According to this algorithm, the data for programming and reading/verifying should be different in the same addresses, correct?

    The register-to-EEPROM mapping is not 1:1; however, the data written to the registers should be the same if you readback from the same register address.

    Regards,

    Jennifer