| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | models.rst | 3 Mesh models
6 Foundation models
9 The Bluetooth Mesh specification defines foundation models that can be
36 Model specification models
39 In addition to the foundation models defined in the Bluetooth Mesh specification, the Bluetooth Mesh
40 Model Specification defines several models, some of which are implemented in Zephyr:
|
| D | access.rst | 8 into elements and models, which are implemented by the application.
10 Mesh models
13 The functionality of a mesh node is represented by models. A model implements
15 thermostat. The mesh models are grouped into *elements*. Each element is
20 element instantiating all the models required for a single aspect of the
25 Bluetooth SIG have defined a set of foundation models (see
26 :ref:`bluetooth_mesh_models`) and a set of models for implementing common
28 <https://www.bluetooth.com/specifications/mesh-specifications/>`_. All models
29 not specified by the Bluetooth SIG are vendor models, and must be tied to a
32 Mesh models have several parameters that can be configured either through
[all …]
|
| D | dfu_srv.rst | 54 Composition Data and Models Metadata
62 will be represented by Composition Data Pages 128, 129, and 130. The Models Metadata of the new
63 firmware image will be represented by Models Metadata Page 128. Composition Data Pages 0, 1 and 2,
64 and Models Metadata Page 0, will represent the Composition Data and the Models Metadata of the old
69 :c:func:`bt_mesh_models_metadata_change_prepare` to store the existing Composition Data and Models
70 Metadata pages before booting into the firmware with the updated Composition Data and Models
73 and 130. The Models Metadata for the old image will be loaded into Models Metadata Page 0, and the
74 Models Metadata for the new image will be loaded into Models Metadata Page 128.
|
| D | shell.rst | 73 uart:~$ mesh models cfg get-comp
79 uart:~$ mesh models cfg appkey add 0 0
111 the foundation models. To receive a packet in the mesh node, you have to add a model with a valid
488 Models subsection
496 module (``mesh models cfg``) inside the ``mesh models`` subcommand list. This module will work on
517 * Monitor the composition data of the local node (``mesh models cfg get-comp``).
523 * Monitor the composition data of the target device (``mesh models cfg get-comp``).
526 ``mesh models cfg target get``
531 ``mesh models cfg help``
536 ``mesh models cfg reset``
[all …]
|
| D | op_agg_srv.rst | 19 The targeted server models should be bound to the same application key that is used
23 respective models and their message handlers. Current implementation assumes that
|
| D | blob.rst | 3 BLOB Transfer models
6 The Binary Large Object (BLOB) Transfer models implement the Bluetooth Mesh Binary Large Object
12 The BLOB Transfer models support transfers of continuous binary objects of up to 4 GB (2 \ :sup:`32`
26 There are two BLOB Transfer models:
92 In the BLOB Transfer models' APIs, the BLOB data handling is separated from the high-level transfer
100 used, and the BLOB Transfer models will move around inside the BLOB's data in blocks and chunks,
191 This section contains types and defines common to the BLOB Transfer models.
|
| /Zephyr-latest/soc/native/inf_clock/ |
| D | soc.c | 13 * the HW models.
15 * The HW models raising an interrupt will "awake the cpu" by calling
19 * given back to the HW models.
21 * The Zephyr OS+APP code and the HW models are gated by a mutex +
23 * HW models run or vice versa
50 * This is how the idle thread halts the CPU and gets halted until the HW models
51 * raise a new interrupt; and how the HW models awake the CPU, and wait for it
64 * HW models shall call this function to "awake the CPU"
87 * until the CPU is awoken again by the HW models) in posix_halt_cpu()
118 * The HW models will call this function to "boot" the CPU
|
| D | posix_native_task.h | 24 * or the HW models are initialized
27 * but before the HW models are initialized
29 * * PRE_BOOT_3: Will be called after the HW models initialization, right before
|
| /Zephyr-latest/dts/bindings/sdhc/ |
| D | espressif,esp32-sdhc-slot.yaml | 31 Clock pin for ESP32 and SoC models with fixed pins for SDIO.
38 Command pin for ESP32 and SoC models with fixed pins for SDIO.
45 Data 0 pin for ESP32 and SoC models with fixed pins for SDIO.
52 Data 1 pin for ESP32 and SoC models with fixed pins for SDIO.
59 Data 2 pin for ESP32 and SoC models with fixed pins for SDIO.
66 Data 3 pin for ESP32 and SoC models with fixed pins for SDIO.
|
| /Zephyr-latest/scripts/native_simulator/common/src/ |
| D | nsi_tasks.h | 32 * or the HW models are initialized
35 * but before the HW models are initialized
37 * * HW_INIT: Will be called during HW models initialization
39 * * PRE_BOOT_3: Will be called after the HW models initialization, right before
|
| D | nsi_hw_scheduler.c | 9 * Overall HW models scheduler for the native simulator
11 * Models events are registered with NSI_HW_EVENT().
24 uint64_t nsi_simu_time; /* The actual time as known by the HW models */
147 * Note that the HW models should register their initialization functions
161 * Note that the HW models should register their initialization functions
|
| /Zephyr-latest/boards/native/doc/ |
| D | bsim_boards_design.rst | 34 .. _Architecture of HW models used for FW development and testing:
43 .. _nRF HW models design documentation:
55 will include some HW models which, to some degree, pretend to be the real
96 the OS, models of peripherals etc. By testing them in conjunction,
128 Relationship between Zephyr, the native simulator, the nRF HW models and BabbleSim
133 expanded by the nRF HW models for that target.
136 The native simulator runner is built together with the HW models which match your desired target.
144 Relationship between Zephyr, the native simulator, the nRF HW models and BabbleSim.
169 HW models thread ( See `Threading`_ ).
171 selecting the HW models which are built in the native simulator runner context, IRQ handling,
[all …]
|
| /Zephyr-latest/boards/native/nrf_bsim/common/ |
| D | bstests.h | 28 * test ticker or other HW models.
31 /* It will be called (in the HW models thread) before the CPU is booted,
32 * after the HW models have been initialized. Note that a possible delayed
38 * It will be called (in the HW models thread) when the CPU goes to sleep
42 /* It will be called (in the HW models thread) each time the bst_timer ticks */
45 * It will be called (in the HW models thread) when the execution is being
|
| /Zephyr-latest/include/zephyr/bluetooth/mesh/ |
| D | large_comp_data_cli.h | 53 /** @brief Optional callback for Models Metadata Status message.
55 * Handles received Models Metadata Status messages from a Large Composition Data
116 /** @brief Send Models Metadata Get message.
118 * This API is used to read a portion of a Models Metadata Page.
130 * @param page Models Metadata Page to read.
131 * @param offset Offset within the Models Metadata Page.
|
| D | access.h | 136 * In case the element has no SIG or Vendor models the helper
140 * @param _mods Array of models.
141 * @param _vnd_mods Array of vendor models.
149 .models = (_mods), \
163 /** The number of SIG models in this element */
165 /** The number of vendor models in this element */
168 /** The list of SIG models in this element */
169 const struct bt_mesh_model * const models; member
170 /** The list of vendor models in this element */
175 * @name Foundation Models
[all …]
|
| /Zephyr-latest/samples/modules/tflite-micro/hello_world/train/ |
| D | README.md | 9 - [Trained Models](#trained-models)
38 ## Trained Models
40 Download Link | [hello_world.zip](https://storage.googleapis.com/download.tensorflow.org/models/tfl…
43 The `models` directory in the above zip file can be generated by following the
|
| /Zephyr-latest/samples/boards/nordic/mesh/onoff_level_lighting_vnd_app/ |
| D | README.rst | 2 :name: Mesh Models
5 Setup a Bluetooth Mesh node with various models (generic OnOff, generic Level, ...).
10 which Root element has following models
29 And Secondary element has following models
39 Associations of Models with hardware
|
| /Zephyr-latest/samples/bluetooth/mesh/ |
| D | README.rst | 11 standard mesh models, and supports provisioning over both the
61 device an Application key and bind it to both Generic OnOff models.
64 bind a dummy Application key to these models.
|
| /Zephyr-latest/samples/bluetooth/mesh/src/ |
| D | main.c | 249 /* This application only needs one element to contain its models */
250 static const struct bt_mesh_model models[] = { variable
260 BT_MESH_ELEM(0, models, BT_MESH_MODEL_NONE),
305 .app_idx = models[3].keys[0], /* Use the bound key */ in gen_onoff_send()
324 return bt_mesh_model_send(&models[3], &ctx, &buf, NULL, NULL); in gen_onoff_send()
360 /* Add an application key to both Generic OnOff models: */ in button_pressed()
367 /* Models must be bound to an app key to send and receive messages with in button_pressed()
370 models[2].keys[0] = 0; in button_pressed()
371 models[3].keys[0] = 0; in button_pressed()
|
| /Zephyr-latest/scripts/native_simulator/common/src/include/ |
| D | nsi_hws_models_if.h | 30 * (Normally HW models will not care about the event ordering, and will simply set a prio like 100)
32 * Only very particular models will need to execute before or after others.
|
| D | nsi_cpu_if.h | 54 * Called during initialization (before the HW models are initialized)
96 * That is, when a embedded SW action in the HW models, causes an immediate
104 * When the runner HW models use them and for what is up to those
105 * specific models.
|
| /Zephyr-latest/subsys/bluetooth/mesh/ |
| D | large_comp_data_srv.c | 125 LOG_DBG("Models Metadata Page 128"); in handle_models_metadata_get()
128 LOG_DBG("Models Metadata Page %u not available", page); in handle_models_metadata_get()
140 LOG_ERR("Unable to get stored models metadata"); in handle_models_metadata_get()
152 LOG_ERR("Failed to get Models Metadata Page 0: %d", err); in handle_models_metadata_get()
159 LOG_ERR("Unable to send Models Metadata Status"); in handle_models_metadata_get()
|
| /Zephyr-latest/subsys/bluetooth/mesh/shell/ |
| D | large_comp_data.c | 79 status_print(err, "Models Metadata", bt_mesh_shell_target_ctx.dst, &rsp); in cmd_models_metadata_get()
87 SHELL_CMD_ARG(models-metadata-get, NULL, "<page> <offset>", cmd_models_metadata_get, 3, 0),
90 SHELL_SUBCMD_ADD((mesh, models), lcd, &large_comp_data_cmds,
|
| /Zephyr-latest/boards/native/native_posix/ |
| D | hw_models_top.c | 8 * Reduced set of HW models sufficient to run some of the sample apps
27 static uint64_t simu_time; /* The actual time as known by the HW models */
180 * Function to initialize the HW models
193 * Function to free any resources allocated by the HW models
|
| /Zephyr-latest/samples/boards/nordic/mesh/onoff_level_lighting_vnd_app/src/mesh/ |
| D | no_transition_work_handler.h | 1 /* Bluetooth: Mesh Generic OnOff, Generic Level, Lighting & Vendor Models
|
