Reset during connection setup

RE: Reset during connection setup

DanKA — Mon, 23 Apr 2018 08:37:39 GMT

Thank you very much for your answer. The searching for 0x3401 helped me.

I noticed that BLE_GATTS_EVT_SYS_ATTR_MISSING was already in on_ble_evt() and i never entered it:

        case BLE_GATTS_EVT_SYS_ATTR_MISSING:
            // No system attributes have been stored.
            NRF_LOG_INFO("System Attribute missing \r\n");
            err_code = sd_ble_gatts_sys_attr_set(m_conn_handle, NULL, 0, 0);
            APP_ERROR_CHECK(err_code);
            break; // BLE_GATTS_EVT_SYS_ATTR_MISSING

I added these lines at BLE_GAP_EVT_CONNECTED:

        case BLE_GAP_EVT_CONNECTED:
            NRF_LOG_INFO("Connected\r\n");
            bsp_board_led_on(CONNECTED_LED_PIN);
            bsp_board_led_off(ADVERTISING_LED_PIN);
            m_conn_handle = p_ble_evt->evt.gap_evt.conn_handle;
            
            // set system attributes
            NRF_LOG_INFO("Set system attributes\r\n");
            err_code = sd_ble_gatts_sys_attr_set(m_conn_handle, NULL, 0, 0);
            APP_ERROR_CHECK(err_code);
            
            err_code = app_button_enable();
            APP_ERROR_CHECK(err_code);
            break; // BLE_GAP_EVT_CONNECTED

Now, the scenario above results NRF_ERROR_INVALID_STATE because the CCCD was not written. But i can check for that with adding BLE_GATTS_EVT_WRITE to on_ble_evt():

        case BLE_GATTS_EVT_WRITE:
            on_write(p_ble_evt);
            NRF_LOG_INFO("A Write Event \r\n");
            break; // BLE_GATTS_EVT_WRITE

With on_write(..) to indicate that everything is set up and to enable the app_button:

static void on_write(ble_evt_t * p_ble_evt)
{
    ble_gatts_evt_write_t * p_evt_write = &p_ble_evt->evt.gatts_evt.params.write; // Prüfen, ob CCCD beschrieben ist
    if ((p_evt_write->handle == m_lbs.button_char_handles.cccd_handle)){
        bsp_board_led_on(CONNECTED_LED_PIN);
        bsp_board_led_off(ADVERTISING_LED_PIN);
        err_code = app_button_enable();
        APP_ERROR_CHECK(err_code);
    }
}

RE: Reset during connection setup

Susheel Nuguru — Fri, 20 Apr 2018 18:44:20 GMT

Hi Dan,

This error is well documented and there is a thread here in devzone that will explain more about it.

You can read more about it here

You need to add the below code in the ble event handler to fix this problem

case BLE_GATTS_EVT_SYS_ATTR_MISSING:
        err_code = sd_ble_gatts_sys_attr_set(m_conn_handle, NULL, 0);
        APP_ERROR_CHECK(err_code);

RE: Reset during connection setup

DanKA — Wed, 18 Apr 2018 10:25:54 GMT

Hi Aryan,

i am afraid i misunderstand you and/or need a little help. I started the project in debug mode (defined DEBUG and no optimazations) and set the breakpoint app_error_handler() / app_error_save_and_stop in the app_error.c file.

I get:

p_file_name = "main.c"
line_num = 501 --> that's the line where APP_ERROR_CHECK is called within the button_event_handler()
err_code = 13313 (0x3401):
NRF_ERROR_STK_BASE (0x3000) + 0x400 -->
NRF_GATTS_ERR_BASE (0x3400) + 1 -->
BLE_GATTS_SYS_ATTR_MISSING (0x3401)

So these are no new Information compared to NRF_LOG. Here is a screenshot:

Could you please guide me where to place the breakpoints correctly?
How do i check for BLE_GATTS_SYS_ATTR_MISSING equivalent to as we did for the invalid handle with if(m_conn_handle != BLE_CONN_HANDLE_INVALID)*?

*even if i do not check for invalid handle, i get err_code = 13313.

Thank your very much in advance

RE: Reset during connection setup

Susheel Nuguru — Tue, 17 Apr 2018 12:28:32 GMT

Hi Dan,

It is quite easy to debug set a breakpoint at the app_error_handler and see which line caused this error.

The answer I gave you in my last post is a fix for one bug we saw. And I realized it within few minutes of setting the breakpoint at everyplace in project that has NVIC_SystemReset();

Please start your project in debug mode and see why the call stack when you see that your breakpoint is hit.