The wireless examples feature many common Bluetooth, zigbee and thread configurations. This article describes each SDK example.
MCUs:
Category | SDK Example Name | Description | comments |
BLE Controller | hci_bb | the HCI black box demo gives access to the BLE controller via serial interface using commands and events. | |
Bluetooth | adv_ext_central |
the adv_ext_central implements a custom GATT based temperature Profile. After pairing with the peripheral, it configures notifications and displays temperature values on a terminal. |
Board to Board |
Bluetooth |
adv_ext_peripheral |
the adv_ext_peripheral implements a custom GATT based temperature Profile. it begins with a general discoverable mode and waits for the central node to connect and configure notifications for the temperature value. |
Board to Board |
Bluetooth |
ancs_c |
the demo acts as a peripheral that advertises a service solicitation for custom ANCS service. Also, can acts as a client once connected to the device offering the ANCS service. The application displays information about ANCS notifications received from the mobile. this service is available on iOS mobile devices. |
|
Bluetooth |
beacon |
the demo has non-connectable advertising packets that are sent on the three advertising channels. From the info sent by the beacon we can see:
|
IoT toolbox app |
Bluetooth |
ble_fscibb |
implements a custom GATT based wireless UART profile. it can be possible to interact with the device through a serial terminal. |
Serial Terminal |
Bluetooth |
ble_shell |
implements a console application that allows the user to interact with a full feature BLE stack library. implements GAP roles and both client and server, to enabling these roles can be done using some commands. this demo allows the user to add, erase or modify services. |
Serial Terminal |
Bluetooth |
eatt_central |
the application behaves as a GAP central node. It scans for an EATT peripheral to connect to. Once connected it performs service discovery, initiates an EATT connection and configures indications on the peripheral for services A and B. The central reports the received service data and steps taken during the setup on a serial terminal. |
Board to Board |
Bluetooth |
eatt_peripheral |
the application behaves as a GAP peripheral node. it works a as general discoverable mode and waits for a GAP central node to connect. This application implements two services, Service A and Service B. After the EATT connection in completed, the peer must enable indications for the two services to periodically receive profile data over EATT. |
Board to Board |
Bluetooth |
hid_device |
(Mouse) the demo moves the cursor in a square pattern between a min and max axis. this demo behaves as a GAP peripheral node with a general discoverable mode that waits for a GAP central node to connect. |
|
Bluetooth |
hid_host |
the application behaves as a GAP central node. it works as a GAP limited discovery Procedure and searches for HID devices to connect to. After connecting with the peripheral node, it configures notifications and displays the received HID reports on a serial terminal. |
Serial Terminal |
Bluetooth |
loc_reader |
the application behaves as a GAP peripheral node. This application has the RASP profile implemented; it advertises for compatible devices, once it connected begins to send ranging data to the central device. |
Board to Board |
Bluetooth |
loc_user_device |
the application behaves as a GAP central node. it scans for compatible devices, once it connected begins to send ranging commands to the peripheral device and calculates the distance estimation based on the information received. |
Board to Board |
Bluetooth |
otac_att |
the over the air programming client is a GAP peripheral which advertising the BLE OTAP service and waits for a connection from an OTAP server. After an OTAP server connects, the OTAP client waits for it to write the OTAP control point CCCD and then starts sending commands via ATT indications. |
over the air programming tool //IoT toolbox app |
Bluetooth |
otac_I2cap |
(different transfer method) The over the air programming client is a GAP peripheral which advertising the BLE OTAP service and waits for a connection from an OTAP server. After an OTAP server connects, the OTAP client waits for it to write the OTAP control point CCCD and then starts sending commands via ATT indications. |
|
Bluetooth |
otas |
the Over the air programming server application is a GAP central which scans for devices advertising the BLE OTAP service. After it finds one, it connects to it and configures the OTAP control point CCC descriptor to receive ATT indications from the device then it waits fir OTAP commands from the device. |
|
Bluetooth |
temp_coll |
the application behaves as a GAP central node, it enters GAP limited discovery procedure and searches for sensor devices to pair with. After pairing with the peripheral, it configures notifications and displays temperature values on a serial terminal. |
Board to Board |
Bluetooth |
temp_sens |
the application behaves as a GAP peripheral node. it enters GAP general discoverable mode and waits for a GAP central node to connect and configure notifications for the temperature value. |
Board to Board |
Bluetooth |
w_uart |
implements a custom GATT based wireless UART profile. it can be possible to interact with the device through a serial terminal. |
IoT toolbox app |
Bluetooth |
wireless_ranging |
Is used to perform secure and highly accurate distance estimation between two BLE device. the application is made of two parts:
Wireless Ranging application allows to:
|
Board to Board |
genfsk |
connectivity_test |
Board to Board |
|
ieee_802.15.4 |
connectivity_test |
Board to Board |
|
reference design |
bluetooth |
this application is based on a GATT temperature Service and demonstrates power consumption optimization in BLE. The power consumption is optimized during advertising, connected and no activity states. |
|