Espeasy: cant update sonoff ch4 R2
Hi everyone! I use sonoff ch4 R2 with old firmware:
Build
20102 - Mega
Libraries
ESP82xx Core 2_4_1, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.0.3
GIT version
mega-20180606
Plugins
47 [Normal]
Build time
Jun 6 2018 02:13:33
Binary filename
ESP_Easy_mega-20180606_normal_ESP8285_1024.bin
Firmware
Build | 20102 - Mega
Libraries | ESP82xx Core 2_4_1, NONOS SDK 2.2.1(cfd48f3), LWIP: 2.0.3
GIT version | mega-20180606
Plugins | 47 [Normal]
Build Md5 | b44aa2c49badf0e2832b4dc7b98cbb
Md5 check | passed.
Build time | Jun 6 2018 02:13:33
Binary filename | ESP_Easy_mega-20180606_normal_ESP8285_1024.bin
ESP board
ESP Chip ID | 13267511 (0xCA7237)
ESP Chip Freq: | 80 MHz
Storage
Flash Chip ID | Vendor: 0x51 Device: 0x4014
Flash Chip Real Size: | 1024 kB
Flash IDE Size: | 1024 kB
Flash IDE speed: | 40 MHz
Flash IDE mode: | DOUT
Flash Writes | 18 daily / 18 boot
Sketch Size | 678 kB (196 kB free)
Now i download latest release - ESPEasy_ESP82xx_mega-20200608
Unzipped from one - ESP_Easy_mega_20200608_normal_ESP8285_1M.bin
Goto web-face to Tools/Firmware/Load and select the ESP_Easy_mega_20200608_normal_ESP8285_1M.bin and press the Update button. After ~5 secs i see Update error: ERROR[4]: Not Enough Space
What is this?
Logs
1149109: SYS : 19.00
1149112: EVENT: uptime#Uptime=19.00
1176669: WD : Uptime 20 ConnectFailures 0 FreeMem 15688
1195111: EVENT: Clock#Time=Sat,00:37
1206669: WD : Uptime 20 ConnectFailures 0 FreeMem 15688
1209109: SYS : 20.00
1209112: EVENT: uptime#Uptime=20.00
1236673: WD : Uptime 21 ConnectFailures 0 FreeMem 15760
1255377: EVENT: Clock#Time=Sat,00:38
1266673: WD : Uptime 21 ConnectFailures 0 FreeMem 15760
1269375: SYS : 21.00
1269378: EVENT: uptime#Uptime=21.00
1296673: WD : Uptime 22 ConnectFailures 0 FreeMem 15760
1315377: EVENT: Clock#Time=Sat,00:39
1326673: WD : Uptime 22 ConnectFailures 0 FreeMem 15640
1329377: SYS : 22.00
1329380: EVENT: uptime#Uptime=22.00
userosos
All 16 comments
Your flash size is only 1 MB, and that's too small to do a single-step update, so you'll need to go the 2-step route:
First upload a .bin file with 'minimal' and 'OTA', and in your case also '8285', in the name, that should leave enough free space to upload, in the second step hence the 2-step name, the .bin you mentioned above.
Edit: Correct answer is below.
tonhuisman
on 27 Jun 2020
Your flash size is only 1 MB, and that's too small to do a single-step update, so you'll need to go the 2-step route:
First upload a .bin file with 'minimal' and 'OTA', and in your case also '8285', in the name, that should leave enough free space to upload, in the second step hence the 2-step name, the .bin you mentioned above.
I used ESP_Easy_mega_20200608_minimal_core_242_ESP8285_1M_OTA.bin
And it not work too - Update error: ERROR[4]: Not Enough Space
userosos
on 27 Jun 2020
Ah, my mistake, I've never used the 2-step upload myself, sorry.
You need the ESPEasy_2step_UploaderMega_1024.bin to be flashed first, then, after the reboot, upload the .bin file you need. The OTA I referred to in the name is the Arduino OTA feature that is available in those builds, not related to the ESPEasy upload feature.
tonhuisman
on 27 Jun 2020
Ah, my mistake, I've never used the 2-step upload myself, sorry.
You need the ESPEasy_2step_UploaderMega_1024.bin to be flashed first, then, after the reboot, upload the .bin file you need. The OTA I referred to in the name is the Arduino OTA feature that is available in those builds, not related to the ESPEasy upload feature.
Hmmm. Sorry but it not work too. Update error: ERROR[4]: Not Enough Space
Where i can see more info about it maybe?
userosos
on 27 Jun 2020
Or i can do an old update. Without the problem? My's firmware is very old now (2018 years).
userosos
on 27 Jun 2020
You can of course upload a newer firmware by disconnecting the sonoff from power, and connect to your computer like you originally installed ESPEasy on it. General advice is to use the latest, as that's the greatest.
tonhuisman
on 27 Jun 2020
You can of course upload a newer firmware by disconnecting the sonoff from power, and connect to your computer like you originally installed ESPEasy on it. General advice is to use the latest, as that's the greatest.
For update will i need use UART everytime? it is not ok for me.
userosos
on 27 Jun 2020
May be can make an firmware has into only tools for upgrade the firmware? For upgrade only.
userosos
on 27 Jun 2020
May be can make an firmware has into only tools for upgrade the firmware? For upgrade only.
That's what the 2-step OTA bin file is made for.
So you flash that build, then you load a build with OTA in the name.
It could be that an old build didn't have the right check for the size, but recent builds do check with the size of the small 2-step OTA in mind.
TD-er
on 27 Jun 2020
No, Sirs, you are all wrong. Reading before posting helps sometimes. Just have a look at what userosos has documented in his first post:
[....]
ESP_Easy_mega-20180606_normal_ESP8285_1024.bin
[....]
@userosos: you will never be able to update this device using OTA. The devil is in detail:
The "normal" build is too big to allow even a 2-step-OTA-upgrade. If you want to be able to upgrade a 1M device like the Sonoff CH4 R2 you have to use the _minimal_ builds. I'm sorry, but you have to flash the device once again using cables. This is pretty well documented in the wiki of ESPEasy. And don't blame the developers, ESPEAsy is too mighty to fit into every flash size. Works as designed - and as documented.
Wiki591
on 28 Jun 2020
No, Sirs, you are all wrong. Reading before posting helps sometimes. Just have a look at what userosos has documented in his first post:
[....]
ESP_Easy_mega-20180606_normal_ESP8285_1024.bin
[....]@userosos: you will never be able to update this device using OTA. The devil is in detail:
The "normal" build is too big to allow even a 2-step-OTA-upgrade. If you want to be able to upgrade a 1M device like the Sonoff CH4 R2 you have to use the _minimal_ builds. I'm sorry, but you have to flash the device once again using cables. This is pretty well documented in the wiki of ESPEasy. And don't blame the developers, ESPEAsy is too mighty to fit into every flash size. Works as designed - and as documented.
Ok. Thx! What different between minimal_ builds and normal builds?
userosos
on 28 Jun 2020
Some features have been disabled and there is only a minimal set of controllers and plugins included.
TD-er
on 28 Jun 2020
Some features have been disabled and there is only a minimal set of controllers and plugins included.
See:
Thx! Now i flashed it! But i has some problem. If i use the reulse from old firmware the LEDs is blink and relays on/off too everytime ~1 Hz. And if i delete the rules LEDs 2 and 3 is on everytime. Reboot not fix it. If i pressed the buttons into the sonoff the LEDs not triggired on it.
rules1.txt
userosos
on 28 Jun 2020
For me the configuration lokks a little bit mixed up. I do have a Sonoff 1CH device which I had to configure in another way.
You'll find configuration instructions for the 4CH including rules here
I'm sorry, its in German but the pictures you need to follow the config are self explaining, I think.
Wiki591
on 28 Jun 2020
For me the configuration lokks a little bit mixed up. I do have a Sonoff 1CH device which I had to configure in another way.
You'll find configuration instructions for the 4CH including rules here
I'm sorry, its in German but the pictures you need to follow the config are self explaining, I think.
Good! Thx!
I have sonoff ch4 r2 . Have it different between GPIO?
userosos
on 28 Jun 2020
Not as far as I know, should be no difference
Wiki591
on 29 Jun 2020
Related issues
wolverinevn
·
4Comments
s0170071
·
3Comments
TD-er
·
4Comments
hamed-ta
·
5Comments
TD-er
·
3Comments
Most helpful comment
No, Sirs, you are all wrong. Reading before posting helps sometimes. Just have a look at what userosos has documented in his first post:
@userosos: you will never be able to update this device using OTA. The devil is in detail:
The "normal" build is too big to allow even a 2-step-OTA-upgrade. If you want to be able to upgrade a 1M device like the Sonoff CH4 R2 you have to use the _minimal_ builds. I'm sorry, but you have to flash the device once again using cables. This is pretty well documented in the wiki of ESPEasy. And don't blame the developers, ESPEAsy is too mighty to fit into every flash size. Works as designed - and as documented.