Fresh 3.3.2 install - Pedal interface stuck start/setup screen

[tothoseofus]

Hardware
pistomp 3
pi CM5 on waveshare mini base board A (https://www.waveshare.com/cm5-io-base-a.htm)
power directly into the pi with official power supply.

I've just done a fresh install with the new install system.
(Tried with the default install method (repositry) and also tried with pistompOS-3.3.2.img.xz image and the alternative install method.
It appeared to go well...
except the loading screen is upside down,
after loading pedalboard jumps straight to a white screen with a QR code and start / restore / setup at the bottom (restore greyed out). I can navigate between start and setup with the navigation encoder, but can not select either of them with any encoder button or footswitch.

Mod seems to be running fine, can access the web interface, sound works, changing pedalboards works through the web interface.
ssh is working.

restarted pistomp with ps-restart
while logging with
journalctl -u mod-ala-pi-stomp -f

Any ideas?
Was all working with 3.1.0

log below

Sep 09 12:58:39 pistomp python[2581]: INFO:root:Init modhandler
Sep 09 12:58:39 pistomp python[2581]: INFO:root:Using uvloop for WebSocket bridge
Sep 09 12:58:39 pistomp python[2581]: INFO:root:WebSocket worker started, connecting to ws://localhost:80/websocket
Sep 09 12:58:39 pistomp python[2581]: INFO:root:WebSocket bridge started
Sep 09 12:58:39 pistomp python[2581]: INFO:root:Init hardware: Pistompcore
Sep 09 12:58:39 pistomp python[2581]: INFO:root:WebSocket connected to ws://localhost:80/websocket
Sep 09 12:58:39 pistomp python[2581]: INFO:root:SPI 66.67 MHz requested, 50.00 MHz actual
Sep 09 12:58:39 pistomp python[2581]: ERROR:root:Initializing LED for footswitch 0: 'GPIO busy'
Sep 09 12:58:39 pistomp python[2581]: INFO:root:pi-Stomp Software Version (pkg): 3.3.2-0
Sep 09 12:58:39 pistomp python[2581]: INFO:root:Entering main loop. Press Control-C to exit.
Sep 09 12:59:39 pistomp python[2581]: INFO:root:WebSocket stats: sent=0, received=152, queue=0, peak_latency=1ms
Sep 09 12:59:41 pistomp python[2581]: INFO:root:Exit.
Sep 09 12:59:41 pistomp systemd[1]: Stopping mod-ala-pi-stomp.service - MOD-ALA-PI-STOMP...
Sep 09 12:59:41 pistomp python[2581]: INFO:root:External MIDI manager closed
Sep 09 12:59:41 pistomp python[2581]: INFO:root:WebSocket worker stopped
Sep 09 12:59:41 pistomp python[2581]: INFO:root:WebSocket bridge stopped
Sep 09 12:59:41 pistomp python[2581]: INFO:root:Completed cleanup
Sep 09 12:59:41 pistomp python[2581]: pygame-ce 2.5.7 (SDL 2.32.10, Python 3.13.5)
Sep 09 12:59:41 pistomp systemd[1]: mod-ala-pi-stomp.service: Deactivated successfully.
Sep 09 12:59:41 pistomp systemd[1]: Stopped mod-ala-pi-stomp.service - MOD-ALA-PI-STOMP.
Sep 09 12:59:41 pistomp systemd[1]: mod-ala-pi-stomp.service: Consumed 3.839s CPU time.
Sep 09 12:59:41 pistomp systemd[1]: Starting mod-ala-pi-stomp.service - MOD-ALA-PI-STOMP...
Sep 09 12:59:41 pistomp systemd[1]: Started mod-ala-pi-stomp.service - MOD-ALA-PI-STOMP.
Sep 09 12:59:42 pistomp python[2943]: INFO:root:restoring audio card settings from: /var/lib/alsa/asound.state
Sep 09 12:59:42 pistomp python[2943]: INFO:rtmidi.midiutil:Opening MIDI output port #0 (Midi Through:Midi Through Port-0 14:0).
Sep 09 12:59:42 pistomp python[2943]: INFO:root:Init modhandler
Sep 09 12:59:42 pistomp python[2943]: INFO:root:Using uvloop for WebSocket bridge
Sep 09 12:59:42 pistomp python[2943]: INFO:root:WebSocket worker started, connecting to ws://localhost:80/websocket
Sep 09 12:59:42 pistomp python[2943]: INFO:root:WebSocket bridge started
Sep 09 12:59:42 pistomp python[2943]: INFO:root:Init hardware: Pistompcore
Sep 09 12:59:42 pistomp python[2943]: INFO:root:WebSocket connected to ws://localhost:80/websocket
Sep 09 12:59:42 pistomp python[2943]: INFO:root:SPI 66.67 MHz requested, 50.00 MHz actual
Sep 09 12:59:42 pistomp python[2943]: ERROR:root:Initializing LED for footswitch 0: 'GPIO busy'
Sep 09 12:59:42 pistomp python[2943]: INFO:root:pi-Stomp Software Version (pkg): 3.3.2-0
Sep 09 12:59:42 pistomp python[2943]: INFO:root:Entering main loop. Press Control-C to exit.
Sep 09 13:00:42 pistomp python[2943]: INFO:root:WebSocket stats: sent=0, received=153, queue=0, peak_latency=1ms
Sep 09 13:01:42 pistomp python[2943]: INFO:root:WebSocket stats: sent=0, received=72, queue=0, peak_latency=1ms

[tothoseofus]

Tried to install 3.3.0 image same result.
Reverted to 3.1.0 now working

[rreichenbach]

Your log shows:
INFO:root:Init hardware: Pistompcore

pistompcore (v2) inverts the screen compared to v3.

Pretty sure this code:
https://github.com/TreeFallSound/pi-gen-pistomp/blob/main/stage2/05-pistomp/files/firstboot.sh#L203

is not dealing with your cm5 correctly, because it's looking for 'Pi 5'. It should probably also check for 'Compute Module 5' or some similar identifier.

I don't have a CM5. Can you try running this to see if it returns anything?
grep -q 'Compute Module 5' /proc/device-tree/model

[tothoseofus]

Just did it on the 3.1.0 install.
grep -q 'Compute Module 5' /proc/device-tree/model
returns nothing, but that's expected with the -q

grep 'Compute Module 5' /proc/device-tree/model
returns grep: /proc/device-tree/model: binary file matches

and cat /proc/device-tree/model
returns Raspberry Pi Compute Module 5 Rev 1.0

Hope this helps.

Edit, looked further down

cat /proc/cpuinfo
returns

processor       : 0
BogoMIPS        : 108.00
Features        : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer : 0x41
CPU architecture: 8
CPU variant     : 0x4
CPU part        : 0xd0b
CPU revision    : 1

processor       : 1
BogoMIPS        : 108.00
Features        : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer : 0x41
CPU architecture: 8
CPU variant     : 0x4
CPU part        : 0xd0b
CPU revision    : 1

processor       : 2
BogoMIPS        : 108.00
Features        : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer : 0x41
CPU architecture: 8
CPU variant     : 0x4
CPU part        : 0xd0b
CPU revision    : 1

processor       : 3
BogoMIPS        : 108.00
Features        : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
CPU implementer : 0x41
CPU architecture: 8
CPU variant     : 0x4
CPU part        : 0xd0b
CPU revision    : 1

Revision        : c04180
Serial          : e1054e27188605fb
Model           : Raspberry Pi Compute Module 5 Rev 1.0

[tothoseofus]

UPDATE:
I re-flashed the cm5 with the repositry install method.

I replaced

# Hardware version: Pi 5 = v3 (pi-Stomp Tre), Pi 3/4 = v2 (pi-Stomp Core).
# v1 is no longer supported.
if grep -q 'Pi 5' /proc/device-tree/model 2>/dev/null; then
    runuser -u pistomp -- /home/pistomp/pi-stomp/util/modify_version.sh 3.0 || true
else
    runuser -u pistomp -- /home/pistomp/pi-stomp/util/modify_version.sh 2.0 || true
fi

with

# Hardware version: v2 (pi-Stomp Core) = Pi 3/4/CM4 and other older/smaller Pis.
# v3 (pi-Stomp Tre) = anything newer (Pi 5, CM5, Pi 500, future models).
# v1 is no longer supported.
if grep -qE 'Raspberry Pi ([234]|Zero|Compute Module [34])' /proc/device-tree/model 2>/dev/null; then
    version=2.0
else
    version=3.0
fi
runuser -u pistomp -- /home/pistomp/pi-stomp/util/modify_version.sh "$version" || true

also removed the if statement around the eeprom update line
runuser -u pistomp -- /home/pistomp/pi-stomp/util/pi5_eeprom_update.sh || true

It seems to be working now.

Loading screen is still upside down

Came to the white screen with the QR code and start / restore / setup
I could select start this time. Footswitches and encoders appear to be working

Shutdown screen is still upside down.
Shuts down to a white screen.

ps-restart log gives me this now.

Sep 21 16:23:44 pistomp python[1071]: INFO:root:Exit.
Sep 21 16:23:44 pistomp systemd[1]: Stopping mod-ala-pi-stomp.service - MOD-ALA-PI-STOMP...
Sep 21 16:23:44 pistomp python[1071]: INFO:root:External MIDI manager closed
Sep 21 16:23:44 pistomp python[1071]: INFO:root:WebSocket worker stopped
Sep 21 16:23:44 pistomp python[1071]: INFO:root:WebSocket bridge stopped
Sep 21 16:23:44 pistomp python[1071]: INFO:root:Completed cleanup
Sep 21 16:23:44 pistomp python[1071]: pygame-ce 2.5.7 (SDL 2.32.10, Python 3.13.5)
Sep 21 16:23:44 pistomp systemd[1]: mod-ala-pi-stomp.service: Deactivated successfully.
Sep 21 16:23:44 pistomp systemd[1]: Stopped mod-ala-pi-stomp.service - MOD-ALA-PI-STOMP.
Sep 21 16:23:44 pistomp systemd[1]: mod-ala-pi-stomp.service: Consumed 9.855s CPU time.
Sep 21 16:23:44 pistomp systemd[1]: Starting mod-ala-pi-stomp.service - MOD-ALA-PI-STOMP...
Sep 21 16:23:44 pistomp systemd[1]: Started mod-ala-pi-stomp.service - MOD-ALA-PI-STOMP.
Sep 21 16:23:45 pistomp python[2150]: INFO:root:restoring audio card settings from: /var/lib/alsa/asound.state
Sep 21 16:23:45 pistomp python[2150]: INFO:rtmidi.midiutil:Opening MIDI output port #0 (Midi Through:Midi Through Port-0 14:0).
Sep 21 16:23:45 pistomp python[2150]: INFO:root:Init modhandler
Sep 21 16:23:45 pistomp python[2150]: INFO:root:Using uvloop for WebSocket bridge
Sep 21 16:23:45 pistomp python[2150]: INFO:root:WebSocket worker started, connecting to ws://localhost:80/websocket
Sep 21 16:23:45 pistomp python[2150]: INFO:root:WebSocket bridge started
Sep 21 16:23:45 pistomp python[2150]: INFO:root:Init hardware: Pistomptre
Sep 21 16:23:45 pistomp python[2150]: INFO:root:WebSocket connected to ws://localhost:80/websocket
Sep 21 16:23:45 pistomp python[2150]: INFO:root:Bound volume encoder to audio parameter: Output Volume
Sep 21 16:23:45 pistomp python[2150]: INFO:root:Bound volume encoder to audio parameter: Output Volume
Sep 21 16:23:45 pistomp python[2150]: INFO:root:pi-Stomp Software Version (pkg): 3.3.2-0
Sep 21 16:23:45 pistomp python[2150]: INFO:root:Entering main loop. Press Control-C to exit.

[tothoseofus]

New edit
if I have POWER_OFF_ON_HALT=0
then the screen stays on the safe to shutdown screen.

Which should be the appropriate desired behaviour?

[rreichenbach]

It's your preference to have POWER_OFF_ON_HALT set to 1 or 0. Just know that regardless, it won't cut power to the other pi-Stomp hardware (LCD, etc.). That requires physically cutting power.

Regarding the flipped boot and shutdown screens, thanks for pointing that out. I forgot that code does it's own rpi model check:
https://github.com/TreeFallSound/pi-gen-pistomp/blob/67bc86c8951e7f58430982260745d4d37ac5a7bd/debpkgs/lcd-splash/src/lcd-splash.c#L134

That's C code so requires a compile step. We'll get that fixed in the next release, likely this week.

[tothoseofus]

Thanks for all of your help.
Feel free to mark this as closed when you are ready.

[rreichenbach]

This should be resolved in the 3.3.3 release.