BLE Busy status VS Insufficient resources and maximising throughput with multiple notifications.
Hey everyone,
I am trying to send out two different characteristic notifications, one after the other and I am getting error 0x93 (BLE_STATUS_BUSY) in return for the second characteristic update, It then takes at least 100mS (often a lot more than this) before I am able to update the second notification. I am assuming that this is a limitation of the underlying BLE stack but can't find any information of what causes a busy status.
When just updating a single characteristic, I get often get an 0x64 which I can easily recover from by listening for the gatt tx pool available event, however I can't find a way of knowing when the second CPU is no longer busy.
Any other tips on optimising throughput when updating multiple characteristics would be greatly appreciated.