Tasmota: MINIMAL firmware - please upgrade

Created on 15 Feb 2019  Â·  21Comments  Â·  Source: arendst/Tasmota

_Also, make sure these boxes are checked [x] before submitting your issue - Thank you!_

  • [X ] _Searched the problem in issues and in the wiki_
  • [X ] _Hardware used_ : Sonoff Basic
  • [X ] _Development/Compiler/Upload tools used_ :
  • [X ] _If a pre-compiled release or development binary was used, which one?_ :
  • [X ] _You have tried latest release or development binaries?_ :
  • [X ] _Provide the output of command_status 0 :
18:35:07 CMD: status 0
18:35:07 MQT: stat/sonoff/STATUS = {"Status":{"Module":1,"FriendlyName":["Sonoff"],"Topic":"sonoff","ButtonTopic":"0","Power":0,"PowerOnState":3,"LedState":1,"SaveData":1,"SaveState":1,"SwitchTopic":"SensorT","SwitchMode":[2,2,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":1,"SensorRetain":0,"PowerRetain":0}}
18:35:07 MQT: stat/sonoff/STATUS1 = {"StatusPRM":{"Baudrate":115200,"GroupTopic":"sonoffs","OtaUrl":"http://thehackbox.org/tasmota/020500/sonoff.bin","RestartReason":"Blocked Loop","Uptime":"0T00:07:07","StartupUTC":"2019-02-15T17:28:00","Sleep":50,"CfgHolder":4617,"BootCount":94,"SaveCount":1836,"SaveAddress":"FB000"}}
18:35:07 MQT: stat/sonoff/STATUS2 = {"StatusFWR":{"Version":"6.4.1.17(b4b1ee9-minimal)","BuildDateTime":"2019-02-14T18:15:07","Boot":31,"Core":"2_5_0","SDK":"3.0.0-dev(c0f7b44)"}}
18:35:07 MQT: stat/sonoff/STATUS3 = {"StatusLOG":{"SerialLog":2,"WebLog":2,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["WIFI",""],"TelePeriod":60,"Resolution":"558180C0","SetOption":["00008089","280500000100000000000000000000000000","00000000"]}}
18:35:07 MQT: stat/sonoff/STATUS4 = {"StatusMEM":{"ProgramSize":381,"Free":620,"Heap":26,"ProgramFlashSize":1024,"FlashSize":1024,"FlashChipId":"146085","FlashMode":3,"Features":["00000809","00082580","000403A2","21021702","000000C0"]}}
18:35:08 MQT: stat/sonoff/STATUS5 = {"StatusNET":{"Hostname":"sonoff-7701","IPAddress":"192.168.1.14","Gateway":"192.168.1.1","Subnetmask":"255.255.255.0","DNSServer":"192.168.1.1","Mac":"80:7D:3A:6B:1E:15","Webserver":2,"WifiConfig":3}}
18:35:08 MQT: stat/sonoff/STATUS6 = {"StatusMQT":{"MqttHost":"192.168.1.15","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_6B1E1515","MqttUser":"MyName","MqttType":1,"MAX_PACKET_SIZE":1000,"KEEPALIVE":15}}
18:35:08 MQT: stat/sonoff/STATUS7 = {"StatusTIM":{"UTC":"Fri Feb 15 17:35:08 2019","Local":"Fri Feb 15 18:35:08 2019","StartDST":"Sun Mar 31 02:00:00 2019","EndDST":"Sun Oct 27 03:00:00 2019","Timezone":"+01:00"}}
18:35:08 MQT: stat/sonoff/STATUS10 = {"StatusSNS":{"Time":"2019-02-15T18:35:08","Switch2":"ON"}}
18:35:08 MQT: stat/sonoff/STATUS11 = {"StatusSTS":{"Time":"2019-02-15T18:35:08","Uptime":"0T00:07:08","Vcc":3.417,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"POWER":"OFF","Wifi":{"AP":1,"SSId":"

To Reproduce
Trying to update using http://sonoff.maddox.co.uk/tasmota/sonoff.bin or http://sonoff.maddox.co.uk/tasmota/sonoff-minimal.bin or by downloading the file and then selecting it; the main page always shows MINIMAL firmware - please upgrade
I've also tried to update to sonoff-minimal.bin and then to sonoff.bin, but no luck

Expected behavior
Device updated and restarted without showing "MINIMAL firmware - please upgrade"

duplicated

Most helpful comment

Yes, all my fault!
However... the fact that several people have made the same mistake indicates the process could be improved a little.
When the minimal firmware loads, the generic message "minimal firmware, please upgrade" is extremely misleading, and has resulted in wasted time by many.
If the firmware knows it is in the process of flashing the real firmware, the message should indicate this. I know that "every byte counts" with Tasmota, but even removing the "please update" part of the message would be less confusing. Just a couple of tiny ideas to remove as much friction as possible for new users. There is enough to learn as it is :)

All 21 comments

Minimal is just an interim version used to free flash memory for the full version. You need to upgrade to the full version.

Use instead the latest version from http://thehackbox.org/tasmota/020500/sonoff.bin

If you want further information about minimal firmware and upgrades, please check the wiki.

If you need further assistant please find us in the Tasmota Support Chat. Thanks

Support Information

See Wiki for more information.
See Chat for more user experience.

http://thehackbox.org/tasmota/020500/sonoff.bin

I've tried that as well but when it restarts, I'm still on the minimal firmware

Please, do a reset 5 in the console and then try again.

If that doesn't work, you will need to erase all flash with esptool.py as
explained in the wiki and flash again with the precompiled bins. Sorry.

El vie., 15 de feb. de 2019 15:16, jacoscar notifications@github.com
escribió:

http://thehackbox.org/tasmota/020500/sonoff.bin

I've tried that as well but when it restarts, I'm still on the minimal
firmware

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/arendst/Sonoff-Tasmota/issues/5239#issuecomment-464147343,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ahw-hz7KjIzaiwFB5OYnRm9Y5q0lHUdtks5vNvlygaJpZM4a-Hk0
.

I don't think reset 5 works; it restarts but it still connects back to the wifi with all the settings as they were

As long as minimal is loaded you won't be able to change any setting so if your otaurl is set for minimal it won't change to anything else.

Try a firmware upgrade by file upload from the GUI which should work.

After that change your otaurl to the correct binary not being a minimal version.

it still doesn’t work 😫

I ended up reflashing it via serial; I won't try to update it again...

Me too. Same issue.
Im still always on the minimal firmware.
Is there any chance to avoid reflash via serial ?

I had a working non-minimal version which was uploaded over serial.
Then did the OTA using the web interface using the file: http://thehackbox.org/tasmota/release/sonoff.bin
It now says I am on minimal.
This is a real issue. (and if the is that I've misunderstood something, then the issue is UI or documentation)

no... the issue is (mostly) me.
Nothing indicated that there was more going on. It actually hadn't finished. Tried again in the time it took to write the above post, and all is well!

https://github.com/arendst/Sonoff-Tasmota/wiki/Upgrading#upgrade-by-web-server

In order to OTA upgrade, there has to be enough free program memory to load a new firmware binary along with the existing firmware. The existing firmware is performing the load and when that is done, it hands of to the new firmware. The only way to get two firmware binaries is to make room for them. So, the first thing Tasmota does is load Minimal next to the existing firmware. Once handed off, there is now enough free space to load the ultimate firmware. Minimal loads it, then hands off. Tasmota's web OTA handles this all for you. What you saw was the interim Minimal load which then was immediately followed by the final update.

So, it was... all you ;-)

Yes, all my fault!
However... the fact that several people have made the same mistake indicates the process could be improved a little.
When the minimal firmware loads, the generic message "minimal firmware, please upgrade" is extremely misleading, and has resulted in wasted time by many.
If the firmware knows it is in the process of flashing the real firmware, the message should indicate this. I know that "every byte counts" with Tasmota, but even removing the "please update" part of the message would be less confusing. Just a couple of tiny ideas to remove as much friction as possible for new users. There is enough to learn as it is :)

Because Tasmota is working with limited ESP82xx resources, it re-uses some artifacts to avoid having to store more than is needed in the limited program space. The "Please Upgrade" message is generic. The Minimal software doesn't know how it got there. When a user updates "manually" using the File Upload OTA, they have to manually load Minimal and then repeat the upgrade to load the final firmware. When Minimal is booted, it simply is broadcasting to its world, "I'm not supposed to be here. Do something!" In fact, sometimes a web OTA does barf and the second step doesn't complete successfully. And, in that case, Minimal needs to say the same thing. Thus, knowing that the web OTA is a two step process is left as wiki reading for the user.

I upgraded from 6.5.0.1 2_3_0 and 2_5_0 to 6.5.1. A couple of sonoffs are now on 6.7.1 minimal, but they wond upgrade further. Even if i force them to upgrade, after the reboot they are still on minimal.

Another sonoff keeps staying on 6.5.0.1 2_5_0 and wont even go on 6.7.1 minimal after reboot.

Ok i solved upgrading those with minimal via FILE upload. They are fine now.

minimal firmware will break your device and leave it in an unresponsive state.
=> see also my open issue #7120
Only way out seems to be to upgrade by serial which is not acceptable if the devices are installed in the wall. I have the issue with 6.4 6.5 and 6.6 stock versions.

Just re-tested it with version 6.5.0.10 and the official minimal-firmware:
http://thehackbox.org/tasmota/tasmota-minimal.bin

What I did....

  • on v 6.5.0.10 run "reset 5"
  • perform an reboot on the device
  • load minimal-firmware
  • (as stated by arendst reset 5 does not work now, so I loaded the 7.1.1.
    => nothing happen, I am stuck in the 7.1.1 minimal firmware
    => it shows that like in issue #7120 minimal firmware is broken

Serial is not practicable when the devices are installed in the wall. Using the stock-firmware (which requires minimal for upgrade) you end up with a broken setup and need to flash by serial, which is deadly if you have 40+ devices mounted in the wall

tasmota-minimal is broken

A work around is to.....

  • compile an own minimal-firmwae load it over the official tasmota-minimal and then load the 7.1.1.

=> something is clearly wrong...

If you are stuck on minimal with OTA, try downloading the normal version, and do an update via file upload. It worked for me

The real problem is the lack of info/log on why an upgrade fails.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Vujagig picture Vujagig  Â·  3Comments

ximonline picture ximonline  Â·  3Comments

jensuffhaus picture jensuffhaus  Â·  3Comments

grizewald picture grizewald  Â·  3Comments

smadds picture smadds  Â·  3Comments