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

    Core dump when calling py.go_to_sleep()

    Scheduled Pinned Locked Moved Expansion Board
    pysensecore dumpdeepsleepdeep sleeppower saving
    2 Posts 2 Posters 1.2k 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.
    • F Offline
      fkoran
      last edited by fkoran

      I'm seeing a core dump when I call setup_sleep. Anyone else seeing this?

      I'm using the latest pysense.py from https://github.com/pycom/pycom-libraries/blob/master/pysense/lib/pysense.py

      My LoPy firmware is 1.10.0.b1

      I'm using https://github.com/adafruit/ampy and screen for file sync and interactive shell

      >>> from pysense import Pysense
      >>> py = Pysense()
      >>> py.read_hw_version()
      2
      >>> py.read_fw_version()
      7
      >>> py.setup_sleep(1)abort() was called at PC 0x4008ca88 on core 0
      
      Backtrace: 0x40 0x4000bef5:0x3ffc5d30 0x4013f2aa:0x3ffc5d50 0x401028b7:0x3ffc5d80 0x40102989:0x3ffc5d
      c0 0x400f3456:0x3ffc5df0 0x400efe21:05d10c5e20 0x400efe89:0x3ffc5e40 0x400fb0f5:0x3ffc5e60 0x400f34ec
      :0xd80 0x40102989:0x3ffc5dc0 0x400f3456:0x3ffc5df0 0x400efe21:0x3ff0x3ffc5fe0 0x400f34ec:0x3ffc6080 0
      x400efe21:0x3ffc60c0 0x400efe3ffc5f00 0x400efe21:0x3ffc5fa0 0x400efe89:0x3ffc5fc0 0x400fb0f5:fe21:0x3
      ffc6220 0x400efe4e:0x3ffc6240 0x400dd853:0x3ffc6260 0x489:0x3ffc60e0 0x400fb0f5:0x3ffc6100 0x400f34ec
      :0x3ffc61a0 0x400eRE DUMP START =================
      DCoAAAsAAABsAQAA
      TEP8P5Bb/D/s00ddad8:0x3ffc6300 0x400dcb6d:0x3ffc6340
      
      ================= CO8AAAAA
      BQAAAPBE/D9NaWNyb1B5AAAAAAAAAAAAAAAAAOxk/D8BAAAAIA0GAAUZPw/
      cFz8P4Bk/D8ueQEAOED8PzhA/D9MQ/w/MED8PxQAAACEwPs/hMD7P0xD/DAEAAAAAAAAA
      uFFAPwAAAAAwjAlAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAAAA
      AAAAABRs/D8AAAAAAAAAAAAAAAB4Kf0/4Cn9P0gq/T8AAAAAAAAAAAAAAAAAAAAAAAAAA
      AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
      AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
      
      
      1 Reply Last reply Reply Quote 0
      • J Offline
        JuanMa
        last edited by

        I suffer the same error with the new firmware version (1.10.2.b1). It seems they have not solved it until now... Have you found any solution?+
        Thanks

        1 Reply Last reply Reply Quote 0

        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