This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

OMAP3530 power consumption in WINCE standby mode

Other Parts Discussed in Thread: OMAP3530

Hi,

I've just ported my code  to TI's WINCE 6.0 BSP v6.14 for OMAP3530. I didn't made other modification except for the necessary driver portation. However I can only get a standby power consumption of 95mA when the system goes standby.

I have verified that all modules like GPS, WIFI are powered off before the system goes into standby. I don't know what else I can do to further reduce the system power consumption. And I also can not find in a TI document which tells me a reference standby current.

What's your standby current? How you made it to reduce the standby power consumption?

 

Thanks!

Luo Yang

  • Luo Yang,

    Please refer the "App Note - Power Management with OMAP EVM35xx Platform running Windows CE 6.pdf" doc under Documentation folder of the BSP release. This doc has a section that talks about Suspend power consumption (Page 9) and also the conditions under which the current were measured (LCD build, Serial port disconnected etc). For BSP 6.14.00 we do have reports that the numbers in the doc do not match what has been observed in the actual release and that the SD card driver is contributing to extra power consumption If you make a build without SD card driver then the numbers come out to be at the expected level.

    My suggestion would be to upgrade to BSP 6.14.01 that was released yesterday (http://focus.ti.com/docs/toolsw/folders/print/dvsdk-winceomap.html). This one has some improvements in the power management area and the above problem has also not been observed in this release. Again refer to the same doc mentioned above (but part of the BSP 6.14.01) release for the latest numbers. The measured power numbers are also better than previous releases. 

    Also my suggestion would be to first try the build on the EVM so that you can cross check the numbers (and eliminate any other variable such as build or some peripheral connection that was not there when the measurements were done) before trying on your hw.

    Hope this helps.

    Jatin