-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Under-voltage detection (bad power supplies and USB cables) #16
Comments
Sounds like something which sound be done in mainline U-Boot. Also i am not sure if it is really worth the efford. After all the board works fine when powered properly. |
Yes, people having decent power supplies and cables should have no problems. It's just that the Pine64 kickstarter campaign advertised that As for the mainline support, the PMIC support will have to be implemented eventually. |
So basically it's the wrong power connector combined with a marketing campaign raising wrong expectations? So it might be an option that the Pine64 folks ask for paid consultantcy or coding efforts to fix their mistakes? |
Good advice. That's what I thought was happening to me. Then, I was suspicious of my wall socket. Eh, it turns out that my 64GB SanDisk MicroSD was intermittently failing. Now 100% dead. Oiy vey! |
Some Pine64 users have bad power supplies or bad USB cables, so they experience reboots or some other stability issues.
As a quick and dirty temporary solution, it might be possible to read the voltage level from the PMIC (via the arisc mailbox interface), then do some simple CPU load testing in the U-Boot while gradually increasing the CPU clock frequency (utilizing more than one CPU core and NEON might be difficult though). If a significant voltage drop is detected, then boot at a low CPU clock frequency into some initrd image, which just shows something like
"Your power supply sucks, please fix this!"
message on the HDMI monitor and the UART serial console, then stops there.Also see:
The text was updated successfully, but these errors were encountered: