@mitu It's the Retropie 4.5 image, fully updated as of the 18th.

@petrockblog Well, right now it is only my assumption that the power supply in combination with the powerstrip and other power supplies causes the problem. If you are interested in further investigations, I can send back the problematic PowerBlocks, or I could do a few simple measurements. Being a beta tester would be fine, I am used to work with hardware/software in development status. However, it depends on the timeframe as I have have an eye on an alternative solution. But if we talk about one, two, three months, I would be glad in acting as beta tester.

After some more trail and error I got it to work by re-installing libc6 and libc6-dev, then doing the manual wiringpi install and then the manual powerblock install.

@superpie3k Thanks for your responses. I was away on vacation and only just got back to this. I had the same experience as above. "Had to install wiringpi manually, and to execute steps from https://github.com/petrockblog/PowerBlock manually. Seems to be a version mismatch with library wiringpi." But I got it working now.

Good to hear all is working well! I still need to buy a Pi 4 so it will take some time for testing it out.. Thanks for the support!

So, I have mounted the PowerBlock and I have tested it for some days. It works almost as expected, spordically it shows unexpected behaviour. I will create a separate thread explaining my observations. Anyway, thanks for supplying me with a replacement device.

Edit: So as to what mitu and the others spoke of, I feel so dumb. Like I said earlier, I was able to boot into noobs just fine, and I had raspbian full installed at the same time as my retropie. I tried accessing the files for retropie that way earlier to see if I could recover my retropie or change configs or remove powerblock drivers, etc... But the issue I had was nothing showed up under the Raspbian desktop file manager earlier. I reinstalled everything after having lost it all earlier, and when I reset up my raspbian desktop just now, I got a link for retropie on the desktop. GO FIGURE, it only showed up after updating and rebooting raspbian desktop.... Since i rarely ever use the desktop os and mainly only ever use retropie, it didnt cross my mind to try updating and rebooting raspbian and see if I could access those files again. So to reiterate, as the others have mentioned if anyone ever stumbles across this and is in the boat I was in, if you're lucky enough to have raspbian installed as well as your retropi, you CAN access your retropie files and fix the mess as mitu said. Hopefully this saves someone else 6hrs+ of recovering lol.

Hello Florian, I just wanted to share that I have managed to swap the cooked component for a new one, and it’s fixed the powerblock back to working order. Thanks for your help. Managed to desolder the old one with some flux, desolder wick and some patience. Getting the new one in was easier than expected.

That looks like it would do the trick, but it also looks like a daunting endeavor. I'd have to modify the design to work in my case with a full size NES case. All those mini jump wires between contacts is going to suck for me too. Plus I have no idea what those other parts (diode, resistor, capacitor, etc) are used for. I wish I knew more about electronic circuits. That's why I liked the Mausberry circuit so much, plug in, put the wires where they need to go, and you're done (after getting the script obviously). The PowerBlock was useful too because you just attach it to the GPIO pins. I still think doing something like the Mausberry would work best, but I'm not sure if they can support the amps. Waiting for them to reply.

From: https://blog.petrockblock.com/powerblock-raspberry-pi-power-switch/

Do you maybe have the micro-USB connector attached to the Raspberry Pi or the PowerBlock? It needs to be attached to the PowerBlock. Could you send me a photo of your hardware setup? Can you tell me which version of RetroPie and which version of the Raspberry Pi you are using? I could try to reproduce the issue at my site.

Sorry or this late reply. Could you please contact me via email and send me your order number? I will make sure that you get a replacement!

If you power the RPi using the microUSB of the RPi itself you will loose the power switch and reset functions on the Powerblock. When the Powerblock is used as designed using its microUSB connector, power to the RPi is controlled by the Powerblock and routed to the Power and Ground pins of the GPIO connector. When the RPi is booted up the driver and control service of the Powerblock will initialy interrogate the status of the Powerblock board and intitiate the boot up process. If the microUSB on the RPi is used to as power source, all of this is bypassed and the RPi will power up as if the Powerblock does not exist. The only way to use microUSB on th RPi together with the Powerblock is to isolate the RPi's micrUSB connections from the RPi itself (cut the traces from the RPi) and rewire them to the Powerblock's microUSB connector. Doing so is a mute, waste of time, potentially damaging to the RPi exercise.

Never mind. Checked on Reddit and got a hit for the problem I believe. Just used the PowerBlock installer in the setup menu. Seemed to work at a glance.

I got everything working flawlessly with a different power supply: 5.2V, 3A. :)

Hi just a quick update to this. I never did find out what the issue was however I have just wiped the card and started again, and readded the crc shutdown code........ and it works a treat!. Many thanks

Hi ! It is misteriously back to normal working. Thanks for responding!

All right. I took a look into the sources of the ControlBlock driver. The same issue that caused the slow shutdown for the PowerBlock also existed there. I have fixed that now.

@douga as @tba mentioned, the scientific term is PEBKAC.