LMK05318B: epr export

Hi Hailiang,

I can explain further here.

The .epr file is a "custom" file type that we created. It contains the EEPROM mapping of the desired register settings. We put in the datasheet that the epr file is not recommended because the epr file contents can technically change at any time. It is custom, so whatever we (TI/LMK05318B team) want to change it, we technically could. Of course, we do not plan to suddenly change this file since users have been using it to send to their contract manufacturer for EEPROM programming.

On the other hand, the register programming sequences cannot be changed because it is simply a list of registers to write in a sequentially order. There is nothing unique about this file type. The register or EEPROM programming sequences are also easier to understand. The epr file also requires use of the "SRAM Direct Writes" method to program the EEPROM. If the user uses a register sequence instead, then the user can use either the "REGCOMMIT" method or the "SRAM Direct Writes" to program the EEPROM.

Let me know if something is still not clear!

Regards,

Jennifer

Hi Hailiang,

"Export EEPROM Map" --> exports an .epr file which is the SRAM/EEPROM mapping (from register settings of current tcs into EEPROM space). It is not possible to select any other format besides .epr file.

"Export EEPROM Instructions" --> exports a .txt file containing the register sequence for EEPROM programming.

I recommend the customer use the register dump from "Export EEPROM Instructions".

Regards,

Jennifer

Hi Hailiang,

Yes, it is OK to use the .epr file. We have kept the .epr file format because of previous customer requests--their contract manufacturers require the .epr for their programming flow.

Regards,

Jennifer