[nRF51822] Connectable Indirected advertising after pairing was done.

RE: [nRF51822] Connectable Indirected advertising after pairing was done.

Ole Morten — Fri, 27 Sep 2013 10:55:58 GMT

Sorry for the delay, but please have a look at this: https://devzone.nordicsemi.com/index.php/source-code-for-master-control-panel-3-4-0

RE: [nRF51822] Connectable Indirected advertising after pairing was done.

Jeffery — Fri, 27 Sep 2013 00:50:30 GMT

Could it be possible to have the source code as I mentioned at previous message? Thanks.

RE: [nRF51822] Connectable Indirected advertising after pairing was done.

Jeffery — Thu, 26 Sep 2013 00:45:48 GMT

Never mind it. I will give up this method. Then, try others. There are another two questions. 1.Could Nordic release firmware source code of nRF51822 USB dongle? The dongle is used for Master Control panel. 2. Could Nordic release windows application source code of Master Control Panel 3.3.0?

Thanks

RE: [nRF51822] Connectable Indirected advertising after pairing was done.

Ole Morten — Wed, 25 Sep 2013 07:15:59 GMT

I'm sorry for the delay, but I had to verify this with a developer. Unfortunately, it seems I have misled you. Moving encryption keys between devices will in fact not work out of the box, since each device have a unique set of root keys, that is used in the bond process.

You would have to do quite extensive modifications to the bond manager to make this work, so this is something I will strongly recommend you to not do.

For production testing, I'd again recommend you to either use the Master Emulator API or to use DTM as outlined in this application note: https://www.nordicsemi.com/eng/nordic/download_resource/20648/5/98128001

I'm terribly sorry for the inconvenience.

RE: [nRF51822] Connectable Indirected advertising after pairing was done.

Jeffery — Wed, 25 Sep 2013 00:42:35 GMT

Dear Ole Morten I had copied all the flash data to another sample as I mentioned in last message. It still cannot work. Please comment it. Thanks.

RE: [nRF51822] Connectable Indirected advertising after pairing was done.

Jeffery — Mon, 23 Sep 2013 02:45:20 GMT

In Desktop 2 source code, Bonding information was stored at flash page 255 and System attribute was stored at flash page 253. Then, I made a experiment. Step1. Pair nRF51822 sample A with BTLE host. Step2. Copy flash page 253 and 255 from sample A to smple B. Step3. Modify sample B to have same device address as sample A. Step4. Try sample B to connect the BTLE host directly without pairing. (The BTLE host already had bonding record of sample A)

The result is frustrating. Sample B still cannot work with BTLE host.

RE: [nRF51822] Connectable Indirected advertising after pairing was done.

Ole Morten — Thu, 19 Sep 2013 09:16:47 GMT

The encryption keys are handled by the bond manager, and written to flash once a bond has been successfully established. You should therefore look at the ble_bondmngr.c file to see how it's stored. Encryption keys are generated when a bond is first established, and then reused on all subsequent connections.

What you want to do is not trivial, and as I said, I'd normally not recommend anyone going down this path.

RE: [nRF51822] Connectable Indirected advertising after pairing was done.

Jeffery — Wed, 18 Sep 2013 01:14:20 GMT

So, you mentioned besides the same device address, I also need same ecryption key. For Desktop 2, where did you set encryption key? Could we read it out? It is a random number? Would it also be stored in flash after bonding done? Thanks.

RE: [nRF51822] Connectable Indirected advertising after pairing was done.

Ole Morten — Tue, 17 Sep 2013 11:27:40 GMT

Connecting with Master Emulator will not make the device appear as a regular HID device, so you will not be able to control anything with it. If wanted, I guess you could in principle parse the data in the application to know whether it makes sense or not, or else you'll have to just assume that everything is good if you actually get data.

Doing tricks to make multiple devices appear as the same device to Windows is not easy to solve, and I'm not sure I'd recommend trying that. Remember that you'd also have to make sure that all devices have the same encryption key for this to work; it is not sufficient that they have the same address. This would therefore require modifications to your program.

Most customers seems to be using the Master Emulator to do production testing.

RE: [nRF51822] Connectable Indirected advertising after pairing was done.

Jeffery — Tue, 17 Sep 2013 00:34:55 GMT

Dears I am thinking the vendors will not accept Master Emulator to do function test. For instance, mouse was only gotten X-Y prameters , button value, and scroll value at Master Emulator. These values are no use in product line. Operators tested visible testing items at real Windows 8, such as drawing cricles, report rates and so on. So, the best way is to bond with BTLE real host. Or, after bonding with dongle with Master Emulator, mouse or keyboard can really work as they suppose to act at Windows 8? Besides, my initial question is used Connectable Indirected ADV to a already bonded BTLE host. The all mouse or keyboard set the same device address in product line. Could it be possible?

RE: [nRF51822] Connectable Indirected advertising after pairing was done.

Ole Morten — Mon, 16 Sep 2013 05:34:53 GMT

If you're looking at developing a test for mass production, I'd recommend you to have a look at nAN-34: https://www.nordicsemi.com/eng/nordic/download_resource/20648/5/85114866

An alternative to the setup that is proposed there is to make a Master Emulator application to do the test, instead of relying on the built-in Windows features to do the bonding. This will make it easy to create and remove bonds from the code, removing the need for operators to manually do any deletion except for on the device.

RE: [nRF51822] Connectable Indirected advertising after pairing was done.

Jeffery — Fri, 13 Sep 2013 23:22:46 GMT

Continue...

As to the device address, I know each sample has unique device address. So, there is a trick to overwrite their device address same as the first sample has. This constant device address only be implemented in product line. So, adverstising packet got same device address.

RE: [nRF51822] Connectable Indirected advertising after pairing was done.

Jeffery — Fri, 13 Sep 2013 23:17:31 GMT

Hi dears

Actually, this application is a testing kit used in MP. I don't want to do pairing for everey sample in a single PC since operators will got mad to repeat it. Besides, the performace of PC will become worse after a lot of bonding records were accumulated.

So, my idea is only to pair for the first sample. Then, the bonding record will exist in the PC. Then, for other samples that they didn't have whitelist anyhow, just advertise by Connectable Indirected advertising. However, it seems not work.

RE: [nRF51822] Connectable Indirected advertising after pairing was done.

Ole Morten — Fri, 13 Sep 2013 12:01:37 GMT

Yes, this is most definitely possible, it's just a matter of editing the code used when starting advertising. If you already have a bond, and does not want to initiate a new one, I'd recommend you to use advertising with whitelisting.

When using the bond manager, you can get hold of a whitelist by calling the ble_bondmngr_whitelist_get() function. The following two code snippets should show what's needed:


static void advertising_init(void)
{
    uint32_t      err_code;
    ble_advdata_t advdata;
    uint8_t       flags = BLE_GAP_ADV_FLAG_BR_EDR_NOT_SUPPORTED;
    static ble_gap_whitelist_t whitelist;
    
    ble_uuid_t adv_uuids[] = 
    {
        {BLE_UUID_GLUCOSE_SERVICE,            BLE_UUID_TYPE_BLE},
        {BLE_UUID_BATTERY_SERVICE,            BLE_UUID_TYPE_BLE}, 
        {BLE_UUID_DEVICE_INFORMATION_SERVICE, BLE_UUID_TYPE_BLE}
    };

    // Build and set advertising data
    memset(&advdata, 0, sizeof(advdata));
    
    advdata.name_type               = BLE_ADVDATA_FULL_NAME;
    advdata.include_appearance      = false;
    advdata.flags.size              = sizeof(flags);
    advdata.flags.p_data            = &flags;
    advdata.uuids_complete.uuid_cnt = sizeof(adv_uuids) / sizeof(adv_uuids[0]);
    advdata.uuids_complete.p_uuids  = adv_uuids;
    
    err_code = ble_advdata_set(&advdata, NULL);
    APP_ERROR_CHECK(err_code);

    // Initialise advertising parameters (used when starting advertising)
    err_code = ble_bondmngr_whitelist_get(&whitelist);
    APP_ERROR_CHECK(err_code);
    
    memset(&m_adv_params, 0, sizeof(m_adv_params));
    
    m_adv_params.type        = BLE_GAP_ADV_TYPE_ADV_IND;
    m_adv_params.p_peer_addr = NULL;                           // Undirected advertisement
    
    if ((whitelist.addr_count > 0) || (whitelist.irk_count > 0))
    {
        m_adv_params.fp          = BLE_GAP_ADV_FP_FILTER_BOTH;
        m_adv_params.p_whitelist = &whitelist;
    }
    else
    {
        m_adv_params.fp = BLE_GAP_ADV_FP_ANY;
    }
    m_adv_params.interval    = APP_ADV_INTERVAL;
    m_adv_params.timeout     = APP_ADV_TIMEOUT_IN_SECONDS;
}

...

static void advertising_start(void)
{
    uint32_t err_code;
    
    err_code = sd_ble_gap_adv_start(&m_adv_params);
    APP_ERROR_CHECK(err_code);
    
    nrf_gpio_pin_set(ADVERTISING_LED_PIN_NO);
}