• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 493 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

SGX core and suspend

DavidVescovi
Genius 5470 points

Other Parts Discussed in Thread: OMAP3530, OMAP3503

I can build the standard image (A8_1.00.00) and load it on to my EVM.

Everything works fine and I can suspend (from UI suspend menu) and then wake back up by taping the LCD.

I noticed if I remove the SGX Core components everything also builds and runs fine except after I suspend I can not wake back up by taping the LCD screen.

Why should the tap wake be dependent on the PowerVR component? I would like to suspend/resume on a 3503 w/LCD and touch which does not have DSP or PowerVR.

At first  I suspected it might have more to do with the save/restore than the tap interrupt itself but this does not appear to be the case as a keyboard press (button) still does wakes from suspend just fine. 

I can not locate in the code just where the touch wake interaction occurs?

  • 0
    TI__Expert 4155 points

    David,

    The expected behavior on OMAP3530 chips with/without PowerVR is:

    When the system is suspended, the chip goes to OFF mode. The wakeup resource can be "PWR_ON" key, RTC wakeup.

    Tapping on LCD is not expected to wake up the system if the chip is in OFF mode on Mistral EVM.

    The reason is when chip is in OFF mode, only wakeup domain is active. Only the GPIOs belong to GPIO bank 1 (which is in WAKEUP domain) can wake up the system.

    What EVM did you use for the test without SGX? Any key from the keypad can wake up the system, correct?

     

    For OMAP3503 with SGX core component built in, I am suspecting the chip does not go to OFF mode.

    One way to verify without instrumentation code is to measure the VDD1 and VDD2 current and voltage. In OFF mode, VDD1 and VDD2 current/voltage should drop to 0.

    The following wiki page gives you the information on how to do the measurement on Mistral EVM revG.

    http://processors.wiki.ti.com/index.php/WinCE-TIBSP_Power_Management

     

    -Tao

     

     

  • 0 in reply to Tao Zhang
    Genius 5470 points

    You may be right. I am using an older 3530 EVM (not rev G) to test that could be the problem. (I can not afford a new one being unemployed).

    I know the older revs had silicon issues (mine has 3530 ES2.1). I was using the standard A8_1.00.00 OSDESIGN (only slightly modified) to test with. With std OSDESIGN build it does appear to be going into suspend as all LEDs go out (LAN link, MMC VCC etc.) I can wake by touching LCD.

    I then unchecked the "SGX Core Revision 121 and 125" catalog components and rebuilt. It also works correctly and appears to go into suspend (leds off etc) but can not wake with LCD tap.

    In both cases any keypad key press wakes.

    So present theory is first case it never really went to full "off" but second case it did?

  • 0 in reply to DavidVescovi
    TI__Expert 4155 points

    David,

    You are right that keypad key press can wake up the system from OFF mode.

    The behavior is controlled by a registry setting "EnableWake" in tps659xx_keypad.reg.

    In the current ARM_A8 release, it is enabled.

     

    " So present theory is first case it never really went to full "off" but second case it did?"

    Yes, you can prove the theory by measure the voltage.

    It is not clear for me why 3503 + PowerVR module breaks the suspend/resume functionality.

    Thanks,

    Tao