uklightman
Posts: 2
Joined: Tue Jan 10, 2012 11:52 pm

PiJuice problems with new Raspi 3+

Thu Mar 22, 2018 9:45 pm

My PiJuice has managed to brick my new Raspberry Pi 3+. I am not at all happy, and do not have the confidence to try it on another!

Has this happened to anyone else?

User avatar
DougieLawson
Posts: 41971
Joined: Sun Jun 16, 2013 11:19 pm
Location: A small cave in deepest darkest Basingstoke, UK
Contact: Website Twitter

Re: The PiJuice has bricked my new Raspi 3+

Thu Mar 22, 2018 9:56 pm

You can't "brick" any Raspberry Pi. There's nothing to "brick". You can destroy the hardware by GPIO pin abuse.

Does any part get hot very quickly?
Have you tried burning a fresh SDCard with Raspbian 2018-03-13?
Languages using left-hand whitespace for syntax are ridiculous

DMs sent on Twitter/LinkedIn will be answered next month.
Fake doctors - are all on my foes list.

The use of crystal balls and mind reading is prohibited.

User avatar
Pi Supply
Posts: 13
Joined: Wed Dec 14, 2016 10:39 am
Location: UK
Contact: Website

Re: The PiJuice has bricked my new Raspi 3+

Fri Mar 23, 2018 9:57 am

Sorry to hear that you are having trouble with your PiJuice, however what you describe is unlikely if not impossible. As Dougie says there is nothing to "brick" on the Pi.

Can you actually describe in more detail what the issue you have is?

And before posting inflammatory titles suggesting our product has bricked your Pi it would be great next time if you could actually ask for help first and confirm that is the case. We do have official support channels including on out GitHub page https://github.com/PiSupply/PiJuice
Pi Supply - The Maker Emporium!
https://www.pi-supply.com

jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 30440
Joined: Sat Jul 30, 2011 7:41 pm

Re: The PiJuice has bricked my new Raspi 3+

Fri Mar 23, 2018 10:54 am

I've changed the title to be less inflammatory.
Principal Software Engineer at Raspberry Pi Ltd.
Working in the Applications Team.

Return to “Troubleshooting”