Searched refs:commands (Results 676 – 700 of 1376) sorted by relevance
1...<<21222324252627282930>>...56
47 .. zephyr-app-commands::
3 # and it must therefore be possible to call individual commands, depending
59 .. zephyr-app-commands::
35 .. zephyr-app-commands::
30 .. zephyr-app-commands::
45 .. zephyr-app-commands::
22 issuing one of the following commands then rebuilding the project:
35 issuing one of the following commands then rebuilding the project:
30 issuing one of the following commands then rebuilding the project:
27 .. zephyr-app-commands::
43 .. zephyr-app-commands::
34 .. zephyr-app-commands::
29 .. zephyr-app-commands::
6 The Bluetooth Mesh shell subsystem provides a set of Bluetooth Mesh shell commands for the30 sub-commands. Every time the device boots up, make sure to call ``mesh init`` before any of the31 other Bluetooth Mesh shell commands can be called::55 general configuration commands:69 :ref:`bluetooth_mesh_shell_cfg_cli` commands.106 local unicast address before issuing any configuration commands.118 The Bluetooth Mesh shell commands are parsed with a variety of formats:142 The Bluetooth Mesh shell implements a large set of commands. Some of the commands accept parameters,147 The Bluetooth Mesh shell commands are divided into the following groups:154 Some commands depend on specific features being enabled in the compile time configuration of[all …]
148 .. zephyr-app-commands::197 .. zephyr-app-commands::242 .. zephyr-app-commands::279 .. zephyr-app-commands::312 .. zephyr-app-commands::
62 .. zephyr-app-commands::
49 .. zephyr-app-commands::
44 .. zephyr-app-commands::
60 .. zephyr-app-commands::
7 # (and other commands which end up calling check_c_source_compiles())
26 .. zephyr-app-commands::
