ESP8266 bootloop

[helmarw]

since you were "blaming" the ESP32 for everything ;) I can't get any ESP8266 to work. the libraries im using you can see in the description of my Fork mostly the latest except JSON 5.x of course and pxMatrix, anything else than 1.3.0 doesn't work for me. Back to the ESP8266, I tried Wemos D1 mini and NodeMCU, both the same results. First no display of course, for whatever reason but at least I could access the accesspoint to set the Wifi credentials. after applying the settings all esp8266 (3x Wemos and 1xNodeMCU) are locked in a boot loop. On the serial monitor I can see the wifi ip-address and then it crashes and reboots, 100% reproducible. I tried lots of different setting, CPU, Flash etc frequency, erasing flash all over a.s.o. Any ideas ???

[dragondaud]

I haven't had time to investigate differences with newer versions of board or libraries since I started a new job. If you upload the provided .bin file to an 8266 I guarantee it will work fine, no compiling needed. If you use the indicated library versions things also just work, on the 8266. Beyond that, its open source and as things change it might need some updates. I added the ESP32 support as somebody's request, and never received much feedback, nor did I extensively test it. Since I know its works on the 8266, I naturally thought some of your issues might be related to the ESP32. Might also be different lib or board versions. Things change. If you are getting bad results from WiFiManager you are likely using the wrong version. There is a script for updating libs and for command line building/flashing that sets all the options correctly.

On Thu, Oct 31, 2019 at 8:02 AM helmarw notifications@github.com wrote:

since you were "blaming" the ESP32 for everything ;) I can't get any ESP8266 to work. the libraries im using you can see in the description of my Fork mostly the latest except JSON 5.x of course and pxMatrix, anything else than 1.3.0 doesn't work for me. Back to the ESP8266, I tried Wemos D1 mini and NodeMCU, both the same results. First no display of course, for whatever reason but at least I could access the accesspoint to set the Wifi credentials. after applying the settings all esp8266 (3x Wemos and 1xNodeMCU) are locked in a boot loop. On the serial monitor I can see the wifi ip-address and then it crashes and reboots, 100% reproducible. I tried lots of different setting, CPU, Flash etc frequency, erasing flash all over a.s.o. Any ideas ???

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/dragondaud/myClock/issues/18?email_source=notifications&email_token=AGM5GPQHLW2232EJ7EES3QLQRLQPLA5CNFSM4JHKSTU2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HVZIO3A, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGM5GPXZRHC5KO24EW3DJK3QRLQPLANCNFSM4JHKSTUQ .

-- david denney dragondaud AT gmail DOT com 719-821-8900

[helmarw]

well im just saying that your code doesn't work with the most recent libs for esp8266, i tried everything out of the box from scratch without tempering with your code first, always the same. im fine with the ESP32 they are anyway faster and more stable in my experience. I also have the WifiManager under suspicion, strange versioning, and two braches. Lots of things are happening there any man bugs getting fixed, so it might be important to keep this up do date. in your script this i found: [ ! -d "WiFiManager" ] && ( git clone https://github.com/tzapu/WiFiManager.git && cd WiFiManager && git checkout development -q ) so my guess it you use the 1.0.0 ok but now there is a 1.0.1 since two days or so. i think for ESP32 the development branch in mandatory anyway, which version are you using exactly?

Never know when something gets updated and the old code doesn't work anymore, pretty annoying. Same happened to the PxMatix, anything beyond 1.3.0 doesn't seem to work, and for your code 1.3.0 is more than enough, so i simply linked my own mod of the pxMatrix.h (renamed it of course), this way im sure it always works, and if i want to i can try latest pxMatrix for other projects without breaking the older code ... its one way to keep things closed with out having to relay on external library which might or might not change or break... anyway i think i stick with the ESP32, maybe i can use the 8266 for less problematic projects, they always come in handy