The
TI OMAP5 EVM has 2GB of RAM, which is implemented using 4x Micron 4Gb DDR3L devices (
MT41K256M16HA-125:E).
DDR3L operates at 1.35V and each of those 4Gb (512MB) chips draws 20mA if it is doing nothing more than self-refresh. So when idle, 2GB of this type of RAM should consume about 1.35V * 20mA * 4 = 108mW.
For comparison, with the lid closed and cpu idle, a Pandora uses slightly less than 100mW. That number includes not just its 512MB of RAM but also all the other stuff.
The Pyra battery will be bigger than the Pandora one, and the Pandora has a standby time of about 7 days (4200mAh * 3.7V / 95mW).
Let's say a 2GB Pyra uses 150mW when standby (108mW for RAM and the rest for the other stuff). With a 6000mAh battery that results in 6 days of standby time.
If the same type of RAM is used, 4GB will consume twice as much, so let's say the total is 250mW. In that case, standby time is reduced to less than 4 days.
So the effect on standby time is quite big.
One potential solution would be to use suspend-to-disk instead of suspend-to-ram to achieve better standby times. But the eMMC will probably not be large enough to do that, so you would have to use free space on an SD card. The theoretical maximum transfer speed we can achieve is about 100MB/s. That means that suspending and resuming takes about 20 seconds each if 2GB needs to be transferred between RAM and SD card (it could be less because only used memory needs to be stored/restored), and of course twice as long if 4GB has to be transferred. In practice it would probably be slower than that because SD cards that max out the theoretical speed limit are very expensive. So that does not look like an acceptable solution.
I would rather spend money on more expensive lower-power 2GB RAM, than on 4GB. In general, I would like to make sure that the Pyra improves upon the Pandora in all respects, instead of having it improve some aspects (amount of RAM) by sacrificing other aspects (standby time).