@loonyboi Thanks! I wasn't sure if you meant to mirror the controls by ES' UI or at file system level by copying their config files. So if I understand you correctly, setting them up identically in ES does suffice.
I guessed as much, just me beeing a linux n00b. Thanks and sorry for wasting your time. Still, this could have been prevented with clearer instructions. It went fine with installing the software though, nice and easy to copy the commands, all clear there. Just small things like this one that you who know command line better maybe don’t realize that others don’t get.. Thanks again.
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.