Sir, I had no success with your preconfigured image.
I have still the same issue. So it seems to be a hardware issue I guess.
As I already told, I checked the wires a couple of times and they are correctly connected.
Is it possible that the Controlblock got a short circuit?
Do you have any other solution/idea?
OK, this is probably my last post on this matter. It isn't solved, by any stretch of the imagination, but i do have a workaround!
I don't believe that the short has fried anything, the controlblock is still working exactly as advertised, but it DID scramble the outputs. All the outputs are still there, just in different places!
If it is possible to re-flash the firmware i think it would restore the normal operation, but that is just a hunch, and as it stands now i am not willing to take the risk.
Just in case someone out there ever has a similar problem i'm posting how i rewired the controlblock:
WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! WARNING!
THIS WON'T WORK ON YOUR SYSTEM, IT FIXED MY SYSTEM ONLY. I ONLY POST HERE TO SHOW WHAT THE SHORT DID TO MY CONTROLBLOCK!
In the end i rewired my project to match the new outputs of the scrambled Controlblock as follows:!
Hope that helps, if anyone else finds themself in a similar situation!
END WARNING! END WARNING! END WARNING! END WARNING! END WARNING! END WARNING! END WARNING! END WARNING!
Maybe you did not install the USB HID quirks for Raspbian? It is a known issue with the older Linux kernels and is described here in the section "Installing USB HID Quirks for the GamepadBlock" at https://blog.petrockblock.com/2017/10/10/tutorial-gamepadblock-raspbian/.
Doh, OK, re-running the script after rebooting fixed it. I must not have rebooted since updating the kernel version. Now I can run jstest /dev/input/js0and see the buttons work as well as shutdown view soft power switch and see LED indicate status.
I'm not sure if this post will be useful to others, but one never knows. In any case, the process of writing it out probably helped me figure out what went wrong.
@grant2258 Thanks for sharing your experiences. I didn't take the percentage as a factual statement, so I understood you quite right. :) I like bat tops more, so it's good that we have free choice in that matter. I agree that not every solution is for everyone, so I welcome alternatives from others as I like to give them myself. Cheers.
I don’t know the exact pi out of the pi2scart, but you can find the used pins of the PowerBlock at https://blog.petrockblock.com/powerblock-raspberry-pi-power-switch/:
S1: pin 12
S2: pin 11
If this does not collide with the pi2scart, it should work.
I have just pushed an update for the ControlBlock driver. You can now connect a button to P2, "A": Pressing that button will lead to a simulated press of Start + B, as well as a keyboard button press of "F1".
Does this work for you?
You mean you need a tutorial for updating or reinstalling the PowerBlock driver, right?
What you could try is to run
wget -O - https://raw.githubusercontent.com/petrockblog/PowerBlock/master/install.sh | sudo bash
from the command line to execute the auto-install routine of the PowerBlock driver (as described at https://github.com/petrockblog/PowerBlock#quick-installation). Maybe that solves your issue?
Can you post the output here?
I just checked the installation script with the current RetroPie image and everything went fine for me. I have also added a screencast that shows the console output for the installation. You can find it in the "Videos" section at https://blog.petrockblock.com/powerblock-raspberry-pi-power-switch/.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.