Determine the interrupt source of wkupct_register_callback

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.wsdof.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.

2 posts / 0 new

Last post

Wed, 2017-06-07 10:29

jackiechau

Offline

Last seen:3年5个月前

加入ed:2016-01-15 01:32

Determine the interrupt source of wkupct_register_callback

I implemented wkupct_register_callback() and wkupct_enable_irq() to wake up BLE by an external interrupt pin. If more than 1 interrupt pins are configured in wkupct_enable_irq(), how can I determine which interrupt pins trigger the interrupt API? That means how to read the interrupt status. Thanks.

Device:

DA14583

Wed, 2017-06-07 16:02

MT_dialog

Offline

Last seen:2 months 3 weeks ago

加入ed:2015-06-08 11:34

嗨jackiechau,

There is no register that will indicate the port/pin that the interrupt occured, what you can do in order to check the source of the pulse is to read the status of the pin right after the device has been awaken.

Thanks MT_dialog