ESP8266 Community Forum

- Tue Jan 16, 2018 1:29 pm #73184 So for example a typical sketch has 6 libraries:

Code: Select all#include "FastLED.h"
#include <ESP8266WiFi.h>
#include <ESP8266mDNS.h>
#include <WiFiUdp.h>
#include <ArduinoOTA.h>
#include <NeoPixelBus.h>

and compiles to 280kB, and memory use is 36kB.

Uploading OTA at 921600 baud takes about 5 seconds. Uploading via FTDI at 115200 baud takes 45 seconds. During compiling, with no other programs running or sketches open, the CPU is around 50%, and ram is 2GB/8. The long compile only happens when there is any change to the sketch.

- Tue Jan 16, 2018 3:51 pm #73186 I do the compiling on an old hp notebook with CoreDuo T2300, 2GB and 40GB hd (so "stone age" compared to your system).

A fresh compile of an empty sketch takes over one minute the next compile 10s.
A fresh compile for a larger setch (WiFi, TouchGraphics, EEPROM, timefunctions etc) takes 1'30" and 27" for any following compile.

So what? That's what it takes ... it keeps you from solving problems by "trial and error", enforces thinking and analyzing instead.

- Tue Jan 16, 2018 4:00 pm #73187 I'm trying to design and set up holiday displays where you need to see the effect of changes, so it is tiresome for me. Guess I should use a program designed for that like xLights and use the RPi or something else.

- Tue Jan 16, 2018 5:30 pm #73191

I'm trying to design and set up holiday displays where you need to see the effect of changes, so it is tiresome for me.

Why not take the data out of your code. Put it is SPIFFS. Upload a new data file with an up-loader web page.