Insert data in the extended advertisement of BLE 5

RE: Insert data in the extended advertisement of BLE 5

ziv123 — Tue, 07 Jul 2020 08:25:19 GMT

SOLVED the issue i raised

forgot to change sdk_config.h to work with internal clock

RE: Insert data in the extended advertisement of BLE 5

ziv123 — Tue, 07 Jul 2020 07:45:33 GMT

hi Edvin

i have tried to run the example ble_app_rscs_c from central but for some reason it falls in the

ble_stack_init(); -> nrf_sdh_enable_request(); ->

 ret_code = sd_softdevice_enable(&clock_lf_cfg, app_error_fault_handler);

which goes here :

SVCALL(SD_SOFTDEVICE_ENABLE, uint32_t, sd_softdevice_enable(nrf_clock_lf_cfg_t const * p_clock_lf_cfg, nrf_fault_handler_t fault_handler));

can you help me to understand the reason ?

i work with nrf52832, sdk16.0, s132 ver7.0

best regards

Ziv

RE: Insert data in the extended advertisement of BLE 5

QuentinD — Thu, 28 May 2020 13:02:33 GMT

Thank you very much for your help: it was really useful ;-)

RE: Insert data in the extended advertisement of BLE 5

Edvin — Thu, 28 May 2020 10:32:05 GMT

1: I believe so. It looks like this is how it is done in the example, at least. It is a bit hard to tell, because we don't have anything that can scan for extended advertising out of the box.

However, I did a short test using ble_app_rscs (peripheral) + ble_app_rscs_c (central), where in the central project, I just changed the UUID that it is looking for from BLE_UUID_RUNNING_SPEED_AND_CADENCE to BLE_UUID_HUMAN_INTERFACE_DEVICE_SERVICE, just so it wouldn't connect, but keep scanning.

Then I added the BLE_GAP_EVT_ADV_REPORT to the ble_evt_handler, to see the advertisement reports.

Then I printed out what channels and the length of the advertising packet.

What I saw is that I don't get the original advertising packet at all (the ones on channel 37, 38 and 39). It looks like they are stripped away from the softdevice, because they only contain the information of what channel and phy the extended advertising is coming on. So in fact, all the data that you send is sent in the extended advertising packet.

You may want to turn down the advertising interval, and to insert your peripheral's advertising address in the if check to filter out the other advertisements, or it will be a lot of text printed. To see what address you have, use nRF connect for Desktop, and flash the peripheral DK with another example that doesn't use extended advertising. addr[0] is the address byte to the far right:

Check out the implementation I used to test:

static void ble_evt_handler(ble_evt_t const * p_ble_evt, void * p_context)
{
    ret_code_t            err_code;
    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:
            //if (p_ble_evt->evt.gap_evt.params.adv_report.peer_addr.addr[0] == 0xD3) // comment in this line, and change it to match the address of your DK
            {
                NRF_LOG_INFO("adv_report from %02x:02x:02x:02x:02x:02x", p_ble_evt->evt.gap_evt.params.adv_report.peer_addr.addr[0],
                                                                        p_ble_evt->evt.gap_evt.params.adv_report.peer_addr.addr[1],
                                                                        p_ble_evt->evt.gap_evt.params.adv_report.peer_addr.addr[2],
                                                                        p_ble_evt->evt.gap_evt.params.adv_report.peer_addr.addr[3],
                                                                        p_ble_evt->evt.gap_evt.params.adv_report.peer_addr.addr[4],
                                                                        p_ble_evt->evt.gap_evt.params.adv_report.peer_addr.addr[5]);
                uint8_t channel = p_ble_evt->evt.gap_evt.params.adv_report.ch_index;
                uint16_t len = (uint16_t)p_ble_evt->evt.gap_evt.params.adv_report.data.len;
                NRF_LOG_INFO("adv_report channel %d, len %d", channel, len);
                
                NRF_LOG_INFO("advertisement:");
                for (uint16_t i=0; i<len; i++)
                {
                    NRF_LOG_RAW_INFO("%02x", p_ble_evt->evt.gap_evt.params.adv_report.data.p_data[i]);
                    if(i%10 == 0 && i != 0)
                    {
                        NRF_LOG_RAW_INFO("\r\n");
                    }
                    else if(i<len-1)
                    {
                        NRF_LOG_RAW_INFO(":");
                    }
                }
                NRF_LOG_RAW_INFO("\r\n");
            }
            break;
            case ...

RE: Insert data in the extended advertisement of BLE 5

QuentinD — Wed, 27 May 2020 14:41:01 GMT

Hello Edvin

1.
I also use this example (ble_app_rscs) to develop extended advertising. In this example, they insert data in the "manufacturing data". But as I am new with the Bluetooth frame format, I was wondering if it is in the "manufacturing data" field that we indicate our data in general or so, we add new fields in the "ble_advdata_t" structure which contain our data. It's just a general question.

2.
Thank you very much.

RE: Insert data in the extended advertisement of BLE 5

Edvin — Wed, 27 May 2020 12:33:45 GMT

Hello,

Check out the ble_app_rscs example as this uses extended advertising by default.

It is found in SDK16.0.0\examples\ble_peripheral\ble_app_rscs

As for the company identifier, you can't use Nordic's in an official product, so if you intend to certify this with Bluetooth, you need to use your own company identifier.

That being said, I don't think you need a company identifier. You don't need to include it in the advertising packet, at least. It seems to run just fine without.

You can read a bit more about company identifiers in this blog post. Search for "company ID"

Is there a reason why you only use advertising? It will probably work, but be aware that you will not get any confirmation on whether or not an advertisement is scanned.

BR,

Edvin