Feedback

Exercise 3 – Provisioning the device over Bluetooth LE

In this exercise, we are going to add support for provisioning over Bluetooth LE to our application, using the Wi-Fi Provisioning Core library.

For this exercise, we very much recommend going though the Bluetooth Low Energy Fundamentals course, as we reuse a lot of the API’s that are covered in detail in that course.

Exercise steps

In the GitHub repository for this course, go to the base code for this exercise, found in l2/l2_e3.

1. Enable and configure the necessary configurations.

1.1 Enable the necessary Bluetooth LE configurations.

CONFIG_BT=y
CONFIG_BT_PERIPHERAL=y
CONFIG_BT_PERIPHERAL_PREF_TIMEOUT=75
CONFIG_BT_WIFI_PROV=y
CONFIG_WIFI_PROV_CORE=y
CONFIG_BT_BONDABLE=n

CONFIG_BT_SMP=y
CONFIG_BT_BUF_ACL_RX_SIZE=151
CONFIG_BT_L2CAP_TX_MTU=147
CONFIG_BT_BUF_ACL_TX_SIZE=151
CONFIG_BT_RX_STACK_SIZE=22000
CONFIG_BT_DEVICE_NAME_DYNAMIC=y

Copy

CONFIG_BT=y
CONFIG_BT_PERIPHERAL=y
CONFIG_BT_PERIPHERAL_PREF_TIMEOUT=75
CONFIG_BT_WIFI_PROV=y
CONFIG_WIFI_PROV_CORE=y
CONFIG_BT_BONDABLE=n

CONFIG_BT_SMP=y
CONFIG_BT_BUF_ACL_RX_SIZE=151
CONFIG_BT_L2CAP_TX_MTU=147
CONFIG_BT_BUF_ACL_TX_SIZE=151
CONFIG_BT_RX_STACK_SIZE=22000
CONFIG_BT_DEVICE_NAME_DYNAMIC=y

Kconfig

1.2 Enable the necessary NVS and flash configurations.

CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_FLASH_MAP=y

CONFIG_NVS=y
CONFIG_SETTINGS=y
CONFIG_SETTINGS_NVS=y

Copy

CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_FLASH_MAP=y

CONFIG_NVS=y
CONFIG_SETTINGS=y
CONFIG_SETTINGS_NVS=y

Kconfig

1.3 Enable the IPC radio firmware.

Since we want to use both Wi-Fi and Bluetooth LE in the same application, we need to enable IPC radio firmware. This allows us to use the radio peripheral in the network core (cpunet) from the application core (cpuapp).

1.3.1 Enable the IPC radio firmware in Sysbuild.

This is done through the following Kconfig: SB_CONFIG_NRF_DEFAULT_IPC_RADIO, see Sysbuild Kconfig options.

Open Kconfig.sysbuild and add the following lines

config NRF_DEFAULT_IPC_RADIO
	default y

Copy

config NRF_DEFAULT_IPC_RADIO
	default y

Kconfig

1.3.2 Configure the IPC radio firmware for Bluetooth LE.

In the directory sysbuild/ipc_radio, open the prj.conf file and input the following lines

CONFIG_BT=y
CONFIG_BT_HCI_RAW=y
CONFIG_BT_BUF_ACL_TX_SIZE=151
CONFIG_BT_BUF_ACL_RX_SIZE=151
CONFIG_BT_CTLR_DATA_LENGTH_MAX=151
CONFIG_BT_MAX_CONN=2

CONFIG_IPC_RADIO_BT=y
CONFIG_IPC_RADIO_BT_HCI_IPC=y

Copy

CONFIG_BT=y
CONFIG_BT_HCI_RAW=y
CONFIG_BT_BUF_ACL_TX_SIZE=151
CONFIG_BT_BUF_ACL_RX_SIZE=151
CONFIG_BT_CTLR_DATA_LENGTH_MAX=151
CONFIG_BT_MAX_CONN=2

CONFIG_IPC_RADIO_BT=y
CONFIG_IPC_RADIO_BT_HCI_IPC=y

Kconfig

CONFIG_IPC_RADIO_BT – Set the supported radio configuration to Bluetooth Low Energy serialization.
CONFIG_IPC_RADIO_BT_HCI_IPC – Selects the Bluetooth HCI serialization.

2. Include header files for Bluetooth LE.

Include the necessary Bluetooth LE header files in main.c, as well as the header file for the Wi-Fi Provisioning Service.

Add the following lines in main.c

#include <zephyr/bluetooth/bluetooth.h>
#include <zephyr/bluetooth/hci.h>
#include <zephyr/bluetooth/conn.h>
#include <zephyr/bluetooth/uuid.h>
#include <zephyr/bluetooth/gatt.h>
#include <net/wifi_prov_core/wifi_prov_core.h>
#include <bluetooth/services/wifi_provisioning.h>

Copy

#include <zephyr/bluetooth/bluetooth.h>
#include <zephyr/bluetooth/hci.h>
#include <zephyr/bluetooth/conn.h>
#include <zephyr/bluetooth/uuid.h>
#include <zephyr/bluetooth/gatt.h>
#include <net/wifi_prov_core/wifi_prov_core.h>
#include <bluetooth/services/wifi_provisioning.h>

3. Define a provisioning service variable prov_svc_data structure.

3.1 Define an array prov_svc_data for storing provisioning service data.

static uint8_t prov_svc_data[] = {BT_UUID_PROV_VAL, 0x00, 0x00, 0x00, 0x00};

Copy

static uint8_t prov_svc_data[] = {BT_UUID_PROV_VAL, 0x00, 0x00, 0x00, 0x00};

3.2 Define indexes for the available bits to store information.

Define macros to easily be able to refer to the available bits of prov_svc_data.

#define ADV_DATA_VERSION_IDX          (BT_UUID_SIZE_128 + 0)
#define ADV_DATA_FLAG_IDX             (BT_UUID_SIZE_128 + 1)
#define ADV_DATA_FLAG_PROV_STATUS_BIT BIT(0)
#define ADV_DATA_FLAG_CONN_STATUS_BIT BIT(1)
#define ADV_DATA_RSSI_IDX             (BT_UUID_SIZE_128 + 3)

Copy

#define ADV_DATA_VERSION_IDX          (BT_UUID_SIZE_128 + 0)
#define ADV_DATA_FLAG_IDX             (BT_UUID_SIZE_128 + 1)
#define ADV_DATA_FLAG_PROV_STATUS_BIT BIT(0)
#define ADV_DATA_FLAG_CONN_STATUS_BIT BIT(1)
#define ADV_DATA_RSSI_IDX             (BT_UUID_SIZE_128 + 3)

4. Define the structures for the advertisement data and scan response data.

4.1 Define a variable for the device name device_name.

static uint8_t device_name[] = {'P', 'V', '0', '0', '0', '0', '0', '0'};

Copy

static uint8_t device_name[] = {'P', 'V', '0', '0', '0', '0', '0', '0'};

4.2 Define the data structure bt_data ad[] for the advertisement packet.

Firstly, we set the advertisement flags to advertise in general discoverable mode (BT_LE_AD_GENERAL) and that classic Bluetooth (BR/EDR) is not supported (BT_LE_AD_NO_BRERD).

Secondly, we advertise the UUID of the Wi-Fi Provisioning Service, BT_UUID_PROV_VAL.

Lastly, we want to advertise the device name, which we defined earlier as the variable device_name.

Add the following lines to the main.c file

static const struct bt_data ad[] = {
	BT_DATA_BYTES(BT_DATA_FLAGS, (BT_LE_AD_GENERAL | BT_LE_AD_NO_BREDR)),
	BT_DATA_BYTES(BT_DATA_UUID128_ALL, BT_UUID_PROV_VAL),
	BT_DATA(BT_DATA_NAME_COMPLETE, device_name, sizeof(device_name)),
};

Copy

static const struct bt_data ad[] = {
	BT_DATA_BYTES(BT_DATA_FLAGS, (BT_LE_AD_GENERAL | BT_LE_AD_NO_BREDR)),
	BT_DATA_BYTES(BT_DATA_UUID128_ALL, BT_UUID_PROV_VAL),
	BT_DATA(BT_DATA_NAME_COMPLETE, device_name, sizeof(device_name)),
};

4.3 Define the structure bt_data sd[] for the scan response.

In the scan response, we want to include the provisioning service data stored in prov_svc_data.

static const struct bt_data sd[] = {
	BT_DATA(BT_DATA_SVC_DATA128, prov_svc_data, sizeof(prov_svc_data)),
};

Copy

static const struct bt_data sd[] = {
	BT_DATA(BT_DATA_SVC_DATA128, prov_svc_data, sizeof(prov_svc_data)),
};

5. Define the function update_wifi_status_in_adv() to update prov_svc_data.

5.1 Update prov_svc_data with the firmware version PROV_SVC_VER.

prov_svc_data[ADV_DATA_VERSION_IDX] = PROV_SVC_VER;

Copy

prov_svc_data[ADV_DATA_VERSION_IDX] = PROV_SVC_VER;

5.2 Use the function wifi_prov_state_get() to get the provisioning state of the device, which returns true or false, depending on if the device is provisioned or not, and update prov_svc_data

if (!wifi_prov_state_get()) {
	prov_svc_data[ADV_DATA_FLAG_IDX] &= ~ADV_DATA_FLAG_PROV_STATUS_BIT;
} else {
	prov_svc_data[ADV_DATA_FLAG_IDX] |= ADV_DATA_FLAG_PROV_STATUS_BIT;
}

Copy

if (!wifi_prov_state_get()) {
	prov_svc_data[ADV_DATA_FLAG_IDX] &= ~ADV_DATA_FLAG_PROV_STATUS_BIT;
} else {
	prov_svc_data[ADV_DATA_FLAG_IDX] |= ADV_DATA_FLAG_PROV_STATUS_BIT;
}

5.3 Then request the status of the net interface. If Wi-Fi is not connected and/or an error occurs, mark the status as not connected. If not, mark it as connected.

struct net_if *iface = net_if_get_first_wifi();
struct wifi_iface_status status = {0};

int err = net_mgmt(NET_REQUEST_WIFI_IFACE_STATUS, iface, &status, sizeof(struct wifi_iface_status));
if ((err != 0) || (status.state < WIFI_STATE_ASSOCIATED)) {
	prov_svc_data[ADV_DATA_FLAG_IDX] &= ~ADV_DATA_FLAG_CONN_STATUS_BIT;
	prov_svc_data[ADV_DATA_RSSI_IDX] = INT8_MIN;
} else { /* WiFi is connected. */
	prov_svc_data[ADV_DATA_FLAG_IDX] |= ADV_DATA_FLAG_CONN_STATUS_BIT;
	prov_svc_data[ADV_DATA_RSSI_IDX] = status.rssi;
}

Copy

struct net_if *iface = net_if_get_first_wifi();
struct wifi_iface_status status = {0};

int err = net_mgmt(NET_REQUEST_WIFI_IFACE_STATUS, iface, &status, sizeof(struct wifi_iface_status));
if ((err != 0) || (status.state < WIFI_STATE_ASSOCIATED)) {
	prov_svc_data[ADV_DATA_FLAG_IDX] &= ~ADV_DATA_FLAG_CONN_STATUS_BIT;
	prov_svc_data[ADV_DATA_RSSI_IDX] = INT8_MIN;
} else { /* WiFi is connected. */
	prov_svc_data[ADV_DATA_FLAG_IDX] |= ADV_DATA_FLAG_CONN_STATUS_BIT;
	prov_svc_data[ADV_DATA_RSSI_IDX] = status.rssi;
}

6. Define the work structures for updating advertisement parameters and data.

Declare the work structures k_work_delayable for updating the advertisement parameters (update_adv_param_work) and updating the advertisement data (update_adv_data_work).

static struct k_work_delayable update_adv_param_work;
static struct k_work_delayable update_adv_data_work;

Copy

static struct k_work_delayable update_adv_param_work;
static struct k_work_delayable update_adv_data_work;

7. Define the task functions for the work structures.

7.1 Define update_adv_param_task().

In the case where the advertisement data and/or scan response data changes, we need a function that will stop advertising, then starts advertising again with the updated parameters.

Add the following code snippet in main.c

int err;

err = bt_le_adv_stop();
if (err != 0) {
	LOG_ERR("Cannot stop advertisement: err = %d\n", err);
	return;
}

err = bt_le_adv_start(prov_svc_data[ADV_DATA_FLAG_IDX] & ADV_DATA_FLAG_PROV_STATUS_BIT
			      ? PROV_BT_LE_ADV_PARAM_SLOW
			      : PROV_BT_LE_ADV_PARAM_FAST,
		      ad, ARRAY_SIZE(ad), sd, ARRAY_SIZE(sd));
if (err != 0) {
	LOG_ERR("Cannot start advertisement: err = %d\n", err);
}

Copy

int err;

err = bt_le_adv_stop();
if (err != 0) {
	LOG_ERR("Cannot stop advertisement: err = %d\n", err);
	return;
}

err = bt_le_adv_start(prov_svc_data[ADV_DATA_FLAG_IDX] & ADV_DATA_FLAG_PROV_STATUS_BIT
			      ? PROV_BT_LE_ADV_PARAM_SLOW
			      : PROV_BT_LE_ADV_PARAM_FAST,
		      ad, ARRAY_SIZE(ad), sd, ARRAY_SIZE(sd));
if (err != 0) {
	LOG_ERR("Cannot start advertisement: err = %d\n", err);
}

7.2 Define update_adv_data_task()

Call the function update_wifi_status_in_adv() to update the status through prov_svc_data. Then, update the advertisement and scan response data using bt_le_adv_update_data().

Then reschedule update_adv_data_work.

Add the following code snippet in main.c

int err;

update_wifi_status_in_adv();
err = bt_le_adv_update_data(ad, ARRAY_SIZE(ad), sd, ARRAY_SIZE(sd));
if (err != 0) {
	LOG_INF("Cannot update advertisement data, err = %d\n", err);
}
k_work_reschedule_for_queue(&adv_daemon_work_q, &update_adv_data_work,
			    K_SECONDS(ADV_DATA_UPDATE_INTERVAL));

Copy

int err;

update_wifi_status_in_adv();
err = bt_le_adv_update_data(ad, ARRAY_SIZE(ad), sd, ARRAY_SIZE(sd));
if (err != 0) {
	LOG_INF("Cannot update advertisement data, err = %d\n", err);
}
k_work_reschedule_for_queue(&adv_daemon_work_q, &update_adv_data_work,
			    K_SECONDS(ADV_DATA_UPDATE_INTERVAL));

8. Alter the callback functions for the connected and disconnected connection events.

This is done because when a Bluetooth connection is established, the device will stop advertising and we no longer need to update the advertisement data. However, after a disconnect event, we want the device to start advertising again with updated advertisement data showing the current Wi-Fi status.

8.1 Upon a connected event, we want to cancel update_adv_data_work.

Add the following code snippet to the connected() function in main.c

k_work_cancel_delayable(&update_adv_data_work);

Copy

k_work_cancel_delayable(&update_adv_data_work);

8.2 Upon a disconnected event, reschedule both work items update_adv_param_work and update_adv_data_work.

Add the following code snippet to the disconnected() function in main.c

k_work_reschedule_for_queue(&adv_daemon_work_q, &update_adv_param_work,
			    K_SECONDS(ADV_PARAM_UPDATE_DELAY));
k_work_reschedule_for_queue(&adv_daemon_work_q, &update_adv_data_work, K_NO_WAIT);

Copy

k_work_reschedule_for_queue(&adv_daemon_work_q, &update_adv_param_work,
			    K_SECONDS(ADV_PARAM_UPDATE_DELAY));
k_work_reschedule_for_queue(&adv_daemon_work_q, &update_adv_data_work, K_NO_WAIT);

9. Enable the Bluetooth Wi-Fi Provisioning Service.

After enabling Bluetooth LE, we initialize the provisioning module using wifi_prov_init().

Add the following code snippet in main()

err = wifi_prov_init();
if (err == 0) {
	LOG_INF("Wi-Fi provisioning service starts successfully.\n");
} else {
	LOG_ERR("Error occurs when initializing Wi-Fi provisioning service.\n");
	return 0;
}

Copy

err = wifi_prov_init();
if (err == 0) {
	LOG_INF("Wi-Fi provisioning service starts successfully.\n");
} else {
	LOG_ERR("Error occurs when initializing Wi-Fi provisioning service.\n");
	return 0;
}

10. Start advertising.

10.1 Prepare the advertisement data.

struct net_if *iface = net_if_get_default();
struct net_linkaddr *mac_addr = net_if_get_link_addr(iface);
char device_name_str[sizeof(device_name) + 1];

if (mac_addr) {
	update_dev_name(mac_addr);
}
device_name_str[sizeof(device_name_str) - 1] = '\0';
memcpy(device_name_str, device_name, sizeof(device_name));
bt_set_name(device_name_str);

Copy

struct net_if *iface = net_if_get_default();
struct net_linkaddr *mac_addr = net_if_get_link_addr(iface);
char device_name_str[sizeof(device_name) + 1];

if (mac_addr) {
	update_dev_name(mac_addr);
}
device_name_str[sizeof(device_name_str) - 1] = '\0';
memcpy(device_name_str, device_name, sizeof(device_name));
bt_set_name(device_name_str);

10.2 Start advertising using bt_le_adv_start().

update_wifi_status_in_adv();

err = bt_le_adv_start(prov_svc_data[ADV_DATA_FLAG_IDX] & ADV_DATA_FLAG_PROV_STATUS_BIT ?
	PROV_BT_LE_ADV_PARAM_SLOW : PROV_BT_LE_ADV_PARAM_FAST,
	ad, ARRAY_SIZE(ad), sd, ARRAY_SIZE(sd));
if (err) {
	LOG_ERR("BT Advertising failed to start (err %d)\n", err);
	return 0;
}
LOG_INF("BT Advertising successfully started.\n");

Copy

update_wifi_status_in_adv();

err = bt_le_adv_start(prov_svc_data[ADV_DATA_FLAG_IDX] & ADV_DATA_FLAG_PROV_STATUS_BIT ?
	PROV_BT_LE_ADV_PARAM_SLOW : PROV_BT_LE_ADV_PARAM_FAST,
	ad, ARRAY_SIZE(ad), sd, ARRAY_SIZE(sd));
if (err) {
	LOG_ERR("BT Advertising failed to start (err %d)\n", err);
	return 0;
}
LOG_INF("BT Advertising successfully started.\n");

11. Initialize all work items to their respective task functions

Initialize the work items update_adv_param_work and update_adv_data_work to their respective task functions and schedule one of them for queue.

k_work_init_delayable(&update_adv_param_work, update_adv_param_task);
k_work_init_delayable(&update_adv_data_work, update_adv_data_task);
k_work_schedule_for_queue(&adv_daemon_work_q, &update_adv_data_work,
		K_SECONDS(ADV_DATA_UPDATE_INTERVAL));

Copy

k_work_init_delayable(&update_adv_param_work, update_adv_param_task);
k_work_init_delayable(&update_adv_data_work, update_adv_data_task);
k_work_schedule_for_queue(&adv_daemon_work_q, &update_adv_data_work,
		K_SECONDS(ADV_DATA_UPDATE_INTERVAL));

12. Apply stored Wi-Fi credentials.

net_mgmt(NET_REQUEST_WIFI_CONNECT_STORED, iface, NULL, 0);

Copy

net_mgmt(NET_REQUEST_WIFI_CONNECT_STORED, iface, NULL, 0);

13. Build and erase & flash the application to your board.

When flashing the application, make sure to select the icon on the right-hand side of the Flash bar, called “Erase and Flash to Board“. Otherwise, the application will connect to the network using credentials from the previous exercise.

This exercise uses the PSA backend for storing the Wi-Fi credentials. Therefore, you must build with TF-M.

Board	Build with TF-M	Extra CMake arguments
nRF7002 DK	`nrf7002dk/nrf5340/cpuapp/ns`	N/A
nRF5340 DK + nRF7002 EK	`nrf5340dk/nrf5340/cpuapp/ns`	`-DSHIELD=nrf7002ek`

Turn on the device and wait for it to start up. You should see the following log output when the device is ready to be provisioned

*** Booting nRF Connect SDK ***
[00:00:01.507,080] <inf> bt_hci_core: hci_vs_init: HW Platform: Nordic Semiconductor (0x0002)
[00:00:01.507,110] <inf> bt_hci_core: hci_vs_init: HW Variant: nRF53x (0x0003)
[00:00:01.507,141] <inf> bt_hci_core: hci_vs_init: Firmware: Standard Bluetooth controller (0x00) Version 197.47763 Build 2370639017
[00:00:01.509,063] <inf> bt_hci_core: bt_dev_show_info: Identity: E7:57:B0:79:D1:83 (random)
[00:00:01.509,094] <inf> bt_hci_core: bt_dev_show_info: HCI: version 5.4 (0x0d) revision 0x2102, manufacturer 0x0059
[00:00:01.509,124] <inf> bt_hci_core: bt_dev_show_info: LMP: version 5.4 (0x0d) subver 0x2102
[00:00:01.509,155] <inf> Lesson2_Exercise3: main: Bluetooth initialized.

[00:00:01.509,155] <inf> Lesson2_Exercise3: main: Wi-Fi provisioning service starts successfully.

[00:00:01.511,169] <inf> Lesson2_Exercise3: main: BT Advertising successfully started.

Terminal

Testing

Android
iOS

14.1 Open the nRF Wi-Fi Provisioner app and click Start.

14.2 Click on the device that appears and select Pair in the pop-up.

14.3 Click on Start provisioning.

14.4. Select the network to which you want to provision the device and enter the network password.

14.5. Click on Provision to provision the device.

Wait a few seconds. When the device is provisioned, you should see the following in the app

14.1 Open the nRF Wi-Fi Provisioner app and wait for your device to show up.

14.2 Click on the device that appears and select Pair in the pop-up.

14.3 Click on Scan to scan for nearby advertising Access Points.

14.4 Select the Wi-Fi network you want your board to connect to and scroll down to the Access Point menu.

14.5 Under Access Point, enter the password for your Wi-Fi network, then click Set.

When completed correctly, the Device Status menu should look something like this.6.6 When completed correctly, the Device Status menu should look something like this.

You should see the following log output when the device has been provisioned.

[00:00:39.612,854] <inf> wifi_prov: prov_request_handler: Start parsing...
[00:00:39.612,854] <inf> wifi_prov: prov_set_config_handler: Set_config received...
[00:00:46.372,375] <inf> Lesson2_Exercise3: wifi_connect_handler: Connected to Wi-Fi Network

Terminal

The full log of the process should look like this

*** Booting nRF Connect SDK ***
[00:00:01.507,080] <inf> bt_hci_core: hci_vs_init: HW Platform: Nordic Semiconductor (0x0002)
[00:00:01.507,110] <inf> bt_hci_core: hci_vs_init: HW Variant: nRF53x (0x0003)
[00:00:01.507,141] <inf> bt_hci_core: hci_vs_init: Firmware: Standard Bluetooth controller (0x00) Version 197.47763 Build 2370639017
[00:00:01.509,063] <inf> bt_hci_core: bt_dev_show_info: Identity: E7:57:B0:79:D1:83 (random)
[00:00:01.509,094] <inf> bt_hci_core: bt_dev_show_info: HCI: version 5.4 (0x0d) revision 0x2102, manufacturer 0x0059
[00:00:01.509,124] <inf> bt_hci_core: bt_dev_show_info: LMP: version 5.4 (0x0d) subver 0x2102
[00:00:01.509,155] <inf> Lesson2_Exercise3: main: Bluetooth initialized.

[00:00:01.509,155] <inf> Lesson2_Exercise3: main: Wi-Fi provisioning service starts successfully.

[00:00:01.511,169] <inf> Lesson2_Exercise3: main: BT Advertising successfully started.

[00:00:01.511,199] <inf> Lesson2_Exercise3: wifi_register_cb: Registering Wi-Fi events
[00:00:12.469,573] <inf> Lesson2_Exercise3: connected: BT Connected: 4F:22:C9:76:A6:18 (random)
[00:00:12.668,487] <wrn> bt_att: bt_att_recv: Unhandled ATT code 0x1d
[00:00:12.961,273] <inf> Lesson2_Exercise3: disconnected: BT Disconnected: 4F:22:C9:76:A6:18 (random) (reason 0x13).

[00:00:12.961,456] <inf> Lesson2_Exercise3: update_adv_data_task: Cannot update advertisement data, err = -11

[00:00:19.002,990] <inf> Lesson2_Exercise3: connected: BT Connected: 6E:B0:A2:28:DD:56 (random)
[00:00:19.214,813] <wrn> bt_att: bt_att_recv: Unhandled ATT code 0x1d
[00:00:21.993,743] <inf> Lesson2_Exercise3: pairing_complete: BT pairing completed: 6E:B0:A2:28:DD:56 (random), bonded: 0

[00:00:21.993,927] <inf> Lesson2_Exercise3: security_changed: BT Security changed: 6E:B0:A2:28:DD:56 (random) level 2.

[00:00:22.627,532] <inf> wifi_prov: control_point_ccc_cfg_changed: Wi-Fi Provisioning service - control point: indications enabled
[00:00:22.968,780] <inf> wifi_prov: data_out_ccc_cfg_changed: Wi-Fi Provisioning service - data out: notifications enabled
[00:00:23.456,329] <inf> wifi_prov: prov_request_handler: Start parsing...
[00:00:23.456,359] <inf> wifi_prov: prov_get_status_handler: GET_STATUS received...
OK
[00:00:24.644,958] <inf> wifi_prov: prov_request_handler: Start parsing...
[00:00:24.644,989] <inf> wifi_prov: prov_start_scan_handler: Start_Scan received...
[00:00:30.592,590] <inf> wifi_prov: prov_request_handler: Start parsing...
[00:00:30.592,620] <inf> wifi_prov: prov_stop_scan_handler: Stop_Scan received...
OK
OK

OK
OK
[00:00:39.612,854] <inf> wifi_prov: prov_request_handler: Start parsing...
[00:00:39.612,854] <inf> wifi_prov: prov_set_config_handler: Set_config received...
[00:00:46.372,375] <inf> Lesson2_Exercise3: wifi_connect_handler: Connected to Wi-Fi Network
[00:02:13.993,743] <inf> wifi_prov: control_point_ccc_cfg_changed: Wi-Fi Provisioning service - control point: indications disabled
[00:02:13.993,804] <inf> wifi_prov: data_out_ccc_cfg_changed: Wi-Fi Provisioning service - data out: notifications disabled
[00:02:13.993,957] <inf> Lesson2_Exercise3: disconnected: BT Disconnected: 6E:B0:A2:28:DD:56 (random) (reason 0x13).

Terminal

Nordic Developer Academy Terms of Service

1. Introduction

‍These terms and conditions (“Terms of Use”) apply to the use of the Nordic Developer Academy, provided by Nordic Semiconductor ASA, org. nr. 966 011 726, a public limited liability company registered in Norway (“Nordic Semiconductor”). ‍

Nordic Developer Academy allows the user to take technical courses related to Nordic Semiconductor products, software and services, and obtain a certificate certifying completion of these courses. By completing the registration process for the Nordic Developer Academy, you are agreeing to be bound by these Terms of Use.

These Terms of Use are applicable as long as you have a user account giving you access to Nordic Developer Academy.‍

‍2. Access to and use of Nordic Developer Academy

‍‍Upon acceptance of these Terms of Use you are granted a non-exclusive right of access to, and use of Nordic Developer Academy, as it is provided to you at any time. Nordic Semiconductor provides Nordic Developer Academy to you free of charge, subject to the provisions of these Terms of Use and the Nordic Developer Academy Privacy Policy.

To access select features of Nordic Developer Academy, you need to create a user account. You are solely responsible for the security associated with your user account, including always keeping your login details safe.

You will able to receive an electronic certificate from Nordic Developer Academy upon completion of courses. By issuing you such a certificate, Nordic Semiconductor certifies that you have completed the applicable course, but does not provide any further warrants or endorsements for any particular skills or professional qualifications.

Nordic Semiconductor will continuously develop Nordic Developer Academy with new features and functionality, but reserves the right to remove or alter any existing functions without notice.

‍3. Acceptable use

You undertake that you will use Nordic Developer Academy in accordance with applicable law and regulations, and in accordance with these Terms of Use.‍ You must not modify, adapt, or hack Nordic Developer Academy or modify another website so as to falsely imply that it is associated with Nordic Developer Academy, Nordic Semiconductor, or any other Nordic Semiconductor product, software or service.

You agree not to reproduce, duplicate, copy, sell, resell or in any other way exploit any portion of Nordic Developer Academy, use of Nordic Developer Academy, or access to Nordic Developer Academy without the express written permission by Nordic Semiconductor. You must not upload, post, host, or transmit unsolicited email, SMS, or \”spam\” messages.

You are responsible for ensuring that the information you post and the content you share does not;

contain false, misleading or otherwise erroneous information
infringe someone else’s copyrights or other intellectual property rights
contain sensitive personal data or
contain information that might be received as offensive or insulting.
Such information may be removed without prior notice.

‍Nordic Semiconductor reserves the right to at any time determine whether a use of Nordic Developer Academy is in violation of its requirements for acceptable use.

Violation of the at any time applicable requirements for acceptable use may result in termination of your account. We will take reasonable steps to notify you and state the reason for termination in such cases.

‍4. Routines for planned maintenance

‍Certain types of maintenance may imply a stop or reduction in availability of Nordic Developer Academy. Nordic Semiconductor does not warrant any level of service availability but will provide its best effort to limit the impact of any planned maintenance on the availability of Nordic Developer Academy.

5. Intellectual property rights

‍Nordic Semiconductor retains all rights to all elements of Nordic Developer Academy. This includes, but is not limited to, the concept, design, trademarks, know-how, trade secrets, copyrights and all other intellectual property rights.

Nordic Semiconductor receives all rights to all content uploaded or created in Nordic Developer Academy. You do not receive any license or usage rights to Nordic Developer Academy beyond what is explicitly stated in this Agreement.

‍6. Liability and damages

‍Nothing within these Terms of Use is intended to limit your statutory data privacy rights as a data subject, as described in the Nordic Developer Academy Privacy Policy. ‍You acknowledge that errors might occur from time to time and waive any right to claim for compensation as a result of errors in Nordic Developer Academy. When an error occurs, you shall notify Nordic Semiconductor of the error and provide a description of the error situation.

You agree to indemnify Nordic Semiconductor for any loss, including indirect loss, arising out of or in connection with your use of Nordic Developer Academy or violations of these Terms of Use. ‍Nordic Semiconductor shall not be held liable for, and does not warrant that (i) Nordic Developer Academy will meet your specific requirements, (ii) Nordic Developer Academy will be uninterrupted, timely, secure, or error-free, (iii) the results that may be obtained from the use of Nordic Developer Academy will be accurate or reliable, (iv) the quality of any products, services, information, or other material purchased or obtained by you through Nordic Developer Academy will meet your expectations, or that (v) any errors in Nordic Developer Academy will be corrected.

You accept that this is a service provided to you without any payment and hence you accept that Nordic Semiconductor will not be held responsible, or liable, for any breaches of these Terms of Use or any loss connected to your use of Nordic Developer Academy. Unless otherwise follows from mandatory law, Nordic Semiconductor will not accept any such responsibility or liability.

‍7. Change of terms

‍Nordic Semiconductor may update and change the Terms of Use from time to time. Nordic Semiconductor will seek to notify you about significant changes before such changes come into force and give you a possibility to evaluate the effects of proposed changes. Continued use of Nordic Developer Academy after any such changes shall constitute your acceptance of such changes. You can review the current version of the Terms of Use at any time at https://academy.nordicsemi.com/terms-of-service/

‍8. Transfer of rights

‍Nordic Semiconductor is entitled to transfer its rights and obligation pursuant to these Terms of Use to a third party as part of a merger or acquisition process, or as a result of other organizational changes.

‍9. Third Party Services

‍‍To the extent Nordic Developer Academy facilitates access to services provided by a third party, you agree to comply with the terms governing such third party services. Nordic Semiconductor shall not be held liable for any errors, omissions, inaccuracies, etc. related to such third party services.

‍10. Dispute resolution

‍‍The Terms of Use and any other legally binding agreement between yourself and Nordic Semiconductor shall be subject to Norwegian law and Norwegian courts’ exclusive jurisdiction.

Wi-Fi Fundamentals

Exercise 3 – Provisioning the device over Bluetooth LE

Exercise steps

Switch language?

Change summary

What's new in the latest version

Wi-Fi

MCUboot & Partition Manager