@SacGyver Without a schematic, we don't know what's driving the LED. I do not think it's connected directly to a Pi GPIO pin but maybe from the microcontroller on the ControlBlock or a transistor circuit driven by the microcontroller.
@petrockblog The reset button function is dependent upon unused or unconnected control I/O connection on the ControlBlock. However this does not make it universal for all build scenario since some build like "arcade" and "mame" uses all I/O connections.
I know that the ControlBlock uses a microcontroller(MCU). Since it is not open-source I do not know whether there are available connections to the MCU that you can use as terminal connection, like the power switch, for the reset button. This will make the function more universal for all users. Perhaps a redesign of the board (ControlBlock 3?) to use a larger MCU and use quick connect/release connector for the game buttons as well (the terminal block is a pain to use).
@ortsac Ah! That makes sense! I believe my issue, then, is that I need a proper power supply. I assumed incorrectly that a 5V 4A phone charger would work, but I guess not. So far the best power supply I've used on it was the Surface 3 charger. It seems stable most of the time, but when I get to intensive tasks, I get the yellow lightning bolt. That's only like 2.5A or something like that. Will look into a better power supply, thanks!
Powerblock works fine on Retropie/Raspbian. Open/LibreELEC are embedded systems so if it doesnt work OOTB, it is generaly a pain in the ass to make it work. The support for it should be given by them if they are interested.
Which RPi are you using? Which ControlBlock revision?
Are you overclocking the RPI? The driver is not tested with overclocked RPIs
Does this happen right after boot or only after some time?
Can you give mea description how I could reproduce that behavior?
As described at https://github.com/petrockblog/SNESDev-RPi#button-polling a shutdown command is issued when the button on the GPIO adapter is pressed five times. Maybe that signal is somehow inserted into the RPi when you connect your controller(s).
The dmesgcommand might give you some more insights into what the shutdown is causing.