-
-
Notifications
You must be signed in to change notification settings - Fork 115
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
Web update from 3.6.5 to 3.7.0 on E32 V2 defaults to S32 board profile #2151
Comments
damn, I thought we tested this all. I'll take a look. Maybe its a simple fix by including different named files in the 3.7.0 GH assets |
as a quick fix I made the EMS-ESP-3_7_0-ESP32.bin the same as the 16MB+ (with PSRAM) so that will help E32 users automatically upgrade. But it will crash any older S32 4MB users. Need to look into what is causing that. (the change was part of #1941 ) |
I can't find an easy way to fix this. I'll remove the binaries and people will need to manually upgrade using the table on the BBQKees wiki. |
Maybe for future updates have EMS-ESP check a special page like updates.emsesp.org. There you could run a check or a table and load the correct bin file for each device. So a relay-page. |
The problem is that the partition tables have changed, so the old EMS-ESP application settings (which includes the board profile) are reset when going from 16MB variants to 4MB. The firmware download link in 3.6.5 is not as smart as 3.7.0 and doesn't take into account psram, chip types etc. We have E32 (4MB), E32V2 (16M), S32 (4MB) all on the same chip-type but with different partition tables, There is no "one size" that fits all for 3.6.5 users. The easiest way is what I've done now and remove the binaries, which will error and then users will need to manually download and install following the instructions on the ems-esp and bbqkees wiki. |
redirect users to download.emsesp.org (when it's up) for the time being |
I got several emails already from users with an E32 V2 who updated from 3.6.5 to 3.7.0 release.
After upload and the reboot, the Ethernet port does not work anymore, so they think they bricked the device.
I checked it and can reproduce it: when you try to update from 3.6.5 to 3.7.0 via the web interface, it points to the ESP32.bin instead of the ESP32-16MB+.bin. At reboot the board profile is incorrectly set to S32.
This will disabled Ethernet and also f.i. the reset button does not work anymore.
The text was updated successfully, but these errors were encountered: