Searched refs:procedure (Results 1 – 25 of 86) sorted by relevance
1234
| /Zephyr-Core-3.7.0/doc/connectivity/bluetooth/api/mesh/ |
| D | rpr_cli.rst | 25 The scanning procedure is used to scan for unprovisioned devices located nearby the Remote
26 Provisioning Server. The Remote Provisioning Client starts a scan procedure by using the
56 The above example shows pseudo code for starting a scan procedure on the target Remote Provisioning
57 Server node. This procedure will start a ten-second, multiple-device scanning where the generated
59 specified, the same procedure would only scan for the device with the corresponding UUID. After the
60 procedure completes, the server sends the scan report that will be handled in the client's
72 The Remote Provisioning Client starts a provisioning procedure by using the
92 Server node. This procedure will attempt to provision the device with the corresponding UUID, and
107 * Device Key Refresh procedure: Used to change the device key of the Target node without a need to
109 * Node Address Refresh procedure: Used to change the node’s device key and unicast address.
[all …]
|
| D | sar_cfg_cli.rst | 17 The SAR Transmitter procedure is used to determine and configure the SAR Transmitter state of a SAR
22 The SAR Receiver procedure is used to determine and configure the SAR Receiver state of a SAR
|
| D | dfu.rst | 41 node in the Upload Firmware procedure, then it distributes the uploaded image to other Target
185 according to the Firmware Check Over HTTPS procedure defined by the specification. The firmware
250 The Upload Firmware procedure uses the :ref:`bluetooth_mesh_blob` to transfer the firmware image
251 from the Initiator to the Distributor. The Upload Firmware procedure works in two steps:
290 may initiate the distribution procedure. The BLOB transfer parameters for the distribution are
316 If the distribution procedure completed with at least one Target node reporting that the image has
317 been received and verified, the distribution procedure is considered successful.
320 The firmware distribution procedure only fails if *all* Target nodes are lost. It is up to the
336 procedure on all Target nodes that successfully received and verified the firmware image. The Apply
337 Firmware on Target Node procedure takes no parameters, and to avoid ambiguity, it should be
[all …]
|
| D | blob_cli.rst | 35 Both the transfer capabilities retrieval procedure and the BLOB transfer uses an instance of a
38 to live (TTL) value before it is used in a procedure:
98 procedure populates the transfer capabilities from all Target nodes with the most liberal set of
107 The end of the procedure is signalled through the :c:member:`caps <bt_mesh_blob_cli_cb.caps>`
|
| D | rpr_srv.rst | 21 Provisioning Protocol Interface (NPPI) procedure, the :c:member:`bt_mesh_prov.reprovisioned`
|
| /Zephyr-Core-3.7.0/drivers/ieee802154/ |
| D | Kconfig.b91 | 27 int "CCA procedure RSSI threshold"
30 CCA procedure returns true if the current RSSI value is less than
|
| /Zephyr-Core-3.7.0/doc/connectivity/networking/api/ |
| D | net_mgmt.rst | 23 procedures are not used. Instead, defined procedure handlers are
31 Requesting a defined procedure
37 implied, and the specific management procedure being requested. The
38 available procedure requests depend on what has been implemented in
168 Defining a network management procedure
195 This new management procedure could then be called by using:
|
| /Zephyr-Core-3.7.0/modules/hal_nordic/nrfs/dvfs/ |
| D | Kconfig | 24 int "Voltage downscale procedure safety timeout in us"
|
| /Zephyr-Core-3.7.0/boards/atmel/sam/sam4e_xpro/doc/ |
| D | index.rst | 102 (General-Purpose NVM bit 1). The flash procedure will ensure that GPNVM1 is
107 is to perform a chip erase procedure that will erase all GPNVM bits and the full
112 (flash erasing procedure is started when the erase line is asserted for at
|
| /Zephyr-Core-3.7.0/boards/atmel/sam/sam_e70_xplained/doc/ |
| D | index.rst | 112 (General-Purpose NVM bit 1). The flash procedure will ensure that GPNVM1 is
117 is to perform a chip erase procedure that will erase all GPNVM bits and the full
122 (flash erasing procedure is started when the erase line is asserted for at
|
| /Zephyr-Core-3.7.0/boards/atmel/sam/sam_v71_xult/doc/ |
| D | index.rst | 115 of GPNVM1 (General-Purpose NVM bit 1). The flash procedure will ensure that
120 is to perform a chip erase procedure that will erase all GPNVM bits and the
125 on (flash erasing procedure is started when the erase line is asserted for
|
| /Zephyr-Core-3.7.0/subsys/bluetooth/controller/ |
| D | Kconfig.df | 176 If this feature is not enabled, the Radio initialization procedure will
208 of 16M cycles. Decreasing the offset value beyond the trigger of the AoA/AoD procedure
219 is 1 us. Decreasing the offset beyond the trigger of the AoA/AoD procedure will have
230 is 1 us. Decreasing the offset beyond the trigger of the AoA/AoD procedure will have
242 is 2 us. Decreasing the offset beyond the trigger of the AoA/AoD procedure will have
253 is 2 us. Decreasing the offset beyond the trigger of the AoA/AoD procedure will have
|
| D | Kconfig.ll_sw_split | 317 Enable support for Bluetooth v4.2 LE Data Length Update procedure, up to
644 the event, like control procedure handling and CPU execution speeds.
763 and/or PHY Update procedure to avoid overlap of radio events
882 two for active encryption procedure plus one for rejecting a remote request
893 to buffer(s) for control procedure TX
902 for control procedure tx. This pool is shared across all
907 int "Number of local control procedure contexts to be available across all connections"
913 Set the number control procedure contexts that is to be available.
914 This defines the size of the pool of control procedure contexts available
919 int "Number of remote control procedure contexts to be available across all connections"
[all …]
|
| /Zephyr-Core-3.7.0/samples/boards/nrf/nrf53_sync_rtc/ |
| D | README.rst | 18 that before synchronization procedure is completed, timestamps differ significantly
19 and once procedure is completed timestamps are synchronized. Network core timestamp
|
| /Zephyr-Core-3.7.0/drivers/timer/ |
| D | Kconfig.nrf_grtc | 27 Application defines the initialization procedure and time of the GRTC
|
| /Zephyr-Core-3.7.0/subsys/zbus/ |
| D | Kconfig | 14 int "The priority used during the SYS_INIT procedure."
|
| /Zephyr-Core-3.7.0/doc/develop/toolchains/ |
| D | gnu_arm_embedded.rst | 48 …On macOS, if you are having trouble with the suggested procedure, there is an unofficial package o…
|
| /Zephyr-Core-3.7.0/subsys/net/lib/mqtt/ |
| D | Kconfig | 47 User must provide implementation for transport procedure.
|
| /Zephyr-Core-3.7.0/subsys/bluetooth/host/ |
| D | CMakeLists.txt | 88 A fixed passkey is easy to deduce during the pairing procedure, do not use in
|
| D | Kconfig.gatt | 136 Characteristic Values procedure.
188 Values procedure.
195 Characteristic Values procedure. Mandatory if EATT is enabled, optional
|
| /Zephyr-Core-3.7.0/subsys/net/lib/dhcpv4/ |
| D | Kconfig | 160 procedure. Enabling this config will violate the RFC in this regard, as
163 procedure.
|
| /Zephyr-Core-3.7.0/samples/bluetooth/mesh/ |
| D | README.rst | 13 used for the Out-of-Band provisioning procedure.
|
| /Zephyr-Core-3.7.0/samples/subsys/usb/testusb/ |
| D | README.rst | 15 Follow the general procedure for building and flashing Zephyr device.
|
| /Zephyr-Core-3.7.0/modules/openthread/ |
| D | Kconfig.features | 93 handshake used in the commissioning procedure requires a larger
185 handshake used in the commissioning procedure requires a larger
|
| /Zephyr-Core-3.7.0/drivers/bluetooth/hci/ |
| D | Kconfig | 207 Update procedure for new connections for controllers that do not
208 auto-initiate the procedure if the default data length parameters are
|
1234
