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: Alert pin not always assert after GE pin is asserted

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

The assert configuration is set to 0xFF. following the workflow from 8.2.2.2 of the datasheet, my application is waiting for the alert pin goes low due to initcomp. But from time to time the pin stays high. Any reason can cause this? My understanding is the alert pin will be back high after reading the BatteryAlert(0x0B) register, but the corresponding bits of the BatteryAlert will not be cleared until the condition is removed. Is that correct? Is it better to just poll the register instead of waiting for the interrupts.

  • Hi Leon,
    I would recommend polling the register if you have that flexibility. When you say from time to time, does that mean that it works sometimes and sometimes it doesn't? Was the pin exerted already for a different condition hence it not clearing before being alerted for the initcomp flag? Can you provide a gg file and a log file of the occurrence so we ensure you have things set up properly

    thanks
    Onyx
  • Hi Onyx,

    Thanks for you reply. Yes, I mean it. The alert pin works for most of time but not always. From my oscilloscope, the alert pin is high before I enable the GE pin. But it still stays high after I enable GE pin. I don't know what the gg file is. I'm using a MCU to communicate with evaluation board. 

    Best Regards,

    Leon

  • We always require configuring your board using bqstudio and and EV2400 . You need to acquire one to complete the proper set up of the gauge. pls view the video below for configureart

    r.search.yahoo.com/.../RS=DzzEryVNwPofl6kp2FgxTnM7raI-


    thanks
    Onyx