-
Notifications
You must be signed in to change notification settings - Fork 15
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
MoPi/simbamon power button bit set on boot #63
Comments
Actually, my hack is not reliable. It appears that I am seeing the bit becoming set after first read as well:
I swear that I'm not going anywhere near the power button! |
Interesting. I just had the power button flag set itself spontaneously while the Pi was running. Right after I switched the CPU frequency governor! Could a change in CPU frequency be upsetting the i2c code and causing it to misread data? Or does the MoPi have any firmware hackery for simulating a power button press in overcurrent conditions or something? I currently under-clock the Pi A+ after boot is complete using a set of low |
In development we saw glitching on the i2c bus quite frequently, which lead To fix it, the python communication code did something like multiple calls I suspect what you're seeing is glitching that is a similar process, A possible workaround might be to do multiple reads in the simbamond code; Sorry not to be more definite! Nasty problem to debug :-( h On 13 October 2015 at 17:15, Jonathan Hogg [email protected] wrote:
Hamish Cunningham |
Ta for this. It would seem to match what I'm seeing. I think I may ditch I'll leave this issue open in case it's something that you want to think about; feel free to close if you don't think there's anything useful you can do. |
Thank Jonathan, that sounds like a good solution :-) |
I'm getting three different MoPis (an original Kickstarter one and two recently purchased) causing issues on boot with a RaspberryPi A+. The issue is that
simbamon
reports that the power button has been pressed as it starts up, causing it to tellinit
to halt the system.The A+ is running a variant of Raspbian (wheezy), a custom kernel build (3.18.16+aufs3) and the version of simbamon included in Raspbian (no obvious version number in the script).
Example boot log after applying power and then pressing the power button until the LEDs light up:
My current hack is to read the status in
simbamon
in theif [ -z "$PREVIOUSLY_RUN" ]
block and wait 30 seconds if the shutdown bit is set. This seems to mostly make the problem go away as the next time that it reads the status, that bit isn't set anymore.The text was updated successfully, but these errors were encountered: