element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
    About the element14 Community
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      •  Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
BeagleBoard
  • Products
  • Dev Tools
  • Single-Board Computers
  • BeagleBoard
  • More
  • Cancel
BeagleBoard
Blog BBB - Rechargeable on-board battery system
  • Blog
  • Forum
  • Documents
  • Quiz
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join BeagleBoard to participate - click to join for free!
  • Share
  • More
  • Cancel
Group Actions
  • Group RSS
  • More
  • Cancel
Engagement
  • Author Author: shabaz
  • Date Created: 9 Aug 2013 11:53 PM Date Created
  • Views 19511 views
  • Likes 18 likes
  • Comments 129 comments
  • beaglebone_black
  • bbb
  • bb_black
  • beagle_bone_black
  • ti
Related
Recommended

BBB - Rechargeable on-board battery system

shabaz
shabaz
9 Aug 2013

Note April 2017: There are different revisions of the BeagleBone Black since this post was written in 2013, and without testing them all, it is the user's decision whether to try this solution or not. The revision changes are listed here and a possible option for at least some revision boards is shown in the photo here but I've not investigated this. The newer BeagleBone Blue already has a battery connection, so that is another option.

 

This posting is about implementing a rechargeable battery system for the BeagleBone Black. It is simple, safe and very low cost (less than 6 Euro).

 

image

 

First, some brief information about the power circuitry on the BBB.

 

The BBB has a built-in power management IC (PMIC) based on the TI TPS65217C device. This device contains multiple switch-mode regulators and LDO regulators to provide all voltage levels needed for the entire board. It handles wake-up using a push-button fitted on the BBB. Automatic power-down via the button requires some software to be implemented (to do the equivalent of 'shutdown now' from the command line). When the button is pressed, an interrupt is generated and the microprocessor is supposed to query the PMIC (via I2C) to learn that the button was pressed, and kick off the shutdown sequence. In the event of a failure here, the power can be switched off by holding the button down for 8 seconds.

The IC also contains built-in battery charging capability.

Apart from the USB requirement of 5V, there is no need to run the BBB from 5V; it can happily run from a lower supply. This means that a single 3.7V cell could be used to power the entire board. No need to step-up to 5V or to run dual cells and step-down to 5V, both of which could have been inefficient.

Why is this useful?

It makes it an excellent platform for outdoor/portable use.

For indoor use a battery is useful because it serves as a backup supply in case the main power (from a mains powered supply or from USB) gets disconnected. It could prevent filesystem corruption. If the main supply gets disconnected, the battery immediately takes over. In fact, I permanently leave the battery connected even when I'm running from the mains supply, in case I forget to safely shutdown the board.

What battery can be used?

Any small Lithium Ion (Li-Ion) or Lithium Polymer (Li-Po) single cell can be used, preferably as long as it has a built-in protection circuit. If it doesn't have an in-built circuit, it is highly advisable that one with a built-in thermistor is used. A cell in the range 700mAH to around 2AH is advisable. The one that I used in the photo above is from Olimex part code BATTERY-LIPO1400mAh. It should last around 3.5 hours (EDIT: Now been measured, it lasts 2 hours 50 minutes - see notes below, and comments below) on a full charge (not measured) and should fully charge in around 2 hours. This particular battery is just the right size to fit in between the two rows of headers and is flush so that a cape can still be plugged on top. So, the entire thing can fit inside any enclosure.

You will also need a connector (see next section) and one resistor.

Construction detail

The BBB has four holes that are suitable for connecting up the battery. They are detailed in the BBB system reference manual (SRM):

image

This is what they look like:

image

The Olimex Li-Po has a built-in protection circuit, so I soldered a 10k resistor to TS and GND to simulate the thermistor. (EDIT: You may or may not wish to do this, please study Li-Po and use your own judgement - see comments below) It is desirable to use a connector for the Li-Po.

The LiPo connector was convenient to solder to pins TP6 and TP8, and then  a zero-ohm link between TP5 and TP6 on the underside.

Here is how it was done step-by-step (there are just two steps):

1. Solder the 10k resistor, and a zero-ohm link (both are achieved on the underside of the board) as shown here in the yellow box. These are simple 0603 resistors; I used a 1% tolerance resistor, but 5% should be fine.

image

2. Solder in the connector.

This is straightforward, but complicated slightly by the fact that the connector has 2mm pin spacing, but the board has 0.1" spacing. It means that the pins on the connector need to be splayed or bent into the correct spacing. The connectors are available in vertical mount or right-angle (RA) mount. If you use a vertical mount connector, there may not be enough space to splay the pins. Instead, I used a right-angle connector and bent the pins into a vertical orientation, and then I had space to bend the pins and still have the connector flush with the board as shown here. You can see another view of the connector from the first photo.

image

I'm fairly sure that the desired connector is JST 'PH' series.

 

That's it; plugging in the battery, the board worked instantly. Note that the Li-Po charge method is usually to have a constant current supplied to the battery until it reaches a certain, very precise voltage. After that the charger switches to a constant-voltage mode. For the Li-Po battery that I used, the charger needs to be set to 4.2V, but the BBB by default sets it to 4.1V (It can be set to 4.2V via I2C control but today it doesn't). I'm not sure what the impact of this is (beyond storing less charge), but I believe it is safe. I have been using it daily for three months and the battery is always cool to touch.

Controlling the PMIC

The TPS65217C PMIC is very programmable; it has dozens of configuration settings specifically for charging and it has safety timer capability. The PMIC is configured upon startup via I2C. There are three I2C busses on the BBB, and one is dedicated to on-board peripherals. Control of the PMIC is not normally possibly by the user; it requires driver code or possibly there is access by the device tree infrastructure. Checking the .dts file in /boot did not reveal how to control the battery charger functionality. There are two current Google Summer of Code (GSoC) projects that touch on PMIC:

1. IIO, ADC, PMIC, LCD debug/patchwork (summary page, blog page) - Zubair Lutfullah

2. MINIX I2C drivers (summary page, blog page) - Thomas Cort

Hopefully the guys working on the projects (Zubair and Thomas) can offer some advice on how to set the level to 4.2V. Zubair's project also includes how to use the in-built ADC inside the AM3359 to monitor voltages.

Notes

There really should be some more detail including measurements to show how long the battery lasts and to observe the charging status (via I2C reads). Unfortunately I didn't have time to collect this information. But I've been using it for three months regularly and it functions well.

EDIT: The following simple test was conducted using the Olimex battery referred to above.

1. Power up the BBB using the DC power supply and let it charge the battery while powering the BBB

2. After about 4-5 hours, the DC supply was disconnected, and a script was run on the BBB to log the current date/time to a file, every minute. The script would sleep in-between. The Ethernet connection was left up, and the BBB was left alone until the battery died, and then the log file was examined.

 

#!/bin/bash
while true; do
date >> log.txt
sleep 60
done

 

The result was that the log file showed that the BBB ran for 2 hours 30 minutes before it died. After this, the test was repeated. The second time, it ran for 2 hours 50 minutes. The discrepancy may be because this battery has never been fully charged followed by such a long discharge, and so perhaps it is related to that. No test has been run with the Ethernet disconnected, but the BBB should run for longer in that case of course.

In a third test, the battery again ran for  2 hours 50 minutes (to within 1 minute). Again, this was with the Ethernet interface up.

  • Sign in to reply

Top Comments

  • shabaz
    shabaz over 12 years ago in reply to morgaine +2
    Hi Morgaine, Thanks! That's a good link and tip. I too had found the connector tight. Hi John, (Replying here so that we can retain the battery comments in a single location): John Alexander wrote: How…
  • shabaz
    shabaz over 12 years ago in reply to fustini +2
    Hi Drew, I'm not sure where the 500mV number could be from. The charge voltage will go up to 4.2V, or at least it should, but today is 4.1V until the PMIC is programmed for a 4.2V threshold). Apparently…
  • mcb1
    mcb1 over 12 years ago in reply to shabaz +2
    Nice project. There are LDO regulators that can be lower than 500mV. We had a very interesting talk about LiPo/LiOn batteries by the battery expert at a local large firm that has them in their radios.…
  • gadget.iom
    gadget.iom over 10 years ago in reply to Former Member

    People don't typically give out email addresses on here.

    The whole point of the community is that everybody can benefit from the discussion.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • Former Member
    Former Member over 10 years ago

    Have you any solution to getting the BBB to go into low current consumption sleep mode allowing a 1300mAH Lithium Ion cell to keep the BBB powered in sleep mode for several days?

     

    Can you give me your email address please or mobile number to discuss?

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • shabaz
    shabaz over 10 years ago in reply to Former Member

    I measured it this evening, in the powerdown state the current consumption drops to 23uA for the battery, which is the expected ballpark. If they are seeing 200mA, then either their cape is still somehow being powered (I can't see how), or the BB is not really shutdown.

    I tested an older rev BB running Angstrom, but the result will be no different for the Rev C with Debian.

    Another explanation is that perhaps their battery is connected to the 5V DC connector, not to the the 4-pins on the board like I tested.

    If the customer can get back with some more detail on their test topology and their requirement, that would be great.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • shabaz
    shabaz over 10 years ago in reply to Former Member

    Hi Ian,

     

    I've not tried a Rev C with BB View, however it would be good to understand what peripheral circuits the customer mentions that drain the battery. Do they mean peripheral circuits on the Beaglebone, or do they mean the BB-View, or some other attached circuit?

    I have a Beaglebone here and I can measure the current consumption of it in standby (will have to do this test this evening, am not near any test tools currently) to see what could be occurring. However I don't have a BB-View, so can only test without it.

     

    From the sounds of it, perhaps the battery may be connected to the 5V DC connector? In which case yes, even in powerdown state, current will be consumed, because the BB View most likely uses the 5V rail too (and that rail is not powered down, it is up to the connected circuit (i.e. the BB-View) to self-power-down if it can). If that is what is occurring, then there are two solutions; either the cape could be modified to include a MOSFET to power itself off (Far easier to modify a cape or attach some small circuit, than to build a custom beaglebone) or instead have a circuit to disconnect the battery after some time as they suggest.

     

    If the battery is connected as mentioned in this blog post, then the current consumption should drop (I will measure it tonight), but then they won't have any 5V supply rail without an external 5V supply, to power the display. But I don't know their requirement.

     

    If you prefer, please go ahead and get the customer to reach out to me via my e-mail address or mobile number, to quickly hear exactly how they are using it (or we can continue the discussion here, whichever is more convenient).

     

    Building their own Beaglebone board is a possibility but is a significant undertaking (I know a customer who built their own board), I think the existing PMIC functionality and a MOSFET on any connected cape (or some small adapter board) should meet their needs.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • Former Member
    Former Member over 10 years ago in reply to shabaz

    HI Shabaz

     

    Hope you are well. we have a customer who is having problems with a battery backed up BBB, BB View 4.3 solution. Did you ever work with Rev C board and Debian for this?

    -----------------------------

    The problems of the BB board in this application are multiple. Basically we need to power it down and power it up again in an orderly fashion but the sleep state needs to consume much, much, less current than it currently does to make using the BB “as is” in this application feasible. If it cannot be used as is, then another “add on” board will need to be designed, but QT are currently assessing the worth of doing this (might as well design the whole thing from scratch?).

     

    The main problem is the BB consumes upwards of 200mA in its sleep mode. The processor powers down OK, but the peripheral circuits stay up, draining the battery. The effect of the drained battery is that the power management chip then “drops out”, disturbing the operation of the processor, and in particular the Linux operating sytem (which might not be “hard” enough for this task). The net effect is that the BB neither powers down nor powers up correctly once the back-up battery is drained.  Basically we need no more than 5 mA sleep current. 5uA would be even better. Note that only the Ethernet interface is absolutely necessary for this application.

     

    company is going to consider the feasibility of designing an add on board using a PIC to detect the supply power state (off/on) and to provide power at the switchover from line power to battery power long enough to satisfy the requirements of the processor for orderly shut down/start up. If he decides to design his own board, the opportunity, whether it is large enough or not, is lost for the BBB.

    -------------------------------

    I would be grateful for your expert opinion here.

     

    Ian Bromley

    Premier Farnell

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
<>
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2026 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube