BLE automatic connection to other BLE device

RE: BLE automatic connection to other BLE device

Edvin — Mon, 10 Jan 2022 10:26:25 GMT

It will do so by default. If it doesn't have any devices in the whitelist, it will advertise without the whitelist, accepting any connections. When bonded, it will add the device in the whitelist. The next time it starts advertising scanning, it will use the whitelist unless you specify it to not do so, which means it will only connect to the device in the whitelist.

Best regards,

Edvin

RE: BLE automatic connection to other BLE device

June20 — Fri, 07 Jan 2022 01:21:08 GMT

Thanks for the info.

Sorry for asking the same question again, what I really wanted ask was how to make device have only one bonding (or have 1 whitelist) so that it will reject other connection attempt.

What should I modify for central(nRF52840 DK) so that it will accept only one peripheral(nRF52833 DK)?

Also to peripheral(nRF52833 DK) so that it will reject other centrals(nRF52840 DK) after bonding?

Will setting one whitelist do the trick? And how?

RE: BLE automatic connection to other BLE device

Edvin — Thu, 06 Jan 2022 14:14:11 GMT

[quote user="June20"]I came across Central_Link_Count and Peripheral_Link_Count in sdk_config.h[/quote]

No, they refer to how many simultaneous connections youn can maintain (be connected to at once). It has nothing to do with bonding.

I remembered wrong. It is the peripheral (ble_app_hrs) example that requests the bonding in these two examples. But it should be perfectly fine to do so from the central as well. Just call pm_conn_secure() from the BLE_GAP_EVT_CONNECTED event in main.c.

These examples show you how they will add the bonded device to their whitelist, so that the next time they advertise/scan, then they will only accept connections to eachother, unless you temporary disables the whitelist, or deletes the bonding information.

Best regards,

Edvin

RE: BLE automatic connection to other BLE device

June20 — Thu, 06 Jan 2022 12:14:56 GMT

Hello! Sorry for taking so long, I finally ported HRS into nRF52833 and successfully connected with HRS_C.

We're trying to use bonding so that only one central(nRF52840 DK) and one peripheral(nRF52833 DK) connects to each other.

For example: we have many centrals (nRF52840 DK) and many peripherals (nRF5833 DK). Once Central_1 and Peripheral_1 is bonded, Central_1 cannot connect with Peripheral_2 or Central_2 cannot connect with Peripheral_1.

What configuration should I touch/modify?

I came across Central_Link_Count and Peripheral_Link_Count in sdk_config.h. Do they just mean how many central/peripheral they can connect/store or are there more? Should I put 1 each for both central and peripheral?

Thanks

RE: BLE automatic connection to other BLE device

Edvin — Wed, 05 Jan 2022 08:54:49 GMT

Hello,

Yes. The RAM start and size depends on your BLE setup (number of services/characteristics, number of connections, MTU size, etc.) so you may need to change this in the future as well. Just monitor the log to see what it should be set to.

[quote user="June20"]My question is: is LESC necessary for bonding?[/quote]

No. You can use e.g. Just works.If you like.

[quote user="June20"]I came across cryptp CC310 in sdk_config.h and it says this crypto is only supported in nRF52840. Is CC310 necessary for LESC or bonding?[/quote]

No, you should disable it in sdk_config if you are using the nRF52833. You can use NRF_CRYPTO_BACKEND_MICRO_ECC_ENABLED instead of NRF_CRYPTO_BACKEND_CC310_ENABLED.

[quote user="June20"]Is PM_LESC_ENABLED and NRF_BLE_LESC_ENABLED related?[/quote]

I believe that NRF_BLE_LESC_ENABLED needs to be set if you want to set PM_LESC_ENABLED. I haven't tested. Try to search for PM_LESC_ENABLED and NRF_BLE_LESC_ENABLED in the unmodified pca10056 example to see where it is used.

Best regards,

Edvin

RE: BLE automatic connection to other BLE device

June20 — Wed, 05 Jan 2022 07:43:59 GMT

Thanks, I managed to build successfully built hrs example on nRF52833-DK. (Just in case for other readers, RAM_START is a little different, error message will tell you where it starts)

Problem is that I got stuck at peer_manager_init>pm_init>sm_init> nrf_ble_lesc_init>memset((void *) m_peer_keys, 0, sizeof(m_peer_keys));. (error does not display, I end up in HardFault_Handler.).

One of our coworker managed to make it run, but eventually get into error during ble connection.(sorry for lack of error message, will try his code later)

My question is: is LESC necessary for bonding?

I came across cryptp CC310 in sdk_config.h and it says this crypto is only supported in nRF52840. Is CC310 necessary for LESC or bonding?

Is PM_LESC_ENABLED and NRF_BLE_LESC_ENABLED related?

Thanks

RE: BLE automatic connection to other BLE device

Edvin — Mon, 03 Jan 2022 10:37:07 GMT

Hello.

If it is stuck in 0x0A60, it is stuck in the hardfault handler. Probably related to some memory mapping or wrong device config.

I suggest that you start with a pca10100 project, and then add the peer manager like it is done in the ble_app_hrs_c example.

If you really need to port the pca10056 to the pca10100, then open another pca10100 project, and make sure that the settings that you change look similar:

I think those should cover it.

Best regards,

Edvin

RE: BLE automatic connection to other BLE device

June20 — Wed, 22 Dec 2021 01:29:09 GMT

Any tutorial for porting? Based on your answer, SW or application shouldn't be a issue.

I tried modifying RAM and FLASH in SECTION PLACEMENT MACROS and change nRF52840 and pca10056 into nRF52833 and pca10100 in solution editor (</>). Building seems ok but running part is kinda stuck at "unknown fuction at 0x00000A60".

Are there other things I should modify?

Happy Holiday.

RE: BLE automatic connection to other BLE device

Edvin — Tue, 21 Dec 2021 14:11:21 GMT

Sorry, it doesn't look like we have any other samples that does bonding as a central, and it doesn't look like we have that sample for the nRF52833. It should be possible to port it yourself. Just copy the project folder pca10056, name it pca10100, and look at the settings in the project. You would typically want to change everything that says 52840 to 52833, and adjust the memory areas.

I don't have time for that right now, because of low staffing due to the Christmas holidays, and I am leaving for holidays myself tomorrow.

Either try this approach, or you can start with an example that you imagine you would want to use in your final application, and implement the peer manager to that example, and perform the bonding like it is done in the ble_app_hrs_c example.

PS: We are very short staffed for the Christmas Holidays. I will go on vacation tomorrow, and I will be back in January.

Best regards,

Edvin

RE: BLE automatic connection to other BLE device

June20 — Tue, 21 Dec 2021 09:28:32 GMT

Thank you so much for the reply.

Sorry for the change, I had to switch peripheral device into nRF52833-DK but I couldn't find ble_app_hrs example for the device.

Are there other example recommendation for bonding and pairing with nRF52840-DK central and nRF52833-DK peripheral?

Thank you in advance.

PS I tried copy pasting ble_app_hrs example from nRF52840 S140 to other nRF52833 example. I could build it but couldn't run it (got hard fault error). hids keyboard and mouse seems great but I couldn't find good central example to connect it.

RE: BLE automatic connection to other BLE device

Edvin — Mon, 20 Dec 2021 13:53:58 GMT

Hello,

This is a bit up to your application. As you mentioned, the filters that are used can be used to search for particular devices. Either a specific UUID, an advertising name, or a BLE address.

On the other side you have bonding (pairing = encryption, bonding = storing pairing data for later use). When you bond, you store bonding data for a particular device, so even if a similar device is nearby, it will only connect to the already bonded device.

I suggest that you look into the ble_app_hrs and ble_app_hrs_c examples if you are interrested in bonding. The data is stored by the peer manager in something called FDS (flash Data Storage), but it is not straight forward to see how it is done. The basic information that is stored is the address of the bonded device, and the keys that are used for encryption. This goes both ways, so if only one of the devices have the correct key, they will not be able to connect (security measure). The easiest way to bond two devices is to let them connect and bond like it is done in the ble_app_hrs_c example. Then they will look for one another the next time they are turned on.

On the other hand, if you don't need the security of bonding, you can try to add a filter on the BLE address (this is unique on all devices), and only connect if the advertisement comes from the address that you are looking for.You can do this either by adding the address to a whitelist, like the hrs examples does, or by manually checking the advertising packet and connect if you see that it is coming from the correct device. You can add the BLE_GAP_EVT_ADV_REPORT event to the ble_evt_handler() in main.c to experiment and see what the advertisement looks like. It will trigger whenever you are scanning an advertisement packet.

Best regards,

Edvin