forked from zephyrproject-rtos/zephyr
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request zephyrproject-rtos#5 from ccli8/nvt_m467_esp8266
drivers: wifi: esp8266: numaker: Support numaker_pfm_m467 board
- Loading branch information
Showing
3 changed files
with
52 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
# SPDX-License-Identifier: Apache-2.0 | ||
|
||
# Without enable, ESP8266 shield will continuously push data to board (+IPD) anyway | ||
# on receive and board's Rx buffer can get OOM easily. However, current driver | ||
# implementation on Passive Receive mode has the following concerns: | ||
# 1. On <conn_id>,CLOSED, driver closes the socket prematurely and buffered Rx data on | ||
# ESP8266 shield gets unable to fetch (AT+RECVDATA). | ||
# NOTE: To re-produce the issue, go samples/net/sockets/http_get in which the server | ||
# end will close the connection immediately after replying the http response. | ||
# 2. On +IPD, driver doesn't consider available Rx buffer and straight schedules to fetch | ||
# buffered Rx data on ESP8266 shield, still causing Rx buffer OOM. One approach may | ||
# pre-allocate Rx buffer before the schedule. | ||
# NOTE: To re-produce the issue, go samples/net/sockets/big_http_download/src, adding | ||
# delay e.g. k_msleep(8000) in the download() while loop. | ||
# NOTE: With or without this feature enabled, esp_socket_prepare_pkt() enabling timed | ||
# wait (CONFIG_WIFI_ESP_AT_RX_NET_PKT_ALLOC_TIMEOUT) can relieve the problem to | ||
# some degree. | ||
# | ||
# See: https://github.com/zephyrproject-rtos/zephyr/issues/52702 | ||
#CONFIG_WIFI_ESP_AT_PASSIVE_MODE=y |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
/* SPDX-License-Identifier: Apache-2.0 */ | ||
|
||
&pinctrl { | ||
uart2_esp8266: uart2_esp8266 { | ||
pinmux = <PC1MFP_UART2_TXD 0x0000>, /* UART2 TX */ | ||
<PC0MFP_UART2_RXD 0x0000>, /* UART2 RX */ | ||
<PC3MFP_UART2_nRTS 0x0000>, /* UART2 RTS */ | ||
<PC2MFP_UART2_nCTS 0x0000>; /* UART2 CTS */ | ||
}; | ||
}; | ||
|
||
&uart2 { | ||
status = "okay"; | ||
current-speed = <115200>; | ||
hw-flow-control; | ||
|
||
pinctrl-0 = <&uart2_esp8266>; | ||
pinctrl-names = "default"; | ||
|
||
esp8266: esp8266 { | ||
compatible = "espressif,esp-at"; | ||
label = "esp8266"; | ||
status = "okay"; | ||
target-speed = <115200>; | ||
reset-gpios = <&gpioc 4 GPIO_ACTIVE_LOW>; | ||
}; | ||
}; | ||
|
||
&gpioc { | ||
status = "okay"; | ||
}; |