• State TI Thinks Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 64 subscribers
  • Views 235 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.

Original question:

BQ27Z561-R2: DATA FLASH WRITE IS NOT WORKING

BQ27Z561EVM-011: How to decode the I2C message

chad pham
Prodigy 145 points
Part Number: BQ27Z561EVM-011
Other Parts Discussed in Thread: BQSTUDIO, BQ27Z561

Tool/software:

HI all,

These are the data capture I2C comm between my bqStudio and BQ27Z561EVM-011

write to 0x55 ack data:0x3E 0x80 0x44 0x08 0x08 0x00 0x10 0x00 0xA0 0x0F 0x3C 0x0F 0xAC 0x0D 0x48 0x0D 0x3C 0x37 0x00 0x05 0x01 0x07 0xF0 0x0A 0x0F 0x00 0x05 0x14 0x01 0x0A 0x00 0x0C 0xFE
write to 0x55 ack data: 0x60 0x5C 0x22
write to 0x55 ack data: 0x3E 0x9E 0x44 0x32 0x10
write to 0x55 ack data: 0x60 0xDB 0x06
write to 0x55 ack data: 0x3E 0x80 0x44
write to 0x55 ack data: 0x3E
read to 0x55 ack data: 0x80 0x44 0x08 0x08 0x00 0x10 0x00 0xA0 0x0F 0x3C 0x0F 0xAC 0x0D 0x48 0x0D 0x3C 0x37 0x00 0x05 0x01 0x07 0xF0 0x0A 0x0F 0x00 0x05 0x14 0x01 0x0A 0x00 0x0C 0xFE 0x32 0x10 0x1A 0x24
write to 0x55 ack data: 0x3E 0xA0 0x44 0x27 0x25 0x00 0x74 0x0E 0x5A 0x0A 0x8C 0x0C 0x8C 0x48 0x0D 0xAC 0x0D 0x00 0x05 0x04 0x10 0xA0 0x0F 0x64 0x5F 0x48 0x0D 0xAC 0x0D 0x06 0x08 0x04 0x10
write to 0x55 ack data: 0x60 0xFC 0x22
write to 0x55 ack data: 0x3E 0xBE 0x44 0xA0 0x0F
write to 0x55 ack data: 0x60 0x4E 0x06
write to 0x55 ack data: 0x3E 0xA0 0x44
write to 0x55 ack data: 0x3E
read to 0x55 ack data: 0xA0 0x44 0x27 0x25 0x00 0x74 0x0E 0x5A 0x0A 0x8C 0x0C 0x8C 0x48 0x0D 0xAC 0x0D 0x00 0x05 0x04 0x10 0xA0 0x0F 0x64 0x5F 0x48 0x0D 0xAC 0x0D 0x06 0x08 0x04 0x10 0xA0 0x0F 0x4D 0x24

I am looking for some document or app note to explain the data packages for I2C communications between bqStudio and BQ27Z561EVM. 

I try to learn from these communication in order to set up my BQ27Z56 from my own MCU.

I understood standard command vs. alt commands.  I understood 0x3E,

But I don't understand where 0x80 0x44, 0x9E 0x44, 0xBE 0x44, 0xA0 0x44

  • 0
    TI__Mastermind 26395 points

    Hello Chad,

    This question has been assigned and will be followed up when possible.

    Thank you,
    Alan

  • 0 in reply to Alan Frias
    TI__Mastermind 24931 points

    Hello, 

    These are just the I2C addresses. 

    Regards, 

    Jonny. 

  • 0 in reply to Jonny
    Prodigy 145 points

    Jonny,

    You must be kidding right? Are these bytes 0x80 0x44, 0x9E 0x44, 0xBE 0x44, 0xA0 0x44 are I2C addresses?

  • 0 in reply to Jonny
    Prodigy 145 points

    Jonny,

    Can you elaborate on the I2C addresses? You meant bqStudio sent out these bytes to see if other device is on the bus?

  • 0 in reply to chad pham
    TI__Mastermind 24931 points

    Hello, 

    These are I2C addresses for reserved parameters, these bytes are sent to the gauge. 

    Regards, 

    Jonny. 

  • 0 in reply to Jonny
    Prodigy 145 points

    Hi Jonny,

    When you said I2C addresses, you meant the Register addresses?

    These capture data only specific when I did the Gas Gauge update to Design Capacity to 10000mAh.  Can you please help me to point it out for me in which block (32 bytes) writing is the one?

  • 0 in reply to chad pham
    TI__Mastermind 24931 points

    Hello, 

    Yes, these are the Register addresses. These parameters that are being written to are internal gauging parameters so I cannot describe exactly what is being written here. This is why you do not see these addresses present in the documentation. 

    If you are trying to use a host MCU to write to the gauge, the recommended process is to use BQStudio to obtain a golden image (in the form of either a gm.fs file or a bq.fs file), then have your host MCU mimic these read compare, delay, and write commands to successfully write all of the necessary information to other gauges. These golden images will have all of the information you should need, and there is no need to write other values other than what is in the golden image. 

    Regards, 

    Jonny. 

  • 0 in reply to Jonny
    Prodigy 145 points

    Dear Jonny,

    Thank you for your helps.  I got the Golden Image files now.

    May I confirm if I just want to mimic my BQ27z561 GG, I can just follow the gm.fs correct?  I compare 2 files gm.fs vs. bq.fs, the bq.fs has major additional commands compare to gm.fs file.

    Second question, even though I set my battery Design Capacity is 10000mA but bqStudio only show "Full Charge Capacity" is 9465 mAh.  the missing 535 mAh is from my GG settings configuration or from the GG internally just cap at the margin that GG comfortable with?

  • 0 in reply to chad pham
    TI__Mastermind 24931 points

    Hello, 

    The gm.fs file is just the data flash data whereas the bq.fs file is the data flash AND the FW. 

    The FCC is the full charge capacity, and is essentially the usable capacity for your particular application. The design capacity specd by the cell manufacturer is the total capacity if you charge to the voltage in the cell datasheet with the charge profile listed in the cell datasheet, and if you discharge to the term voltage listed in the cell datasheet. If you have a higher terminate voltage or a lower charge voltage than what is listed in the cell datasheet, then the FCC will be lower than the design capacity. This is expected. 

    Qmax is more comparable to design capacity than FCC is (there will likely be some variation still depending on the cell variation and age, but comparable nonetheless). 

    Regards, 

    Jonny.