-
Notifications
You must be signed in to change notification settings - Fork 15
Update step gets write error for shelly 1 mini gen 3 #108
Description
I just tried multiple times to update my shelly and the update always states that it is successful, but after the reboot of the shelly the normal UI just comes up and no tasmota AP.
Soldering is not my strong suit, so I'd love to do this OTA Update.
In the logs at the end, there is something about a missmatch in a signature, followed by some write errors.
My shelly is running on 1.4.0, i've received them yesterday.
I appended the whole log file, but this is the part I am curious about.
{ "ts": 1721994423.318, "level": 2, "data": "shelly_ota.cpp:771 Update succeeded, will reboot, uba=3, cd=0/ct=0 s", "fd": 1 }, { "ts": 1721994423.32, "level": 2, "data": "shos_system.c:60 Rebooting in 3000 ms", "fd": 1 }, { "ts": 1721994423.366, "level": 2, "data": "shelly_notification:208 Event from sys: {\"component\":\"sys\", \"event\":\"scheduled_restart\", \"time_ms\": 2982, \"ts\":1721994423.32}", "fd": 1 }, { "ts": 1721994423.57, "level": 2, "data": "shelly_ota.cpp:182 OTA status success, 100 %", "fd": 1 }, { "ts": 1721994423.572, "level": 1, "data": "shelly_update.cpp:416 FW signatures: want 07 got 00", "fd": 1 }, { "ts": 1721994423.573, "level": 0, "data": "efuse Bits are not empty. Write operation is forbidden.", "fd": 1 }, { "ts": 1721994423.575, "level": 0, "data": "shelly_update.cpp:443 EFUSE write error bit[1]: 5636", "fd": 1 }, { "ts": 1721994423.576, "level": 0, "data": "efuse Bits are not empty. Write operation is forbidden.", "fd": 1 }, { "ts": 1721994423.578, "level": 0, "data": "shelly_update.cpp:443 EFUSE write error bit[2]: 5636", "fd": 1 }, { "ts": 1721994423.579, "level": 1, "data": "shelly_ota_source_rp:25 leftover RPC source 0x3fcc92f8", "fd": 1 }, { "ts": 1721994423.6, "level": 2, "data": "shelly_notification:208 Event from sys: {\"component\":\"sys\", \"event\":\"ota_success\", \"msg\":\"success\", \"ts\":1721994423.56}", "fd": 1 }