RTOS/CC2640R2F: Default spinlock

Hey Zhiwen,

What SDK version are you using?

Also, do you have a sniffer capture of the fail case?

I suggest you also follow these guidelines: software-dl.ti.com/.../ble-debugging.html

I'm using multi_role example of the blestack in simplelink_cc2640r2_sdk_1_40_00_45.I don't have a sniffer capture of the fail case.In the default project,it regists an AssertHandler.When occur the problem,it print "***ERROR*** >> DEFAULT SPINLOCK!".

Zhiwen,

Are you trying to use BLE5 or BLE4.2?

If BLE4.2, do you see the issues with SDK v1.50.00.58?

Also, when you receive the spinlock in debug mode, can you pause the system and send me a picture of what your call stack looks like leading into the spinlock?

I'd like to stress that a sniffer capture could be really helpful in debugging this.

Zhiwen,

I'll look into this some. Can you please send me a picture of your call stack when you pause the program after it reaches spin lock? May look something like this:

I'm so sorry that my english is so bad.I can not see your picture or download your picture.Is it your mean that I should debug my program and add a breakpoint at AssertHandler funtion and wait for the program reaches spin lock and then take a picture to you?I try to do it.but when reaching spin lock ,it warning
:Cortex_M3_0: JTAG Communication Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 7.0.188.0)
Cortex_M3_0: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging;

so I can not enter the breakpoint and can't found the bluetooth device.

Zhiwen,

Your English is great! Don't be concerned about that.

I'm sorry, I'm not sure why you can't see the picture I linked. Basically, when you reach a spinlock in debug mode, click pause, and tell me what your callstack looks like underneath the section that says "project_devicename_app" > "Texas Instruments XDS110 USB Debug Probe...". Can you provide that?

You may be running out of Heap, have you used the HEAPMGR to debug if there are any heap failures?
software-dl.ti.com/.../ble-memory_problems.html

Zhiwen,

That's great! Can you send me the same set of pictures with the optimization level set to 0? You can do this by going to properties>build>arm compiler>optimization>optimization level

What this will do is it will give us more details in the call stack to see what specifically in the call stack led to the HAL Assert.

Interesting, did you refer any to the documentation on heap manager metrics?
Have you used the HEAPMGR to debug if there are any heap failures?
software-dl.ti.com/.../ble-memory_problems.html

Thank you!I have changed the UUID.I am trying to find out the reason which occur this issue.

Thank you for you help!The reason occured this issue is heap.

It has error in simpleProfileAttrTbl table in simple_gatt_profile.c of multi_role project.it only has 5 attribute in simpleProfileAttrTbl table in my own application,but SERVAPP_NUM_ATTR_SUPPORTED default is 17,I haven't changed it.