Which is the output of the command cat /etc/version? If is different from weekly-159 please update to the last Yocto image, you can get it from here. Additionally, could you provide more information on the setup, hardware you are using and the connection under which you are getting this behavior?
>> cat /etc/version
The harwdare/software is described here:
PS: I live in Hillsboro and I would be happy to drop it off at the Intel site (JF or RA) for you to look at if you like.
I got same problem with the IoT kit Grove relay (open and close some times) or Grove buzzer (beep for several seconds).
In my scenario it happens also on "reboot" command. All IO pins changes their state. This is a problem if you have attached something that open a lock.
This problem doesn't happen if the power is turned off and on.
I'm very interested to know if it is possible to find a solution.
We tried it connecting it directly to the pin, without the Groove shield and we got the same behavior you are describing in pin 2, 3 and 13. Please try with any other pin, except with the ones previously mentioned and let us know the relay is still toggling at during the reboot process.
I changed the garage door server python script (running on the Edison)
OLD>> relay = mraa.Gpio(3)
NEW>> relay = mraa.Gpio(8)
This solved the problem.
"shutdown now" or "shutdown -r now" no longer has the side effect of toggling the relay.
I am happy with this solution, since I can easily move the relay GPIO connection.
I'm experiencing a similar problem - except I'm seeing this behavior on pin 4.
However, due to my application, this pin being on for too long is a genuine fire hazard!
I'm happy to switch pins to one that won't go high during reboot - can anyone provide any strong answers as to which pins definitely won't go high? I'm only seeing pin 4 go high right now.