exit_and_deep_sleep_until_alarms not working on rp2040

[adriangalilea]

CircuitPython version

Adafruit CircuitPython 8.0.0-beta.4 on 2022-10-30; Raspberry Pi Pico W with rp2040

Code/REPL

import alarm
import time
import board

print("Waking up")

# Create an alarm for 60 seconds from now, and also a pin alarm.
time_alarm = alarm.time.TimeAlarm(monotonic_time=time.monotonic() + 20)
pin_alarm = alarm.pin.PinAlarm(pin=board.GP12, value=False)

# Deep sleep until one of the alarm goes off. Then restart the program.
alarm.exit_and_deep_sleep_until_alarms(time_alarm, pin_alarm)

Behavior

I get no errors and simply it doesn't wake up again, neither from the time nor the pin alarms.

Description

Using thonny as IDE

Additional information

No response

[DavePutz]

Testing with Adafruit CircuitPython 8.1.0-beta.2 on 2023-04-26; Raspberry Pi Pico W with rp2040
If I remove the pin_alarm the time_alarm works consistently.
With the pin_alarm enabled I see wildly inconsistent results (even though nothing was connected to the pin);
sometimes with the alarm getting called constantly, and sometimes including a hard crash:

Auto-reload is on. Simply save files over USB to run them or enter REPL to disable.
code.py output:
Waking up
Auto-reload is off.
Running in safe mode! Not running saved code.

You are in safe mode because:
CircuitPython core code crashed hard. Whoops!
Fault detected by hardware.
Please file an issue with your program at https://github.com/adafruit/circuitpython/issues.
Press reset to exit safe mode.

Sometimes even rebooting only into the boot handler, requiring a reload of the .uf2.

[DavePutz]

Tested on a plain Pico (no W) running CP 8.1 beta and both alarms worked correctly. Re-tested the PICO W without wifi on and still saw the issues with the pin_alarm.

[DavePutz]

I believe this issue may be occurring when the status of the pin is already in the triggered state when the alarm is being created. . @adriangalilea ; could you test your script adding in "edge=True" to the pin_alarm parameter list?

[adriangalilea]

Apologies but I might not be able to test it for now, will add a reminder, sorry 😞

[bablokb]

With the pin_alarm enabled I see wildly inconsistent results (even though nothing was connected to the pin);

Nothing connected means floating... Can you reproduce the behavior with a small pullup attached?

[kbsriram]

Adding some additional notes here after testing on a Pico W with

Adafruit CircuitPython 9.0.0-beta.2 on 2024-02-20; Raspberry Pi Pico with rp2040

and this code:

import alarm
import board
import digitalio
import time

# Just to make sure we're awake.
with digitalio.DigitalInOut(board.GP14) as status:
    status.switch_to_output(value=True)
    time.sleep(2)
    status.switch_to_output(value=False)

# Create an alarm for 10 seconds from now, and also a pin alarm.
time_alarm = alarm.time.TimeAlarm(monotonic_time=time.monotonic() + 10)
pin_alarm = alarm.pin.PinAlarm(pin=board.GP15, value=False, pull=True)

# Deep sleep until one of the alarm goes off. Then restart the program.
alarm.exit_and_deep_sleep_until_alarms(time_alarm, pin_alarm)

When running connected (i.e., supervisor runtime faking deep sleep), both sleep and pin alarm work correctly, and wake up the device out at the appropriate times. I see this output when GP14 is pulled low, or after 10 seconds.

Press any key to enter the REPL. Use CTRL-D to reload.
Pretending to deep sleep until alarm, CTRL-C or file write.
Woken up by alarm.

However, when running disconnected, only the sleep timer wakes up the device - pulling GP14 low does not wake up the device. (This remains the case even if explicitly pulling the pin high during boot up, and then pulling it low once it goes into sleep.)