Chapter 4. API Guides
Some TCP-based applications need only one TCP connection. However, they may choose to close this TCP con-
nection and create a new one when an error (such as a sending failure) occurs. This may result in multiple TCP
connections existing in the system simultaneously, because it may take a long time for a TCP connection to close,
according to the TCP state machine (refer to RFC793).
4.21 OpenThread
OpenThread is a IP stack running on the 802.15.4 MAC layer which features mesh network and low power consump-
tion.
4.21.1 Mode of the OpenThread stack
OpenThread can run under the following modes on Espressif chips:
Standalone node
The full OpenThread stack and the application layer runs on the same chip. This mode is available on chips with 15.4
radio such as ESP32-H2.
Radio Co-Processor (RCP)
The chip will be connected to another host running the OpenThread IP stack. It will send and received 15.4 packets
on behalf of the host. This mode is available on chips with 15.4 radio such as ESP32-H2. The underlying transport
between the chip and the host can be SPI or UART. For sake of latency, we recommend to use SPI as the underlying
transport.
OpenThread host
For chips without 15.4 radio, it can be connected to an RCP and run OpenThread under host mode. This mode
enables OpenThread on Wi-Fi chips such as ESP32, ESP32-S2, ESP32-S3 and ESP32-C3. The following diagram
shows how devices work under different modes:
Fig. 38: OpenThread device modes
Espressif Systems 1432
Submit Document Feedback
Release v4.4
To Next Page
Loading...
Need help?
General