mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-01 14:22:33 +00:00
f288d1e4a7
Tick rate is becoming a platform tunable in the tickless world. Some apps were setting it due to requirements of drivers or subsystems (or sometimes for reasons that don't make much sense), but the dependency goes the other way around now: board/soc/arch level code is responsible for setting tick rates that work with their devices. A few tests still use hard-configured tick rates, as they have baked-in assumptions (like e.g. "a tick will be longer than a millisecond") that need to be addressed first. Signed-off-by: Andy Ross <andrew.j.ross@intel.com> |
||
|---|---|---|
| .. | ||
| src | ||
| CMakeLists.txt | ||
| microbit_gatt.conf | ||
| prj_bbc_microbit.conf | ||
| prj_nrf51_blenano.conf | ||
| prj.conf | ||
| README.rst | ||
| sample.yaml | ||
.. _ble_mesh: Bluetooth: Mesh ############### Overview ******** This sample demonstrates Bluetooth Mesh functionality. It has several standard Mesh models, and supports provisioning over both the Advertising and the GATT Provisioning Bearers (i.e. PB-ADV and PB-GATT). The application also needs a functioning serial console, since that's used for the Out-of-Band provisioning procedure. Requirements ************ * A board with Bluetooth LE support, or * QEMU with BlueZ running on the host Building and Running ******************** This sample can be found under :zephyr_file:`samples/bluetooth/mesh` in the Zephyr tree. See :ref:`bluetooth samples section <bluetooth-samples>` for details on how to run the sample inside QEMU. For other boards, build and flash the application as follows: .. zephyr-app-commands:: :zephyr-app: samples/bluetooth/mesh :board: <board> :goals: flash :compact: Refer to your :ref:`board's documentation <boards>` for alternative flash instructions if your board doesn't support the ``flash`` target.