Lines Matching refs:be
19 in BLE Mesh, and Scan Duplicate Type must be set by choosing the
38 allow sufficient free internal memory then alternate mode can be
78 be used, and internal DRAM will be allocated for FreeRTOS objects.
84 Choose the memory to be used for FreeRTOS objects.
92 can only be used for task stack when SPIRAM_ALLOW_STACK_EXTERNAL_MEMORY
100 FreeRTOS objects, i.e. mutex, queue. Note: IRAM region cannot be used
148 Enable this option to allow BLE Mesh fast provisioning solution to be used.
152 into a node successfully, it can be changed to a temporary Provisioner.
157 Enable the device to be provisioned into a node. This option should be
158 enabled when an unprovisioned device is going to be provisioned into a
164 Enable the device to be a Provisioner. The option should be enabled when
171 int "Maximum number of unprovisioned devices that can be added to device queue"
175 This option specifies how many unprovisioned devices can be added to device
181 int "Maximum number of devices that can be provisioned by Provisioner"
185 This option specifies how many devices can be provisioned by a Provisioner.
186 This value indicates the maximum number of unprovisioned devices which can be
200 This option specifies how many devices can be provisioned at the same time
212 This option specifies how many devices can be provisioned at the same
219 int "Maximum number of mesh subnets that can be created by Provisioner"
224 … Indeed, this value decides the number of network keys which can be added by a Provisioner.
227 int "Maximum number of application keys that can be owned by Provisioner"
232 … Indeed, this value decides the number of the application keys which can be added by a Provisioner.
250 list of SRC and DST which can be used to decide if a heartbeat message will
251 be processed and notified to the application layer by Provisioner.
264 BLE Mesh, this option should be always enabled.
271 Enable this option to allow the device to be provisioned over the
272 advertising bearer. This option should be enabled if PB-ADV is
273 going to be used during provisioning procedure.
286 BLE_MESH_FAST_PROV is selected, the value is better to be 3 seconds, or less.
293 Enable this option to allow the device to be provisioned over GATT.
294 This option should be enabled if PB-GATT is going to be used during
313 This option should be enabled if a node is going to be a Proxy Server.
327 set by this option. And after that, Network ID will be advertised.
337 list of addresses which can be used to decide which messages will be forwarded
364 of the device will be stored persistently, including unicast address, NetKey,
367 be stored persistently, including the information of provisioned nodes, NetKey,
381 will be stored immediately once there are updates.
390 sequence number will be stored to flash on every 100th increment.
395 so that it starts off with a value that's guaranteed to be larger than
406 node receives messages rarely, then the value can be as low as 0 (which
411 introduce message replay attacks and system security will be in a
425 be failure in recovering node information during node restarting
442 default NVS partition. Note that the specified partition must be registered
446 flash (e.g. more than 20), this option is recommended to be enabled.
464 A and provisions three devices, these information will be treated as
467 information will be treated as mesh information instance B.
468 Here instance A and instance B will be stored in different namespaces.
489 Indeed, this value decides the number of the network keys which can be owned by a node.
497 … Indeed, this value decides the number of the application keys which can be owned by a node.
505 can be bound.
513 be subscribed.
520 This option specifies how many Label UUIDs can be stored.
521 … Indeed, this value decides the number of the Virtual Addresses can be supported by a node.
533 For Provisioner, the replay protection list size should not be smaller than
534 the maximum number of nodes whose information can be stored. And the element
535 number of each node should also be taken into consideration. For example, if
537 then the replay protection list size of Provisioner should be at least 40.
574 be powered off once in a while, we need to store persistently
578 ways that the node will be used and what kind of power source it
595 message at a time. And if another segmented message is going to be sent, it
598 value should be configured properly.
607 message at a time. And if another segmented message is going to be received,
610 value should be configured properly.
626 This value should typically be fine-tuned based on what
628 message payload that the node needs to be able to send.
640 when setting this option to a higher value. There must be at
651 be enabled or disabled by proper configuration messages. Disabling this
660 When selected, self-send packets will be put in a high-priority
661 queue and relay packets will be put in a low-priority queue.
681 is required by a node, this option should be enabled. And once the node
704 for Friend nodes. If this option is disabled LPN mode needs to be manually
784 The initial value of the PollTimeout timer when Friendship is to be
811 Enable this option to be able to act as a Friend Node.
827 Minimum number of buffers available to be stored for each local Friend Queue.
828 This option decides the size of each buffer which can be used by a Friend node
836 Size of the Subscription List that can be supported by a Friend node for a
858 messages destined for the Friend queue be received simultaneously.
954 the default value will be used which is four seconds.
1094 lets the state to be changed at any time.
1095 If IV Update test mode is going to be used, this option should be enabled.
1115 needs to be invoked to add the node information into the mesh stack.