Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

  • State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 41 subscribers
  • Views 221 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC3235SF: Waking up CC3235SF device from LPDS via GPIO works but not as expected.

Darpan Noel DSouza
Intellectual 685 points
Part Number: CC3235SF

Hi,

I have implemented LPDS functionality on the mentioned device, I have different callbacks for LPDS wake up and another for GPIO trigger. The device works fine most of the time, it is just when waking up from GPIO I need to disable the Power Policy in its callback and re enable it else where.

I do not know when would be the ideal situation in order to re enable the power policy, could you recommend a solution.

Thanks.

Noel.

  • 0
    TI__Mastermind 38980 points

    Hi Noel,

    The power policy has both a resumeLPDSHookFxn and wakeupGPIOFxnLPDS parameter. The resumeLPDSHookFxn always triggers when the device wakes from LPDS, and then after the peripherals are restored, wakeupGPIOFxnLPDS will execute if the wake cause was GPIO (instead of NWP or scheduling).

    In the Thermostat TI Design, I have three callbacks. I use wakeLPDSFxn as the resume hook to post a semaphore to trigger a sensor read, since I want that to happen every time I wake up. The design has a GPIO PIR, and whenever that is the wake cause, gpioWakeFxn will then turn on the LCD screen. I also have a regular GPIO interrupt for the PIR that triggers the gpioPIRFxn callback, and I turn this interrupt off and on periodically so it's not constantly triggering.

    Why do you need to disable the power policy? When the MCU wakes, it should finish executing the wake functions, and then the scheduler will determine if the MCU can go back to sleep. If you want to stay awake for some period of time (maybe you're waiting for sensor data), I suggest starting a hardware timer, since the MCU cannot enter LPDS until the timer is stopped.

    Best regards,

    Sarah