Long range with SDK16.0.0

[Steven983]

Hi all,

I am trying to deploy the long range mode with nRF52840. I modified the blinky example under SK 16.0.0 and it just keeps resetting 

and the error code is 0x0007. Is there anyone can help me with that? Thanks.

static ble_gap_adv_data_t m_adv_data =
{
    .adv_data =
    {
        .p_data = m_enc_advdata,
        .len    = BLE_GAP_ADV_SET_DATA_SIZE_MAX
    },
    .scan_rsp_data =
    {
        .p_data = NULL,
        .len    = 0

    }
};

static void advertising_init(void)
{
    ret_code_t    err_code;
    ble_advdata_t advdata;
  //  ble_advdata_t srdata;

    ble_uuid_t adv_uuids[] = {{LBS_UUID_SERVICE, m_lbs.uuid_type}};

    // Build and set advertising data.
    memset(&advdata, 0, sizeof(advdata));

    advdata.name_type          = BLE_ADVDATA_FULL_NAME;
    advdata.include_appearance = true;//false
    advdata.flags              = BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE;


//    memset(&srdata, 0, sizeof(srdata)); 
//    srdata.uuids_complete.uuid_cnt = sizeof(adv_uuids) / sizeof(adv_uuids[0]);
//    srdata.uuids_complete.p_uuids  = adv_uuids;
//
     err_code = ble_advdata_encode(&advdata, m_adv_data.adv_data.p_data, &m_adv_data.adv_data.len);
     APP_ERROR_CHECK(err_code);


//    err_code = ble_advdata_encode(&srdata, m_adv_data.scan_rsp_data.p_data, &m_adv_data.scan_rsp_data.len);
//    APP_ERROR_CHECK(err_code);

    ble_gap_adv_params_t adv_params;


    // Set advertising parameters.
    memset(&adv_params, 0, sizeof(adv_params));

 //      BLE_GAP_ADV_TYPE_EXTENDED_NONCONNECTABLE_SCANNABLE_UNDIRECTED
    adv_params.primary_phy     = BLE_GAP_PHY_CODED;
    adv_params.secondary_phy   = BLE_GAP_PHY_CODED;
    adv_params.duration        = APP_ADV_DURATION;
    adv_params.properties.type = BLE_GAP_ADV_TYPE_EXTENDED_NONCONNECTABLE_SCANNABLE_UNDIRECTED;
    adv_params.p_peer_addr     = NULL;
    adv_params.filter_policy   = BLE_GAP_ADV_FP_ANY;
    adv_params.interval        = APP_ADV_INTERVAL;
    adv_params.p_peer_addr     = NULL;
    adv_params.scan_req_notification = 1,
    err_code = sd_ble_gap_adv_set_configure(&m_adv_handle, &m_adv_data, &adv_params);
  
    APP_ERROR_CHECK(err_code);

}

[Simonr]

Hi

I see that you haven't added the payload in the scan response. Can you try setting adv_data.p_data to NULL? You can use this project as a template for how a Coded PHY example should be set up for advertising, as not much has changed in that regard since SDK v.15.2.

nRF5_SDK_15.2.0_mod.zip

Best regards,

Simon

[Steven983]

Hi Simon,

It doesn't work after I set adv_data.p_data to NULL. The reson that I didn't add the payload in the scan response is that in this Blog post https://devzone.nordicsemi.com/f/nordic-q-a/38267/long-range/183279#183279, Harvard said that srdata (scan response data) is not used together with extended advertising, and should not be encoded and suggeted that srdata should set to NULL. 

Any more advice?

Best,

Steven

[Simonr]

Can you try to enable authorization for read/write of the characteristic that returns error code 0x0007? That error code means that there's an insufficient encryption key size somewhere.

I suggest you check out the project I uploaded and see if you can find anything that differs from your project as well, as that project is confirmed to work from our end.

Best regards,

Simon

[Steven983]

It works. Thanks Simon.

[Steven983]

I still have one more question. In the Uart example, the structure of ble_advertising_init_t is used to initiate the advertising module. However, the stucture of  ble_gap_adv_params_t  is used in the blinky example. What is the difference between these two types of structure? And how to choose them in different situations?