Help needed with pairing a central UART over BLE module to a peripheral UART over BLE advertiser using whitelisting

RE: Help needed with pairing a central UART over BLE module to a peripheral UART over BLE advertiser using whitelisting

Simon — Mon, 10 Dec 2018 10:10:11 GMT

Sorry for the long delay.

Strange, It is working fine for me. If you haven't made any modifications to the ble_app_uart peripheral example, the act of sending and receiving messages are event driven and handled by interrupts and event handlers. Thus, it sounds like you have modified the example by sending messages directly from main.

If you upload your main function, I might be able to see where it fails.

RE: Help needed with pairing a central UART over BLE module to a peripheral UART over BLE advertiser using whitelisting

coop — Mon, 26 Nov 2018 17:18:04 GMT

Hi Simon,

Thank you for your reply! I implemented the whitelisting functionality in the same way you suggested and noticed that the peripheral paired with the central whose MAC address was recorded in the XX fields of whitelist_addrs = {0, BLE_GAP_ADDR_TYPE_RANDOM_STATIC, {0x XX, 0x XX, 0x XX, 0x XX, 0x XX, 0x XX}}, but I also noticed that the program stops sending the string of characters over BLE. In other words, once the connection is established, the peripheral stops executing any of the code in main.

Could you please help me figure out why that might be?

Thank you!

Alin

RE: Help needed with pairing a central UART over BLE module to a peripheral UART over BLE advertiser using whitelisting

Simon — Thu, 22 Nov 2018 08:30:23 GMT

After some trial and error I managed to communicate between the central and peripheral, with whitelisting added to the peripheral side. Here I will go through the steps taken.

First, you will need the MAC address of the device in which the central is running on. I got it by flashing and running the BLE UART Peripheral example on the device (it can also be found by reading the FICR register in this manner), then I opened the nRF Connect app on the mobile phone and wrote down the 6 byte MAC address. In my case it was 0xE2:8B:65:53:71:9B. Then I erased the chip, and flashed the BLE UART Central Example onto the chip.

Changes to made to the BLE UART Peripheral Example

Initially I added this line at the top of main

static ble_gap_addr_t whitelist_addrs = {0, BLE_GAP_ADDR_TYPE_RANDOM_STATIC, {0x9B, 0x71, 0x53, 0x65, 0x8B, 0xE2}};

In advertising_init() I added this line

init.config.ble_adv_whitelist_enabled          = true;

Inside the function advertising_start() these lines were added

ret_code_t err_code;
ble_gap_addr_t const     *p_whitelist_addr[] = {&whitelist_addrs};
err_code = sd_ble_gap_whitelist_set(p_whitelist_addr, 1);

Eventually, I modified the handler for advertising events (on_adv_evt()), by including the case BLE_ADV_EVT_WHITELIST_REQUEST

case BLE_ADV_EVT_WHITELIST_REQUEST:
        {

             // Apply the whitelist.
             err_code = ble_advertising_whitelist_reply(&m_advertising,
                                                       &whitelist_addrs,
                                                       1,
                                                       NULL,
                                                       0);
        } break; //BLE_ADV_EVT_WHITELIST_REQUEST

Remember to call sd_ble_gap_whitelist_set() before running ble_advertising_start(), if not the function sd_ble_gap_adv_set_configure(..) will fail with the error NRF_ERROR_INVALID_PARAM.

It is also important to add the function ble_advertising_whitelist_reply(..) as shown above. The comment above the function declaration says the following:

"The whitelist must be set by the application upon receiving a BLE_ADV_EVT_WHITELIST_REQUEST event."

Hopefully I haven't forgotten anything, just in case, I have attached the code.

devzone.nordicsemi.com/.../ble_5F00_app_5F00_uart_5F00_whitelist.zip

Best regards,

Simon