• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 65 subscribers
  • Views 332 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.

BQ34110: Initialization time (INITCOMP flag)

Pial
Expert 7280 points
Part Number: BQ34110

Dear team,

My customer have a concern in programming BQ34110 in the production lin.


When starting the circuit first time it seems to take a long time before possible to communicate the circuit.

It seems INITCOMPlete flag will not be set until 1000-1500 ms after power on.

Is this initialization time expected or do we initialize the wrong way?

 

Is it possible to read out important data before INITCOMplete is set?
My customer needs to know FW version at an early stage to decide if programming should be done or not.

 

They also need to determine if the circuit is in application or ROM-mode at an early stage.

 

I need your help to state:

  1. When and how can we determine if circuit is in application or in ROM-mode?
  2. When can we start trusting responses in reading data/flags from the circuit?

 

As you understand from the background, the faster the better.

Thanks a lot !

Best regards,

PA

 

  • 0
    TI__Expert 7280 points

    Answered offline:

    #1: the gauge runs on a 1 second cycle. It will take several measurements to get a good initial estimate of capacity so that’s why the 1000-1500ms are expected before INITCOMP is set.

     

    None of the gauging results will be meaningful before INITCOMP is one. 

     

    About INITCOMP: One of the main mistakes with a gauge is to power cycle or reset it when it isn’t absolutely necessary. The gauge will adapt over time to the battery and that will not work if the gauge is reset (e.g. during system boot if the driver resets the gauge during driver initialization).

    Please make sure you do not reset or power cycle the gauge unless it cannot be avoided.

     

    #2: The gauge will respond to I2C address 0x16 (8-bit) if it is in ROM mode.

     

    #3: After INITCOMP is 1.

  • 0 in reply to Pial
    Prodigy 20 points

    Even if the GasGauge shouldn't be power cycled or reset under normal use we will still need to handle the cases where it is. In our application it is reset at every board reset if there isn't a battery mounted. It's also reset after a battery replacement in order to trigger a new RemaningCapacity estimation.

    Pial said:
    None of the gauging results will be meaningful before INITCOMP is one.

    Ok, but how about non gauging related registers such as FW_VERSION? When can the response to that MAC subcommand trusted?

    Pial said:
    #2: The gauge will respond to I2C address 0x16 (8-bit) if it is in ROM mode.

    We've noticed that during startup och the GasGauge. The problem is that it seems to respond to ROM adress 0x16 for a short period of time before it automatically enters FW mode and starts to respond to FW adress (0xAA) instead. So the question is:

    At what point in time after a power reset can we check if the GasGauge is going to stay in ROM mode or FW mode?

  • 0 in reply to Pial
    TI__Guru 52115 points

    Hi ,

    I guess you already contacted us to get the answers.  Who did you contact? I will have my colleague comment again.

    Andy