Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Dec 12 16:34

    sle118 on httpd

    AirPlay sync improvement release commit NVS parameter on reboot … and 5 more (compare)

  • Dec 07 12:17

    sle118 on v0.4.214-v3.1.5-SqueezeAmp8MBFlash-master

    (compare)

  • Dec 07 12:15

    sle118 on v0.4.214-v3.1.5-SqueezeAmp4MBFlash-master

    (compare)

  • Dec 07 12:13

    sle118 on v0.4.214-v3.1.5-I2S-4MFlash-master

    (compare)

  • Dec 07 12:12

    philippe44 on master

    manual handling of analogue fro… (compare)

  • Dec 06 12:09

    sle118 on v0.4.213-v3.1.5-SqueezeAmp8MBFlash-master

    (compare)

  • Dec 06 12:08

    sle118 on v0.4.213-v3.1.5-SqueezeAmp4MBFlash-master

    (compare)

  • Dec 06 12:06

    sle118 on v0.4.213-v3.1.5-I2S-4MFlash-master

    (compare)

  • Dec 06 12:04

    philippe44 on master

    jack muting jack muting - release (compare)

  • Dec 03 16:32
    daduke closed #16
  • Dec 03 16:30

    daduke on master

    allow spaces in player name (compare)

  • Dec 03 14:29

    sle118 on httpd

    wip httpd implementation (compare)

  • Dec 02 16:25

    sle118 on v0.4.210-v3.1.5-SqueezeAmp8MBFlash-master

    (compare)

  • Dec 02 16:23

    sle118 on v0.4.210-v3.1.5-SqueezeAmp4MBFlash-master

    (compare)

  • Dec 02 16:22

    sle118 on master

    fix http response handling in o… (compare)

  • Dec 02 16:22

    sle118 on v0.4.210-v3.1.5-I2S-4MFlash-master

    (compare)

  • Dec 02 16:20

    sle118 on master

    fix for broken generic i2s buil… (compare)

  • Nov 28 05:33

    sle118 on v0.4.209-v3.1.5-SqueezeAmp8MBFlash-master

    (compare)

  • Nov 28 05:31

    sle118 on v0.4.209-v3.1.5-SqueezeAmp4MBFlash-master

    (compare)

  • Nov 28 05:28

    philippe44 on master

    commit NVS parameter on reboot … (compare)

Sébastien
@sle118
are you saying that you were able to try a second time and that the download failed again?
if OTA isn't working for you, we could check the nvs parameters that govern OTA just to make sure they are ok
Christian Herzog
@daduke
(also unlocks if an error is reported)
Sébastien
@sle118
some NVS parameters to check:
ota_erase_blk: 249856 ota_prio: 6 ota_stack 10240
michaelherger
@michaelherger
Oh, I hadn't tried to restart the flash process
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
Sébastien
@sle118
you probably have bad memories from when the OTA was still in its infancy :)
it's definitely not perfect yet, but it will typically end up working
philippe44
@philippe44
But I think if you update the recovery partition (needs the USB to serial) with the latest version, the OTA is much more stable now
I've done ~15 in a row w/o a failed one
Sébastien
@sle118
@philippe44 I think he's on fw: v0.4.208-IDFv3.1.5-SqueezeAmp8M
(from what he wrote earlier here)
michaelherger
@michaelherger
Almost: fw: v0.4.209-IDFv3.1.5-SqueezeAmp8M
philippe44
@philippe44
on the recovery or on the ota partition
did you update the recovery partition as well Michael?
michaelherger
@michaelherger
Ahm... how would I do that?...
Last time I did some terminal work was with 0.3.x
Is this what I'd do using the esptool.py script?
Sébastien
@sle118
From the UI, to to the firmware page and choose reboot. This will reboot to the recovery partition. When the HTTP UI refreshes, the status bar at the bottom should be red, and show which recovery you are running
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
Chris Hill
@ChrisHill_gitlab
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.
Sébastien
@sle118
I would like to get 5 of them reserved from the Vancouver bundle in case (no pun intended) the demand is strong
Philippe will ship my SqueezeAmp from there
michaelherger
@michaelherger
Good day! I'm in trouble again.
I'm on 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!.[0m

As 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.

michaelherger
@michaelherger
Tried flashing the latest from the terminal: same result.
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?
michaelherger
@michaelherger
Oh my... so I went back to the web UI while in Recovery mode and decided to try another OTA update. And guess what: it was no longer in recovery mode. Re-configured squeezelite, and it's playing again.
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:
Christian Herzog
@daduke
recovery mode is meant to basically perform 2 tasks: a) configure wifi and b) OTA flash the actual player part (squeezelite). So as long as you haven't flashed to player payload, any reboot within recovery will only reboot onto itself (there is nothing else to reboot to)
does this help or am I missing something?
michaelherger
@michaelherger
I'm not sure what "flash the actual player part" would mean: configure Squeezelite and have it start?
The biggest question probably is how I ended up in recovery mode to start with. Could a failed OTA update cause this?
Christian Herzog
@daduke
the firmware consists of two files: recovery and the SL payload. OTA only flashes the payload. If OTA fails, the only working thing left is recovery (hence the name)
michaelherger
@michaelherger
Ok, ok. I'll know next time.
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:
philippe44
@philippe44
A failed OTA will move you back to recovery
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