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.

bq27x00: GPIO pin function?

Anonymous
Anonymous
Guru 17045 points
Other Parts Discussed in Thread: BQ27200, BQ27210

Hi,

I would like to ask a question on bq27x00.

[Pin 9, GPIO] is

1.    Not connected in datasheet example.

2.    Described as can be configured as I/O based on EEPROM(PKCFG.GPIEN) and Flash (MODE.GPIEN, MODE.GPSTAT) register bits.

In bq27200 EVM sluu210, it is

1.    Connected.

2.    Without clear description in the document.

 

 

 

There are already I2C or HDQ pins for communication with the host, why is this GPIO pin still provided? Isn't it redundant? Could anyone advise me of the functionality of this pin?

 

Zheng

  • The GPIO pin can be controlled by the host to give it access inside the battery pack.  For example, the GPIO pin of the bq27210 could be configured as an input so that the host can read the status of a circuit inside the battery pack via the bq27210.  Or the bq27210 GPIO pin could be configured as an output so that the host can control a circuit inside the battery pack via the bq27210.  For example, the host could send a command to the bq27210 and it could blink an LED, trigger a music circuit, and then self-destruct.  The possibilities are limitless!

    It's shown as unconnected in the Typical Application Circuit because it's not necessary and in fact most customers don't use it.  In the EVM circuit it is shown connected because it comes out to the J3 connector so that you can experiment with it, but you don't have to use it.

    If you don't use it I would recommend tying it to VSS instead of leaving it floating.  It should be okay to leave it floating, but if it somehow gets configured as an input by mistake, it could float to a mid-range voltage and cause shoot-through and waste power.  That's why it's better to tie it low.

  • Anonymous
    0 Anonymous in reply to dMax

    dMax,

    This is definitely resolved. Thank you.

    Zheng