I'm using Wiced SDK 3.7 with a BCM943341 WiFi/BT combo chip.
We have a FreeRTOS based OS and is starting the BT stack in order to be open for connections from the outside.
When the BT stack is active, it causes a context switch every 100ms. I previously measured this incorrectly, getting >50
context switches per second which seemed a bit high. I guess I can't really complain about 10 switches/s, but is there something
in the BT protocol that really requires this? Can't it be handled interrupt driven?
(This is when BT is connectable, but neither connected, discoverable nor advertising. BLE is adverting on a LOW setting, but is not connected.)
For your query in the BT protocol that really requires this? Can't it be handled interrupt driven?
A) It can't be changed to interrupt driven. BT thread can't be configured for the same.