Home arrow Support arrow Forums

Luminary Micro Forums

<< Start < Prev 1 2 3 4 5 Next > End >>

ckuecker

Expert Boarder
Click here to see the profile of this user

2008/06/27 11:42

Re:LM3S6965 crashes in hibernate

Just talked to my boss - looks like using hibernate is doomed, both from a time and a power draw (when active) perspective. So, this will have to remain unsolved, I guess.

The latest tack is to use the Luminary part strictly to support the Ethernet, which is a required part of our application, but only active for a very short time. We will use another small processor to power-up the Luminary part only when we need to communicate. The small processor will handle the low-power application 99% of the time.

Thanks A whole lot for your assistance. I am sure I will have more questions once we get into the Luminary / Ethernet side of the code.

login or register to reply

cb1

Platinum Boarder
Click here to see the profile of this user

2008/06/27 12:37

Re:LM3S6965 crashes in hibernate

Sorry to hear that - 2 micros causes new issues and complications.

If you'd be good enough to detail what you mean by, "from a time & power draw," I'd be willing to pursue on our own hardware...

Almost 100 have followed your "hibernate crash" saga now - I'd like this to end on a success for LMI's neat, new hibernate module...

login or register to reply

ckuecker

Expert Boarder
Click here to see the profile of this user

2008/06/27 14:46

Re:LM3S6965 crashes in hibernate

Unfortunately, we need to come up and react in a few milliseconds, maximum, from low power. We can't wait for even one second for an oscillator to stabilize.

If we use the Luminary part as an Ethernet portal, we can afford to take our time bringing it up, since we are only communicating a few times a day for a few seconds each time. Our application is battery powered, and the sleep and deep sleep mode power draws are right now an order of magnitude higher than our existing small micros. We are currently using Texas Instruments MSP430 parts, but without Ethernet capability, which we want to add.

We currently have a wireless link that uses an MSP430 and a radio module. The Luminary part would essentially replace the radio module. What we were looking at with hibernate was the possibility of replacing the MSP430 with a tiny fraction of the Luminary part's capability, but it appears that the best steady-state low power drain we can expect with that approach is on the order of a couple of milliamps - where the MSP series draws a couple of microamps.

I am taking my current draw numbers from the 6965 data sheet, and rounding up, since my copy states 'pending' in all the maximum columns. I see a typical sleep draw of 21 mA in sleep, and 4.81 mA in deep sleep. Active currents of between 57 and 156 mA are much better than our present radio module, which draws upwards of 600 mA when active, but these levels of draw are still much too high for us to consider the Luminary part as a stand-alone replacement for the MSP430.

login or register to reply

cb1

Platinum Boarder
Click here to see the profile of this user

2008/06/27 16:57

Re:LM3S6965 crashes in hibernate

Your 6965 "may" be able to meet your response requirements! Critical, spec'ed timing parameters appear to be H4 (wake assert to hib deassert) 124uS Max and H7 (hib deassert to VDD) 250uS Max.

The earlier, longer delay mentioned was ONLY to "get your hibernate module UP & Running - just in case" delay there was causing your earlier hibernate problem.

Again - I don't have this hw (yet) to perform/confirm any of these measurements - probably best that you re-visit your Ap with LMI Tech Staff - who know most and have newest data. As this new hibernate module vastly expands usage it would be appreciated if you could inform the forum of LMI's comments...

login or register to reply
<< Start < Prev 1 2 3 4 5 Next > End >>