-
Notifications
You must be signed in to change notification settings - Fork 13.3k
All Wemos D1 mini code stopped working after esp8266 Boards upgrade from 2.5.2 to 3.0.2 #8475
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Another version of the same weather station code that was working, now does this:
THIS IS THE CODE throwing the above errors. This was working archival code:
|
Thanks for the report. |
I used github's code sample. Ran it. It blew up.
I have been testing all my Wemos code from simple to 500 line programs I used to write code for GE/Honeywell mainframes in the late 1970s, and |
You must install it as instructed in the documentation. No one except you can decode the stack trace.
Did you try the erase "All flash" arduino IDE option ? |
Try this tool |
EXCEPTION DECODER: --------------- CUT HERE FOR EXCEPTION DECODER --------------- Soft WDT reset
ctx: cont --------------- CUT HERE FOR EXCEPTION DECODER --------------- |
|
@TSBrownie My drive Try it! |
This is a video of Setting the Real Time Clock (code from above) showing it worked when it was compiled using Board 2.5.2. |
Note that the code from #8475 (comment) cannot be built using 3.0.2 with warnings enabled
I suppose that is b/c you are using 'no-warnings' option? |
Do you mean Tools -->Debug Level: None??? or Exceptions: Disabled??? |
Debug Level one |
Uninstalled IDE 1.8.16, installed 1.8.19, and esp8266 by ESP8266 Community. Tried versions below on the weather program above (closed IDE between each upgrade + "Erase all flash content" + hardware reset of Wemos). Then I tried a simple program that reads the Wemos D1 mini SD card/RTC shield's clock (per above). 3.0.0 --> Compiles, Runs correctly. |
I did one better and integrated those into the only routine that called them. (The program is 4 programs I cobbled together, so I'm now removing redundancy and such.) The results are the same. `//SD CARD FUNCTIONS ================================= void print2File(String B){ //Write connect data to SD file void print3File(String B) { //Print data to SD file char openFile4(byte RW, String FN) { //Open SD FName3 file. char RW. Only 1 at a time. void print4File(String B) { //Print data to SD file void initTempFile(){ //Initialize SD card connect file |
My mistake, I was referring to the Arduino IDE preferences 'Compiler warnings' The code cannot omit return statement if the function was declared as something other than int something() {
}
void setup() {
something();
}
void loop() {
}
|
Fixes esp8266#8475 We disable all errors for `None` mode, so manually re-enable the return-type check as an error (because the code behavior is undefined and will crash the core).
Fixes esp8266#8475 We disable all errors for `None` mode, so manually re-enable the return-type check as an error (because the code behavior is undefined and will crash the core).
Assuming this was eventually solved |
No, it was not resolved. I went back to pre-3.xx board manager. 3.xx still does not work. |
No, not resolved. 3.xx board manger does not work. Still waiting, still using version 2.7.3
…________________________________
From: Max Prokhorov ***@***.***>
Sent: Tuesday, February 22, 2022 3:43 AM
To: esp8266/Arduino ***@***.***>
Cc: TSBrownie ***@***.***>; Mention ***@***.***>
Subject: Re: [esp8266/Arduino] All Wemos D1 mini code stopped working after esp8266 Boards upgrade from 2.5.2 to 3.0.2 (Issue #8475)
Assuming this was eventually solved
#8492<#8492> adds documentation entry in the crash FAQ about compiler warnings and their possible impact on the resulting program
—
Reply to this email directly, view it on GitHub<#8475 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ATLZ7BAP56LS3GK5P4DLA6TU4NSGFANCNFSM5NLMEHPA>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
per esp8266#8421 and esp8266#8475 after checking HW, suggest to check SW as well by at least by enabling some or all compiler warnings (and also note of the IDE weirdest defaults causing issues we expected to stay solved)
Basic Info
Platform
Settings in IDE
Problem Description
Working code (plus 10 past versions) stopped working immediately after updating from Boards esp8266 by ESP8266 Community version 2.5.2 to 3.0.2.
Code still complies w/o error. (Takes take 3x longer.)
I have tried all the Wemos LOLIN boards on the 3.0.2, include generic esp8266. Similar chksum errors from all.
Output before:
========= 20220201,Tue,07:54:28
Device Altitude(abs): 6.00 meters AMSL
Temperature: 28.47C; 83.25F Falling
Barometric Pressure(abs): Rising-Fair Weather
955.597 hPa(mbar); 95559.720 Pa
950.916 hPa, Short Term Past Average
716.757 mmHg
0.943101 Atm
Barometric Pressure-Comp'ed To Sealevel
956.247 hPa(mbar); 95624.692 Pa
717.244 mmHg
0.943742 Atm
Output after:
ets Jan 8 2013,rst cause:4, boot mode:(3,6)
wdt reset
load 0x4010f000, len 3460, room 16
tail 4
chksum 0xcc
load 0x3fff20b8, len 40, room 4
tail 4
chksum 0xc9
csum 0xc9
v00055920
~ld
MCVE Sketch
One sample of previously working code here (compile info below):
https://github.com/TSBrownie/Arduino-Wemos-D1-Weather-Basic/tree/main/2022WeatherBMP280-04x
Debug Messages
NOTE: Simple code such as the following still compiles / works, but only after initially reporting checksums:
OUTPUT:
ets Jan 8 2013,rst cause:2, boot mode:(3,6)
load 0x4010f000, len 3460, room 16
tail 4
chksum 0xcc
load 0x3fff20b8, len 40, room 4
tail 4
chksum 0xc9
csum 0xc9
v00042ec0
~ld
2022/02/02 Wed 15:36:42
2022/02/02 Wed 15:36:43
2022/02/02 Wed 15:36:44
2022/02/02 Wed 15:36:45
If the above date and times are correct, the RTC is updated.
The text was updated successfully, but these errors were encountered: