KW45B41Z83- BLE stack hanging after sometime

[jaimy_v]

We are using a custom board with KW45B41z83 module. The board is used as peripheral and connects with Android phone app. When run for long intervals or after repeated connect/disconnect, sometimes the BLE stack seems to hang. It does not happen always, but occurs in random. Other tasks in the code are running.

In code it is waiting inside BluetoothLEHost_HandleMessages in 

OSA_EventWait((osa_event_handle_t)mAppEvent,

osaEventFlagsAll_c,

(uint8_t)FALSE,

gAppTaskWaitTimeout_ms_c ,

&event);

gAppTaskWaitTimeout_ms_c was initially defined as osaWaitForever_c.

Later we changed this to 100s and we saw that it is getting timed out.

Could you help us to debug the issue. We are using the lib_ble_OPT_host_peripheral_cm33_gcc.a lib

[luis_maravilla]

Hello,

Could you help us share details about what does your BLE stack hang mean? Could it refer to a loss of transmission, packet loss, interrupt connection?

Are you using an SDK example as a base for your project? Could you help us confirm if you can run an example code without modifications from the latest SDK and replicate this issue?

Could you help confirm about how did you implement the change from [osaWaitForever_c] to gAppTaskWaitTimeout_ms_c 1000?

Best Regards

Luis

[jaimy_v]

Hi,

The SDK example we have taken is wireless_examples - bluetooth- eatt_peripheral-freertos.

[jaimy_v]

Hi,

BLE stack is hanging - we are not able to disconnect/reconnect the device. No data is being received. There is no event in mAppEvent and it is waiting forever.

We modified gAppTaskWaitTimeout_ms_c in app_preinclude_common.h. We are using SDK example as base, but have modified it for our application. We wanted to know how we can debug to know where it was getting stuck. Is there any place we can check in BLE stack to know what could be going wrong.

[luis_maravilla]

Hello,

Could you help us test the example without modifications and let us know if you observe the same behavior?

Since you are using the eatt_peripheral_freertos example, please note that the expected responses for data reception are displayed on the board running the EATT Central example.

For more information on the expected terminal outputs for both EATT Central and EATT Peripheral roles, please refer to the Bluetooth Low Energy Demo Applications User’s Guide Chapter 5.4 and 5.5

If possible, could you help us verify the behavior by testing with another board running the EATT Central example instead of the mobile app?

Could you help us share the modifications implemented for gAppTaskWaitTimeout_ms_c?

Best Regards

Luis