> Don't know if it is worth your time, I've been on this some months ago and
> desisted.
> I would go for ESP32, looks cleaner and uses a newer lwIP release.
Beginning to think you are right, better to go with the newer part, even though
I may not need the BLE portion of the module.
Thanks eve
This is getting off-topic for the list, if you need further info please
feel free to write a personal message.
The company I work for resells Espressif chips/modules, they are focused
on ESP32 right now, I don't think they will work on the 8266, but you
never can tell.
I found what I think i
I agree ESP8266 LwIP stack is heavily modified and source provided with
FreeRTOS sdk it never compiles. I even post on forum but no response from dev
team. Most of the errors were of implicit function declaration, stack is
calling functions in library with no header file defining its prototype.
OK...
you are using some vendor port for some device.
You have to check on your vendor's forums for the intricacies of
debugging your particular device. I could help with some ARMs and there
surely are some other guys knowing other processors here, but this is
not the right place for that.
Fi
TCP/IP stack in ESP8266 is a heavily modified development branch between
1.4.0 and 1.4.1 stable versions.
The non-OS usage of this little beast requires releasing cpu quite
frequently for wifi duties, so they require using os_ versions of the
standard C library functions. Don't know how friendly
Hallo Simon,
The corruptions seems to come from the shutdown function. I tracked this
down with the MEMP_SANITY_CHECK.
I only got problems with the LWIP Stack when using the webserver. I've got
other Applications which use TCPIP heavily didn't cause any problem (like
JPEG/MJPEG streamer where I f
