nRF5 SDK 15 adv_report

RE: nRF5 SDK 15 adv_report

Embedded_Engineer — Fri, 31 Jan 2020 09:06:35 GMT

Keep up the good support,

Thank you

RE: nRF5 SDK 15 adv_report

Einar Thorsrud — Fri, 31 Jan 2020 08:24:11 GMT

You should not assume that the data is valid after the event handler returns. If you need it longer, you should copy it to a static buffer or similar. (The details depend on undocumented SoftDevice internals and can depend on several factors, and change at any time.)

RE: nRF5 SDK 15 adv_report

Embedded_Engineer — Fri, 31 Jan 2020 05:56:24 GMT

Hi Einar Thorsrud,

As the scanning is resumed after handling BLE event. I would like to know when does the

p_adv_report->data.p_data

is modified by the softdevice [am using S140]. Is it cleared after scanning is resumed or only over written when new packet advertised is received? I came across a situation when there was data available in p_adv_report->data.p_data but p_adv_report->data.len was zero [FYI scan response bit was set].

Thank you

RE: nRF5 SDK 15 adv_report

Einar Thorsrud — Mon, 24 Sep 2018 08:37:46 GMT

Yes, this is required in SDK 15, as it uses S132/S140 version 6. See API documentation for sd_ble_gap_scan_start() for details.

RE: nRF5 SDK 15 adv_report

mich_x — Fri, 21 Sep 2018 21:03:18 GMT

I noticed that both your code and the examples resume scanning after handling the ble_evt. Is it required for SDK 15? Because I did not do this on SDK 14 and it seems to be ok.

RE: nRF5 SDK 15 adv_report

Einar Thorsrud — Thu, 20 Sep 2018 07:51:09 GMT

I do not see any code that initiates scanning in your code snippets.

I made a simple active scanner example for SDK 15 the other day, which you can find in this post. That should do what you want out of the box, so perhaps you can start with that instead?

RE: nRF5 SDK 15 adv_report

mich_x — Wed, 19 Sep 2018 18:55:10 GMT

This is how I handle the ble_evt. I dumped all the adv_report it got but could not find the data I send by another device running SDK14. I am sure that the advertising of the SDK14 is correct.

static void ble_evt_handler(ble_evt_t const * p_ble_evt, void * p_context)
{
    ble_gap_evt_t const * p_gap_evt = &p_ble_evt->evt.gap_evt;

    switch (p_ble_evt->header.evt_id)
    {
        case BLE_GAP_EVT_ADV_REPORT:
        {
            ble_gap_evt_adv_report_t const * p_adv_report = &p_gap_evt->params.adv_report;
			NRF_LOG_DEBUG("In parse"); 
        	NRF_LOG_DEBUG("%d", p_adv_report->data.len);
        	NRF_LOG_HEXDUMP_DEBUG(p_adv_report->data.p_data, p_adv_report->data.len);
        }break; // BLE_GAP_EVT_ADV_REPORT

        default:
            break;
    }
}

This is how I initialize the scan module.

static void blend_ble_stack_init(void )
{
    ret_code_t err_code;

    err_code = nrf_sdh_enable_request();
    APP_ERROR_CHECK(err_code);

    // Configure the BLE stack using the default settings.
    // Fetch the start address of the application RAM.
    uint32_t ram_start = 0;
    err_code = nrf_sdh_ble_default_cfg_set(APP_BLE_CONN_CFG_TAG, &ram_start);
    APP_ERROR_CHECK(err_code);

    // Enable BLE stack.
    err_code = nrf_sdh_ble_enable(&ram_start);
    APP_ERROR_CHECK(err_code);

    // Register a handler for BLE events.
    NRF_SDH_BLE_OBSERVER(_blend_ble_observer, APP_BLE_OBSERVER_PRIO, ble_evt_handler, NULL);
	_blend_scan_instance.scan_buffer.p_data = _blend_scan_instance.scan_buffer_data;
	_blend_scan_instance.scan_buffer.len = NRF_BLE_SCAN_BUFFER;
}

Can you maybe check for me where I did wrong? Because this is the exact way I did in SDK14 and that was perfectly fine. I am not sure what has changed about the softdevice API during the upgrade.

RE: nRF5 SDK 15 adv_report

Einar Thorsrud — Fri, 14 Sep 2018 12:24:32 GMT

Hi,

I recommend you refer to the ble_app_hrc_c example to see how you can use the ble_advdata_* functions to parse the advertising data. If you want to do it without any helper functions you can access the full raw advertising data from ble_gap_evt_adv_report_t::data.p_data (length is ble_gap_evt_adv_report_t::data.len) when you get the BLE_GAP_EVT_ADV_REPORT event.