How to search for extended advertising in NRF52832 + S132 ?

[Karr]

I am trying to receive extended advertising from a device on nRF52832.

I have made the following changes:

sdk_config

#define NRF_BLE_SCAN_BUFFER BLE_GAP_SCAN_BUFFER_EXTENDED_MIN

nrf_ble_scan.c

static void nrf_ble_scan_default_param_set(nrf_ble_scan_t * const p_scan_ctx)
{
    // Set the default parameters.
    p_scan_ctx->scan_params.active        = 1;
#if (NRF_SD_BLE_API_VERSION > 7)
    p_scan_ctx->scan_params.interval_us   = NRF_BLE_SCAN_SCAN_INTERVAL * UNIT_0_625_MS;
    p_scan_ctx->scan_params.window_us     = NRF_BLE_SCAN_SCAN_WINDOW * UNIT_0_625_MS;
#else
    p_scan_ctx->scan_params.interval      = NRF_BLE_SCAN_SCAN_INTERVAL;
    p_scan_ctx->scan_params.window        = NRF_BLE_SCAN_SCAN_WINDOW;
#endif // (NRF_SD_BLE_API_VERSION > 7)
    p_scan_ctx->scan_params.timeout       = NRF_BLE_SCAN_SCAN_DURATION;
    p_scan_ctx->scan_params.filter_policy = BLE_GAP_SCAN_FP_ACCEPT_ALL;
    p_scan_ctx->scan_params.scan_phys     = BLE_GAP_PHY_1MBPS;
    p_scan_ctx->scan_params.extended      = true;
}

My question is:

Before I added

p_scan_ctx->scan_params.extended = true;

I could always receive BLE_GAP_EVT_ADV_REPORT events in nrf_ble_scan_on_ble_evt, and I was able to receive legacy advertising normally.

However, after setting

I can no longer receive BLE_GAP_EVT_ADV_REPORT events in nrf_ble_scan_on_ble_evt at all — not even legacy advertising.

Is there anything else I need to configure or enable in order to receive advertising reports?

[Susheel Nuguru]

I do not think S132 <6.1.0 supports extended advertising. which version of S132 are you using?

[Karr]

I am aware of this information, but the SDK I am using is nRF5_SDK_17.0.2_d674dde, which should support this feature.

[Susheel Nuguru]

nRF5_SDK_17.0.2_d674dde does not automatically gives the device the extended advertising capabilities. The capabilities lies inside the Softdevice controller version. Not all Softdevice controller versions support this feature. So your assumption that using a particular SDK version with any softdevice controller should support this feature is incorrect.