Welcome to the Pycom forum Forum
    • \[\[global:header.categories\]\]
    • \[\[global:header.recent\]\]
    • \[\[global:header.tags\]\]
    • \[\[global:header.popular\]\]
    • Login

    Explore Pybytes | Official Documentation | Report a Firmware Bug/Issue | GitHub

    Machine.reset_cause()

    Scheduled Pinned Locked Moved LoPy
    2 Posts 2 Posters 183 Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A Offline
      Asb
      last edited by

      Hi.

      Is it possible to determine whether the on-board reset button was pressed vs. the LoPy turning back on again after a power outage?
      I've tried using the machine.reset_cause(), but it looks like both of my scenarios will go under machine.PWRON_RESET?

      Thanks.

      robert-hhR 1 Reply Last reply Reply Quote 0
      • robert-hhR Offline
        robert-hh @Asb
        last edited by

        @asb No, because the reset pin, connected to CHIP_PU on the ESP32, actually switches the power. That is in the data sheet:

        CHIP_PU
        High: On; enables the chip
        Low: Off; the chip powers off

        1 Reply Last reply Reply Quote 1

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        • 1 / 1
        • First post
          Last post

        Pycom on Twitter

        Pycom