Home
last modified time | relevance | path

Searched refs:models (Results 1 – 25 of 78) sorted by relevance

1234

/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dmodels.rst3 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:
Dshell.rst73 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
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``
541 ``mesh models cfg timeout [Timeout(s)]``
[all …]
Daccess.rst8 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 …]
Dop_agg_srv.rst19 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
Dblob.rst3 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.
Dhealth_srv.rst7 :ref:`bluetooth_mesh_models_health_cli` models. It is primarily used to report
38 device they're provisioning, as well as through the Health models at runtime.
Dcfg.rst7 configuration directly, without going through the Configuration models.
/Zephyr-latest/samples/bluetooth/mesh/src/
Dmain.c250 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()
370 models[2].keys[0] = 0; in button_pressed()
371 models[3].keys[0] = 0; in button_pressed()
/Zephyr-latest/subsys/bluetooth/mesh/shell/
Dlarge_comp_data.c87 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,
Dod_priv_proxy.c51 SHELL_SUBCMD_ADD((mesh, models), od_priv_proxy, &od_priv_proxy_cmds,
Dop_agg.c64 SHELL_SUBCMD_ADD((mesh, models), opagg, &op_agg_cmds, "Opcode Aggregator Cli commands",
Dsol_pdu_rpl.c68 SHELL_SUBCMD_ADD((mesh, models), sol_pdu_rpl, &sol_pdu_rpl_cmds,
/Zephyr-latest/tests/bsim/bluetooth/mesh/src/
Dtest_access.c212 static const struct bt_mesh_model models[] = { variable
234 BT_MESH_ELEM(0, models, vnd_models),
270 ASSERT_OK(bt_mesh_model_extend(model, &models[4])); in model3_init()
388 bt_mesh_model_send(&models[2], &ctx, &msg, NULL, NULL); in test_tx_ext_model()
391 bt_mesh_model_send(&models[3], &ctx, &msg, NULL, NULL); in test_tx_ext_model()
394 bt_mesh_model_send(&models[4], &ctx, &msg, NULL, NULL); in test_tx_ext_model()
397 bt_mesh_model_send(&models[5], &ctx, &msg, NULL, NULL); in test_tx_ext_model()
400 bt_mesh_model_send(&models[6], &ctx, &msg, NULL, NULL); in test_tx_ext_model()
523 const struct bt_mesh_model *model = &models[2]; in msgf_publish()
685 const struct bt_mesh_model *model = &models[2]; in tx_period()
[all …]
/Zephyr-latest/samples/modules/tflite-micro/hello_world/train/
DREADME.md9 - [Trained Models](#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/boards/native/doc/
Dbsim_boards_design.rst34 .. _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/samples/modules/tflite-micro/tflm_ethosu/
DCMakeLists.txt11 target_include_directories(app PRIVATE src/models/keyword_spotting_cnn_small_int8)
/Zephyr-latest/samples/bluetooth/mesh/
DREADME.rst11 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/boards/arm/fvp_baser_aemv8r/doc/
Daarch32.rst101 …://developer.arm.com/tools-and-software/simulation-models/fixed-virtual-platforms/arm-ecosystem-mo…
104 .. [3] https://developer.arm.com/tools-and-software/simulation-models/fixed-virtual-platforms/docs
Daarch64.rst111 …://developer.arm.com/tools-and-software/simulation-models/fixed-virtual-platforms/arm-ecosystem-mo…
114 .. [3] https://developer.arm.com/tools-and-software/simulation-models/fixed-virtual-platforms/docs
/Zephyr-latest/doc/connectivity/bluetooth/api/
Dmesh.rst18 mesh/models.rst
/Zephyr-latest/boards/native/nrf_bsim/doc/
Dnrf54l15bsim.rst38 This boards include models of some of the nRF54L15 SOC peripherals:
60 check the `HW models implementation status`_.
68 .. _HW models implementation status:
Dnrf5340bsim.rst29 These boards include models of some of the nRF5340 SOC peripherals:
51 check the `HW models implementation status`_.
62 .. _HW models implementation status:
92 runner, SOC HW models, that image, and an empty image for the other MCU.
/Zephyr-latest/boards/bbc/microbit/
Dboard.cmake7 # https://www.segger.com/products/debug-probes/j-link/models/other-j-links/bbc-microbit-j-link-upgr…
/Zephyr-latest/boards/bbc/microbit_v2/
Dboard.cmake8 # https://www.segger.com/products/debug-probes/j-link/models/other-j-links/bbc-microbit-j-link-upgr…
/Zephyr-latest/subsys/bluetooth/mesh/
Daccess.c134 const struct bt_mesh_model *model = &elem->models[j]; in bt_mesh_model_foreach()
245 const struct bt_mesh_model *model = &elem->models[j]; in bt_mesh_metadata_page_0_size()
330 const struct bt_mesh_model *model = &elem->models[j]; in bt_mesh_metadata_get_page_0()
404 const struct bt_mesh_model *model = &elem->models[i]; in comp_add_elem()
590 temp_size += is_cor_present(&elem->models[i], NULL, 0) ? 2 : 1; in page1_elem_size()
591 temp_size += mod_items_size(&elem->models[i], 0); in page1_elem_size()
637 prep_model_item_header(&comp->elem[i].models[j], &cor_id, &ext_mod_cnt, buf, in bt_mesh_comp_data_get_page_1()
640 add_items_to_page(buf, &comp->elem[i].models[j], ext_mod_cnt, in bt_mesh_comp_data_get_page_1()
989 return &elem->models[mod_idx]; in bt_mesh_model_get()
1048 mod->rt->mod_idx = mod - elem->models; in mod_init()
[all …]

1234