CONFIG_OPENTHREAD_MANUAL_START
Start OpenThread stack manually
Type: bool
Help
If enabled, OpenThread stack will have to be configured and
started manually, with respective API calls or CLI/NCP commands.
Otherwise, OpenThread will configure the network parametrs and try to
join the Thread network automatically during initialization (using
credentials stored in persistend storage, obtained during
commissioning or pre-commissioned with other Kconfig options,
depending on configuration used).
Direct dependencies
NET_L2_OPENTHREAD
|| (NET_L2_OPENTHREAD
&& NETWORKING
)
(Includes any dependencies from ifs and menus.)
Default
y
Symbols that select this symbol
Kconfig definitions
At <nRF>/subsys/net/openthread/Kconfig.defconfig:49
Included via <Zephyr>/Kconfig:8
→ <Zephyr>/Kconfig.zephyr:33
→ <Zephyr>/modules/Kconfig:6
→ <nRF>/doc/_build/kconfig/Kconfig.modules:2
→ <nRF>/Kconfig.nrf:7
Menu path: (Top) → Modules → nrf (/home/runner/work/sdk-nrf/sdk-nrf/ncs/nrf)
config OPENTHREAD_MANUAL_START
bool
default y
depends on NET_L2_OPENTHREAD
At <Zephyr>/subsys/net/l2/openthread/Kconfig:48
Included via <Zephyr>/Kconfig:8
→ <Zephyr>/Kconfig.zephyr:44
→ <Zephyr>/subsys/Kconfig:39
→ <Zephyr>/subsys/net/Kconfig:81
→ <Zephyr>/subsys/net/l2/Kconfig:82
Menu path: (Top) → Sub Systems and OS Services → Networking → Link layer and IP networking support → Link layer options → OpenThread L2
config OPENTHREAD_MANUAL_START
bool "Start OpenThread stack manually"
depends on NET_L2_OPENTHREAD && NETWORKING
help
If enabled, OpenThread stack will have to be configured and
started manually, with respective API calls or CLI/NCP commands.
Otherwise, OpenThread will configure the network parametrs and try to
join the Thread network automatically during initialization (using
credentials stored in persistend storage, obtained during
commissioning or pre-commissioned with other Kconfig options,
depending on configuration used).
(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)