CCS/CC2650: CC2650

Hi Roshan,

Can you give a little more context?
- What BLE state is the device in when you call this function?
- How does the devList[] variable look when you're calling the function?

Can you try to use breakpoints and step through the code to determine where it goes to spin-lock

Hi Marie,
- What BLE state is the device in when you call this function?
Answer :- BLE state is " device discovery complete".
calling from switch case "GAP_DEVICE_DISCOVERY_EVENT:" in function SimpleBLECentral_processRoleEvent

- devList[] variable has my BLE Peripheral (SLAVE) address

- When i call SimpleBLECentral_connectToFirstDevice(); function
if it is in "connecting" state for long then only i get below error
>>>STACK ASSERT
***ERROR***
>> DEFAULT SPINLOCK!

my peripheral (slave) advetises for every 10 min, and central checks whether slave is advertising continously, if yes then only i call function SimpleBLECentral_connectToFirstDevice(); and connect with slave and then disconnect, then after few minutes again check weather slave is advertising, if yes connect and disconnect and so on.

Above things works fine for some duration properly, after some duration
my central will be in "connecting" state for long and enters into below error
>>>STACK ASSERT
***ERROR***
>> DEFAULT SPINLOCK!

Please help me to resolve above issue.
Can you just suggest me some alternative ( or ideas) to resolve above issue.

Hi Marie,

if my BLE Central in "Connecting" state for long, then how can I come out of the "Connecting" state.

Please suggest me some ideas to come out of the "Connecting" state.

Thanks
Roshan

Hi Marie,
I commented //RegisterAssertCback(AssertHandler);
This resolved my issue.

Hi Roshan,

It sounds like you're only masking the problem (by commenting out the assert handler callback).