Tetis Clock RESET ets Jan 8 2013,rst cause:2, boot mode:(3,7)

[BCChad]

Something has changed in one of the libraries - I recompiled the clock after daylight savings here in March 2019, and of course it used the latest libraries. Something is causing a hardware overflow and reset. Result - the clock will not finish booting up and run normally.
This is happening both with my version of the clock and with Toblum's original version (the reset errors are slightly different).

[BCChad]

More information - the error seems triggered when calling NTP.getTimeStr() as I can comment out this call and the crash does not occur. I have used Toblum's TetrisAnimation library examples to experiment further with this bug. My display hardware is working perfectly with the examples; the crash appears even with his examples, where an NTP call is made.

[toblum]

Sorry that I couldn't contribute such much this time as I don't have hardware (and the required time) to try out everything at the moment. I ordered a fresh matrix, as the last one was broken. Maybe the scripts have to be adapted to the latest library versions.

Let me know if you find something out, so I could update the code accordingly.

[BCChad]

I will certainly let you know, as the challenge is tormenting me(!). :) I saw you have a newer commit than I had been using, but I downloaded your newest and it also crashes, and without any of my additions. I also wonder if there is some hidden firmware on my ESP8266 causing the trouble but I bought a new NodeMCU ESP8266 and it still crashes. Best guess currently is the NTP library. Thanks for responding!

…

On Fri, Mar 15, 2019, 1:20 PM Tobias Blum ***@***.***> wrote: Sorry that I couldn't contribute such much this time as I don't have hardware (and the required time) to try out everything at the moment. I ordered a fresh matrix, as the last one was broken. Maybe the scripts have to be adapted to the latest library versions. Let me know if you find something out, so I could update the code accordingly. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#6 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AltOuAax1TjoMxkKFrpPBEdd-yHfmUtgks5vW9ZHgaJpZM4bwJcI> .

[toblum]

I'm not sure on what ESP core version I was when implementing this. There could be changes as well. Maybe you could try to go back with that version as well? Just as an idea.

[BCChad]

Yes I tried going back several versions, they're up to 2.5.0beta3 right now, which is worrisome. Why 3 betas?

…

On Fri, Mar 15, 2019, 1:39 PM Tobias Blum ***@***.***> wrote: I'm not sure on what ESP core version I was when implementing this. There could be changes as well. Maybe you could try to go back with that version as well? Just as an idea. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#6 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AltOuJcMd_Wfg6CJ8v9fqJNTV8nNyHe7ks5vW9rkgaJpZM4bwJcI> .

[toblum]

I think last march it must have been 2.4.0 or 2.4.1 that was the latest version.

[BCChad]

One of the things that changed from 2.4.1 to 2.5.0 beta is there are more "SPIFFS" options. 2.4.1 offers only 1 or 3M SPIFFS. 2.5.0 offers more, including 0M SPIFFS. Mine had defaulted to 0 (unless I changed it to 0 unwittingly). I did try changing the settings with the 2.5.0 option but it did not seem to prevent the crash. I do not understand what SPIFFS (SPI FLASH FILE SYSTEM) does - perhaps you can enlighten me better?? I'm about to try experimenting with the 2.4.1 core.

…

On Fri, Mar 15, 2019 at 2:01 PM Tobias Blum ***@***.***> wrote: I think last march it must have been 2.4.0 or 2.4.1 that was the latest version. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#6 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AltOuMah_k25ucEFSdA8rEWimYZf6ODIks5vW9_4gaJpZM4bwJcI> .

-- Bruce Chadbourne 306 Fern Circle Lebanon PA 17042

[BCChad]

No success - it still crashes in exactly the same way with version 2.4.0 of the board, using your original version of the sketch. You mention needing a new display - but you can actually see the problem with the serial monitor - it happens within seconds of starting the main loop(). On Sat, Mar 16, 2019 at 11:58 AM Bruce Chadbourne < bruce.chadbourne@gmail.com> wrote:

…

One of the things that changed from 2.4.1 to 2.5.0 beta is there are more "SPIFFS" options. 2.4.1 offers only 1 or 3M SPIFFS. 2.5.0 offers more, including 0M SPIFFS. Mine had defaulted to 0 (unless I changed it to 0 unwittingly). I did try changing the settings with the 2.5.0 option but it did not seem to prevent the crash. I do not understand what SPIFFS (SPI FLASH FILE SYSTEM) does - perhaps you can enlighten me better?? I'm about to try experimenting with the 2.4.1 core. On Fri, Mar 15, 2019 at 2:01 PM Tobias Blum ***@***.***> wrote: > I think last march it must have been 2.4.0 or 2.4.1 that was the latest > version. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#6 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AltOuMah_k25ucEFSdA8rEWimYZf6ODIks5vW9_4gaJpZM4bwJcI> > . > -- Bruce Chadbourne 306 Fern Circle Lebanon PA 17042

-- Bruce Chadbourne 306 Fern Circle Lebanon PA 17042

[toblum]

Hi @BCChad,

good point, I tried out different version combinations:
I could see restarts when using the latest versions for all libs. I then turned all libs and the ESP core back to the version from last april when it definitely worked. This version compiled an started without problems. I then updated the libraries one after the other to the latest and found it not working when upgrading to the latest Adafruit GFX lib. If I pin that lib to the 1.3.6 version and use the latest versions for all other libraries it seems to work also. Only judging from the serial output as I don't have a working matrix at hand.
So I updated the platform.io config accordingly. Please try out that combination if it works for you.

Best regards
Tobias

[BCChad]

Great news, I'll check it out, and will send you confirmation that hopefully the clock "looks" right.

…

On Sat, Mar 16, 2019 at 4:57 PM Tobias Blum ***@***.***> wrote: Hi @BCChad <https://github.com/BCChad>, good point, I tried out different version combinations: I could see restarts when using the latest versions for all libs. I then turned all libs and the ESP core back to the version from last april when it definitely worked. This version compiled an started without problems. I then updated the libraries one after the other to the latest and found it not working when upgrading to the latest Adafruit GFX lib. If I pin that lib to the 1.3.6 version and use the latest versions for all other libraries it seems to work also. Only judging from the serial output as I don't have a working matrix at hand. So I updated the platform.io config accordingly. Please try out that combination if it works for you. Best regards Tobias — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#6 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AltOuIBgMXCcCpS-ZIDlLhUrVJYAhRYIks5vXVq1gaJpZM4bwJcI> .

-- Bruce Chadbourne 306 Fern Circle Lebanon PA 17042

[BCChad]

So yes, I set Adafruit GFX to 1.3.6 and the clock is working perfectly. Thanks. My wife is happy, she has been missing her clock! So two questions: 1. With the newest board manager - the flash size defaults to 4M No SPIFFS, obviously working. It used to say 1M SPIFFS - does that mean more memory is freed up, not being allocated to a file system (that you are not using?)? 2. So any guesses on what happened to Adafruit GFX after version 1.3.6? On Sat, Mar 16, 2019 at 5:05 PM Bruce Chadbourne <bruce.chadbourne@gmail.com> wrote:

…

Great news, I'll check it out, and will send you confirmation that hopefully the clock "looks" right. On Sat, Mar 16, 2019 at 4:57 PM Tobias Blum ***@***.***> wrote: > Hi @BCChad <https://github.com/BCChad>, > > good point, I tried out different version combinations: > I could see restarts when using the latest versions for all libs. I then > turned all libs and the ESP core back to the version from last april when > it definitely worked. This version compiled an started without problems. I > then updated the libraries one after the other to the latest and found it > not working when upgrading to the latest Adafruit GFX lib. If I pin that > lib to the 1.3.6 version and use the latest versions for all other > libraries it seems to work also. Only judging from the serial output as I > don't have a working matrix at hand. > So I updated the platform.io config accordingly. Please try out that > combination if it works for you. > > Best regards > Tobias > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#6 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AltOuIBgMXCcCpS-ZIDlLhUrVJYAhRYIks5vXVq1gaJpZM4bwJcI> > . > -- Bruce Chadbourne 306 Fern Circle Lebanon PA 17042

-- Bruce Chadbourne 306 Fern Circle Lebanon PA 17042

[BCChad]

I'm not quite out of the woods - my updated version of your sketch still crashes, with AdaFruit GFX 1.3.6, but at least we know your baseline is stable. I had not channged my sketch, just recompiled with the latest libraries.
I wonder about the SPIFFS...