SDK7.2.0 to SDK8.1.0 migration problems

RE: SDK7.2.0 to SDK8.1.0 migration problems

Susheel Nuguru — Thu, 02 Jul 2015 18:12:11 GMT

If you want to use both app_gpiote library and nrf_drv_gpiote, there is a conflict, I created a thread for it. devzone.nordicsemi.com/.../

RE: SDK7.2.0 to SDK8.1.0 migration problems

wim — Wed, 01 Jul 2015 10:56:00 GMT

ok, clear;

Some additional questions, things that are not covered by the migration document: the button en gpiote libraries also seem to have changed. What is then philosophy there? See also devzone.nordicsemi.com/.../

I get following linker errors:

In function `buttons_init': 
    undefined reference to `APP_BUTTON_INIT'
In function `detection_delay_timeout_handler':
    undefined reference to `nrf_drv_gpiote_in_is_set'
In function `gpiote_event_handler':
    undefined reference to `nrf_drv_gpiote_in_is_set'
In function `app_button_init':
    undefined reference to `nrf_drv_gpiote_is_init'
    undefined reference to `nrf_drv_gpiote_init'
    undefined reference to `nrf_drv_gpiote_in_init'
In function `app_button_enable':
    undefined reference to `nrf_drv_gpiote_in_event_enable'
In function `app_button_disable':
    undefined reference to `nrf_drv_gpiote_in_event_disable'
In function `app_button_is_pushed':
    undefined reference to `nrf_drv_gpiote_in_is_set'

I then tried to add nrf_drive_gpiote.c to my project, but then I get lots of other errors. Please help

RE: SDK7.2.0 to SDK8.1.0 migration problems

Susheel Nuguru — Wed, 01 Jul 2015 10:31:13 GMT

In your case you do not have to implement BLE_GAP_EVT_SEC_INFO_REQUEST. The peer will automatically understand that this device does not have any security

RE: SDK7.2.0 to SDK8.1.0 migration problems

wim — Wed, 01 Jul 2015 08:36:34 GMT

ok, clear; how about the sd_ble_gap_sec_info_reply - currently I have this code:

   case BLE_GAP_EVT_SEC_INFO_REQUEST:
        p_enc_info = &m_auth_status.periph_keys.enc_info;
        if (p_enc_info->div == p_ble_evt->evt.gap_evt.params.sec_info_request.div)
        {
            err_code = sd_ble_gap_sec_info_reply(m_conn_handle, p_enc_info, NULL);
            APP_ERROR_CHECK(err_code);
        }
        else
        {
            // No keys found for this device
            err_code = sd_ble_gap_sec_info_reply(m_conn_handle, NULL, NULL);
            APP_ERROR_CHECK(err_code);
        }
        break;

How should I rewrite this? Should I just do

err_code = sd_ble_gap_sec_info_reply(m_conn_handle,NULL, NULL, NULL); ?

RE: SDK7.2.0 to SDK8.1.0 migration problems

Susheel Nuguru — Wed, 01 Jul 2015 08:29:19 GMT

The LBS example is not adapted to latest SDK. But you can check ble_app_uart example which does not do any bonding.

sd_ble_gap_sec_params_reply(m_conn_handle, BLE_GAP_SEC_STATUS_PAIRING_NOT_SUPP, NULL, NULL);

RE: SDK7.2.0 to SDK8.1.0 migration problems

wim — Wed, 01 Jul 2015 08:05:35 GMT

The reason for me asking: I am not using bonding, and in the release notes it says what to do in case of bonding, but not in the other case; should I make the pointers NULL in the sd_ble_gap_sec_params_reply? Or do I have to instantiate some dummy security parameters struct?

RE: SDK7.2.0 to SDK8.1.0 migration problems

wim — Wed, 01 Jul 2015 08:00:48 GMT

Aryan

thanks for the document. Question: is the LBS example and app note adapted accordingly? Or is there an example I could check, which does not need pairing or bonding or security?

Wim

RE: SDK7.2.0 to SDK8.1.0 migration problems

Susheel Nuguru — Wed, 01 Jul 2015 07:25:47 GMT

Please read the migration documents of SD8.0 version. All the answers to your questions are clearly explained there. For your convenience, I am attaching them here.

s110_nrf51_8.0.0_migration-document.pdf