• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 3 answers
  • Subscribers 22 subscribers
  • Views 621 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.

LMK03318: Programming - HEX reg value file from TICSpro, reserved bit, undocumented registers

Adam Polus
Prodigy 30 points

Part Number: LMK03318

HI Support,

1) Is "Export HEX register values" file generated by TICSpro the correct production programming file that should be used to program LMK03318 in production on virgin boards (using onboard I2C bus master for example processor)? Question is if LMK03318 will be FULLY programmed using this TICSpro output "Export HEX register values" file. LMK03318 is used in Soft Pin Mode - planning to use only one EEPROM page (one configuration).

2) It appears that "Export HEX register values" file generated by TICSpro has register addresses that aren't documented in datasheet. Do those need to be written and programmed into the device as well?

3) Datasheet indicates there are RESERVED bytes/registers and RESERVED bits within byte registers. Datasheet states: "Certain device registers and bits are reserved meaning that they must not be changed from their default reset state." Does this datasheet statement forces user to perform READ/MODIFY on RESERVED bytes/registers and registers with RESERVED bits within them? 

4) Datasheet states: "Certain device registers and bits are reserved meaning that they must not be changed from their default reset state." Does this datasheet statement indicates that "Export HEX register values" file generated by TICSpro ISN'T everything needed in production to program the device because programming tool / software need to know the location of the reserved bytes and bits to perform READ/MODIFIY?

Best regards,

Adam

  • 0
    TI__Mastermind 23280 points

    Adam,

    1. If only using a single EEPROM page, then the register file is all that is required. On startup, the registers can be written to the device, and the below steps can be followed:
    2. If using the register commit flow (the process documented above), please write all registers for programming.
    3. Reserved bits should not b changed. If a reserved bit is present in a register, the register must be read first in order to preserve the value of the reserved bits.
    4. Anything not included in the "Export Hex Register Values" is either unused or for internal purposes only. These do not need to be read/written for each device, only the register values provided in the output document. The mapping is provided in the EEPROM map in the datasheet.

    Thanks,

    Kadeem

  • 0 in reply to Kadeem Samuel
    Prodigy 30 points

    HI Kadeem, 

    Thank you for response. 

    How to deal with registers that ARE in the "Export Hex Register Values" file but AREN'T documented in datasheet? When registers AREN'T documented than it isn't know if there are reserved BITS in register bytes requiring the read/modify/write approach.

    Best regards, 

    Adam

  • 0 in reply to Adam Polus
    TI__Mastermind 23280 points

    Adam,

    Any registers that are in the "Export Hex Register Values" file but not in the datasheet should not be modified from their values. Those registers should be treated as "Reserved".

    Thanks,

    Kadeem

  • 0 in reply to Kadeem Samuel
    Prodigy 30 points

    Hi Kadeem, 

    Thank you but I am getting confused here. 

    1) Your response to question 2 in my initial post stated "If using the register commit flow (the process documented above), please write all registers for programming." - that I read to program ALL registers from the file to device. 

    Your recent response states to "not modify" the registers that aren't documented in datasheet - I read it as "dont write into undocumented 8bit registers".

    Now you suggest that I need to extract form datasheet RESERVED registers and RESERVED bits in registers and perform read/modify/write on those but further I need to prepare list of registers that your tool exports but aren't documented in datasheet and not write into those?

    2) Feels odd that this programming process based on "Export Hex Register Values" file isn't documented in the datasheet. 

    If I capture I2C transactions when TICSpro is performing "Write all registers" will I find the same read/modify/write on registers containing reserved fields and undocumented registers skipped (not written to) even though the TICSpro register map shows undocumented registers?

    3) We are planning to perform verification after programming - keen to compare against register values from "Export Hex Register Values" file. How to go about that? 

    best regards,

    Adam

  • 0 in reply to Adam Polus
    TI__Mastermind 23280 points

    Adam,

    Let me clarify. In the "Export Hex Register Values" file, the registers that are present here are mostly registers that are shown in the datasheet. You can see that there are some gaps here, such as between R145 and R169. These registers should be considered to be "Reserved".  Within an individual register, there are some fields that can be marked as "Reserved" as well.

    When programming a device, the registers not shown in the "Export Hex Register Values" document should not be changed. The "Reserved" fields in the registers that are in the "Export Hex Register Values" document are able to be changed without issues. For programming, the registers can be loaded into the device by importing the "Export Hex Register Values" document, and following the programming sequence listed above.

    For verification, readback and comparison of read/write fields is suitable.

    Thanks,

    Kadeem