Searched refs:model (Results 301 – 325 of 1024) sorted by relevance
1...<<11121314151617181920>>...41
6 The Firmware Distribution Server model implements the Distributor role for the18 Distribution Client model on a different device to give it information and trigger image
36 implemented by the :ref:`bluetooth_mesh_dfu_srv` model. A transfer may be targeting any number of69 replace the Firmware Distribution Server model with a proprietary mechanism that will access the70 Firmware Update Client model directly, e.g. over a serial protocol.200 DFU. Depending on the availability of the Remote Provisioning Server model on the old and new image,220 Update Server model calls the :c:member:`bt_mesh_dfu_srv_cb.check` callback, the application can257 #. The Initiator's BLOB Transfer Client model transfers the firmware image to the Distributor's BLOB299 The Distributor's Firmware Update Client model uses its BLOB Transfer Client model's broadcast303 1. The Distributor's Firmware Update Client model generates a BLOB ID and sends it to each Target304 node's Firmware Update Server model, along with the other BLOB transfer parameters, the Target306 check and prepares their BLOB Transfer Server model for the transfer, before sending a status[all …]
20 The Bridge Configuration Server model is mandatory for supporting the Subnet Bridge feature.21 The Bridge Configuration Client model is optional and allows nodes to configure the Subnet Bridge on28 A node implementing the Bridge Configuration Client model can act as a *Configuration Manager* for61 by the Bridge Configuration Server model.72 Server model on the target node, using the :c:func:`bt_mesh_brg_cfg_cli_set` function.79 Server model on the target node, calling the :c:func:`bt_mesh_brg_cfg_cli_table_add` or
8 model = "Seagate Legend 3.5 board";
14 model = "emsdp";
15 model = "emsdp";
12 model = "GigaDevice GD32F350R Evaluation Kit";
13 model = "STMicroelectronics STM32H745I-DISCO board";
13 model = "Nordic NRF7002 DK NRF5340 Application";
13 model = "Nordic Thingy53 NRF5340 Application";
15 model = "em_starterkit-em7d";
15 model = "em_starterkit-em11d";
15 model = "em_starterkit-em9d";
12 model = "Redbear BLE Nano";
13 model = "SiFive HiFive 1";
13 model = "NXP i.MX95 EVK board";
14 model = "NXP LPCXpresso55S16 board";
12 model = "STMicroelectronics STM32H745ZI-Q-NUCLEO board";
11 model = "STMicroelectronics STM32U575ZI-NUCLEO-Q board";
14 model = "Ezurio BL5340 (nRF5340) Network";
11 model = "FVP BaseR AEMv8R";
41 For the nRF52840-PDK board, these are the model associations:104 address as it is the only one that has a configuration server model. If108 The meshctl utility also supports a onoff model client that can be used to111 that has that LED's model and issuing the onoff command.
12 model = "Space Cubics OBC module 1";
