Have I fried my Controlblock (or Pi5)?

StuMcBill

So. I had my Pi5 setup and working with my ControlBlock, but I was concerned that the bottom of the ControlBlock was very close to my metal fan on my Pi5, and that something would short out?

I bought one of these: https://shop.pimoroni.com/products/40-pin-gpio-extension-cable

With the intention of putting some space between the GPIO pins and the Pi. I tried it today, and the pi would only turn on via the ControlBlock and wouldn’t turn off.

Is it possible that I plugged the ControlBlock into the cable and / or pi incorrectly and have fried something? Or has my configuration just got messed up somehow and starting again would sort it out?

Thanks

Edit, I should also have said that I plugged back in directly and got the same response.

I’m just going to try it again on my pi4, try and rule out the controlblock.

StuMcBill

@StuMcBill

Same behaviour on my Pi4. Have I fried my controlblock?

I do have an older micro-USB version, can I use that with the Pi5, or would it need to be a USB-C version?

StuMcBill

@StuMcBill just for some more info, I tried reconnecting to my Pi5 without the fan attached and I get the same result. I think I’ve fried something. I should also say, the control section of the controlblock still works great. No issues with the controls.

Unless there is something I can salvage, I see my options are as follows:

*Utilise my Micro-USB version (unsure if this would work with the power requirements of a Raspberry Pi5)

*Buy a powerblock and use that as my power management, using my IPac-2 that I already have as button management. Looking at the pictures I think this would avoid the potential interference from the Pi5 fan?

*Buy another USB-C ControlBlock.

Tagging @petrockblog for info

StuMcBill

Sorry for spamming the forum, could I just do this, and leave the ControlBlock purely doing the Joysticks and Buttons?

Would this work with the A1Up switch?

StuMcBill

@StuMcBill said in Have I fried my Controlblock (or Pi5)?:

Sorry for spamming the forum, could I just do this, and leave the ControlBlock purely doing the Joysticks and Buttons?

Would this work with the A1Up switch?

This doesn’t work with the A1Up switch, looks like it needs to be momentary.

petrockblog

@StuMcBill If the Pi does not respond to a power button event, I would look for

The connection between the button and the ControlBlock: Do you see the same behavior with another button or, for example, just by using jumper wires like most simple buttons?
The ControlBlock service installation: Does the ControlBlock LED stop pulsing and switch to a steady on state after booting? If not, the ControlBlock service is not running properly for some reason.
The ControlBlock configuration: This is rare, but sometimes the power switch functionality is not enabled in the ControlBlock configuration in /etc/controlblockconfig.cfg.

Perhaps these items will give you a clue as to what is causing your observation?

StuMcBill

@petrockblog said in Have I fried my Controlblock (or Pi5)?:

@StuMcBill If the Pi does not respond to a power button event, I would look for

The connection between the button and the ControlBlock: Do you see the same behavior with another button or, for example, just by using jumper wires like most simple buttons?

The ControlBlock service installation: Does the ControlBlock LED stop pulsing and switch to a steady on state after booting? If not, the ControlBlock service is not running properly for some reason.

The ControlBlock configuration: This is rare, but sometimes the power switch functionality is not enabled in the ControlBlock configuration in /etc/controlblockconfig.cfg.

Perhaps these items will give you a clue as to what is causing your observation?

Hi,

Thanks for the response.

I've not tried this, however, I have tried directly connected to GPIO of my Pi5 and my Pi4 - same behaviour - Controls work, but Power doesn't.
I will check this
I have tried toggling on and off in controlblock configuration - no change

I'll report back.