-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cpu/esp8266: enable lwIP for ESP8266 #12949
Merged
Merged
Conversation
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
gschorcht
added
Area: cpu
Area: CPU/MCU ports
Area: pkg
Area: External package ports
Platform: ESP
Platform: This PR/issue effects ESP-based platforms
State: waiting for other PR
State: The PR requires another PR to be merged first
Type: enhancement
The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation
labels
Dec 14, 2019
benpicco
reviewed
Dec 15, 2019
benpicco
removed
the
State: waiting for other PR
State: The PR requires another PR to be merged first
label
Dec 16, 2019
Please squash. |
Sure, go ahead. |
gschorcht
force-pushed
the
cpu/esp8266/enable_lwip
branch
from
December 16, 2019 15:21
d6aa5b8
to
921ab40
Compare
I had to rebase to push 921ab40. All other commits are unchanged. |
benpicco
approved these changes
Dec 16, 2019
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes are looking good - please squash.
gschorcht
force-pushed
the
cpu/esp8266/enable_lwip
branch
from
December 17, 2019 07:29
921ab40
to
ddc34b4
Compare
gschorcht
added
the
CI: ready for build
If set, CI server will compile all applications for all available boards for the labeled PR
label
Dec 17, 2019
@benpicco Squashed. |
Thanks for reviewing and merging. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Area: cpu
Area: CPU/MCU ports
Area: pkg
Area: External package ports
CI: ready for build
If set, CI server will compile all applications for all available boards for the labeled PR
Platform: ESP
Platform: This PR/issue effects ESP-based platforms
Type: enhancement
The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contribution description
This PR provides very small changes that make it possible to use
pkg/lwip
also with ESP8266.Background
The SDK interface of the WiFi module uses the
lwIP
'spbuf
structure for packets sent to and received from the WiFi interface. For compatibility reasons with the binary SDK libraries, moduleesp_wifi
has to include the SDKlwIP
pbuf
header and can't use that frompkg/lwip
.To avoid compilation errors, all settings in
pkg/lwIP
that are also defined by SDKlwIP
header files have to be undefined inesp_wifi
.Tests
The following tests were executed:
tests/lwip
esp_wifi
tests/lwip_sock_ip
esp_wifi
esp_wifi
intest_sock_ip_recv6__socket
withEAGAIN
esp_wifi
tests/lwip_sock_tcp
esp_wifi
test_tcp_connect6__EINVAL_netif
with 0 (meanssock_tcp_connect
success)test_tcp_connect6__EINVAL_netif
with 0 (meanssock_tcp_connect
success)tests/lwip_sock_udp
esp_wifi
test_sock_udp_recv6__socketed
but the node is reachable withping
esp_wifi
It seems that the tests 'fail' when they are executed with enabled
esp_wifi
because of the existence of the real network interface or because packets injected to the test device are interfered by incoming packets from the WiFi interface.Testing procedure
Flash
tests/lwip
with enabled moduleesp_wifi
on any ESP8266 boardand execute
ifconfig
on ESP8266 node and ping the node from any machine in the LAN.Issues/PRs references
Depends on PR #12948.
Depends on PR #12903 for IPv4.