带有几个来源的唤醒定时器

Hi gbmej,

I am not sure i get exactly the point, the part that you mentioned when you get the lock confused me a bit, tried to replicate what you mentioned, i ve done the following test in the hrp_sensor which allready implements one wake up source. The "static" wake up source is triggered LOW and the default pin configuration is PULLUP the changing wakeup source (the one that changes configuration in the interrupt routine) has initially the same pollarity, and the code that performs the change is attached below.

//Global variables

__RETAINED HW_GPIO_MODE my_gpio_mode = HW_GPIO_MODE_INPUT_PULLUP;
__ retated hw_gpio_func my_gpio_function;

静态void wkup_cb（空白）
{

#if dg_configBLACK_ORCA_IC_REV == BLACK_ORCA_IC_REV_A
hw_wkup_reset_counter（）;
#endif
hw_wkup_reset_interrupt();
hw_gpio_get_pin_function（cfg_start_advertising_trigger_1_gpio_port，cfg_start_advertising_trigger_1_gpio_pin，＆my_gpio_mode，＆my_gpio_function）;
if（my_gpio_mode == hw_gpio_mode_input_pulldown）{
my_gpio_mode = HW_GPIO_MODE_INPUT_PULLUP;
} else {
my_gpio_mode = HW_GPIO_MODE_INPUT_PULLDOWN;
}
hw_gpio_set_pin_function(CFG_START_ADVERTISING_TRIGGER_1_GPIO_PORT, CFG_START_ADVERTISING_TRIGGER_1_GPIO_PIN, my_gpio_mode, HW_GPIO_FUNC_GPIO);

hw_wkup_configure_pin(CFG_START_ADVERTISING_TRIGGER_1_GPIO_PORT, CFG_START_ADVERTISING_TRIGGER_1_GPIO_PIN, true,
my_gpio_mode！= hw_gpio_mode_input_pulldown？hw_wkup_pin_state_low：hw_wkup_pin_state_high）;

hw_cpm_trigger_sw_cursor(); //this will help identify the interrupt in the power profiler with a thin red line each time the interrupt triggers
hrp_wkup_cb();
}

在periph_init（）：

hw_gpio_set_pin_function(CFG_START_ADVERTISING_TRIGGER_1_GPIO_PORT, CFG_START_ADVERTISING_TRIGGER_1_GPIO_PIN, my_gpio_mode, HW_GPIO_FUNC_GPIO);

As long as you trigger the interrupt and then release the line from the triggered state both of the interrupts occur as they should, please check how the change is performed on the snippet above and how the wake up condition of the pin is configured based on the default state of the pin, hw_gpio_get_pin_function() used to check the default pin configuration hw_gpio_set_pin_function() is used to set the proper default pin state (opposite from the previous interrupt hit).

Thanks MT_dialog

Hi gbmej,

You mean that there is no interrupt while the M0 is executing ISR of a button press ? Is that correct ? This doesn't have to do with the wake up controller but how the M0 and the NVIC operates, if the processor gets an interrupt while there is another interrupt executing the interrupt handler, since both interrupts have the same priority the pending interrupt flag will be set to 1 and as soon as the previous ISR gets executed it will be invoked again to serve the pending interrupt, and as far as i have tested this is exactly what the 68x does.

Now in your case i see that your pins are configured with the internal resistors in pulldown and pullup, i can imagine that this is the reason for the interrupts to lock, perhaps in case that the external device is not properly driving the line in a specific state the pullups will take place and keep the interrupt signal for the wake up controller asserted for at least one pin source which i suppose is the one that toggles its state, and this is enough for no interrupts to occur and the wake up controller to wait for the interrupt to be asserted before reporting another interrupt. So you can try to either not to use the internal pull ups in case you are certain that the external sensor is driving the lines properly, or if you would like to use the internal resistors you should alter the default state of the resistor to the opposite of the state that will trigger the wake up, something like i have mentioned in my previous post, using the hw_gpio_set_pin_function() in order to change the default pin configuration.

Thanks MT_dialog