Problem while suspend/resume RRS feed

  • Question

  • Hai Gurus,

    OS Platform : Windows Embedded Handheld 6.5

    HW Platform : OMAP3430

    Problem : Using an application performing Suspend/Resume cycle for 1200 cycles continuously. Device is hanging randomly after around 600 cycles sometimes earlier. Debugged using KITL, sometimes it is failing at the exit of display driver and other time in Battery driver exit. 

    Few occasions hanging without display during suspend and other occasions during resume. If say 12 devices are under test, randomly 2-3 devices fails, rest are passing.

    So while doing reliability testing (around 1200 cycles) only it is failing.

    Please throw us some light on where to suspect.

    With Regards,


    Tuesday, November 5, 2013 1:35 PM

All replies

  • I assume that the suspend you are trying after the device is fully resumed.

    If not increase the delay subsequently between suspend and resume to happen properly or check the device state before sending suspend/resume command.

    If the issue is still persisting i guess you need to debug this two drivers (Battery an display) for that you have to find which instruction is failing

    May be something you are doing in suspend which you are not undoing in resume or there could be other possibilities which may be H/W specific 

    Hope this may give you some help to resolve the issue.

    --- Misbah

    Senior Design Engineer T.E.S Electroni Solutions (Bangalore-India)

    • Marked as answer by ArunRM Wednesday, November 6, 2013 12:31 PM
    • Unmarked as answer by ArunRM Wednesday, November 6, 2013 12:48 PM
    Wednesday, November 6, 2013 5:20 AM
  • Thanks for the inputs.

    I have few clarifications from your reply.

    1. How do we check whether it is completely resume. Hope using the Device power state.

    2. Using KITL for placing more logs to find the issue. Is there any limitations to the KITL debugging that it may not be able to help in identifying the instruction where it is failing. Or any other effective debugging mechanism available.

    3. Any specific pointers on H/W specific would help to define the test case and hence locating the issue.

    And also we have increased the delay but it is still failing.

    With Regards,


    Wednesday, November 6, 2013 12:38 PM
  • Hai Gurus,

    Appreciate for any updates for the request.

    With Regards,


    Wednesday, November 13, 2013 8:38 AM

  • GetSystemPowerState() is what you need to make sure system has resumed properly.

    Build the OS in debug mode Enable kernel debugger while downloading the image. This will give most of the debug message.

    You need to check the power manageable devices and oem implementation "oem_pm.c" and "power.c"

    If you are sure where is the problem just put debug messages at those corresponding power manageable drivers and oal implementations 

    For H/W related issues you need to figure out which power management policy is implemented in your BSP like TI's Smart reflex etc and check if save and restore are happening properly or not.

    --- Misbah

    Senior Design Engineer T.E.S Electroni Solutions (Bangalore-India)

    Wednesday, November 13, 2013 11:15 AM