ANNOUNCE: Squeezelite-ESP32 (dedicated thread)

[sle118]

I could not upload it from fw: I2S-4MFlash.521.master-cmake in squeezelite mode, I had to switch to recovery to use the upload button in the web gui.

I (5141) httpd_handlers: serving /status.json to peer 192.168.0.100 port 45539
I (5141) httpd_handlers: serving /messages.json?1 to peer 192.168.0.100 port 45795
W (11891) httpd_uri: httpd_uri: URI '/flash.json' not found
W (11891) httpd_handlers: redirect_processor(1055): 192.168.0.100 requested invalid URL: [/flash.json]
W (11891) httpd_txrx: httpd_resp_send_err: 404 Not Found - This URI does not exist
I (18591) httpd_handlers: serving /status.json to peer 192.168.0.100 port 46307
W (49261) httpd_uri: httpd_uri: URI '/flash.json' not found
W (49261) httpd_handlers: redirect_processor(1055): 192.168.0.100 requested invalid URL: [/flash.json]
W (49271) httpd_txrx: httpd_resp_send_err: 404 Not Found - This URI does not exist
W (55981) httpd_txrx: httpd_sock_err: error in recv : 104
W (55981) httpd_txrx: httpd_sock_err: error in recv : 104
I (56281) httpd_handlers: serving /scan.json to peer 192.168.0.100 port 48867
I (56301) httpd_handlers: serving /commands.json to peer 192.168.0.100 port 49379

Yes, this is expected since we are rebooting the esp32 to recovery. I will possibly hipster the upload button code to reboot to recovery before uploading if necessary.

[mark wollschlager]

I noticed that after I flashed the fw: SqueezeAmp.517.master-cmake I have had a couple of hangs.
The first time, the squeezeamp stopped in the middle of a song and became unresponsive ( no web interface ) wifi dropped also.
I powered it off and back on with no change, although the green led was flashing the 1 per sec/sec+. Powering it off for a longer period of time seemed to 'fix it'.
That was last night. I left it on all night. This morning it was fine but paused at the end of a song and stuck. I was able to advance to the next song in the LMS web interface and since then no problems.
The song files are all FLAC. Not high volume play. 2m from the wifi access point. No logged issues on my LMS server or access point.
I have placed a couple of heat sinks on the SOC as it gets pretty hot, they have been there since before the new FW.
Just an observation. First issue I have had.

[philippe_44]

I noticed that after I flashed the fw: SqueezeAmp.517.master-cmake I have had a couple of hangs.
The first time, the squeezeamp stopped in the middle of a song and became unresponsive ( no web interface ) wifi dropped also.
I powered it off and back on with no change, although the green led was flashing the 1 per sec/sec+. Powering it off for a longer period of time seemed to 'fix it'.
That was last night. I left it on all night. This morning it was fine but paused at the end of a song and stuck. I was able to advance to the next song in the LMS web interface and since then no problems.
The song files are all FLAC. Not high volume play. 2m from the wifi access point. No logged issues on my LMS server or access point.
I have placed a couple of heat sinks on the SOC as it gets pretty hot, they have been there since before the new FW.
Just an observation. First issue I have had.

I don’t think this is a heat issue, but what supply voltage do you use?

[funkybassman]

Is anyone able to clarify the bat_config setup?
I am running the audio kit V2.2 board on a 4000mah battery (just 2 wires), and cannot work out the battery parameters.
Currently running the A1S-517 firmware.

[mark wollschlager]

I don’t think this is a heat issue, but what supply voltage do you use?

12v 1a

[philippe_44]

12v 1a

Yes, so it's not a heat issue

[sle118]

Yes, so it's not a heat issue

All, the most stable version right now is 142 (older UI) or 145. I'm still busy stabilizing some of the changes introduced at a later point.

[ElFishi]

All, the most stable version right now is 142 (older UI) or 145. I'm still busy stabilizing some of the changes introduced at a later point.

I have fw: I2S-4MFlash.521.master-cmake running, so far without issue. But it gathered one or two hours only.

[sle118]

I have fw: I2S-4MFlash.521.master-cmake running, so far without issue. But it gathered one or two hours only.

There's a known performance hog on the web UI right now, coming from the status update. Provided there's no client, it shouldn't be an issue.

[mark wollschlager]

All, the most stable version right now is 142 (older UI) or 145. I'm still busy stabilizing some of the changes introduced at a later point.

Had another hang this morning. I powered the squeezeamp on and about 5 minutes after starting to play it hung.
The song stopped and while the 'green led' remained solid on the squeezeamp web interface was unavailable.
After about 10 minutes the green led flashed a pattern and rebooted. I was able to resume play without powering off the device.
It's been going now for about an hour with no hiccups.
Edit. And after another hour it hung again and rebooted. The web interface stayed up and the log indicates a successful start.
And again about 50 minutes later. It reboots after about 4 minutes according to the web interface.
Where is the debug log?

[KeBul]

I tried both my USB to serial adapter and the inbuilt UART port, did you have to switch it into flash mode, If I use the on and rst buttons to do that I can't get it to do anything different, if I manually pull down GPIO 0 and then reset, D4 lights up but I still can't flash it.

Kev

Having made some progress today I'd thought I'd post my findings here in case anyone hits similar problems.

I'm trying an ESP32 A1S AI Thinker Audio Developer Board, I bought it from eBay, very cheap so no problem with the risk and it ambled its way across from China on a slow boat within a couple of weeks.
What I received was V2.2 of the board, quite possibly, not an official build, certain aspects of the printing on both the ESP32 A1S chip and the general screen printing made me suspicious.

I had been unable to download firmware using either my USB to TTL adapter or the inbuilt uart and was increasingly convinced it was at the very least a fake ESP32 chip.

Anyway today I managed to connect to it through its built in uart port using putty and confirm pressing and holding the boot button then a press and release of the RST button followed by releasing the boot button did indeed boot it into download mode. However, I still could not get it to download the Squeezelite ESP32 A1S firmware using the ESP Download Tool, getting sync errors and timeouts.

Digging around on many ESP and Arduino forums I eventually found a thread that suggested hitting the boot button at the time the firmware download was started. A little experimenting found that if you start the download and when display output stops press and hold the boot button for a couple of seconds the download process then continues... and completes... woohoo success! I could then go through the rest of the process setting up the Squeezelite ESP32 A1S.

So if you hit similar issues with a cheap eBay V2.2 "AI Thinker ESP32-A1S audio developer board" then try this...

My process was to connect from USB to uart (CP210x Windows drivers installed) using a decent USB to micro USB cable, power the module from a 5v 2A psu as well, hold boot, hit reset, release boot. Start the ESP Download tool configured up as per Philippe's instructions in #1 post of this thread, selecting the com port for the CP210x uart (check device manager/Ports(COM & LPT) for correct com port) and a speed of 115200. Start download, watch the download tool dos box display and when it stops, press the boot button for a second or two.

It looks like there is a hardware design fault on my board, the apparent fix is to add a 1uF-10uF capacitor between the EN (rst) pin and GND. I'll try that in the next day or so and report back.
***Update*** added the 1uF capacitor and that helps a lot, flashing works reliably now, but erase sometimes seems to go on forever, when it does that, after 10 minutes or so I press the boot button for 1-2 seconds and it completes OK.

I went for 142 as that's on my two SqueezeAMPs and is working well and at least initially wanted to try the A1S with something I could trust and although I had my usual initial battle with Bluetooth, especially to my Bose headphones, I've settled on using the new Anker Soundcore 2 bluetooth speaker a purchased a couple of weeks ago and that's working well.

Not as small and sexy as a SqueezeAMP, about twice the footprint and no case for it yet, but it sounds good though especially for £14.09 delivered. It has six buttons built in to play around with, so a bit more learning to do there. Could also do with finding out how to tame the green power led which currently feels it has to try and provide light for South East London

Kev

[schmurtz]

Wow look at that !

https://www.seeedstudio.com/ESP32-Development-board-WT32-SC01-p-4735.html

ESP32-WROVER-B 4MB SPI Flash and 8MB PSRAM. , 3.5-inch 320x480 capacitive 2-point multi-touch screen

Datasheet here
Now I'm dreaming about a very small "Squeezelite-ESP32-Touch" !

[patrick31698]

Wow look at that !

https://www.seeedstudio.com/ESP32-Development-board-WT32-SC01-p-4735.html

Datasheet here
Now I'm dreaming about a very small "Squeezelite-ESP32-Touch" !

[ATTACH=CONFIG]32123[/ATTACH]

VERY nice! But there is not audio out?

[philippe_44]

Wow look at that !

https://www.seeedstudio.com/ESP32-Development-board-WT32-SC01-p-4735.html

Datasheet here
Now I'm dreaming about a very small "Squeezelite-ESP32-Touch" !

I don't want to throw cold water at this but believe me this is very likely above the capabilities of the esp32. I already had a lot (and I mean a lot) of difficulties to fit the wifi, all codecs (faad did not work and I had to tweak mp3 a lot), gain, resampler (sox did not work, I had to do my kind of my own), equalizer, i2s, fft, display and a few more without overloading the CPU. Here, if you want to have JiveLite, you're going to face CPU and memory issues.

The largest WROVER is 2x240Mhz xtensa32 core and has 32MB of Flash (that might be ok) but only BMB of SRAM of which only 4MB are accessible directly. The other 4MB must be paginated *manually*, so although I wanted to use it at the beginning (for buffers) I gave up. And JiveLite is absolutely lite, but is "lite" for a Pi

Now, in addition, this CPU is not using a NAND + DDR system, but instead it's a serial NOR (with XPI and that's good) and serial PSRAM. These are Quad-SPI memories that I've set SPI lines @ 80MHz. With cache it does marvel (beyong my expectations), but you can't compared that to a DDR with separated A/D buses, page & burst modes and all that jazz. And you have little to no hardware accelerators. In comparison, a Touch is an ARM11 @ 533MHz with 128MB of Flash and 128MB of DDR (32 bits parallel bus)

That's the reason why I always compare Squeezelite-ESP32/SqueezeAMP to a new generation of Boom/Classic but nothing else.

[funkybassman]

Not as small and sexy as a SqueezeAMP, about twice the footprint and no case for it yet, but it sounds good though especially for £14.09 delivered. It has six buttons built in to play around with, so a bit more learning to do there. Could also do with finding out how to tame the green power led which currently feels it has to try and provide light for South East London

Kev

I agree that this board has its quirks, and having studied the schematic, it would appear that the green led is connected to a power/charge chip which is not addressable. My highly technical remedy for the overly bright green light, is a small square of insulating tape!😉