• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 64 subscribers
  • Views 281 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

BQ27441EVM-G1B: how to bring up of fuel gauge in uboot

Rutvij Trivedi
Prodigy 40 points
Part Number: BQ27441EVM-G1B

Hi Folks,

I am working Linux based platform and successfully bring up the FG(Fuel Gauge) in kernel. 

Now, I want to bring up same in "Uboot"  also.

Is there any document available to bring up FG(Fuel Gauge) in uboot for VIM3L?

Or else if you can suggest us in this regards.

Your help will be appreciated.

  • 0
    TI__Expert 8245 points

    Hi Rutvij,

    I do not believe that we have any documentation for this but I will check with my team tomorrow and get back to you to be sure.

    Thanks,

    Jackson

  • 0 in reply to Jackson DiGiovanna
    TI__Guru 51636 points

    TI doesn't maintain drivers for gauges. There's open source code (part of the official Linux Kernel) but that isn't actively maintained by TI. Neither is u-boot code for TI gauges.

    There's generic information how to program ROM gauges like the bq27441 in www.ti.com/.../slua801.pdf

  • 0 in reply to Jackson DiGiovanna
    Prodigy 40 points

    Hi Jackson,
    Thank you for the quick replay, appreciate if we can have some pointers on it.

    -
    Thanks

  • 0 in reply to Dominik Hartl11
    Prodigy 40 points

    Hi Domnik,

    Thank you for the quick replay, i will try some-other way around as well.

    -
    Thanks

  • 0
    Prodigy 40 points

    Hi,

    I have added support of FG in uboot and  taking reading at every 500mSec to check the driver.

    As from logs I have seen that  FG parameters AverageCurrent(0x10 and 0x11) are getting zero in between of readings.

    I have also check datasheet for that and found "In NORMAL mode, it is updated once per second".

    Is there any specific reason for that readings? 

    Logs:
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    :: FG :: FUEL GAUGE CHIP ID                             >> 0x0421
    :: FG :: BATTERY DESIGN CAPACITY                >> 2000 mAh
    :: FG :: BATTERY STATE OF CHAREG               >> 42 %  
    :: FG :: BATTERY VOLTAGE NOW                      >> 3799 mV  
    :: FG :: BATTERY CURRENT NOW                    >> -5 mA  
    :: FG :: BATTERY FULL CHARGE CAP              >> 1885 mAh
    :: FG :: BATTERY NOMINAL AVAILABLE CAP   >> 851 mAh
    :: FG :: Flags                                                        >> 0x0188
    :: FG :: POWER_SUPPLY_STATUS                    >>  DISCHARGING
    :: FG :: POWER_SUPPLY_CAPACITY_LEVEL   >>  NORMAL

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    :: FG :: FUEL GAUGE CHIP ID                            >> 0x0421
    :: FG :: BATTERY DESIGN CAPACITY                >> 2000 mAh
    :: FG :: BATTERY STATE OF CHAREG               >> 42 %  
    :: FG :: BATTERY VOLTAGE NOW                      >> 3800 mV  
    :: FG :: BATTERY CURRENT NOW                    >> -5 mA  
    :: FG :: BATTERY FULL CHARGE CAP              >> 1885 mAh
    :: FG :: BATTERY NOMINAL AVAILABLE CAP   >> 851 mAh
    :: FG :: Flags                                                        >> 0x0188
    :: FG :: POWER_SUPPLY_STATUS                    >>  DISCHARGING
    :: FG :: POWER_SUPPLY_CAPACITY_LEVEL   >>  NORMAL

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    :: FG :: FUEL GAUGE CHIP ID                            >> 0x0421
    :: FG :: BATTERY DESIGN CAPACITY                >> 2000 mAh
    :: FG :: BATTERY STATE OF CHAREG               >> 42 %  
    :: FG :: BATTERY VOLTAGE NOW                      >> 3800 mV  
    :: FG :: BATTERY CURRENT NOW                    >> -5 mA  
    :: FG :: BATTERY FULL CHARGE CAP              >> 1885 mAh
    :: FG :: BATTERY NOMINAL AVAILABLE CAP   >> 851 mAh
    :: FG :: Flags                                                        >> 0x0188
    :: FG :: POWER_SUPPLY_STATUS                    >>  DISCHARGING
    :: FG :: POWER_SUPPLY_CAPACITY_LEVEL   >>  NORMAL

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    :: FG :: FUEL GAUGE CHIP ID                           >> 0x0421
    :: FG :: BATTERY DESIGN CAPACITY               >> 2000 mAh
    :: FG :: BATTERY STATE OF CHAREG              >> 42 %  
    :: FG :: BATTERY VOLTAGE NOW                     >> 3799 mV  
    :: FG :: BATTERY CURRENT NOW                    >> -5 mA  
    :: FG :: BATTERY FULL CHARGE CAP              >> 1885 mAh
    :: FG :: BATTERY NOMINAL AVAILABLE CAP   >> 851 mAh
    :: FG :: Flags                                                        >> 0x0188
    :: FG :: POWER_SUPPLY_STATUS                    >>  DISCHARGING
    :: FG :: POWER_SUPPLY_CAPACITY_LEVEL   >>  NORMAL

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    :: FG :: FUEL GAUGE CHIP ID                           >> 0x0421
    :: FG :: BATTERY DESIGN CAPACITY               >> 2000 mAh
    :: FG :: BATTERY STATE OF CHAREG              >> 42 %  
    :: FG :: BATTERY VOLTAGE NOW                     >> 3799 mV  
    :: FG :: BATTERY CURRENT NOW                    >> 0 mA  
    :: FG :: BATTERY FULL CHARGE CAP              >> 1885 mAh
    :: FG :: BATTERY NOMINAL AVAILABLE CAP   >> 851 mAh
    :: FG :: Flags                                                        >> 0x0188
    :: FG :: POWER_SUPPLY_STATUS                    >>  NOT_CHARGING
    :: FG :: POWER_SUPPLY_CAPACITY_LEVEL   >>  NORMAL

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    :: FG :: FUEL GAUGE CHIP ID                             >> 0x0421
    :: FG :: BATTERY DESIGN CAPACITY                 >> 2000 mAh
    :: FG :: BATTERY STATE OF CHAREG                >> 42 %  
    :: FG :: BATTERY VOLTAGE NOW                       >> 3799 mV  
    :: FG :: BATTERY CURRENT NOW                      >> -5 mA  
    :: FG :: BATTERY FULL CHARGE CAP                >> 1885 mAh
    :: FG :: BATTERY NOMINAL AVAILABLE CAP    >> 851 mAh
    :: FG :: Flags                                                         >> 0x0188
    :: FG :: POWER_SUPPLY_STATUS                    >>  DISCHARGING
    :: FG :: POWER_SUPPLY_CAPACITY_LEVEL   >>  NORMAL

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    :: FG :: FUEL GAUGE CHIP ID                            >> 0x0421
    :: FG :: BATTERY DESIGN CAPACITY               >> 2000 mAh
    :: FG :: BATTERY STATE OF CHAREG              >> 42 %  
    :: FG :: BATTERY VOLTAGE NOW                      >> 3799 mV  
    :: FG :: BATTERY CURRENT NOW                    >> 0 mA  
    :: FG :: BATTERY FULL CHARGE CAP              >> 1885 mAh
    :: FG :: BATTERY NOMINAL AVAILABLE CAP   >> 851 mAh
    :: FG :: Flags                                                        >> 0x0188
    :: FG :: POWER_SUPPLY_STATUS                   >>  NOT_CHARGING
    :: FG :: POWER_SUPPLY_CAPACITY_LEVEL  >>  NORMAL

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    Thanks

  • 0 in reply to Rutvij Trivedi
    TI__Guru 51636 points

    The gauge runs on a one second measurement cycle, hence the data won't update faster than once per second and it's pointless to read the data more often. In addition, it is possible to trigger a WDT reset inside the gauge if you poll data at a high rate (the d/s limits the polling frequency because of this potential problem).

    The gauge has a deadband setting for the current, which will zero out current that is below this threshold. So if you see that the current drops to zero while you know that there is a current then I recommend checking the deadband setting (in the calibration subclass).