Home
last modified time | relevance | path

Searched refs:provision (Results 1 – 19 of 19) sorted by relevance

/Zephyr-Core-3.7.0/tests/bsim/bluetooth/mesh/src/
Dtest_access.c309 static void provision(uint16_t addr) in provision() function
375 provision(UNICAST_ADDR1); in test_tx_ext_model()
416 provision(UNICAST_ADDR2); in test_sub_ext_model()
467 provision(UNICAST_ADDR2); in test_sub_capacity_ext_model()
689 provision(UNICAST_ADDR1); in tx_period()
730 provision(UNICAST_ADDR2); in rx_period()
777 provision(UNICAST_ADDR1); in tx_transmit()
828 provision(UNICAST_ADDR2); in rx_transmit()
877 provision(UNICAST_ADDR1); in test_tx_cancel()
935 provision(UNICAST_ADDR2); in test_rx_cancel()
Dtest_beacon.c1096 static void provision(const struct bt_mesh_test_cfg *dev_cfg) in provision() function
1114 provision(&tx_cfg); in tx_priv_setup()
1152 provision(&tx_cfg); in test_tx_priv_adv()
1310 provision(&rx_cfg); in test_rx_priv_invalid()
1369 provision(&tx_cfg); in test_tx_priv_interleave()
1500 provision(&rx_cfg); in test_rx_priv_beacon_cache()
1712 provision(cfg); in tx_proxy_adv_common_init()
2137 provision(&tx_cfg); in test_tx_priv_gatt_proxy()
2166 provision(&rx_cfg); in test_rx_priv_gatt_proxy()
Dtest_dfu.c348 static void provision(uint16_t addr) in provision() function
389 provision(addr); in dist_prov_and_conf()
403 provision(addr); in dist_self_update_prov_and_conf()
419 provision(addr); in target_prov_and_conf()
Dtest_blob.c291 static void provision(uint16_t addr) in provision() function
319 provision(addr); in blob_srv_prov_and_conf()
345 provision(addr); in blob_cli_prov_and_conf()
/Zephyr-Core-3.7.0/doc/connectivity/bluetooth/api/mesh/
Drpr_cli.rst12 This model provides functionality to remotely provision devices into a mesh network, and perform
92 Server node. This procedure will attempt to provision the device with the corresponding UUID, and
Dshell.rst43 The simplest way to provision the device is through self-provisioning. To do this the user must
44 provision the device with the default network key and address ``0x0001``, execute::
49 devices, as long as they're assigned non-overlapping unicast addresses. Alternatively, to provision
52 provisioner, which can provision the node into its network.
310 To allow a device to provision devices, the :kconfig:option:`CONFIG_BT_MESH_PROVISIONER` and
326 To allow a device to provision devices over GATT, the :kconfig:option:`CONFIG_BT_MESH_PROVISIONER`
387 * ``NetKeyIdx``: Index of the network key to provision.
396 detect nearby unprovisioned devices and provision them. To enable this command, the
1735 ``mesh models rpr provision-remote <UUID(1-16 hex)> <NetKeyIdx> <Addr>``
1825 ``mesh provision`` and ``mesh provision-adv`` will be added automatically if the
/Zephyr-Core-3.7.0/doc/security/standards/
Detsi-303645.rst160 - the provision is a mandatory requirement
163 - the provision is a recommendation
166 - the provision is a mandatory requirement and conditional
169 - the provision is a recommendation and conditional
172 - The provision is supported by Zephyr
175 - The provision is not supported by Zephyr
178 - The provision is not applicable to Zephyr or it is product makers responsibility
/Zephyr-Core-3.7.0/samples/bluetooth/mesh_provisioner/
DREADME.rst22 provision detected devices automatically. Once provisioning is done, the
/Zephyr-Core-3.7.0/samples/bluetooth/mesh/
DREADME.rst57 external provisioner device, or self-provision through a button press.
/Zephyr-Core-3.7.0/samples/boards/nrf/mesh/onoff-app/
DREADME.rst67 provision <discovered UUID>
/Zephyr-Core-3.7.0/samples/boards/nrf/mesh/onoff_level_lighting_vnd_app/
DREADME.rst83 provision <discovered UUID>
/Zephyr-Core-3.7.0/subsys/bluetooth/mesh/shell/
Drpr.c422 SHELL_CMD_ARG(provision-remote, NULL, "<UUID(1-16 hex)> <NetKeyIdx> <Addr>",
/Zephyr-Core-3.7.0/doc/security/
Dsensor-threat.rst299 [th-initial-provision]_. In
309 c. **Re-provisioning**. Sometimes it is necessary to re-provision a
390 .. [th-initial-provision]
/Zephyr-Core-3.7.0/doc/kernel/services/other/
Dfloat.rst156 register context, there are no provision for saving an ISR's FPU context
206 register context, there are no provision for saving an ISR's FPU context
/Zephyr-Core-3.7.0/samples/net/lwm2m_client/
DREADME.rst197 already joined device with joiner capabilities, or provision it manually
/Zephyr-Core-3.7.0/doc/releases/
Drelease-notes-2.0.rst832 * :github:`17497` - Bluetooth: Mesh: How to Write provision and configure data to flash?
1246 * :github:`15504` - Can I use one custom random static bd_addr before provision?
Drelease-notes-2.1.rst682 * :github:`19685` - Samples: BluetoothMesh: not able to connect with device over GATT to provision …
Drelease-notes-2.3.rst1386 * :github:`15504` - Can I use one custom random static bd_addr before provision?
Drelease-notes-2.4.rst1305 * :github:`26804` - Bluetooth mesh repeated provision/gatt bearer connection crash