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.

BQ35100EVM-795: BQ35100 usage question

Part Number: BQ35100EVM-795
Other Parts Discussed in Thread: BQ35100, BQSTUDIO

Hello,

   My Application uses the Primary cell  Battery (LISOCI2 ) and just started exploring the capabilities of BQ35100, Could you please clarify below questions?

  1. We are thinking of using this IC in EOS mode, Do the IC BQ35100 need to be programmed using BQ STUDIO prior to usage? the Is there any other way to program the BQ35100 IC ?
  2. I am trying to read the CONTROL STATUS using the below sequence of I2C transactions, seems like it is not working, it is returning 0x8020 for CONTROL STATUS, and also returning the same value for reading CHEM ID.

please let me know what I am missing.

a. Writing the CONTROL REGISTER SUB COMMAND(CONTROL_STATUS)                               START, 0xaa,0x00,0x00,xx00,STOP , wait 2ms

b. Reading - START,0xaa,00,START,AB,<READ TWO BYTES>,STOP.

 

c. Writing the CONTROL REGISTER SUB COMMAND(CHEM ID)                               START, 0xaa,0x00,0x06,xx00,STOP , wait 2ms

d. Reading - START,0xaa,00,START,AB,<READ TWO BYTES>,STOP.

 

3. Also Please let me know if you have any driver source code for this IC.

Thanks,

Naga.

  • Hi Naga,

    There is an example of writing to data flash in the BQ35100 TRM (see Chapter 12). It is easiest to start with BQStudio if you are unfamiliar with how to write to data flash. For data flash writes, you also need to include checksum and length (to 0x60 and 0x61).

    Here is a thread where I explained how to write to data flash earlier today (example for a different device):https://e2e.ti.com/support/power-management/f/196/t/939805

    TI does not have a driver to offer for this device. If you search for "BQ35100 driver" on Google, you will see that some drivers have been written by other users.

    Best regards,

    Matt

  • Hi Matt,

      Thanks for the reply, you did not answer my 1st question.

    1. Do we have to program each BQ35100 IC with the CHEM ID or any other data using BQ STUDIO? or can we avoid it.

    2.   Can we directly use the IC in EOS mode (OPERATING CONFIG-A -GMSEL=2) by skipping the above step?

    3.  It seems like the EOS ALERT bit will set when the IMPEDANCE reaching alarm Level, but how can I  tell if the Battery is about 50% capacity ?

     4. You have provided me the I2C transaction example about reading DATA FLASH, but I am talking about COMMAND STATUS (sub command =0x000),

         COMMAND STATUS read also require the same method that of DF(Data flash) handling? Please clarify.

  • Any updates here?

  • Hello Naga,

    1. You will need to program each IC per the user's guide.

    2. No

    3. It is difficult, EOS is meant for end of service.

    4. No, i2c commands are sent to control. The TRM has a section on the direct memory access, I will refer you to the tech reference manual on accessing data memory.

    Thanks!