- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I have often seen, that the CyBle_ProcessEvents() function is called in the main loop to process the BLE stack work. But in my situation, the cycle time highly depends on the external peripheral and can take more time than my connection interval. So I have to call the CyBle_ProcessEvents() function minimum twice. Right now, I tried to call this function in a timer ISR where my timer period represents an average between the minimum and maximum connection interval. So are there any disadvantages for me or why is it not implemented in any example code?
Thanks!
Solved! Go to Solution.
- Labels:
-
BLE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
You need to call CyBle_ProcessEvents() once every connection interval. If any custom function consumes more time for execution, call CyBle_ProcessEvents() inside it as well.
-Sayani.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
You need to call CyBle_ProcessEvents() once every connection interval. If any custom function consumes more time for execution, call CyBle_ProcessEvents() inside it as well.
-Sayani.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
ofcourse, I could do that, but what is said against calling the function from an ISR? In my opinion this should be the most efficient way do ahndy BLE stack events!
Regards