Howto: Powering the Stellaris Launchpad with a LiPo battery

According to the Stellaris Launchpad User's Manual there are only two power options:

4.75-5.25 VDC from one of the following sources:
Debugger (ICDI) USB Micro-B cable (connected to a PC)
USB Device Micro-B cable (connected to a PC)

Well, powering this thing with USB is very convenient, but I like to make my projects portable or at least 'untethered' if USB is not needed for debugging or communications. And there is this unpopulated 3-pin header in the bottom-left corner of the board, labeled VBUS just begging to be populated with a 2mm JST header for a single-cell LiPo. There is a twist, though: The Launchpad expects 4.75-5.25 VDC on VBUS, nothing that a single cell LiPo could provide. I know that the system voltage is 3.3 VDC and that the voltage regulator on the board has a very low dropout voltage, so powering the Launchpad with anything between 3.4-5.25 VDC should work well. The voltage of a single-cell LiPo ranges between 3.0-4.2 VDC, so let's populate this header and plug a fully charged LiPo in it! Being a practical guy, I did just that.

Guess what, nothing happened!

At least there was no magic smoke released, but no fancy fading of the RGB led either. But the green LED on the debugger portion of the board lit up, so I started probing voltages with a multimeter. Imagine my surprise when I measured perfectly stable 3.3V on the 3V3 rail! Everything seemed to be fine, so I dug out the schematic aka the 'User Manual' for the Stellaris Launchpad. The interesting part for me was the schematic of the power management circuitry, found on page 19: You'll see the problem within seconds, if you're familiar with the operation of voltage supervisors. The green LED D4 lit up and I measured 3.3V on the 3.3V rail, hence the voltage regulator U8 was working fine. The power select switch SW3 is not relevant because the LiPo is connected to +VBUS directly. My guess was that U4 pulled RESET low for some reason, therefore preventing the micro from running its code. Probing RESET with a multimeter and taking a look on the first page of the TLV803 datasheet confirmed my theory: Turns out that U4 is a 5V voltage supervisor, pulling RESET low if +VBUS is below 4.38V. I'm not familiar with the correct implementation of these voltage supervisors, but for maximum hackability it would have been nice to use a 3.3V supervisor on the 3V3 rail instead of a 5V one on +VBUS.

Howto outsmart mission control

Although the Launchpad design includes the voltage supervisor for a reason, to ensure stable operation, this design feature was more of a design flaw for me: The 5V version of TLV803 has a treshold voltage of 4.38V, a LiPo battery has a maximum of 4.2V which means that the TLV803 would pull RESET low all the time, rendering the Launchpad unusable powered with a LiPo.
Simple problem, simple solution: Remove U4! R17 is a 10k pullup resitor and will keep both, TARGETRST and ICDI_RST high. Even simpler and no desoldering involved: Cut the tiny trace between U4 and D2: Now you can power your Launchpad with a standard single cell LiPo or anything between 3.4VDC and 5.25VDC.

Disclaimer:

This is a quick'n'dirty hack, so please be aware that connecting your Launchpad to USB while a LiPo is plugged into it will propably harm the LiPo and maybe the USB port, too. I highly recommend to use LiPo batteries with integrated protection circuitry for this hack, because LiPo batteries tend to react very bad to overcharge!
Additionally you should keep an eye on your battery voltage, a LiPo should not be discharged under 3V or it may take damage and will lose some of its capacity. Keep in mind that there is no kind of low-voltage shutdown on the Launchpad with the voltage supervisor removed!

If you are willing to take these 'risks' this hack will give you plenty of power for your portable experiments with the Stellaris Launchpad. Happy hacking! ;)

Thank you for using scriptogr.am. While we’re still in early beta development, we think you’ll enjoy the app. It’s designed to be fast, simple and to get the most creativity out of you.

scriptogr.am uses Markdown, a lightweight markup language, originally created by John Gruber and Aaron Swartz. Markdown is a text-to-HTML conversion tool for web writers. Markdown allows you to write using an easy-to-read, easy-to-write plain text format, then convert it to structurally valid XHTML (or HTML). See the Syntax page for details pertaining to Markdown’s formatting syntax. You can try it out, right now, using the online Dingus.

Getting started

After connecting your Dropbox account to scriptogr.am, some necessary files and folders are added to your Dropbox at Apps/scriptogram. First the GET_STARTED.txt text file that pretty much explains the exact same as what you’re reading now. Next, we’ve added a posts folder. This is where you add your blog post (& page) files. These files are plain textfiles, but needs to be saved with the .md (markdown) extension like this: yourfile.md

Please use standard, non foreign filenames. Dropbox sometimes have problem syncing filenames that contains invalid HTML characters. We’ve added a post example page (this file) there for you to get familiar with.

The template data

All files needs to contain "front block". The front block must be the first thing in the file and takes the form of:

Date: 2012-04-17
Title: My first post

You can set any of the predefined variables (see below for a reference). But, the Title is required. Without the title, the system will fail.

Predefined global variables

All the variable names below are case-sensitive:

Required:

Title

The title of your post (or page)

Not required, but close to:

Date

The following date format is the correct one to use: 2011-12-31 12:31 or 2011-12-31. (The Date variable can be used to ensure correct sorting of posts.)

Optional:

Published

Set to ’false’ if you don’t want a post to show up when the site is generated.

Type

Set to ’page’ if you wan’t the post to act as a ’page’ instead of a ’post’.

Slug

Custom permalink (replaces the auto generated url based on the "Title:" variable), especially useful if titles tend to be long or they change frequently. E.g ’my-custom-permalink-url’

Link

Links the "post" or "page" title to an external source. E.g ’http://google.com’

Tags

Add tags to your posts and pages. Comma separated words. Once added, scriptogr.am will transform all tags to valid basic HTML characters.

Excerpt

Add an excerpt¹ to your post or page.

Difference between ’posts’ and ’pages’

A post is a blog post.

A page is a similar as a post, but generates a link visible in the menu on your site that will lean to a page permalink.

Publishing your posts

This is simple. Just head to your admin panel and hit the ”Synchronize” button. When logged in to scriptogr.am and visiting your own page, you’ll see the scriptogr.am logotype symbol on the top right of the browser window. This is the link that leads to your admin panel.

Published vs unpublished

Total count of published and unpublished posts (& pages) are visible next to the ”Synchronize” button. ”Unpublished” means that you either removed a post text file from your Dropbox or that something went wrong while trying to sync your Dropbox with scriptogr.am. Also, if you’ve set a post to be published with the Published: false variable.

Finally, happy posting. If you have any questions, suggestions or thoughts just drop us an e-mail at any time.