Re: [riot-devel] ESP8266 - Easy tcp/ip support
Hello David, 2015-03-17 0:02 GMT+01:00 David Lyon david.l...@clixx.io: Hello Ludwig, Lately, I've been putting a lot of time into the ESP8266 wifi modules, and learning how to get them to work. How is the unified network driver system going? Here's my conclusion on the ESP8266. If Riot has a unified network driver system, it might be worth looking at trying to integrate these modules with riot. We currently don't have an example for an embedded stack, but I guess the ESP8266 would be great to supply such an example. Since the ESP8266 supplies, as far as I understand it, everything up to tcp and udp, I would propose not to write a netdev driver for it, but writing a netapi threads directly, one for TCP and one for UDP, so our future new socket API speaks directly to it. If you need some inspiration how to implement a transport layer thread have a look at Hauke's prelimanary UDP implementation [1]. The trick with the ESP8266 modules seems to be to use the LUA firmware. And use some simple serial bridging code from Riot to then talk to the modules. If there are no timing issues over speaking to the devices registers over e.g. SPI directly (if it is possible this way at all), we can try that, but in general I would prefer the solution that yields the better performance. Let me know if this is an interesting option? Since it would show the flexibility of our new network stack this chip would be a great option! :-) Regards, Martine [1] https://github.com/RIOT-OS/RIOT/pull/2430 ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] ESP8266 - Easy tcp/ip support
Hi Martine, On 2015-03-17 20:49, Martine Lenders wrote: We currently don't have an example for an embedded stack, but I guess the ESP8266 would be great to supply such an example. Since the ESP8266 supplies, as far as I understand it, everything up to tcp and udp, I would propose not to write a netdev driver for it, but writing a netapi threads directly, one for TCP and one for UDP, so our future new socket API speaks directly to it. If you need some inspiration how to implement a transport layer thread have a look at Hauke's prelimanary UDP implementation [1]. I will check that. If there are no timing issues over speaking to the devices registers over e.g. SPI directly (if it is possible this way at all), we can try that, but in general I would prefer the solution that yields the better performance. It's a UART/Serial interface so there's no SPI. There's memory limits on the LUA firmware so it's not suited to big amounts of data going through. The Lua interface currently operates at 9600. Since it would show the flexibility of our new network stack this chip would be a great option! :-) It would give TCP/UDP/MQTT pretty quickly. Regards David ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] ESP8266 - Easy tcp/ip support
Hello Ludwig, Lately, I've been putting a lot of time into the ESP8266 wifi modules, and learning how to get them to work. How is the unified network driver system going? Here's my conclusion on the ESP8266. If Riot has a unified network driver system, it might be worth looking at trying to integrate these modules with riot. The trick with the ESP8266 modules seems to be to use the LUA firmware. And use some simple serial bridging code from Riot to then talk to the modules. Let me know if this is an interesting option? Regards David ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
