|
|
|
|
|
by forthfifthsixth
3111 days ago
|
|
I can't imagine the utility of low-power processors that "aren't trying to be energy efficient per operation" and are "really bad at processing" - I thought that was the whole point! These really are completely different type of computers - I believe if you can apply the MSP430 successfully to your application then the GA144 is probably the wrong chip to use. But what if you need real-time nano-second reaction times on many separate pins? What if you need to process a 30 Mhz signal? While controlling a display and accepting input? All at the same time? Then you might need the GA144, which can do all those things at the same time without needing to worry about interrupts or waking up from low power sleep modes or any of the other complex mechanism computers employ to minimize power loss. |
|
10 seconds a week running a WiFi radio, TCP/IP, SSL and all that. 604,790 seconds a week waiting for a button to be pressed. Battery powered.
If you can monitor a button on 1 microamp, and run WiFi on 60 milliamps, 50% of your battery capacity will go on sleeping and 50% on waking.
And wake-state power consumption is dominated by the radio module, so the best way to cut down on wake state power consumption is to make the wake as short as possible.