DEADBEAF from src\ll_ctrl.s0.c

[SHTILL]

I use softdevice s110 7.3.0 and SDK version 7.2.

Some times softdevice call app_error_handler with: error_code 0xDEADBEEF line num - 990 file_name - src\ll_ctrl.s0.c

I can't recognize why that happens. softdevice call app_error_handler after i try to disconnect form device and delete bond information.

This is my code:

err_code = dm_device_delete_all(&m_app_handle);	 
APP_ERROR_CHECK(err_code);

if( m_conn_handle == BLE_CONN_HANDLE_INVALID )return NRF_SUCCESS;

err_code = sd_ble_gap_disconnect(m_conn_handle, BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION);	

if( err_code != NRF_ERROR_INVALID_STATE )
{
	APP_ERROR_CHECK(err_code);
}
return NRF_SUCCESS;

[Susheel Nuguru]

Did you make sure if all the interrupts configured by your app are either APP_PRIORITY_LOW?

[SHTILL]

I understood why and when such error occur.

In my application device periodically starts Connection Update Procedure.

I use 2 sets of connection parameters.

First one have connection min connection interval 90ms and max connection interval 110ms.

Second one have connection min connection interval 1450ms and max connection interval 1550ms.

It takes quite long time to change connection interval from 1450ms to 90ms.

When I call sd_ble_gap_disconnect while Connection Update Procedure has not been finished error occur.

When Connection Update Procedure is in progress and try to disconnect from Master Controll Panel the reason of disconnection is quete strange:

[Susheel Nuguru]

that should not create a softdevice assert in my opinion. I will investigate it further.

[SHTILL]

I use no interrupt in that project in my own code. But I use gpiote and app_timer library from SDK. But in other project I use sd_nvic_EnableIRQ to enable interrupts. As I suppose sd_nvic_EnableIRQ should return error if interrupt isn’t configured as APP_PRIORITY_LOW.

[SHTILL]

I noteced nor more thing. I use Master Controll Panel to communicate with my device.

When Connection Update Procedure is in progress and I try to disconnect from Master Controll Panel reason of disconnection is quite strange: Lost connection to device. Reason: BTLE_STATUS_CODE_LMP_RESPONSE_TIMEOUT.

And when Connection Update Procedure isn't in progress reason is obvious: Lost connection to device. Reason: BTLE_LOCAL_HOST_TERMINATED_CONNECTION.