Open davidmcnabnz opened 1 year ago
@davidmcnabnz I experience the exact same issue. It is also very very slow the reaction time to an interrupt seems to be very late. I have the feeling that this sleep mode and in general the sleep mode of the RP2040 is pretty bad. (at least with micropython)
Did you got any new results?
Sorry for the (very) late reply. Like mentioned in the README, this workaround is very experimental, as indeed the sleep mode is not at all supported with micropython :smile:
I did not experience this failure on my tests, but it may vary depending on the exact code, or even device to device. So if you can provide me with a specific model and minimal code where you can reproduce the issue it would be much helpful (as there is now multiple devices in addition to the original Pico on which I developed the workaround).
Please note that sometime the sleep mode may cause the REPL to stop working, but not the pico. So if you rely on a print statement to check if the device was successfully waken up, you may be mislead.
I recommend testing with by turning on and off a LED on the device for a more reliable diagnostic.
this issue is very old, but i just wanted to say: it is exactly as @tomjorquera says. I was fooled myself, but in fact the operation resumes nicely. The REPL is unusable until a reconnect, though. Nothing that can be fixed, I guess - after all this is powering down hard, so.... what would the REPL talk to?
Hi,
Based on the logic in the example, I've configured a pin to generate an interrupt on falling-edge. My code then calls dormant_until_pin() to enter sleep.
Sometimes, a falling edge on the pin wakes the device back up, which is good.
But sometimes, the same falling edge has no effect.
Any suggestions for how to investigate?
Cheers David