The Pi is also connected to the computer via a piUART cable which again provides power.
This means that I can connect to it in a few different ways:
- via SSH (with authentication keys).
- Using VNC, avoiding the SSH authentication.
- via the cable for when I tinker and break something network related (it happens a lot).
This is essentially my test rig and as such the OS is always up to date and the SD card has all of the necessary libraries and permissions needed.
The other night I left it all plugged in and closed the laptop lid, effectively putting the machine into ‘Suspend’ mode.
This meant that the Pi was powered by 2 sources; the official power supply, and power coming through the piUART cable.
I woke up to a dead Pi** and a fried motherboard***.
** / ***
** Yes, I have been through every possible test to see if the Pi is dead. It is.
*** Yes, the motherboard is fried, it has been disassembled, the immediately obvious blown components identified, and the board replaced.
My questions are:
- How is this even possible?
- Has there been some sort of weird power feedback from the Pi back in to the computer causing this?
- Is there any way of perforning an autopsy on the Zero? (@gadgetoid Do you want me to send this back so you can slice it open?)
This only happened since using the piUART cable, everything worked fine before introducing it into the testing setup.
I’m kind of nervous now about plugging the UART cable back in, as I don’t want to blow up a brand new Chromebook!
Any thoughts or insights greatly appreciated.