Global Sources
EE Times AsiaWebsite
Stay in touch with EE Times Asia
eeBlogs-Article content Home / eeBlog / eeBlogs
Profile
Nickname: Jack Ganssle     Articles(165)     Visits(161956)     Comments(29)     Votes(150)     RSS
Jack Ganssle is a lecturer and consultant specializing in embedded systems' development issues. He has been a columnist with Embedded Systems Design for over 20 years.
Blog Archive
2014 -  Dec.,   Nov.,   Oct.,   Sep.,   Aug.,   Jul.,   Jun.,   May.,   Apr.,   Mar.,   Feb.,   Jan.  
2013 -  Dec.,   Nov.,   Oct.,   Sep.,   Aug.,   Jul.,   Jun.,   May.,   Apr.,   Mar.,   Feb.,   Jan.  
2012 -  Dec.,   Nov.,   Oct.,   Sep.,   Aug.,   Jul.,   Jun.,   May.,   Apr.,   Mar.,   Feb.,   Jan.  
View All
Comment | Add to Favorites

Posted: 08:24:29 PM, 23/05/2014

Is brown-out reset any good?

   

A few readers have written about how they defend against a dying battery using a brown-out reset (BOR) circuit, a feature pretty much every low-power microcontroller has. Unfortunately, most are poorly designed and/or lightly documented and should not be used.



One popular ultra-low power MCU, from a vendor who noisily advertises two to three decades of coin cell operation, has a BOR which is off by default. On, it requires somewhere between 8 (typical) and 16 uA (worst case). Remember that, for a decade of life from a CR2032, the system’s average power draw cannot exceed 2.5 uA. Even if one were to foolishly use the typical number, the BOR by itself will deplete the battery in just a couple of years.



Another vendor, pushing extremely-low power ARM parts, rates the BOR at 0.49 to 1.26 uA – typical. There’s no max listed; there’s not the slightest guidance of what statistical distribution one can expect when making thousands of systems. 1,26 uA eats half the 2.5 uA budget.


In another case the datasheet reads about the BOR: “In the deeper sleep modes, this will contribute significantly to the total current consumption.”



As Deming said: “In God we trust, all others bring data.” They didn’t, and it strikes me as risky to expect divine intervention instead of doing careful analysis. I’d be wary of using these uncharacterized parts in long-lived applications. As always, read the datasheets pessimistically and carefully.



When does the BOR interrupt occur? In some cases the voltage range is very wide; an example is an MCU where it is listed as 2.05 (min), 2.2 (typ), and 2.35 volts (max). Doing worst-case design you’d have to assume that the BOR may occur at 2.35 volts.



The following graph is one I have used before; it shows the voltage a CR2032 can deliver as it discharges as a function of load. The 10 mA load line is pretty common for an awake MCU with enabled peripherals; 30 mA is not unexpected if there’s any sort of wireless comm going on. The heavy red line is at 2.35 volts, the max value where we may see a BOR interrupt. Note that in this case the BOR circuit will signal a dead battery, if there’s a 30 mA load, shortly after you ship the product. With a 10 mA load the battery-dead indication happens when there’s still 31% capacity left.
 


In other words, the BOR circuit is useless.



A much better alternative is to leave the BOR off and use the A/D. Wake up from time to time, apply a load similar to what the system normally needs when awake, and read Vcc. If it’s near 2.0, then signal a battery failure (or take whatever action your system needs in this situation).


If such a reading is taken once every ten hours (surely, more often than needed), and 10 mA were pulled for 1 ms, over a decade this eats only 0.03 mAh, or 0.01% of a CR2032’s capacity. And, by manually reading the A/D a more nuanced approach to battery management is possible than by relying on a single, poorly-controlled, BOR voltage.

Views(460) Comments(0)
Total [0] users voted     
[Last update: 08:24:29 PM, 23/05/2014]
Have Your Say!

Bloggers Say

Got something to say? Why not share it with other engineers?

Just introduce yourself to us, we'll contact you and set you up. Yes, it's that simple!

See what engineers like you are posting on our pages.

eeBlogs

• Collaborative approach: Does it wor...
Posted:10/12/14 06:57 PM
• Learn about the engineering desk-to...
Posted:02/12/14 07:19 PM

• LCD inventor shook things up at DAR...
Posted:07/12/12 10:32 AM
• Robotics passion inspires Android c...
Posted:29/11/12 04:38 PM

• The perils of software/hardware hom...
Posted:18/09/14 05:39 PM
• How secure is the IoT?
Posted:20/08/14 06:53 PM

• More than hardware sockets - Opport...
Posted:01/12/14 06:09 PM
Interviews & Viewpoints

Talk

Learn how senior executives are seeing the industry from interviews and contributed opinions.

Back
 
Back to Top