No 3 second soft power down with picade hat


#1

So I just wired power button up and downloaded the picade software. The power button works great to turn on the system but no matter how long I hold the button down, there is no response.
I would assume this is due to a problem with the monitoring part of the picade software?

I am running a Pi2 powered by a 3.7v 6600 battery and a powerboost 1000c.

I have power running into the picade hat, not the pi.

I am running the newest Retropie image install with 4.9 kernel.

Thanks


#2

Are the rest of the controls working?

Is there anything running that might interfere with BCM 17?


#3

Good question. I didn’t hook up the rest of the buttons yet so I can try that.

I am running a Waveshare pitft but only through HDMI. I installed the overlay using the info here

Other than that, no. I can test other buttons and reply again.


#4

This screen, https://www.waveshare.com/3.2inch-rpi-lcd-b.htm
If yes that uses the GPIO not HDMI?


#5

No I am using the 4" TFT with HDMI not connected to gpio only through the hdmi port.


#6

Ok, thanks for confirming that, just wanted to make sure.


#7

Okay so I wired up a button to button 1 and Emulation Station does not seem to recognize it when I try and set up the controller. I have the USB keyboard still plugged in, is that a problem? It will still detect the keyboard but apparently not the button on the hat.
I also tried reinstalling the software but the same results.
So right now I have power button hooked up, speaker hooked up and the 1 button hooked up. The power button still boots the system fine, and I do get sound from the speaker, but ES does not seem to recognize the button press on the HAT and I still can not shutdown.

Thanks


#8

That means the input script isn’t running, or something’s gone awry with it.

Try running: cat /var/run/picadehatd.log

Or running systemctl status picadehatd


#9

The first command didn’t seem to work. The second did. Looks like it’s running but still no luck on being recognized.


#10

This could mean the picadehatd script isn’t running.

Would be worth checking for it with ps aux | grep python

And seeing if /var/run/picadehatd.pid exists.

If it’s crashing on launch we might be able to find out why and get some debug output by running it directly:

picadehatd

#11

The file does exist. Running the program does not seem to do anything. Is there a way to generate a log when I run it?

pi@retropie:/var/run $ ls
avahi-daemon dhcpcd.sock mount sendsigs.omit.d thd.socket
blkid dhcpcd.unpriv.sock network shm tmpfiles.d
crond.pid dnsmasq ntpd.pid sshd udev
crond.reboot initctl picadehatd.pid sshd.pid user
dbus lock resolvconf sshwarn utmp
dhcpcd log rsyslogd.pid systemd
dhcpcd.pid machine-id samba thd.pid

pi@retropie:~ ps aux USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1 0.4 0.5 5356 3872 ? Ss 02:01 0:02 /sbin/init root 2 0.0 0.0 0 0 ? S 02:01 0:00 [kthreadd] root 3 0.0 0.0 0 0 ? S 02:01 0:00 [ksoftirqd/0] root 4 0.0 0.0 0 0 ? S 02:01 0:00 [kworker/0:0] root 5 0.0 0.0 0 0 ? S< 02:01 0:00 [kworker/0:0H] root 7 0.0 0.0 0 0 ? S 02:01 0:00 [rcu_sched] root 8 0.0 0.0 0 0 ? S 02:01 0:00 [rcu_bh] root 9 0.0 0.0 0 0 ? S 02:01 0:00 [migration/0] root 10 0.0 0.0 0 0 ? S< 02:01 0:00 [lru-add-drain] root 11 0.0 0.0 0 0 ? S 02:01 0:00 [cpuhp/0] root 12 0.0 0.0 0 0 ? S 02:01 0:00 [cpuhp/1] root 13 0.0 0.0 0 0 ? S 02:01 0:00 [migration/1] root 14 0.0 0.0 0 0 ? S 02:01 0:00 [ksoftirqd/1] root 15 0.0 0.0 0 0 ? S 02:01 0:00 [kworker/1:0] root 16 0.0 0.0 0 0 ? S< 02:01 0:00 [kworker/1:0H] root 17 0.0 0.0 0 0 ? S 02:01 0:00 [cpuhp/2] root 18 0.0 0.0 0 0 ? S 02:01 0:00 [migration/2] root 19 0.0 0.0 0 0 ? S 02:01 0:00 [ksoftirqd/2] root 21 0.0 0.0 0 0 ? S< 02:01 0:00 [kworker/2:0H] root 22 0.0 0.0 0 0 ? S 02:01 0:00 [cpuhp/3] root 23 0.0 0.0 0 0 ? S 02:01 0:00 [migration/3] root 24 0.0 0.0 0 0 ? S 02:01 0:00 [ksoftirqd/3] root 26 0.0 0.0 0 0 ? S< 02:01 0:00 [kworker/3:0H] root 27 0.0 0.0 0 0 ? S 02:01 0:00 [kdevtmpfs] root 28 0.0 0.0 0 0 ? S< 02:01 0:00 [netns] root 29 0.0 0.0 0 0 ? S 02:01 0:00 [khungtaskd] root 30 0.0 0.0 0 0 ? S 02:01 0:00 [oom_reaper] root 31 0.0 0.0 0 0 ? S< 02:01 0:00 [writeback] root 32 0.0 0.0 0 0 ? S 02:01 0:00 [kcompactd0] root 33 0.0 0.0 0 0 ? S< 02:01 0:00 [crypto] root 34 0.0 0.0 0 0 ? S< 02:01 0:00 [bioset] root 35 0.0 0.0 0 0 ? S< 02:01 0:00 [kblockd] root 36 0.0 0.0 0 0 ? S< 02:01 0:00 [watchdogd] root 37 0.0 0.0 0 0 ? S 02:01 0:00 [kworker/0:1] root 38 0.0 0.0 0 0 ? S< 02:01 0:00 [rpciod] root 39 0.0 0.0 0 0 ? S< 02:01 0:00 [xprtiod] root 40 0.0 0.0 0 0 ? S 02:01 0:00 [kswapd0] root 41 0.0 0.0 0 0 ? S< 02:01 0:00 [vmstat] root 42 0.0 0.0 0 0 ? S< 02:01 0:00 [nfsiod] root 52 0.0 0.0 0 0 ? S< 02:01 0:00 [kthrotld] root 53 0.0 0.0 0 0 ? S< 02:01 0:00 [bioset] root 54 0.0 0.0 0 0 ? S< 02:01 0:00 [bioset] root 55 0.0 0.0 0 0 ? S< 02:01 0:00 [bioset] root 56 0.0 0.0 0 0 ? S< 02:01 0:00 [bioset] root 57 0.0 0.0 0 0 ? S< 02:01 0:00 [bioset] root 58 0.0 0.0 0 0 ? S< 02:01 0:00 [bioset] root 59 0.0 0.0 0 0 ? S< 02:01 0:00 [bioset] root 60 0.0 0.0 0 0 ? S< 02:01 0:00 [bioset] root 61 0.0 0.0 0 0 ? S< 02:01 0:00 [bioset] root 62 0.0 0.0 0 0 ? S< 02:01 0:00 [bioset] root 63 0.0 0.0 0 0 ? S< 02:01 0:00 [bioset] root 64 0.0 0.0 0 0 ? S< 02:01 0:00 [bioset] root 65 0.0 0.0 0 0 ? S< 02:01 0:00 [bioset] root 66 0.0 0.0 0 0 ? S< 02:01 0:00 [bioset] root 67 0.0 0.0 0 0 ? S< 02:01 0:00 [bioset] root 68 0.0 0.0 0 0 ? S< 02:01 0:00 [bioset] root 69 0.0 0.0 0 0 ? S< 02:01 0:00 [bioset] root 70 0.0 0.0 0 0 ? S< 02:01 0:00 [bioset] root 71 0.0 0.0 0 0 ? S< 02:01 0:00 [bioset] root 72 0.0 0.0 0 0 ? S< 02:01 0:00 [bioset] root 73 0.0 0.0 0 0 ? S< 02:01 0:00 [bioset] root 74 0.0 0.0 0 0 ? S< 02:01 0:00 [bioset] root 75 0.0 0.0 0 0 ? S< 02:01 0:00 [bioset] root 76 0.0 0.0 0 0 ? S< 02:01 0:00 [bioset] root 77 0.0 0.0 0 0 ? S< 02:01 0:00 [iscsi_eh] root 78 0.0 0.0 0 0 ? S< 02:01 0:00 [dwc_otg] root 79 0.0 0.0 0 0 ? S 02:01 0:00 [kworker/2:1] root 80 0.0 0.0 0 0 ? S< 02:01 0:00 [DWC Notificati root 81 0.1 0.0 0 0 ? S< 02:01 0:00 [VCHIQ-0] root 82 0.0 0.0 0 0 ? S< 02:01 0:00 [VCHIQr-0] root 83 0.0 0.0 0 0 ? S< 02:01 0:00 [VCHIQs-0] root 84 0.0 0.0 0 0 ? S 02:01 0:00 [VCHIQka-0] root 85 0.0 0.0 0 0 ? S< 02:01 0:00 [SMIO] root 86 0.0 0.0 0 0 ? S 02:01 0:00 [kworker/2:2] root 87 0.0 0.0 0 0 ? S 02:01 0:00 [kworker/3:1] root 88 0.0 0.0 0 0 ? S< 02:01 0:00 [bioset] root 89 0.0 0.0 0 0 ? S 02:01 0:00 [mmcqd/0] root 91 0.0 0.0 0 0 ? S 02:01 0:00 [jbd2/mmcblk0p2 root 92 0.0 0.0 0 0 ? S< 02:01 0:00 [ext4-rsv-conve root 93 0.5 0.0 0 0 ? D 02:01 0:03 [kworker/1:1] root 94 0.0 0.0 0 0 ? S< 02:01 0:00 [ipv6_addrconf] root 113 0.0 0.0 0 0 ? S 02:01 0:00 [kworker/u8:1] root 137 0.2 0.0 0 0 ? S 02:01 0:01 [kworker/0:2] root 146 0.1 0.0 0 0 ? S 02:01 0:00 [kworker/3:2] root 147 0.0 0.3 11640 2992 ? Ss 02:01 0:00 /lib/systemd/sy root 152 0.0 0.3 8708 2552 ? Ss 02:01 0:00 /lib/systemd/sy root 224 0.0 0.0 0 0 ? S 02:01 0:00 [spi0] root 229 0.0 0.0 0 0 ? S 02:01 0:00 [irq/183-ads784 root 230 0.0 0.0 0 0 ? S 02:01 0:00 [kworker/u8:2] root 408 0.0 0.3 5068 2356 ? Ss 02:02 0:00 /usr/sbin/cron root 409 0.0 0.3 32140 2632 ? Ssl 02:02 0:00 /usr/sbin/rsysl avahi 410 0.1 0.3 4004 2420 ? Ss 02:02 0:00 avahi-daemon: r root 412 0.0 0.2 3392 2124 ? Ss 02:02 0:00 /lib/systemd/sy message+ 413 0.0 0.4 5488 3060 ? Ss 02:02 0:00 /usr/bin/dbus-d avahi 415 0.0 0.0 3872 244 ? S 02:02 0:00 avahi-daemon: c root 416 0.0 0.0 0 0 ? S< 02:02 0:00 [cfg80211] nobody 473 0.0 0.1 2288 1448 ? Ss 02:02 0:00 /usr/sbin/thd - root 550 0.0 0.2 2560 1700 ? Ss 02:02 0:00 /sbin/dhcpcd -q root 551 0.0 0.5 7860 4308 ? Ss 02:02 0:00 /usr/sbin/sshd root 560 0.5 0.2 36576 1856 ? Dl 02:02 0:02 /usr/local/bin/ root 587 0.0 0.3 5216 2472 tty1 Ss 02:02 0:00 /bin/login -f root 588 0.0 0.2 3868 1924 ? Ss+ 02:02 0:00 /sbin/agetty -- ntp 589 0.0 0.4 5684 3708 ? Ss 02:02 0:00 /usr/sbin/ntpd root 601 0.0 0.0 0 0 ? S< 02:02 0:00 [kworker/3:1H] root 602 0.0 0.0 0 0 ? S< 02:02 0:00 [kworker/2:1H] root 603 0.0 0.5 22500 4372 ? Ss 02:02 0:00 /usr/sbin/nmbd root 614 0.0 1.6 35676 12572 ? Ss 02:02 0:00 /usr/sbin/smbd root 622 0.0 0.6 35676 4896 ? S 02:02 0:00 /usr/sbin/smbd pi 628 0.0 0.5 6320 4276 tty1 S+ 02:02 0:00 -bash root 930 0.0 0.6 11548 4884 ? Ss 02:06 0:00 sshd: pi [priv] pi 936 0.0 0.4 11548 3428 ? R 02:06 0:00 sshd: pi@pts/0 pi 938 0.1 0.5 6252 4256 pts/0 Ss 02:06 0:00 -bash root 1031 0.0 0.0 0 0 ? S 02:07 0:00 [kworker/1:2] root 1033 0.0 0.0 0 0 ? S 02:07 0:00 [kworker/2:0] pi 1100 0.0 0.2 4736 2108 pts/0 R+ 02:10 0:00 ps aux pi@retropie:~ ps aux | grep python
pi 1103 0.0 0.2 4272 1908 pts/0 S+ 02:12 0:00 grep --color=auto python
pi@retropie:~ $


#12

picadehatd should be in /usr/bin/picadehatd


#13

Yes it is. It does nothing when I type in picadehatd
no errors, just appears to do nothing pauses for a half second.

Also I now seem to be getting a error when launching games Volume Control init () failed to find sound mixer

Also I still have sound with the speaker hooked up to the picade hat


#14

I set this up on a fresh RetroPie image yesterday with no trouble, so I suspect something must have gone wrong during the install process. Simply running it again might fix the problem:

curl -sS https://get.pimoroni.com/picadehat | bash

Let me know if that does/doesn’t help.


#15

23 AM

Does it matter if I had already run emulation station and setup my keyboard as a controller before installing the hat?

No improvement from reinstalling.


#16

I was able to run the cat /var/log/picadehatd.log
here are the results.

I did this through SSH connection without exiting from ES first (as I had previously done)

55 AM

I also tried to run SHOWKEY and got this
pi@retropie:/ $ showkey
Couldn’t get a file descriptor referring to the console


#17

What happens if you: sudo modprobe uinput?

Does /dev/uinput exist?


#18

43 AM


#19

Worth checking the contents of /dev after running sudo modprobe uinput, and also any recent output from dmesg which will tell you if uinput has failed for some reason.

It shouldn’t matter if you’ve already configured EmulationStation, although it will make it tricky to reconfigure to match the Picade HAT key bindings.

At this point I’d probably have reflashed to the latest version of RetroPie and started from scratch- but there doesn’t seem to be much wrong with your setup apart from a missing /dev/uinput which is one of the first things the picadehatd tries to set up: https://github.com/pimoroni/picade-hat/blob/master/daemon/usr/bin/picadehatd#L28


#20

37 AM

Are you saying there should be more than one uinput is /dev? There is one.

Also, would this explain why the SOFT POWER down still is non-functional?