ESP8266 Community Forum

- Tue Feb 03, 2015 7:05 pm #8905 Looks like we will have a new player for the IP support library of the eps8266. Important here is the multicast udp support ... including working mdns and OLSR mesh stuff WOW!

tweet from one of thier developers.:
https://twitter.com/maximevince/status/528936982077276160

User Docs:
http://162.13.84.104/user_doc.pdf

Project Code:
https://github.com/tass-belgium/picotcp/

- Wed Feb 04, 2015 3:52 am #8927 good news.

ESP8266.com Moderator
Lets get the party started and +1

[url=https://www.banggood.com/custlink/KvGGhGF4wG[/url]

I like ESP8266 and ESP8285 and ESP32

- Tue Feb 10, 2015 12:34 pm #9406 Has someone looked at the sources? I find "include/arch/pico_esp8266.h" for porting, but i can't find a picotcp device driver for the esp8266. How does picotcp access the mac layer? Isn't the mac layer closed source without api?

- Tue Feb 10, 2015 2:19 pm #9411 I haven't seen picoTCP code yet but closed mac layer isn't really that big problem. You can communicate with lower layers the same way LwIP does (emulating usage of typical LwIP data structures like netif and pbuf) - if you have any data to send, you call ieee80211_output_pbuf() function, if there is any data to be read, the XTOS task with prio 28 (for STA interface) or 29 (for AP interface) will be posted with the pointer to pbuf structure in event->par in argument.

If you're interested in how LwIP is set up, take a look at https://github.com/kadamski/esp-lwip/bl ... _lwip_if.c

EDIT: I've made a quick look at both documentation and source now. There is no driver initialization code on github but it looks like it should be easy to implement using the information I provided above. The only problem is that you need to create/manage LwIP netif structure with the same ABI as internal SDK functions expect.