[riot-notifications] [RIOT-OS/RIOT] cpu/esp*: esp_now and esp_wifi cleanup (#10929)
notifications at github.com
Wed Jul 31 17:32:07 CEST 2019
I tested with the freshly rebased version and the following setup: `PC<->WiFiAP<->ESPbr<->ESPnow`
Both ESPs used `gnrc_networking`, programed as follows:
USEMODULE='esp_now esp_wifi' \
CFLAGS='-DGNRC_IPV6_NIB_CONF_SLAAC=1 -DGNRC_NETIF_IPV6_ADDRS_NUMOF=4 -DESP_NOW_CHANNEL=11 -DESP_WIFI_SSID=\"somessid\" -DESP_WIFI_PASS=\"somepw\"' \
make BOARD=esp32-wroom-32 PORT=/dev/ttyUSB0 all flash term
USEMODULE='esp_now' CFLAGS='-DESP_NOW_CHANNEL=11' make all flash term BOARD=esp32-wroom-32 PORT=/dev/ttyUSB1
`GNRC_NETIF_IPV6_ADDRS_NUMOF=4 ` was added because the ESPbr already needs to store two addresses it gets from the WiFiAP plus its own LLA.
Without `GNRC_IPV6_NIB_CONF_SLAAC=1` all the addresses on ESPbr's esp_wifi interface were marked as tentative so pinging other hosts from ESPbr didn't work.
Setup of the nodes:
ifconfig 9 add 2001:db8::1
rpl init 9
rpl root 1 2001:db8::1
*connect to same WiFiAP as ESPbr*
ip -6 route add 2001:db8::/64 via <global_IPv6_addr_of_ESPbr> dev <wireless_interface>
Using that setup everything worked: I could ping every host from every other host in the setup.
I found one (unrelated?) problem where I left the ESPbr in this setup running without using it and after around 40 minutes it printed the following message before the shell stopped responding to input:
` W (1422385) [ wifi]: no timer handle`. Though, I didn't manage to reproduce it yet.
Nonetheless I can confirm that this PR indeed enabled using esp_now and esp_wifi on the same node, so I will add the tested label.
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the notifications