Home
last modified time | relevance | path

Searched refs:procedure (Results 1 – 25 of 96) sorted by relevance

1234

/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Drpr_cli.rst25 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 …]
Dsar_cfg_cli.rst17 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
Ddfu.rst41 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 …]
Dblob_cli.rst35 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>`
Drpr_srv.rst21 Provisioning Protocol Interface (NPPI) procedure, the :c:member:`bt_mesh_prov.reprovisioned`
/Zephyr-latest/doc/connectivity/bluetooth/
Dbluetooth-ctlr-arch.rst148 * Miscellaneous procedure initiation API
167 * Holds local and remote procedure request queues as well as conn specific LLCP data
171 …* General procedure context data, contains miscellaneous procedure data and state as well as sys_s…
176 …* Mem pool used to implement procedure contexts resource - instantiated in both a local and a remo…
183 LLCP local and remote request/procedure state machines
189 * Local procedure queue handling
195 * Also handling of remote procedure initiation by llcp_rx_new()
196 * Miscellaneous procedure collision handling (in rr_st_idle())
199 * Individual procedure implementations (ull_llcp_common.c collects the simpler ones)
200 * Naming concept: lp_<...> => local initiated procedure, rp_<...> => remote initiated procedure
[all …]
/Zephyr-latest/modules/hal_nordic/nrfs/dvfs/
DKconfig24 int "Voltage downscale procedure safety timeout in us"
30 int "Additional delay to let secdom finish dowscale procedure in us"
/Zephyr-latest/drivers/ieee802154/
DKconfig.b9127 int "CCA procedure RSSI threshold"
30 CCA procedure returns true if the current RSSI value is less than
/Zephyr-latest/doc/connectivity/networking/api/
Dnet_mgmt.rst23 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-latest/samples/net/mqtt_sn_publisher/
DKconfig9 bool "Whether to statically define the Gateway. Will use Search procedure if False."
/Zephyr-latest/boards/atmel/sam/sam4e_xpro/doc/
Dindex.rst95 (General-Purpose NVM bit 1). The flash procedure will ensure that GPNVM1 is
100 is to perform a chip erase procedure that will erase all GPNVM bits and the full
105 (flash erasing procedure is started when the erase line is asserted for at
/Zephyr-latest/doc/services/ipc/ipc_service/backends/
Dipc_service_icbmsg.rst230 The endpoint binding procedure must be finished before sending this control message.
269 See the next section for details on the binding procedure.
289 See the next section for details on the binding procedure.
298 After ICBMsg initialization, you are ready for the endpoint binding procedure.
348 The endpoint binding procedure from the initiator's point of view is the following:
359 If the follower receives a binding message before it starts the binding procedure on that endpoint,…
362 The endpoint binding procedure from the follower's point of view is the following:
365 …The message may be a newly received message or a message stored before the binding procedure start…
/Zephyr-latest/boards/atmel/sam/sam_e70_xplained/doc/
Dindex.rst105 (General-Purpose NVM bit 1). The flash procedure will ensure that GPNVM1 is
110 is to perform a chip erase procedure that will erase all GPNVM bits and the full
115 (flash erasing procedure is started when the erase line is asserted for at
/Zephyr-latest/boards/atmel/sam/sam_v71_xult/doc/
Dindex.rst108 of GPNVM1 (General-Purpose NVM bit 1). The flash procedure will ensure that
113 is to perform a chip erase procedure that will erase all GPNVM bits and the
118 on (flash erasing procedure is started when the erase line is asserted for
/Zephyr-latest/subsys/bluetooth/controller/
DKconfig.df176 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
/Zephyr-latest/samples/boards/nordic/nrf53_sync_rtc/
DREADME.rst18 that before synchronization procedure is completed, timestamps differ significantly
19 and once procedure is completed timestamps are synchronized. Network core timestamp
/Zephyr-latest/drivers/timer/
DKconfig.nrf_grtc26 Application defines the initialization procedure and time of the GRTC
/Zephyr-latest/doc/develop/toolchains/
Dgnu_arm_embedded.rst48 …On macOS, if you are having trouble with the suggested procedure, there is an unofficial package o…
/Zephyr-latest/subsys/net/lib/mqtt/
DKconfig47 User must provide implementation for transport procedure.
/Zephyr-latest/subsys/zbus/
DKconfig14 int "The priority used during the SYS_INIT procedure."
/Zephyr-latest/subsys/bluetooth/host/
DCMakeLists.txt92 A fixed passkey is easy to deduce during the pairing procedure, do not use in
DKconfig.gatt135 Characteristic Values procedure.
187 Values procedure.
194 Characteristic Values procedure. Mandatory if EATT is enabled, optional
/Zephyr-latest/samples/bluetooth/mesh/
DREADME.rst14 used for the Out-of-Band provisioning procedure.
/Zephyr-latest/subsys/net/lib/dhcpv4/
DKconfig168 procedure. Enabling this config will violate the RFC in this regard, as
171 procedure.
/Zephyr-latest/samples/subsys/usb/testusb/
DREADME.rst15 Follow the general procedure for building and flashing Zephyr device.

1234