samples: bluetooth: Use "Bluetooth LE" terminology
Replace occurrences of "BLE" by the recommended "Bluetooth LE" term. Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
This commit is contained in:
parent
d23d19d7f0
commit
d1858d2074
50 changed files with 99 additions and 99 deletions
|
@ -14,7 +14,7 @@ Requirements
|
|||
************
|
||||
|
||||
* BlueZ running on the host, or
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
|
||||
Building and Running
|
||||
********************
|
||||
|
|
|
@ -17,7 +17,7 @@ Requirements
|
|||
************
|
||||
|
||||
* BlueZ running on the host, or
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
|
||||
Building and Running
|
||||
********************
|
||||
|
|
|
@ -12,7 +12,7 @@ This code sample provides a template for implementing a `BTHome <https://bthome.
|
|||
Requirements
|
||||
************
|
||||
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
* A BTHome compatible listener, for example `Home Assistant <https://www.home-assistant.io/>`_ with the BTHome integration running.
|
||||
|
||||
Building and Running
|
||||
|
|
|
@ -2,20 +2,20 @@
|
|||
:name: Central
|
||||
:relevant-api: bluetooth
|
||||
|
||||
Implement basic BLE Central role functionality (scanning and connecting).
|
||||
Implement basic Bluetooth LE Central role functionality (scanning and connecting).
|
||||
|
||||
Overview
|
||||
********
|
||||
|
||||
Application demonstrating very basic BLE Central role functionality by scanning
|
||||
for other BLE devices and establishing a connection to the first one with a
|
||||
Application demonstrating very basic Bluetooth LE Central role functionality by scanning
|
||||
for other Bluetooth LE devices and establishing a connection to the first one with a
|
||||
strong enough signal.
|
||||
|
||||
Requirements
|
||||
************
|
||||
|
||||
* BlueZ running on the host, or
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
|
||||
Building and Running
|
||||
********************
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
:name: Central / GATT Write
|
||||
:relevant-api: bluetooth
|
||||
|
||||
Scan for a BLE device, connect to it and write a value to a characteristic.
|
||||
Scan for a Bluetooth LE device, connect to it and write a value to a characteristic.
|
||||
|
||||
Overview
|
||||
********
|
||||
|
@ -14,7 +14,7 @@ Requirements
|
|||
************
|
||||
|
||||
* BlueZ running on the host, or
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
|
||||
Building and Running
|
||||
********************
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
:name: Heart-rate Monitor (Central)
|
||||
:relevant-api: bluetooth
|
||||
|
||||
Connect to a BLE heart-rate monitor and read heart-rate measurements.
|
||||
Connect to a Bluetooth LE heart-rate monitor and read heart-rate measurements.
|
||||
|
||||
Overview
|
||||
********
|
||||
|
@ -15,7 +15,7 @@ Requirements
|
|||
************
|
||||
|
||||
* BlueZ running on the host, or
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
|
||||
Building and Running
|
||||
********************
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
:name: Health Thermometer (Central)
|
||||
:relevant-api: bluetooth
|
||||
|
||||
Connect to a BLE health thermometer sensor and read temperature measurements.
|
||||
Connect to a Bluetooth LE health thermometer sensor and read temperature measurements.
|
||||
|
||||
Overview
|
||||
********
|
||||
|
@ -15,7 +15,7 @@ Requirements
|
|||
************
|
||||
|
||||
* BlueZ running on the host, or
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
|
||||
Building and Running
|
||||
********************
|
||||
|
|
|
@ -7,7 +7,7 @@
|
|||
Overview
|
||||
********
|
||||
|
||||
Application demonstrating BLE Central role functionality by scanning for other
|
||||
Application demonstrating Bluetooth LE Central role functionality by scanning for other
|
||||
BLE devices and establishing connection to up to 62 peripherals with a strong
|
||||
enough signal.
|
||||
|
||||
|
@ -15,7 +15,7 @@ Requirements
|
|||
************
|
||||
|
||||
* BlueZ running on the host, or
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
|
||||
Building and Running
|
||||
********************
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
:name: Central OTC
|
||||
:relevant-api: bluetooth
|
||||
|
||||
Connect to a BLE peripheral that supports the Object Transfer Service (OTS)
|
||||
Connect to a Bluetooth LE peripheral that supports the Object Transfer Service (OTS)
|
||||
|
||||
Overview
|
||||
********
|
||||
|
@ -15,7 +15,7 @@ to read data, and to calculate checksum of selected objects.
|
|||
Requirements
|
||||
************
|
||||
|
||||
* A board with BLE support and 4 buttons.
|
||||
* A board with Bluetooth LE support and 4 buttons.
|
||||
|
||||
Building and Running
|
||||
********************
|
||||
|
|
|
@ -7,13 +7,13 @@
|
|||
Overview
|
||||
********
|
||||
|
||||
A simple application demonstrating the BLE Periodic Advertising Sync Transfer
|
||||
A simple application demonstrating the Bluetooth LE Periodic Advertising Sync Transfer
|
||||
functionality as the sender.
|
||||
|
||||
Requirements
|
||||
************
|
||||
|
||||
* A board with BLE 5.1 support
|
||||
* A board with Bluetooth LE 5.1 support
|
||||
|
||||
Building and Running
|
||||
********************
|
||||
|
|
|
@ -7,21 +7,21 @@
|
|||
Overview
|
||||
********
|
||||
|
||||
Application demonstrating the BLE Direct Advertising capability. If no device is bonded
|
||||
Application demonstrating the Bluetooth LE Direct Advertising capability. If no device is bonded
|
||||
to the peripheral, casual advertising will be performed. Once bonded, on every subsequent
|
||||
boot direct advertising to the bonded central will be performed. Additionally this sample
|
||||
provides two BLE characteristics. To perform write, devices need to be bonded, while read
|
||||
provides two Bluetooth LE characteristics. To perform write, devices need to be bonded, while read
|
||||
can be done just after connection (no bonding required).
|
||||
|
||||
Please note that direct advertising towards iOS based devices is not allowed.
|
||||
For more information about designing BLE devices for Apple products refer to
|
||||
For more information about designing Bluetooth LE devices for Apple products refer to
|
||||
"Accessory Design Guidelines for Apple Devices".
|
||||
|
||||
Requirements
|
||||
************
|
||||
|
||||
* A board with BLE support
|
||||
* Second BLE device acting as a central with enabled privacy. For example another Zephyr board
|
||||
* A board with Bluetooth LE support
|
||||
* Second Bluetooth LE device acting as a central with enabled privacy. For example another Zephyr board
|
||||
or any modern smartphone
|
||||
|
||||
Building and Running
|
||||
|
|
|
@ -2,12 +2,12 @@
|
|||
:name: Direction Finding Central
|
||||
:relevant-api: bluetooth
|
||||
|
||||
Connect to a BLE Direction Finding peripheral and request Constant Tone Extension.
|
||||
Connect to a Bluetooth LE Direction Finding peripheral and request Constant Tone Extension.
|
||||
|
||||
Overview
|
||||
********
|
||||
|
||||
A simple application demonstrating the BLE Direction Finding CTE reception in
|
||||
A simple application demonstrating the Bluetooth LE Direction Finding CTE reception in
|
||||
connected mode by requesting transmission of a packet containing Constant
|
||||
Tone Extension by connected peer device.
|
||||
|
||||
|
|
|
@ -2,12 +2,12 @@
|
|||
:name: Direction Finding Periodic Advertising Locator
|
||||
:relevant-api: bt_gap bluetooth
|
||||
|
||||
Implement BLE Direction Finding CTE Locator functionality.
|
||||
Implement Bluetooth LE Direction Finding CTE Locator functionality.
|
||||
|
||||
Overview
|
||||
********
|
||||
|
||||
A simple application demonstrating the BLE Direction Finding CTE Locator
|
||||
A simple application demonstrating the Bluetooth LE Direction Finding CTE Locator
|
||||
functionality by receiving and sampling sending Constant Tone Extension with
|
||||
periodic advertising PDUs.
|
||||
|
||||
|
|
|
@ -2,12 +2,12 @@
|
|||
:name: Direction Finding Periodic Advertising Beacon
|
||||
:relevant-api: bt_gap bluetooth
|
||||
|
||||
Implement BLE Direction Finding CTE Broadcaster functionality.
|
||||
Implement Bluetooth LE Direction Finding CTE Broadcaster functionality.
|
||||
|
||||
Overview
|
||||
********
|
||||
|
||||
A simple application demonstrating the BLE Direction Finding CTE Broadcaster
|
||||
A simple application demonstrating the Bluetooth LE Direction Finding CTE Broadcaster
|
||||
functionality by sending Constant Tone Extension with periodic advertising PDUs.
|
||||
|
||||
Requirements
|
||||
|
|
|
@ -2,12 +2,12 @@
|
|||
:name: Direction Finding Peripheral
|
||||
:relevant-api: bluetooth
|
||||
|
||||
Implement BLE Direction Finding peripheral transmitting CTE in connected mode.
|
||||
Implement Bluetooth LE Direction Finding peripheral transmitting CTE in connected mode.
|
||||
|
||||
Overview
|
||||
********
|
||||
|
||||
A simple application demonstrating the BLE Direction Finding CTE transmission in
|
||||
A simple application demonstrating the Bluetooth LE Direction Finding CTE transmission in
|
||||
connected mode by response to a request received from connected peer device.
|
||||
|
||||
Requirements
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
:name: Eddystone
|
||||
:relevant-api: bluetooth
|
||||
|
||||
Export an Eddystone Configuration Service as a BLE GATT service.
|
||||
Export an Eddystone Configuration Service as a Bluetooth LE GATT service.
|
||||
|
||||
Overview
|
||||
********
|
||||
|
@ -19,7 +19,7 @@ Requirements
|
|||
************
|
||||
|
||||
* BlueZ running on the host, or
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
|
||||
Building and Running
|
||||
********************
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
:name: Encrypted Advertising
|
||||
:relevant-api: bluetooth
|
||||
|
||||
Use the BLE encrypted advertising feature.
|
||||
Use the Bluetooth LE encrypted advertising feature.
|
||||
|
||||
Overview
|
||||
********
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
:name: Extended Advertising
|
||||
:relevant-api: bluetooth
|
||||
|
||||
Use the BLE extended advertising feature.
|
||||
Use the Bluetooth LE extended advertising feature.
|
||||
|
||||
Overview
|
||||
********
|
||||
|
|
|
@ -2,13 +2,13 @@
|
|||
:name: HCI Power Control
|
||||
:relevant-api: bt_hrs bluetooth
|
||||
|
||||
Dynamically control the Tx power of a BLE Controller using HCI vendor-specific commands.
|
||||
Dynamically control the Tx power of a Bluetooth LE Controller using HCI vendor-specific commands.
|
||||
|
||||
Overview
|
||||
********
|
||||
|
||||
This sample application demonstrates the dynamic Tx power control over the LL
|
||||
of the BLE controller via Zephyr HCI VS commands. The application implements a
|
||||
of the Bluetooth LE controller via Zephyr HCI VS commands. The application implements a
|
||||
peripheral advertising with varying Tx power. The initial advertiser TX power
|
||||
for the first 5s of the application is the Kconfig set default TX power. Then,
|
||||
the TX power variation of the advertiser is a repeatedly descending staircase
|
||||
|
@ -25,7 +25,7 @@ Requirements
|
|||
************
|
||||
|
||||
* BlueZ running on the host, or
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
* A central device & monitor (e.g. nRF Connect) to check the RSSI values
|
||||
obtained from the peripheral.
|
||||
|
||||
|
|
|
@ -13,7 +13,7 @@ using the H:4 HCI transport protocol (requires HW flow control from the UART).
|
|||
Requirements
|
||||
************
|
||||
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
|
||||
Default UART settings
|
||||
*********************
|
||||
|
@ -35,8 +35,8 @@ Using the controller with emulators and BlueZ
|
|||
|
||||
The instructions below show how to use a Nordic nRF5x device as a Zephyr BLE
|
||||
controller and expose it to Linux's BlueZ. This can be very useful for testing
|
||||
the Zephyr Link Layer with the BlueZ Host. The Zephyr BLE controller can also
|
||||
provide a modern BLE 5.0 controller to a Linux-based machine for native
|
||||
the Zephyr Link Layer with the BlueZ Host. The Zephyr Bluetooth LE controller can also
|
||||
provide a modern Bluetooth LE 5.0 controller to a Linux-based machine for native
|
||||
BLE support or QEMU-based development.
|
||||
|
||||
First, make sure you have a recent BlueZ version installed by following the
|
||||
|
@ -130,7 +130,7 @@ Then attach RTT as described here: :ref:`Using Segger J-Link <Using Segger J-Lin
|
|||
Support for the Direction Finding
|
||||
=================================
|
||||
|
||||
The sample can be built with the support for the BLE Direction Finding.
|
||||
The sample can be built with the support for the Bluetooth LE Direction Finding.
|
||||
To enable this feature build this sample for specific board variants that provide
|
||||
required hardware configuration for the Radio.
|
||||
|
||||
|
|
|
@ -13,7 +13,7 @@ using the H:5 HCI transport protocol.
|
|||
Requirements
|
||||
************
|
||||
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
|
||||
Default UART settings
|
||||
*********************
|
||||
|
@ -35,8 +35,8 @@ Using the controller with emulators and BlueZ
|
|||
|
||||
The instructions below show how to use a Nordic nRF5x device as a Zephyr BLE
|
||||
controller and expose it to Linux's BlueZ. This can be very useful for testing
|
||||
the Zephyr Link Layer with the BlueZ Host. The Zephyr BLE controller can also
|
||||
provide a modern BLE 5.0 controller to a Linux-based machine for native
|
||||
the Zephyr Link Layer with the BlueZ Host. The Zephyr Bluetooth LE controller can also
|
||||
provide a modern Bluetooth LE 5.0 controller to a Linux-based machine for native
|
||||
BLE support or QEMU-based development.
|
||||
|
||||
First, make sure you have a recent BlueZ version installed by following the
|
||||
|
@ -130,7 +130,7 @@ Then attach RTT as described here: :ref:`Using Segger J-Link <Using Segger J-Lin
|
|||
Support for the Direction Finding
|
||||
=================================
|
||||
|
||||
The sample can be built with the support for the BLE Direction Finding.
|
||||
The sample can be built with the support for the Bluetooth LE Direction Finding.
|
||||
To enable this feature build this sample for specific board variants that provide
|
||||
required hardware configuration for the Radio.
|
||||
|
||||
|
|
|
@ -16,7 +16,7 @@ of the HCI UART sample may be different.
|
|||
Requirements
|
||||
************
|
||||
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
|
||||
Default UART settings
|
||||
*********************
|
||||
|
|
|
@ -8,7 +8,7 @@ Overview
|
|||
********
|
||||
|
||||
Make a USB Bluetooth dongle out of Zephyr. Requires USB device support from the
|
||||
board it runs on (e.g. :ref:`nrf52840dk_nrf52840` supports both BLE and USB).
|
||||
board it runs on (e.g. :ref:`nrf52840dk_nrf52840` supports both Bluetooth LE and USB).
|
||||
|
||||
Requirements
|
||||
************
|
||||
|
|
|
@ -8,7 +8,7 @@ Overview
|
|||
********
|
||||
|
||||
Make a USB H4 Bluetooth dongle out of Zephyr. Requires USB device support from
|
||||
the board it runs on (e.g. :ref:`nrf52840dk_nrf52840` supports both BLE and
|
||||
the board it runs on (e.g. :ref:`nrf52840dk_nrf52840` supports both Bluetooth LE and
|
||||
USB).
|
||||
|
||||
Requirements
|
||||
|
|
|
@ -18,7 +18,7 @@ connection can also be added, depending on configuration choices.
|
|||
Requirements
|
||||
************
|
||||
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
* A central device & monitor (e.g. nRF Connect) to check the advertiments and
|
||||
send scan requests.
|
||||
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
:name: ISO (Peripheral)
|
||||
:relevant-api: bt_bas bluetooth
|
||||
|
||||
Implement a BLE Peripheral that uses isochronous channels.
|
||||
Implement a Bluetooth LE Peripheral that uses isochronous channels.
|
||||
|
||||
Overview
|
||||
********
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
:name: Synchronized Receiver
|
||||
:relevant-api: bt_iso bluetooth
|
||||
|
||||
Use BLE Synchronized Receiver functionality.
|
||||
Use Bluetooth LE Synchronized Receiver functionality.
|
||||
|
||||
Overview
|
||||
********
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
:name: Mesh
|
||||
:relevant-api: bt_mesh bluetooth
|
||||
|
||||
Use basic BLE Mesh functionality.
|
||||
Use basic Bluetooth LE Mesh functionality.
|
||||
|
||||
Overview
|
||||
********
|
||||
|
|
|
@ -2,17 +2,17 @@
|
|||
:name: Periodic Advertising
|
||||
:relevant-api: bt_gap bluetooth
|
||||
|
||||
Use BLE Periodic Advertising functionality.
|
||||
Use Bluetooth LE Periodic Advertising functionality.
|
||||
|
||||
Overview
|
||||
********
|
||||
|
||||
A simple application demonstrating the BLE Periodic Advertising functionality.
|
||||
A simple application demonstrating the Bluetooth LE Periodic Advertising functionality.
|
||||
|
||||
Requirements
|
||||
************
|
||||
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
|
||||
Building and Running
|
||||
********************
|
||||
|
|
|
@ -18,7 +18,7 @@ wait for disconnect before connecting to another synced device.
|
|||
Requirements
|
||||
************
|
||||
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
* A controller that supports the Periodic Advertising with Responses (PAwR) - Advertiser feature
|
||||
|
||||
Building and Running
|
||||
|
|
|
@ -2,12 +2,12 @@
|
|||
:name: Periodic Advertising with Responses (PAwR) Advertiser
|
||||
:relevant-api: bt_gap bluetooth
|
||||
|
||||
Use BLE Periodic Advertising with Responses (PAwR) Advertiser functionality.
|
||||
Use Bluetooth LE Periodic Advertising with Responses (PAwR) Advertiser functionality.
|
||||
|
||||
Overview
|
||||
********
|
||||
|
||||
A simple application demonstrating the BLE Periodic Advertising with
|
||||
A simple application demonstrating the Bluetooth LE Periodic Advertising with
|
||||
Responses Advertiser functionality.
|
||||
|
||||
This sample will scan for the corresponding sync sample and send the required
|
||||
|
@ -24,7 +24,7 @@ the assigned subevent and response slot.
|
|||
Requirements
|
||||
************
|
||||
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
* A controller that supports the Periodic Advertising with Responses (PAwR) - Advertiser feature
|
||||
|
||||
Building and Running
|
||||
|
|
|
@ -2,18 +2,18 @@
|
|||
:name: Periodic Advertising Synchronization
|
||||
:relevant-api: bt_gap bluetooth
|
||||
|
||||
Use BLE Periodic Advertising Synchronization functionality.
|
||||
Use Bluetooth LE Periodic Advertising Synchronization functionality.
|
||||
|
||||
Overview
|
||||
********
|
||||
|
||||
A simple application demonstrating the BLE Periodic Advertising Synchronization
|
||||
A simple application demonstrating the Bluetooth LE Periodic Advertising Synchronization
|
||||
functionality.
|
||||
|
||||
Requirements
|
||||
************
|
||||
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
|
||||
Building and Running
|
||||
********************
|
||||
|
|
|
@ -17,7 +17,7 @@ for a new connection to be established.
|
|||
Requirements
|
||||
************
|
||||
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
* A controller that supports the Periodic Advertising with Responses (PAwR) - Scanner feature
|
||||
|
||||
Building and Running
|
||||
|
|
|
@ -2,12 +2,12 @@
|
|||
:name: Periodic Advertising with Responses (PAwR) Synchronization
|
||||
:relevant-api: bt_gap bluetooth
|
||||
|
||||
Implement BLE Periodic Advertising with Responses Synchronization.
|
||||
Implement Bluetooth LE Periodic Advertising with Responses Synchronization.
|
||||
|
||||
Overview
|
||||
********
|
||||
|
||||
A simple application demonstrating the BLE Periodic Advertising with
|
||||
A simple application demonstrating the Bluetooth LE Periodic Advertising with
|
||||
Responses Synchronization functionality.
|
||||
|
||||
This sample will echo the data received in subevent indications back to the
|
||||
|
@ -25,7 +25,7 @@ advertiser concurrently.
|
|||
Requirements
|
||||
************
|
||||
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
* A controller that supports the Periodic Advertising with Responses (PAwR) - Scanner feature
|
||||
|
||||
Building and Running
|
||||
|
|
|
@ -2,12 +2,12 @@
|
|||
:name: Peripheral
|
||||
:relevant-api: bt_gatt bluetooth
|
||||
|
||||
Implement basic BLE Peripheral role functionality (advertising and exposing GATT services).
|
||||
Implement basic Bluetooth LE Peripheral role functionality (advertising and exposing GATT services).
|
||||
|
||||
Overview
|
||||
********
|
||||
|
||||
Application demonstrating the BLE Peripheral role. It has several well-known and
|
||||
Application demonstrating the Bluetooth LE Peripheral role. It has several well-known and
|
||||
vendor-specific GATT services that it exposes.
|
||||
|
||||
|
||||
|
@ -15,7 +15,7 @@ Requirements
|
|||
************
|
||||
|
||||
* BlueZ running on the host, or
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
|
||||
Building and Running
|
||||
********************
|
||||
|
|
|
@ -7,7 +7,7 @@
|
|||
Overview
|
||||
********
|
||||
|
||||
This application demonstrates the BLE advertising accept filter list feature.
|
||||
This application demonstrates the Bluetooth LE advertising accept filter list feature.
|
||||
If no device is bonded to the peripheral, casual advertising will be performed.
|
||||
Once a device is bonded, on subsequent boots, connection requests will only be
|
||||
accepted if the central device is on the accept list. Additionally, scan response
|
||||
|
@ -15,15 +15,15 @@ data will only be sent to devices that are on the accept list. As a result, some
|
|||
BLE central devices (such as Android smartphones) might not display the device
|
||||
in the scan results if the central device is not on the accept list.
|
||||
|
||||
This sample also provides two BLE characteristics. To perform a write, devices need
|
||||
This sample also provides two Bluetooth LE characteristics. To perform a write, devices need
|
||||
to be bonded, while a read can be done immediately after a connection
|
||||
(no bonding required).
|
||||
|
||||
Requirements
|
||||
************
|
||||
|
||||
* A board with BLE support
|
||||
* Second BLE device acting as a central. For example another Zephyr board or smartphone
|
||||
* A board with Bluetooth LE support
|
||||
* Second Bluetooth LE device acting as a central. For example another Zephyr board or smartphone
|
||||
|
||||
Building and Running
|
||||
********************
|
||||
|
|
|
@ -16,7 +16,7 @@ Requirements
|
|||
************
|
||||
|
||||
* BlueZ running on the host, or
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
|
||||
Building and Running
|
||||
********************
|
||||
|
|
|
@ -15,7 +15,7 @@ Requirements
|
|||
************
|
||||
|
||||
* BlueZ running on the host, or
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
|
||||
Building and Running
|
||||
********************
|
||||
|
|
|
@ -15,7 +15,7 @@ Requirements
|
|||
************
|
||||
|
||||
* BlueZ running on the host, or
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
|
||||
Building and Running
|
||||
********************
|
||||
|
|
|
@ -15,7 +15,7 @@ Requirements
|
|||
************
|
||||
|
||||
* BlueZ running on the host, or
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
|
||||
Building and Running
|
||||
********************
|
||||
|
|
|
@ -21,7 +21,7 @@ Requirements
|
|||
************
|
||||
|
||||
* BlueZ running on the host, or
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
|
||||
Building and Running
|
||||
********************
|
||||
|
|
|
@ -16,7 +16,7 @@ Requirements
|
|||
************
|
||||
|
||||
* BlueZ running on the host, or
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
|
||||
Building and Running
|
||||
********************
|
||||
|
|
|
@ -19,7 +19,7 @@ Requirements
|
|||
************
|
||||
|
||||
* BlueZ running on the host, or
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
|
||||
Building and Running
|
||||
********************
|
||||
|
|
|
@ -14,7 +14,7 @@ Requirements
|
|||
************
|
||||
|
||||
* BlueZ running on the host, or
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
|
||||
Building and Running
|
||||
********************
|
||||
|
|
|
@ -16,7 +16,7 @@ Requirements
|
|||
************
|
||||
|
||||
* BlueZ running on the host, or
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
|
||||
Building and Running
|
||||
********************
|
||||
|
|
|
@ -15,7 +15,7 @@ Requirements
|
|||
************
|
||||
|
||||
* BlueZ running on the host, or
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
|
||||
Building and Running
|
||||
********************
|
||||
|
|
|
@ -7,13 +7,13 @@
|
|||
Overview
|
||||
********
|
||||
|
||||
A simple application demonstrating the BLE Periodic Advertising Synchronization
|
||||
A simple application demonstrating the Bluetooth LE Periodic Advertising Synchronization
|
||||
Transfer (PAST) functionality as the receiver.
|
||||
|
||||
Requirements
|
||||
************
|
||||
|
||||
* A board with BLE 5.1 support
|
||||
* A board with Bluetooth LE 5.1 support
|
||||
|
||||
Building and Running
|
||||
********************
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
:name: Peripheral SC-only
|
||||
:relevant-api: bt_conn bluetooth
|
||||
|
||||
Enable "Secure Connections Only" mode for a BLE peripheral.
|
||||
Enable "Secure Connections Only" mode for a Bluetooth LE peripheral.
|
||||
|
||||
Overview
|
||||
********
|
||||
|
@ -16,7 +16,7 @@ Requirements
|
|||
************
|
||||
|
||||
* BlueZ running on the host, or
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
|
||||
Building and Running
|
||||
********************
|
||||
|
|
|
@ -2,12 +2,12 @@
|
|||
:name: Scan & Advertise
|
||||
:relevant-api: bt_gap bluetooth
|
||||
|
||||
Combine BLE Broadcaster & Observer roles to advertise and scan for devices simultaneously.
|
||||
Combine Bluetooth LE Broadcaster & Observer roles to advertise and scan for devices simultaneously.
|
||||
|
||||
Overview
|
||||
********
|
||||
|
||||
A simple application demonstrating combined BLE Broadcaster & Observer
|
||||
A simple application demonstrating combined Bluetooth LE Broadcaster & Observer
|
||||
role functionality. The application will periodically send out
|
||||
advertising packets with a manufacturer data element. The content of the
|
||||
data is a single byte indicating how many advertising packets the device
|
||||
|
@ -17,7 +17,7 @@ Requirements
|
|||
************
|
||||
|
||||
* BlueZ running on the host, or
|
||||
* A board with BLE support
|
||||
* A board with Bluetooth LE support
|
||||
|
||||
Building and Running
|
||||
********************
|
||||
|
|
|
@ -1,5 +1,5 @@
|
|||
.. zephyr:code-sample:: bluetooth_st_ble_sensor
|
||||
:name: ST BLE Sensor Demo
|
||||
:name: ST Bluetooth LE Sensor Demo
|
||||
:relevant-api: bt_gatt bluetooth
|
||||
|
||||
Export vendor-specific GATT services over BLE.
|
||||
|
@ -7,16 +7,16 @@
|
|||
Overview
|
||||
********
|
||||
|
||||
This application demonstrates BLE peripheral by exposing vendor-specific
|
||||
This application demonstrates Bluetooth LE peripheral by exposing vendor-specific
|
||||
GATT services. Currently only button notification and LED service are
|
||||
implemented. Other BLE sensor services can easily be added.
|
||||
implemented. Other Bluetooth LE sensor services can easily be added.
|
||||
See `BlueST protocol`_ document for details of how to add a new service.
|
||||
|
||||
Requirements
|
||||
************
|
||||
|
||||
* `ST BLE Sensor Android app`_
|
||||
* A board with BLE support
|
||||
* `ST Bluetooth LE Sensor Android app`_
|
||||
* A board with Bluetooth LE support
|
||||
|
||||
Building and Running
|
||||
********************
|
||||
|
@ -24,14 +24,14 @@ Building and Running
|
|||
This sample can be found under :zephyr_file:`samples/bluetooth/st_ble_sensor` in the
|
||||
Zephyr tree.
|
||||
|
||||
Open ST BLE Sensor app and click on "CONNECT TO A DEVICE" button to scan BLE devices.
|
||||
Open ST Bluetooth LE Sensor app and click on "CONNECT TO A DEVICE" button to scan Bluetooth LE devices.
|
||||
To connect click on the device shown in the Device List.
|
||||
After connected, tap LED image on Android to test LED service.
|
||||
Push SW0 button on embedded device to test button service.
|
||||
|
||||
See :ref:`bluetooth samples section <bluetooth-samples>` for details.
|
||||
|
||||
.. _ST BLE Sensor Android app:
|
||||
.. _ST Bluetooth LE Sensor Android app:
|
||||
https://play.google.com/store/apps/details?id=com.st.bluems
|
||||
|
||||
.. _BlueST protocol:
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue