This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

SDK7.2.0 to SDK8.1.0 migration problems

Hi

I thought: let us quickly migrate to the latest SDK. But that seems to be harder than anticipated. I run into a number issues when compiling with the new code:

  • too few arguments in sd_ble_gatts_sys_attr_set : which flag should I use? I use this function call on a connect event, because I previously got a BLE_ERROR_GATTS_SYS_ATTR_MISSING error;

  • too few arguments in sd_ble_gap_sec_params_reply

  • ble_gap_evt_auth_status_t has no member perish_keys

  • ble_gap_enc_info_t has no member div

  • too few arguments in sd_ble_gap_sec_info_reply

  • BLE_GAP_TIMEOUT_SRC_ADVERTISEMENT undeclared

Is there some guide explaining all these differences?

Parents Reply
  • 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); ?

Children
No Data
Related