if OTA isn't working for you, we could check the nvs parameters that govern OTA just to make sure they are ok
ota_erase_blk: 249856
ota_prio: 6
ota_stack 10240
but it's at 40% now... vs. 9% before
Well, that worked. Thanks a lot!
As always this was much easier than I thought :-D
it's definitely not perfect yet, but it will typically end up working
I've done ~15 in a row w/o a failed one
(from what he wrote earlier here)
did you update the recovery partition as well Michael?
Last time I did some terminal work was with 0.3.x
Is this what I'd do using the
esptool.py script?
From there, you can click reboot in the firmware page to go back to squeezelite
I had assumed that on the 26, you flashed recovery...
If you're not on 0.4.x then yes, you need to repeat the TTL flash with esptool.py
Do any of you guys want an acrylic box for a SqueezeAMP? I sent some to Philippe so that he can include them with the shipments to his European customers, but I have quite a few left, which I'm intending to send as a bundle to Vancouver. Before I do that I'll be happy to send some out to you guys if you PM me a postal address.
Philippe will ship my SqueezeAmp from there
I'm on
So I tried to update to the latest firmware about 12h ago. After that it "disappeared".
I connected the serial cable and figured out it was in AP mode again. Connected to it, entered the wlan's password. Which gave me some promising feedback in the terminal:
fw: v0.4.209-IDFv3.1.5-SqueezeAmp8M, mode: recovery(well, wasn't recovery before my attempt to update)So I tried to update to the latest firmware about 12h ago. After that it "disappeared".
I connected the serial cable and figured out it was in AP mode again. Connected to it, entered the wlan's password. Which gave me some promising feedback in the terminal:
.[0;32mI (61865) http_server: http_server_netconn_serve: POST /connect.json.[0m
.[0;32mI (61885) wifi_manager: MESSAGE: ORDER_CONNECT_STA - Begin.[0m
.[0;32mI (61885) http_server: http_server_netconn_serve: done serving connect.json.[0m
.[0;32mI (61885) wifi_manager: Wifi Connecting....[0m
I (62015) wifi: new:<1,0>, old:<1,0>, ap:<1,0>, sta:<1,0>, prof:1
I (62705) wifi: state: init -> auth (b0)
I (62705) wifi: state: auth -> assoc (0)
I (62715) wifi: state: assoc -> run (10)
I (62745) wifi: connected with Fritzli, channel 1, bssid = 38:10:d5:11:90:fc
I (62745) wifi: pm start, type: 0
.[0;32mI (62745) wifi_manager: WIFI_EVENT_STA_CONNECTED. Channel: 1, Access point: Fritzli, BSSID: 38:10:d5:11:90:fc .[0m
.[0;32mI (63035) http_server: System host name squeezelite-esp32, http requested host: 192.168.4.1..[0m
.[0;32mI (63035) http_server: Processing ap.json request.[0m
.[0;32mI (63045) http_server: Starting wifi scan.[0m
.[0;32mI (63045) http_server: Done serving ap.json.[0m
.[0;32mI (63055) http_server: System host name squeezelite-esp32, http requested host: 192.168.4.1..[0m
.[0;32mI (63065) http_server: Serving status.json.[0m
.[0;32mI (63065) http_server: Done Serving status.json.[0m
.[0;32mI (63595) tcpip_adapter: sta ip: 192.168.0.5, mask: 255.255.255.0, gw: 192.168.0.250.[0m
.[0;32mI (63595) wifi_manager: SYSTEM_EVENT_STA_GOT_IP. IP=192.168.0.5, Gateway=192.168.0.250, NetMask=255.255.255.0, Interface: TCPIP_ADAPTER_IF_STA Address was changed.[0m
.[0;32mI (63605) wifi_manager: MESSAGE: EVENT_STA_GOT_IP.[0m
.[0;32mI (63615) wifi_manager: Set STA IP String to: 192.168.0.5.[0m
.[0;32mI (63615) wifi_manager: About to save config to flash.[0m
.[0;32mI (63705) esp_app_main: I have a connection!.[0mAs you can see it successfully connected to my network, got an IP, gateway information etc. It even reflected the information in the footer of the setup page.
Alas it's still listening on its own, private network. I wouldn't see it on my router. It wouldn't respond to that new IP address.
Hit the reboot button, and it was back on step 1.
I tried to set the network from the terminal, but that didn't work either.
Ok, some more info: once it claims to have the new IP address I can indeed connect to it on that network. But it would still be in recovery mode. And if I then press the
Reboot button, I'm back on its old network.
Maybe that's just me hitting the wrong button? What am I supposed to do once it's on my network but in recovery mode?
I'd still like to know what went wrong. I might be learning each time I struggle. But to understand what I did wrong would be helpful, too :smiley:
does this help or am I missing something?
The biggest question probably is how I ended up in recovery mode to start with. Could a failed OTA update cause this?
Thanks!
I'll hopefully also remember to check the AP mode when it disappears. I wouldn't have to dig it out of its enclosure in a dark corner of my room to connect the serial cable :smiley:
As the flash partition that holds the actual squeezelite is erased
So upon boot, as Christian says it will not find anything in the application partition so it will ´stay’ with the recovery partition
Failed OTA are very rare now but it can happen. I had one recently over 30 updates
we’ll more soon as almost all the boards have been shipped