Searched +full:thread +full:- +full:border +full:- +full:router (Results 1 – 10 of 10) sorted by relevance
/Zephyr-latest/doc/connectivity/networking/api/ |
D | thread.rst | 3 Thread protocol 12 Thread is a low-power mesh networking technology, designed specifically for home 13 automation applications. It is an IPv6-based standard, which uses 6LoWPAN 15 a Thread mesh network to the internet with a Thread Border Router. 17 The Thread specification provides a high level of network security. Mesh networks 18 built with Thread are secure - only authenticated devices can join the network 20 Thread protocol can be found at 21 `Thread Group website <https://www.threadgroup.org>`_. 23 Zephyr integrates an open source Thread protocol implementation called OpenThread, 29 A Thread Border Router is required to connect mesh network to the internet. [all …]
|
/Zephyr-latest/samples/net/openthread/coprocessor/ |
D | README.rst | 1 .. zephyr:code-sample:: openthread-coprocessor 2 :name: OpenThread co-processor 3 :relevant-api: openthread 5 Build a Thread border-router using OpenThread's co-processor designs. 10 OpenThread Co-Processor allows building a Thread Border Router. The code in this 11 sample is only the MCU target part of a complete Thread Border Router. 12 The Co-Processor can act in two variants: Network Co-Processor (NCP) and Radio 13 Co-Processor (RCP), see https://openthread.io/platforms/co-processor. 15 Additional required host-side tools (e.g. otbr-agent) to build a Thread Border 16 Router can be obtained by following [all …]
|
/Zephyr-latest/modules/openthread/ |
D | Kconfig.features | 4 # SPDX-License-Identifier: Apache-2.0 10 This option selects version of Thread stack 37 bool "Backbone Router functionality" 50 bool "Border Agent support" 53 bool "Border agent ephemeral PSKc" 56 bool "Create and save border agent ID" 59 bool "Border Router support" 62 bool "Border routing support" 65 bool "Border routing counters support" 68 bool "DHCPv6-PD support in border routing" [all …]
|
D | CMakeLists.txt | 19 set(OT_THREAD_VERSION ${CONFIG_OPENTHREAD_THREAD_VERSION} CACHE STRING "User selected Thread stack … 42 kconfig_to_ot_option(CONFIG_OPENTHREAD_BACKBONE_ROUTER OT_BACKBONE_ROUTER "Enable backbone router f… 46 kconfig_to_ot_option(CONFIG_OPENTHREAD_BORDER_AGENT OT_BORDER_AGENT "Enable Border Agent") 47 …NFIG_OPENTHREAD_BORDER_AGENT_EPHEMERAL_KEY_ENABLE OT_BORDER_AGENT_EPSKC "Border agent ephemeral PS… 48 kconfig_to_ot_option(CONFIG_OPENTHREAD_BORDER_AGENT_ID OT_BORDER_AGENT_ID "Create and save border a… 49 kconfig_to_ot_option(CONFIG_OPENTHREAD_BORDER_ROUTER OT_BORDER_ROUTER "Enable Border Router") 50 kconfig_to_ot_option(CONFIG_OPENTHREAD_BORDER_ROUTING OT_BORDER_ROUTING "Enable Border routing") 51 …FIG_OPENTHREAD_BORDER_ROUTING_COUNTERS OT_BORDER_ROUTING_COUNTERS "Enable Border routing counters") 52 …PENTHREAD_BORDER_ROUTING_DHCP6_PD OT_BORDER_ROUTING_DHCP6_PD "DHCPv6-PD support in border routing") 57 kconfig_to_ot_option(CONFIG_OPENTHREAD_COAP_BLOCK OT_COAP_BLOCK "Enable CoAP Block-wise option supp… [all …]
|
/Zephyr-latest/samples/net/openthread/coap/ |
D | README.rst | 1 .. zephyr:code-sample:: ot-coap 3 :relevant-api: openthread 5 Build a Full Thread Device (FTD) CoAP server and client. 13 By running a client and server on two boards, a local Thread network can be created. 40 .. zephyr-app-commands:: 41 :zephyr-app: samples/net/openthread/coap 43 :west-args: -T sample.net.openthread.ftd.coap.server 49 .. zephyr-app-commands:: 50 :zephyr-app: samples/net/openthread/coap 52 :west-args: -T sample.net.openthread.ftd.coap.client [all …]
|
/Zephyr-latest/samples/net/sockets/echo_client/ |
D | README.rst | 1 .. zephyr:code-sample:: sockets-echo-client 3 :relevant-api: bsd_sockets tls_credentials 10 The echo-client sample application for Zephyr implements a UDP/TCP client 20 - :ref:`networking_with_host` 26 usage scenario is to run echo-client application inside QEMU. This is 30 echo-client directory: 32 - :file:`prj.conf` 35 - :file:`overlay-ot.conf` 38 - :file:`overlay-802154.conf` 44 - :file:`overlay-qemu_802154.conf` [all …]
|
/Zephyr-latest/doc/releases/ |
D | release-notes-1.12.rst | 12 - Asymmetric multiprocessing (AMP) via integration of OpenAMP 13 - Persistent storage support for Bluetooth Low Energy including Mesh 14 - 802.1Q - Virtual Local Area Network (VLAN) traffic on an Ethernet network 15 - Support multiple concurrent filesystem devices, partitions, and FS types 16 - Ethernet network management interface 17 - Networking traffic prioritization on a per-connection basis 18 - Support for Ethernet statistical counters 19 - Support for TAP net device on the native POSIX port 20 - Command-line Zephyr meta-tool "west" 21 - SPI slave support [all …]
|
D | release-notes-2.7.rst | 17 * Support for M-Profile Vector Extensions (MVE) on ARMv8.1-M 18 * Improved thread safety for Newlib and C++ on SMP-capable systems 20 * New Action-based Power Management API 23 * Linker Support for Tightly-Coupled Memory in RISC-V 25 * Support for extended PCI / PCIe capabilities, improved MIS-X support 27 * Added Zephyr Thread Awareness for OpenOCD to West 33 * The kernel now supports both 32- and 64-bit architectures 36 * We added support for Point-to-Point Protocol (PPP) 37 * We added support for UpdateHub, an end-to-end solution for over-the-air device updates 38 * We added support for ARM Cortex-R Architecture [all …]
|
D | release-notes-2.6.rst | 13 * Added support for 64-bit ARCv3 14 * Split ARM32 and ARM64, ARM64 is now a top-level architecture 15 * Added initial support for Arm v8.1-m and Cortex-M55 22 https://github.com/zephyrproject-rtos/example-application 34 * CVE-2021-3581: Under embargo until 2021-09-04 41 <https://github.com/zephyrproject-rtos/zephyr/issues?q=is%3Aissue+is%3Aopen+label%3Abug>`_. 46 * Driver APIs now return ``-ENOSYS`` if optional functions are not implemented. 47 If the feature is not supported by the hardware ``-ENOTSUP`` will be returned. 48 Formerly ``-ENOTSUP`` was returned for both failure modes, meaning this change 194 * Added support for null pointer dereferencing detection in Cortex-M. [all …]
|
/Zephyr-latest/boards/nxp/usb_kw24d512/doc/ |
D | index.rst | 6 The USB-KW24D512 is an evaluation board in a convenient USB dongle 7 form factor based on the NXP MKW24D512 System-in-Package (SiP) device 9 MKW24D512 wireless MCU provides a low-power, compact device with 11 network node, border router or as a development board. 16 - Kinetis KW2xD-2.4 GHz 802.15.4 Wireless Radio Microcontroller 17 (50 MHz, 512 KB flash memory, 64 KB RAM, low-power, crystal-less USB) 18 - USB Type A Connector 19 - Two blue LEDs 20 - One user push button 21 - One reset button [all …]
|