ANNOUNCE: Squeezelite-ESP32 (dedicated thread)

[funkybassman]

Just been reading the posts regarding SPI display configuration.
I had a go with an SSD1351 display and came up with the following config. Maybe it might help someone?
DC - pin 5
MOSI - pin 13 (MTCK)
CLK - pin 14 (MTMS)
CS - pin 15 (MTDO)

[mboxler]

Merus MA12070P

For fun I connected my Merus MA12070P evaluation board to my ESP32-WROVER board, and got no sound. I realize there is no driver for this amp chip, but as I understand it it may be possible to get this working. The first thing I noticed is that the default i2s_framesize for the amp is 64 (2 * 32) bits. As I understand it, the ESP32-WROVER has a maximum of 32 (2 * 16) bits. According to the datasheet (page 78)

https://docs.google.com/viewer?url=https%3A%2F%2Fwww.infineon.com%2Fdgdl%2FInfineon-MA12070P-DS-v01_00-EN.pdf%3FfileId%3D5546d46264a8de7e0164b761f2f261e4

register address 0X36(4:3) needs be changed to 10.

Can someone help me with the command needed in dac_controlset to accomplish this? At least I think that's the right place to initiate a register change.
I'm sure there are a lot of other problems, but I thought this would be a fun project.

Thanks, Mike

[philippe_44]

For fun I connected my Merus MA12070P evaluation board to my ESP32-WROVER board, and got no sound. I realize there is no driver for this amp chip, but as I understand it it may be possible to get this working. The first thing I noticed is that the default i2s_framesize for the amp is 64 (2 * 32) bits. As I understand it, the ESP32-WROVER has a maximum of 32 (2 * 16) bits. According to the datasheet (page 78)

https://docs.google.com/viewer?url=https%3A%2F%2Fwww.infineon.com%2Fdgdl%2FInfineon-MA12070P-DS-v01_00-EN.pdf%3FfileId%3D5546d46264a8de7e0164b761f2f261e4

register address 0X36(4:3) needs be changed to 10.

Can someone help me with the command needed in dac_controlset to accomplish this? At least I think that's the right place to initiate a register change.
I'm sure there are a lot of other problems, but I thought this would be a fun project.

Thanks, Mike

I assume you've set dac_config with bck, ws, do, model, sda, scl and i2c properly. Then, "dac_controlset" should look like

{ init: [ {"reg":54,"val":17} ] }

PS: please verify the value. You might have to set register 0x35 to 0x00, but I'm not sure

[ElFishi]

crashes

I get random crashes in one of my systems.

It plays music, makes some noise like repeating the last milliseconds over and over for a second and then the ESP reboots.
From the log I can't see much.

[05:07:57.992304] output_thread_i2s_stats:612 
[05:07:57.992536] output_thread_i2s_stats:613               ----------+----------+-----------+-----------+  
[05:07:57.992768] output_thread_i2s_stats:614               max (us)  | min (us) |   avg(us) |  count    |  
[05:07:57.992985] output_thread_i2s_stats:615               ----------+----------+-----------+-----------+  
[05:07:57.993226] output_thread_i2s_stats:616  Buffering(us)      2239|       782|       1101|        107|
[05:07:57.993505] output_thread_i2s_stats:617    i2s tfr(us)     45635|     44214|      45311|        107|
[05:07:57.993785] output_thread_i2s_stats:618               ----------+----------+-----------+-----------+
[05:08:02.988925] output_thread_i2s_stats:602 Output State: 2, current sample rate: 44100, bytes per frame: 4
[05:08:02.989472] output_thread_i2s_stats:603               +----------+----------+----------------+-----+----------------+
[05:08:02.991106] output_thread_i2s_stats:604               |      max |      min |        average |     |        count   |
[05:08:02.992182] output_thread_i2s_stats:605               |  (bytes) |  (bytes) |        (bytes) |     |                |
[05:08:02.992407] output_thread_i2s_stats:606               +----------+----------+----------------+-----+----------------+
[05:08:02.992600] output_thread_i2s_stats:607         stream|    408597|    212156|          310434|   60|             108|
[05:08:02.992972] output_thread_i2s_stats:608         output|   1837500|   1817020|         1828710|   89|             108|
[05:08:02.993320] output_thread_i2s_stats:609               +----------+----------+----------------+-----+----------------+
[05:08:02.993548] output_thread_i2s_stats:610       received|      2048|      2048|            2048|  100|             108|
[05:08:02.993895] output_thread_i2s_stats:611               +----------+----------+----------------+-----+----------------+
[05:08:02.994547] output_thread_i2s_stats:612 
[05:08:02.994784] output_thread_i2s_stats:613               ----------+----------+-----------+-----------+  
[05:08:02.995039] output_thread_i2s_stats:614               max (us)  | min (us) |   avg(us) |  count    |  
[05:08:02.995248] output_thread_i2s_stats:615               ----------+----------+-----------+-----------+  
[05:08:02.995456] output_thread_i2s_stats:616  Buffering(us)      2117|       750|       1129|        108|
[05:08:02.995746] output_thread_i2s_stats:617    i2s tfr(us)     45805|     44279|      45279|        108|
[05:08:02.996006] output_thread_i2s_stats:618               ----------+----------+-----------+-----------+
I (13542751) monitor: Heap internal:37200 (min:36364) external:1258072 (min:1197020)
[05:08:07.989907] output_thread_i2s_stats:602 Output State: 2, current sample rate: 44100, bytes per frame: 4
[05:08:07.995071] output_thread_i2s_stats:603               +----------+----------+----------------+-----+----------------+
[05:08:07.995827] output_thread_i2s_stats:604               |      max |      min |        average |     |        count   |
[05:08:07.996063] output_thread_i2s_stats:605               |  (bytes) |  (bytes) |        (bytes) |     |                |
[05:08:07.996289] output_thread_i2s_stats:606               +----------+----------+----------------+-----+----------------+
[05:08:07.996506] output_thread_i2s_stats:607         stream|    211111|     11535|          109949|   21|             108|
[05:08:07.996858] output_thread_i2s_stats:608         output|   1837500|   1817020|         1828113|   89|             108|
[05:08:07.997163] output_thread_i2s_stats:609               +----------+----------+----------------+-----+----------------+
[05:08:07.997380] output_thread_i2s_stats:610       received|      2048|      2048|            2048|  100|             108|
[05:08:07.997685] output_thread_i2s_stats:611               +----------+----------+----------------+-----+----------------+
[05:08:07.997906] output_thread_i2s_stats:612 
[05:08:07.998115] output_thread_i2s_stats:613               ----------+----------+-----------+-----------+  
[05:08:07.998341] output_thread_i2s_stats:614               max (us)  | min (us) |   avg(us) |  count    |  
[05:08:07.998570] output_thread_i2s_stats:615               ----------+----------+-----------+-----------+  
[05:08:07.998801] output_thread_i2s_stats:616  Buffering(us)      2012|       837|       1113|        108|
[05:08:07.999465] output_thread_i2s_stats:617    i2s tfr(us)     45718|     44513|      45311|        108|
[05:08:07.999730] output_thread_i2s_stats:618               ----------+----------+-----------+-----------+
[05:08:08.306904] decode_thread:100 decode complete
[05:08:08.422044] codec_open:279 codec open: 'm'
[05:08:08.424289] stream_sock:508 connecting to 192.168.0.121:9000
[05:08:08.475565] stream_sock:585 header: GET /stream.mp3?player=84:0d:8e:d2:61:d4 HTTP/1.0




[05:08:08.936059] stream_thread:264 headers: len: 491
HTTP/1.1 200 OK

Server: Logitech Media Server (8.0.0 - 1603391272)

Connection: close

Content-Type: audio/mpeg

Set-Cookie: Squeezebox-albumView=; path=/

Set-Cookie: Squeezebox-expandPlayerControl=true; path=/

Set-Cookie: Squeezebox-expanded-MY_MUSIC=0; path=/

Set-Cookie: Squeezebox-expanded-FAVORITES=0; path=/

Set-Cookie: Squeezebox-expanded-PLUGINS=0; path=/

Set-Cookie: Squeezebox-expanded-PLUGIN_MY_APPS_MODULE_NAME=0; path=/

Set-Cookie: Squeezebox-expanded-RADIO=0; path=/

[05:08:09.347454] mad_decode:247 setting track_start

fw: development.148-I2S-4MFlash
config attached.

I can only log by telnet atm, getting a serial wire in would be cumbersome.

Does anyone else observe such behaviour?

[philippe_44]

I get random crashes in one of my systems.

It plays music, makes some noise like repeating the last milliseconds over and over for a second and then the ESP reboots.
From the log I can't see much.

I can only log by telnet atm, getting a serial wire in would be cumbersome.

Does anyone else observe such behaviour?

Ah, this is annoying as stability has been a key attribute so far for us. Can you tell a bit more about what is playing when it happens? Any pattern? Any chance you could go back in time and say which version has the issue (start with a pretty large jump back, at least a good month and then do a dichotomy approach from there)

[ElFishi]

Ah, this is annoying as stability has been a key attribute so far for us. Can you tell a bit more about what is playing when it happens? Any pattern? Any chance you could go back in time and say which version has the issue (start with a pretty large jump back, at least a good month and then do a dichotomy approach from there)

Unfortunately no pattern I could observe. I was playing mp3s and oggs from my file server. Incidents occurred rarely 10min apart, mosty hours.
So I can try and roll back, but it will take time...

I presume I'm alone with this...

[KeBul]

I presume I'm alone with this...

I've been testing extensively (playing all day) with development.145.master-cmake squeezeAMP8MBFlash over the last few weeks and haven't noticed any crashes, although not always in the room listening to it, so if it crashed it rebooted and continued to play.

Using I2S not SPDIF though. Did not always have a display configured and connected either.

On another setup to a bluetooth speaker I tried 148 but couldn't get bluetooth working, so dropped back to 142 which is the latest version available that I seem to be able to get music to play on bluetooth.

Kev

[ElFishi]

thx for the response.
I feel a bit embarrassed atm. Played some hours today without glitch.
At one time after power up the unit was unresponsive, be it from LMS, telnet or web interface - yet the display scrolled the title. Eventually it rebooted and went back to normal.

I can't rule out a flakey WiFi connection. I had that before (too many neighbors I believe).

Edit: there is a way to crash the ESP: write a forum post that there is no error. 5 mins later it goes down.

[philippe_44]

thx for the response.
I feel a bit embarrassed atm. Played some hours today without glitch.
At one time after power up the unit was unresponsive, be it from LMS, telnet or web interface - yet the display scrolled the title. Eventually it rebooted and went back to normal.

I can't rule out a flakey WiFi connection. I had that before (too many neighbors I believe).

Edit: there is a way to crash the ESP: write a forum post that there is no error. 5 mins later it goes down.

2 things
- can you try to play for a couple of days w/o display?
- can you try to run for another couple of day and make sure that nothing is using the web interface?

[ElFishi]

2 things
- can you try to play for a couple of days w/o display?
- can you try to run for another couple of day and make sure that nothing is using the web interface?

Duh, I just cleared display_config and get lots of

[01:02:21.124500] process:555 unhandled grfe
[01:02:21.136980] process:555 unhandled grfe
[01:02:21.306428] process:555 unhandled grfe
[01:02:21.310112] process:555 unhandled grfe
[01:02:21.433752] process:555 unhandled grfe
[01:02:21.442494] process:555 unhandled grfe
[01:02:21.610787] process:555 unhandled grfe
[01:02:21.631126] process:555 unhandled grfe
[01:02:21.725542] process:555 unhandled grfe
[01:02:21.738595] process:555 unhandled grfe
[01:02:21.908878] process:555 unhandled grfe
[01:02:21.911424] process:555 unhandled grfe

[sle118]

New build, fresh from the oven

I just wanted to report a new build which was generated through GitHub's Actions.

https://github.com/sle118/squeezelite-esp32/actions?query=workflow%3ACross-Build

I intentionally bumped the build number and the release is now at #508.

There are 2 main changes to report

• The new build system will always align to the latest and greatest ESP-IDF release v4.0.
• The consequence of the previous change is that it is no longer possible to use WiFi power save None as a workaround for WiFi stability. Given that the firmware uses the latest ESP-IDF v4.0, I am hoping that the workaround will no longer be needed.

As usual, please report any issues you might have, including issues playing back to a bluetooth external sink.

[mherger]

ANNOUNCE: Squeezelite-ESP32(dedicated thread)

I installed the "SqueezeAMP" build 508. Quick test played Spotty, TIDAL
(flac), Radio Paradise (flac), some local station (mp3). But the UI says
"fw: custom.build". What am I missing?

(playing "Bohemian Rhapsody" from TIDAL's "My Mix" right now :-))

--

Michael

[sle118]

I installed the "SqueezeAMP" build 508. Quick test played Spotty, TIDAL
(flac), Radio Paradise (flac), some local station (mp3). But the UI says
"fw: custom.build". What am I missing?

(playing "Bohemian Rhapsody" from TIDAL's "My Mix" right now :-))

--

Michael

Thanks for pointing this out. The build version is cooked in by the build system through environment variables. I guess I need to check my Github Actions to make sure it propagates that variable properly.

EDIT: This issue is now resolved!

[sle118]

I've been testing extensively (playing all day) with development.145.master-cmake squeezeAMP8MBFlash over the last few weeks and haven't noticed any crashes, although not always in the room listening to it, so if it crashed it rebooted and continued to play.

Using I2S not SPDIF though. Did not always have a display configured and connected either.

On another setup to a bluetooth speaker I tried 148 but couldn't get bluetooth working, so dropped back to 142 which is the latest version available that I seem to be able to get music to play on bluetooth.

Kev

Out of curiosity, have you tried versions between 143, 145 or 147 to see if bluetooth is working?

[KeBul]

Out of curiosity, have you tried versions between 143, 145 or 147 to see if bluetooth is working?

Yes, stepped backwards from 148 and 142 was the first version I got to that worked.

I can try again, It's not overly important to me what version I'm running, just playing around and testing, that SqueezeAMP is spare at the moment, but trying it with the Bluetooth speaker as a possible for fitting inside the speaker to make a fully portable setup, speaker battery life is declared as 24 hour, had it running non stop for nine hours yesterday, didn't hear any issues, so 142 bluetooth is pretty solid.

I'll report back when I have another round of testing and run back through the versions again.

Cheers

Kev