Hi ha1* my guess is that you would at least need to update bcm-firmware-blob and perhaps kernel .ha107642 wrote:What criteria need to be met
Just to check you have the right pins, by "fifth and sixth", you do mean pins 5 and 6, the third pair of pins from the end?ha107642 wrote: I connected the fifth and sixth pins on my Raspberry Pi when it was in a halt state. Unfortunately, it did not wake the Pi from halt.
Works for me. I've tried a rev1 (Revision=2) and a rev2 (Revision=0xe) Pi1 model B.hurz wrote:I'd like to chime in as I'm experiencing the same issues as already mentioned by different people in this thread, but with a Raspberry Pi B (Rev2):
Do you get the 10 flashes on ACT LED after halting?hurz wrote:So I tried all commands again with Volumio2 (Raspbian based, kernel 4.4.9) and there halt behaves just like shutdown -h now or poweroff, without adding a -p.
But also on this OS I can't start with grounding Pin5, only via header P6.
Any ideas what I could do to change this? What OS are you guys running? Maybe the standard Raspbian allows for this?
Yes, vanilla raspbian. Can you test with vanilla raspbian?hurz wrote: @dom: Are you running the vanilla Raspbian or any other OS on your pis?
Code: Select all
# shutdown script for Raspberry Pi # watch LOW level on pin 5 to enter sleep mode # status led on pin 7: ON = ready, BLINK = confirm button import RPi.GPIO as GPIO import os import time # use the pin number as on the raspi board GPIO.setmode(GPIO.BOARD) # set pin 7 as output and HIGH, pin 5 is input GPIO.setup(7, GPIO.OUT) GPIO.output(7, True) GPIO.setup(5, GPIO.IN) # start the loop for every .5 seconds, waiting for LOW on pin 5 # then 2 short flashes with led to confirm and shutdown to sleep mode while True: if not (GPIO.input(5)): GPIO.output(7, False) time.sleep(.1) GPIO.output(7, True) time.sleep(.1) GPIO.output(7, False) time.sleep(.1) GPIO.output(7, True) os.system("sudo shutdown -h now") time.sleep(.5)
It won't damage the bus. i2c devices work by pulling the bus low. There are resistors on the Pi that provide a pull-up to 3.3V on pins 3 and 5.
Is there any way to configure which GPIO pin is used to wakeup? I am working on a CM3+CMIO3, and both GPIO1 and GPIO3 are occupied (I'm using the dpi24 overlay). I am able to shutdown via the gpio-shutdown overlay, and wake by grounding the RUN pin. But it would be ideal if I could configure the same pin for wakeup as well as shutdown. Is this possible?I've now added a way to wake the board through GPIO.
A falling edge on GPIO1 or GPIO3 will wake the board up, and it will continue to boot into linux.
No. The low power mode following "halt" is achieved by not powering on a number of power domains/clocks.qsrc wrote: ↑Tue Oct 10, 2017 10:24 pmIs there any way to configure which GPIO pin is used to wakeup? I am working on a CM3+CMIO3, and both GPIO1 and GPIO3 are occupied (I'm using the dpi24 overlay). I am able to shutdown via the gpio-shutdown overlay, and wake by grounding the RUN pin. But it would be ideal if I could configure the same pin for wakeup as well as shutdown. Is this possible?