And also does the ble callback(conencted, disconnected, data received, .etc) execute in ble interrupt context or execute in rwip_schedule(main context)?
Device:
⚠️
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.
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.
Hi cgha,
Timer callback and BLE messages are generated from low-level interrupts, the BLE stack handled them and manage them as a message queue with rwip_scheduler. Thus from a user view, you can see them as in the main context.