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.

AM3517 wakeup issue

Other Parts Discussed in Thread: AM3517

Hi,

I can't wakeup AM3517 from sleeping when using the Froyo V2.2 Android.

The belowing is the log files,

 

request_suspend_state: wakeup (3->0) at 36775817874 (1970-01-01 00:00:36.775817874 UTC)

request_suspend_state: sleep (0->3) at 166765960693 (1970-01-01 00:02:46.765930175 UTC)

omaplfb: **** SUSPEND

PM: Syncing filesystems ... done.

Freezing user space processes ... 

Freezing of tasks aborted after 0.00 seconds (191 tasks refusing to freeze):

Restarting tasks ... done.

suspend: exit suspend, ret = -16 (1970-01-01 00:03:19.142456085 UTC)

PM: Syncing filesystems ... done.

Freezing user space processes ... 

Freezing of tasks aborted after 0.00 seconds (193 tasks refusing to freeze):

Restarting tasks ... done.

suspend: exit suspend, ret = -16 (1970-01-01 00:03:28.176239001 UTC)

PM: Syncing filesystems ... done.

Freezing user space processes ... 

Freezing of tasks aborted after 0.00 seconds (192 tasks refusing to freeze):

Restarting tasks ... done.

suspend: exit suspend, ret = -16 (1970-01-01 00:03:32.722503664 UTC)

PM: Syncing filesystems ... done.

Freezing user space processes ... 

Freezing of tasks aborted after 0.00 seconds (190 tasks refusing to freeze):

Restarting tasks ... done.

suspend: exit suspend, ret = -16 (1970-01-01 00:03:34.363586429 UTC)

PM: Syncing filesystems ... done.

Freezing user space processes ... (elapsed 0.01 seconds) done.

Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.

Suspending console(s) (use no_console_suspend to debug)

 

Could you please give me some suggestion? Many thanks!

  • In am35x platform there is no keypad connected to the wake up domain. So wake up is not possible by pressing keys.

    So power management is disabled by default in TI DevKit v2.2 release for am35x platform.

    One workaround to wake up the device would be like this

    1) Press Enter on Console so that Kernel would wake up for a moment

    2) Press Any Key on the keypad so that Android Layer will wake up and The Screen Gurd will show up.

    Regards,

    Arun

     

  • Hi Arun,

    Many thanks for your help!

  • Hi Arun,

    I  replaced init.rc by init_pm.rc following TI-Android-FroYo-Devkit-V2.2UserGuilde.pdf,  and enable PM.

    But the belowing doesn't work,

    1) Press Enter on Console so that Kernel would wake up for a moment

    2) Press Any Key on the keypad so that Android Layer will wake up and The Screen Gurd will show up.

    So could you please tell me what the matter is. Thank you.

  • Hi Gino,

    The Actual problem is like this.

    1) In AM3517 EVM, The Keypad (and also touchscreen) is not connected to the wake up domain. So there is no way to wake up the kernel via keypad.

    2) Console events can wake up the kernel, but the console events are not reaching the Android Power Manager Layer.

    3) For the Android System to wake up, The power manager service need to fetch an Event and a Wakelock need to be created to prevent the system to go suspend again.

    So I suggested the above workaround and it worked for me.

    In init_pm.rc, the option "hw.nopm" is set to false and gives necessary permissions to /sys/power/state entry.

    Can you please tell me what are you getting when you try to wake up the system?

    Regards,

    Arun

     

     

     

  • Hi,

    Logic PD release their new Wattson software for the AM3517 EVM today which will help you see actual power consumption across all power rails on the CPU and SOM design.  There is an adapter required to connect to the PC available from this website: http://createnewstuff.webs.com/breakoutboardwattson.htm

    The Logic PD software is available from here: http://www.logicpd.com/wattson

    -A