• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 62 subscribers
  • Views 335 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.

BQ78350-R2-DEVICE-FW: Has the format for LifetimeDataBlock5() changed with R2 firmware?

Phil Reid
Prodigy 210 points
Part Number: BQ78350-R2-DEVICE-FW
Other Parts Discussed in Thread: BQSTUDIO

I'm trying to decode the data from LifetimeDataBlock5() 0x0064 and I think it has change from R1 to R2.

SLUUBD2D Sept 2015 shows 14 bytes returned.

But I now get 18 bytes returned running R2. The TRM Addendum for R2 does not show any changes for this command.

However the bqStudio Lifetimes, Time block shows 18 bytes for R2.

However the 0x0064  also seems to be return teh data in big endian, not little endian.

Or there is some other padding going on.

Any help appreciated.

Phil

  • 0
    TI__Guru* 81035 points

    Hi Phil,

    You are correct - LifetimeDataBlock5() did change from R1 to R2 to adjust to the new temperature ranges in R2. The Addendum document does not describe this.

    Best regards,

    Matt

  • 0 in reply to Matt Sunna
    Prodigy 210 points

    G'day Matt,

    Yes thought as much. However the data format from the LifetimeDataBlock5() 0x0064 still doesn't look right if it's supposed to be Little Endian. 

    Here's an image of the returned array dumped in a debugger. Which looks to be Big Endian.

    Versus what read from the Data Memory (After a LT flush to write RAM to Flash)

    All other data returns as Little Endian, so I just want to confirm this is a bug in the R2 firmware and it's in Big Endian, and not that there's an extra byte at the start that means something else or some other weirdness.

  • 0 in reply to Phil Reid
    TI__Guru* 81035 points

    Hi Phil,

    I do not think the byte order has changed on this command from R1 to R2. Have you confirmed it is Little Endian in the other LifetimeDataBlock commands? 

    I had another user report that some commands actually return data in Big Endian format.

    Matt

  • 0 in reply to Matt Sunna
    Prodigy 210 points

    G'day Matt,

    Section 18.2.1 / 18.2.2 of the TRM says it's Little Endian.

    And 10.2.5 doesn't indicates the previous block was LE based on that.

    I guess I'll find out in ~500 hrs when the count rolls over to use the MSB.

  • +1 in reply to Phil Reid
    TI__Guru* 81035 points

    Hi Phil,

    I confirmed the LifetimeDataBlock Times are reported in Big Endian on my board and I found an older E2E post that confirms these times have always been reported in Big Endian format. I will note this for the next revision of the TRM.

    Thanks for catching this,

    Matt