ANNOUNCE: Squeezelite-ESP32 (dedicated thread)

[troffasky]

Trying to get a SSD1322 OLED working with esp32-a1s Audio Kit V2.2 in SPI mode.
I thought my OLED might have been a dud because I have tried many permutations of GPIO pins and not getting anywhere. Tested it on a Pi using Luma OLED library [https://github.com/rm-hull/luma.examples] and struggled there too, until I passed the --spi-device 1 parameter [default is 0] and suddenly it's working.
So I know my OLED module works but I don't know what the equivalent of --spi-device 1 is with cfg-hw-display.
This is my first attempt at anything with SPI. The Luma docs aren't especially enlightening:
https://luma-core.readthedocs.io/en/...ace.serial.spi
"device (int) – SPI device, usually 0 (default) or 1."

Any ideas?

[philippe_44]

Trying to get a SSD1322 OLED working with esp32-a1s Audio Kit V2.2 in SPI mode.
I thought my OLED might have been a dud because I have tried many permutations of GPIO pins and not getting anywhere. Tested it on a Pi using Luma OLED library [https://github.com/rm-hull/luma.examples] and struggled there too, until I passed the --spi-device 1 parameter [default is 0] and suddenly it's working.
So I know my OLED module works but I don't know what the equivalent of --spi-device 1 is with cfg-hw-display.
This is my first attempt at anything with SPI. The Luma docs aren't especially enlightening:
https://luma-core.readthedocs.io/en/...ace.serial.spi
"device (int) – SPI device, usually 0 (default) or 1."

Any ideas?

SSD1322 certainly works but A1S is funny with certain GPIO. What is your wiring?

[Paul Webster]

I expect that the experts will need to see your configuration.

The current squeezelite-esp32 docs say:

SPI
The NVS parameter "spi_config" set the spi's gpio used for generic purpose (e.g. display). Leave it blank to disable SPI usage. The DC parameter is needed for displays. Syntax is

data=<gpio>,clk=<gpio>[,dc=<gpio>][,host=1|2]

[troffasky]

I have only tried three permutations of GPIOs since writing it down but this is what I've tried so far:

cfg-hw-spi -d 19 -k 18 -c 23 -h 1
cfg-hw-display -t SPI -d SSD1322 -w 256 -h 64 --cs=5 --reset=22

cfg-hw-spi -d 19 -k 15 -c 13 -h 1
cfg-hw-display -t SPI -d SSD1322 -w 256 -h 64 --cs=5 --reset=22

cfg-hw-spi -d 19 -k 18 -c 21 -h 1 [and 2]
cfg-hw-display -t SPI -d SSD1322 -w 256 -h 64 --cs=5 --reset=22

13 and 15 are shared with other functions, selectable by DIP switch. Documentation specific to this board seems to have disappeared from the internet. It is very reasonably priced though.

[philippe_44]

I have only tried three permutations of GPIOs since writing it down but this is what I've tried so far:

cfg-hw-spi -d 19 -k 18 -c 23 -h 1
cfg-hw-display -t SPI -d SSD1322 -w 256 -h 64 --cs=5 --reset=22

cfg-hw-spi -d 19 -k 15 -c 13 -h 1
cfg-hw-display -t SPI -d SSD1322 -w 256 -h 64 --cs=5 --reset=22

cfg-hw-spi -d 19 -k 18 -c 21 -h 1 [and 2]
cfg-hw-display -t SPI -d SSD1322 -w 256 -h 64 --cs=5 --reset=22

13 and 15 are shared with other functions, selectable by DIP switch. Documentation specific to this board seems to have disappeared from the internet. It is very reasonably priced though.

But can you send me the config stances you use with squeezelite-esp32?

[troffasky]

But can you send me the config stances you use with squeezelite-esp32?

Attached.

[philippe_44]

Attached.

I have to check what my simplified parser does, but "display_config": "SPI:width=256,height=64,cs=5,reset=22,speed=80000 00,driver=SSD1322", should be "display_config": "SPI,width=256,height=64,cs=5,reset=22,speed=8000000,dr iver=SSD1322". Can you capture the serial log when it boots? It will tell me if the configuration is properly taken into account. You just need either a terminal or "idf.py monitor" on the pseudo-COM, or use telnet

[troffasky]

I (2870) display: Trying to configure display with SPI:width=256,height=64,cs=5,reset=22,speed=8000000,driver=SSD1322
I (2980) SSD1322: SSD1322 with offset 28, page 8, iRAM 0x3ffc7104
I (2990) display: Display is SPI host 2 with cs:5
I (2990) gds: Adding line 1 at -3 (height:14)
I (2990) gds: Adding line 2 at 8 (height:24)

Running version: ESP32-A1S.552.master-cmake

[Harry1999]

this is, what i'm using spi with ESP32 Audio Kit V2.2 and an 0.96" OLED monochrom (only first 10 lines are yellow, the rest is blue)

fw: ESP32-A1S.552.master-cmake

spi_config: data=13,clk=15,dc=19,host=1
display_config: SPI:width=128,height=64,cs=12,reset=22,speed=80000 00,driver=SSD1306,HFlip,VFlip
DIP: off,off,off,on,on

[sle118]

I have to check what my simplified parser does, but "display_config": "SPI:width=256,height=64,cs=5,reset=22,speed=80000 00,driver=SSD1322", should be "display_config": "SPI,width=256,height=64,cs=5,reset=22,speed=8000000,dr iver=SSD1322". Can you capture the serial log when it boots? It will tell me if the configuration is properly taken into account. You just need either a terminal or "idf.py monitor" on the pseudo-COM, or use telnet

This is odd. It looks like an old bug that was fixed 4 months ago
https://github.com/sle118/squeezelit...cessors.c#L222