Processor not waking up from sleep when running from RAM

你好,谢谢你的回应。PFB details:

SDK版本:6.0.12。1020
低Power Clock : LP_CLK_RCX20
睡眠模式:ARCH_EXT_SLEEP_ON
Below 3 pins are configured as wakeup source:
[GPIO_PORT_0, GPIO_PIN_0]
[GPIO_PORT_0, GPIO_PIN_1]
[GPIO_PORT_0, GPIO_PIN_3]

Thanks, AA

Hi,

Thanks for the response. I have gone through the example projects. My usecase is slightly different: During inactivity (when the ADC shows flat data), I want to put the processor into extended sleep mode by keeping the BLE core active. Then, use a GPIO interrupt to wakeup the prcoessor from extended sleep. In the implementation, the main loop returns GOTO_SLEEP when the process is inactive (when the ADC shows flat data) for sometime. Then the callback function registered in WKUPCT driver is responsible for changing the return to KEEP_POWERED such that it can wakeup the processor from extended sleep. As I described in the initial post, it works fine when when debugging using JTAG. When running from RAM, it goes to sleep and the wakeup interrupt is not getting triggered once it enteres sleep.

Let me know if additional details are required for helping me out!

Thanks in advance!

Hi,

Please find below answers:

>>>>> Can you please clarify this statement? So, do you need to put the device into sleep mode and keep advertising? If app_default_sleep_mode is set to ARCH_EXT_SLEEP_ON in user_config.h file, then the device will go to sleep mode between advertising intervals and will wake-up automatically via the BLE timer.

- Yes, I want to put the device into sleep mode and keeep advertising (Let the BLE timer wakes-up the device automatically for advertising) That is why I chose ARCH_EXT_SLEEP_ON setting but the application code decides when to put the device into sleep mode. Also the application wants to wakeup the processor from extended sleep using GPIO interrupt.

>>>>>> Does the device stop advertising and sleep permanently?

- No, it does not stop advertising (that confirms the BLE timer is able to wake-up the device periodically) but the GPIO interrupt is not getting triggered and hence the application is not able to change the main loop retrun from GOTO_SLEEP to KEEP_POWERED.

>>>> Where and how the WKUP controller is configured?

- The application detects inactivity for 5 seconds and then returns GOTO_SLEEP from main loop. Before this, it configures the WKUP controller such that the GPIO interrupt can wake the device up on activity. If an interrupt is triggered it changes main loop return to KEP_POWERED so that the processor can wake-up.

/* callback function (Registered in WKUPCT driver) */
static void app_on_wakeup_cb(void)
{
wkupct_disable_irq();
sleep_interrupted = true;
}

/* Sets SW1 as wakeup trigger. This function gets called when the application has been idle for 5 secs. */
void sc_int_config_irq(void)
{
wkupct_disable_irq();

wkupct_register_callback(app_on_wakeup_cb);
wkupct_enable_irq(WKUPCT_PIN_SELECT(SW_1_PORT, SW_1_PIN),
WKUPCT_PIN_POLARITY(SW_1_PORT, SW_1_PIN, WKUPCT_PIN_POLARITY_HIGH),
1,
10);
}

>>> Can you replicate this if the device boots from SPI Flash?

- I haven't tried it yet.

The reason why I wanted to put the device into sleep and wake it up this way is because, I want to turn OFF peripherals like ADC & LED during inactivity and turn them back ON during activity.

Let me know if there are further questions. Thanks.