sd_ble_gap_conn_param_update error 8

RE: sd_ble_gap_conn_param_update error 8

Ole Bauck — Thu, 19 Jan 2017 10:27:54 GMT

Great that you found the cause of the problem (and the solution)! I will tell the developers that this needs to be looked at.

RE: sd_ble_gap_conn_param_update error 8

vea45 — Thu, 19 Jan 2017 07:49:14 GMT

Ok I tested the solution proposed by this post: devzone.nordicsemi.com/.../

And now it works! The problem was a timeout timer that executes inmediately after some time... I got my board running for 24h without any errors so I think that the timer library was the problem.

This is the timer.c file with the proposed fixes by the other post applied on the SDK 12.2: app_timer.c

RE: sd_ble_gap_conn_param_update error 8

vea45 — Wed, 18 Jan 2017 14:35:23 GMT

The timeout connection handler... The other times the timer works well...

static void connection_timeout_handler(void * p_context){
            UNUSED_PARAMETER(p_context);
        	  uint32_t err_code = sd_ble_gap_disconnect(m_conn_handle, BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION);
            APP_ERROR_CHECK(err_code);
        		timeout_timer_running=false;
        }

RE: sd_ble_gap_conn_param_update error 8

vea45 — Wed, 18 Jan 2017 14:34:38 GMT

Omg... Now I discovered that I have a connection timeout that executes instantly when someone establishes a connection. This timer is started when the connection starts (BLE_GAP_EVT_CONNECTED) and it kills the connection if the phone gets stuck with it... but is configured to kill the connection after 50 sec and this number is a constant so I don't know why this timer randomly executes insantly, any ideas?

#define TIMEOUT_CONNECTION	APP_TIMER_TICKS(50000, APP_TIMER_PRESCALER)

case BLE_GAP_EVT_CONNECTED:
m_conn_handle = p_ble_evt->evt.gap_evt.conn_handle;
	if (first_time){
		err_code= app_timer_start(m_timeout_timer_id, FIRST_TIMEOUT_CONNECTION, NULL);
	}else{
		err_code= app_timer_start(m_timeout_timer_id, TIMEOUT_CONNECTION, NULL);
	}
	timeout_timer_running=true;
	APP_ERROR_CHECK(err_code);
	led_write_handler_led(1,LED_RED_CH);
break;

RE: sd_ble_gap_conn_param_update error 8

vea45 — Wed, 18 Jan 2017 14:21:45 GMT

doing this the parameters update timer never starts and it works as "normaly" I can connect to it without problems the first times... The only change is that now I'm facing exactly the same behaviour but the error appears on another function "sd_ble_gatts_exchange_mtu_reply()" inside the "BLE_GATTS_EVT_EXCHANGE_MTU_REQUEST" event, also with error 8...

RE: sd_ble_gap_conn_param_update error 8

vea45 — Wed, 18 Jan 2017 14:19:44 GMT

I'm using the SDK library. The only modification is the one that I posted here (the added condition on the 'if'). Now I'm trying to find the source of the error and I blocked the parameters update (I read on another post that this can be done safely) commenting those lines on the same file inside the function "conn_params_negotiation(void)"

if (m_update_count == 0){ // First connection parameter update timeout_ticks = m_conn_params_config.first_conn_params_update_delay; }else{ timeout_ticks = m_conn_params_config.next_conn_params_update_delay; }

       /* err_code = app_timer_start(m_conn_params_timer_id, timeout_ticks, NULL);
        if ((err_code != NRF_SUCCESS) && (m_conn_params_config.error_handler != NULL)){
            m_conn_params_config.error_handler(err_code);
        }*/

[...]

RE: sd_ble_gap_conn_param_update error 8

Ole Bauck — Wed, 18 Jan 2017 14:04:01 GMT

Ok, I thought you used the sd_ble_gap_conn_param_update(..) directly in your code and not the SDK library.

I checked and the only time sd_ble_gap_conn_param_update(..) will return error NRF_ERROR_INVALID_STATE (0x8) is if the device is not in a connection. The only explanation I can think of as to why you get this error code is that the peer has disconnected, but the application has yet not gotten the disconnected event or have not executed the code that is to be run on disconnect (the event is pending because other interrupts at equal or higher level has to be executed first). So the SoftDevice knows that the connection is lost, but the application don't.

I assume that you have not altered the SDK library code (ble_conn_params).

RE: sd_ble_gap_conn_param_update error 8

vea45 — Tue, 17 Jan 2017 13:09:51 GMT

Nope, inside ble_conn_params.c -> update_timeout_handler() I forced to check again the m_conn_handle but the error appears appears when the device is connected.

static void update_timeout_handler(void * p_context)
{
    UNUSED_PARAMETER(p_context);

    if (m_conn_handle != BLE_CONN_HANDLE_INVALID)
    {
        // Check if we have reached the maximum number of attempts
        m_update_count++;
        if (m_update_count <= m_conn_params_config.max_conn_params_update_count)
        {
            uint32_t err_code;

            // Parameters are not ok, send connection parameters update request.
            err_code = sd_ble_gap_conn_param_update(m_conn_handle, &m_preferred_conn_params);
            if ((err_code != NRF_SUCCESS) && (m_conn_params_config.error_handler != NULL)&& (m_conn_handle != BLE_CONN_HANDLE_INVALID))
            {
                m_conn_params_config.error_handler(err_code);///error here!
            }
        }
        else
[...]

RE: sd_ble_gap_conn_param_update error 8

Ole Bauck — Tue, 17 Jan 2017 11:49:27 GMT

You probably get the invalid state error because you are not in a connection. Add a check for the connection handle:

if (m_conn_handle != BLE_CONN_HANDLE_INVALID)

To check if you are in a connection, or disregard the error code returned from the function.