[riot-notifications] [RIOT-OS/RIOT] cpu/esp*: esp_now and esp_wifi cleanup (#10929)

MrKevinWeiss notifications at github.com
Mon Jul 1 09:54:41 CEST 2019


MrKevinWeiss requested changes on this pull request.

So when testing with the test procedure I am only able to get the esp_now interface pinging the node with ripple if there is no wifi (so I enter the wrong ssid and the rpl for the esp_now node is working).  If the right ssid is entered I connect and can ping from my cpu through the router to the esp border router but the esp now node no longer can get the rpl address.

I don't know if that is a bug with this PR or not...  However there should be a note that rpl isn't functioning on esp_now interface when wifi is connected.


1. Flash the node with ` USEMODULE='esp_now gnrc_rpl' CFLAGS='-DESP_NOW_CHANNEL=6' BOARD=esp8266-esp-12x PORT=/dev/ttyUSB1 make term -C examples/gnrc_networking`

2. Flash the border router with `USEMODULE=gnrc_rpl CFLAGS='-DESP_NOW_CHANNEL=6 -DESP_WIFI_SSID=\"<correct_ssid>" -DESP_WIFI_PASS=\"<correct_password>"'  make flash term`

3. From my cpu `ping6 <border_router_if_8_global_addr>`, all good

4. Use `rpl` on the node, nothing is there

5. Flash the border router with `USEMODULE=gnrc_rpl CFLAGS='-DESP_NOW_CHANNEL=6 -DESP_WIFI_SSID=\"<incorrect_ssid>" -DESP_WIFI_PASS=\"<correct_password>"'  make flash term`

6. Now `rpl` on the esp node with esp_now interface works and can ping the esp border router interface 7 global address



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/10929#pullrequestreview-256180926
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190701/e3a9ab13/attachment.html>


More information about the notifications mailing list