Has anyone already tried to make an ESP8266 serial programmer using an ESP8266? Something like ESP8266_1 connects to ESP8266_2 using serial, ESP8266_1 pulls up and down the GPIO_0, GPIO_2 and RST lines of ESP8266 and starts sending the new firmware. Most of this is not rocket science, but I am too l...

As said I don't really have a purpose for very fast tcp or udp connections. Even if I'd want to, I have very little iram left, because the Espressif libs take up most of it. I've only about 4k left, from which I use 2k for interrupt handlers and timing critical code. I2C benefits greatly from code i...

I think the LWIP interface is difficult to use anyway, anyhow, especially if all you need is a very few TCP and UDP sockets. But that may be caused by bad documentation just as well. In the LWIP documentation I never found a "proper" way where to "start". FWIW my firwmare impleme...

BTW I couldn't find the espconn sources in the NON-OS tree. Also I doubt whether the LWIP sources there are a drop-in replacement for the precompiled library.

Hi Pradik, It's a pity that you don't have access to non-public sources / documentation, because that is exactly what's missing at the moment. I am quite sure there are quite a few registers that nobody outside Espressif know they exist (and that are not related to the wireless phy). For example the...

Hi Pratik, I had a glance at the esp32 documentation lately and I was positively surprised. Much better documentation and much closer to professional documentation we're used to from other manufacturers. I guess that saves me from doing a "lecture" about wat we (I) am expecting. Problem wi...

I respect and understand the policy regarding the WiFi-related registers. The problem is all the other registers that are inadequately documented (or not at all). I have e.g. serial communication using the UART working, after a lot of trial and error. What we need is a proper description of ALL (non...

I'd gladly donate the existing code, but I am not going to actuallty integrate it into the SDK in any way, as long as large parts (not only the parts required for WiFi) of the SDK are closed source. Also there is still no proper direct hardware datasheet (list of every non-WiFi register with proper ...

Actually, the problem is like this and when using I2c one will meet it quote a bit. - esp8266 does NOT have hardware support for I2c (even though it's suggested) - the "driver" code (software emulation) that comes with the SDK is awfully bad. It's slow, is not adhering to the standard and ...

Actually I don't think the ESP8266 will get any further attention. I can only hope the SDK for the ESP32 is better, but I do fear...