I have a project based on SimplePeripheral from BTStack 2.1. It was working fine until additional characteristic attributes' notification are enabled. There is no problem when only one characteristic attribute's notification is enabled, but when the 2nd attribute's is enabled (after the 1st one), the abort ICall message (see attached) will come and freeze the runtime. The abort ICall message doesn't come immediately but rather 5s after the 2nd attribute notification is enabled. There is no data transfer between central (iPhone) and peripheral (SmartRF06) during the test - just enabling notification. The central side receives the correct notification enable responses. The gatt attribute table for the service is triple checked to be setup correctly.
Questions:
1/ Any idea what could be wrong?
2/ I assume the abort is coming from the BLE stack. How do I know the reason of the abort?
../ming
