• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 63 subscribers
  • Views 226 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.

TPS23861: Will the software I2C continuous read operation (Burst read) lock the MSB/LSB?

Charlie Xiao
Expert 7495 points
Part Number: TPS23861
Other Parts Discussed in Thread: TPS23881

Hi Team,

The software continuously reads the current value between the LSB and MSB registers.

Will the software I2C continuous read operation (Burst read) lock the MSB/LSB?

The PSE chip is updating the current data. If the LSB is a value near 0xFx, the current fluctuation will cause the MSB to carry. Will it cause the read LSB and MSB data to be out of sync? Thanks.

Regards,

Charlie

  • 0
    TI__Intellectual 1520 points

    Good evening, Charlie,

    The LSB and MSB data are read at the same time, so they should not fall out of sync. For instance, in the example shown above, if the LSB, 30h, is pulled with two bytes, the MSB, 31h, will also be pulled at that same time. 

    Best Regards, 

    Nate Inkster

  • 0 in reply to Nate Inkster
    TI__Expert 7495 points

    Hi Nate,

    Thanks for your support. But my customer still raised questions:

    If I2C does not read data continuously, there must be a problem of MSB/LSB readings being out of sync.

    Please clarify whether the I2C continuous reading operation (Burst read) will lock the MSB/LSB, that is, when reading the LSB, the MSB value will not be updated until the MSB bit is read?
    PSE chip also includes TPS23881, please confirm together.

    Regards,

    Charlie

  • 0 in reply to Charlie Xiao
    TI__Intellectual 1520 points

    Hi Charlie,

    Thank you for the clarification. The LSB and MSB are tied together such that when the LSB is pulled to read, the MSB gets pulled right along with it, so there should be no issue with desynchronization. 

    Respectfully,

    Nate