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

    Guru meditation error

    Scheduled Pinned Locked Moved WiPy 2&3
    wipyguru meditation
    5 Posts 2 Posters 559 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.
    • M Offline
      Martinnn
      last edited by

      Hi, I have a handful of Wipys that have been running the past days sending stuff to AWS IoT using the builtin MQTT library.

      One died quickly with

      Guru Meditation Error: Core 1 panic'ed (Unknown reason)
      Register dump:
      Guru Meditation Error: Core 1 panic'ed (Guru Meditation Error: Core 1 panic'ed (Unknown reason)
      Register dump:
      Guru Meditation Error: Core 1 panic'ed (Unhandled kernel exception)
      Register dump:
      Guru Meditation Error: Core 1 panic'ed (Unhandled kernel exception)
      Register dump:

      Any clue what this could be? There are six other modules running fine.

      • Martin
      1 Reply Last reply Reply Quote 0
      • M Offline
        Martinnn
        last edited by

        I should add that this happened although I activated the watchdog. So it seems the watchdog does not catch this; it seems the wdt functionality is not using the ESP32 watchdogs.
        BTW interesting to see that other users reporting this problem are working with the AWS IoT library. Is it the threads module causing problems?
        Anyway it seems one needs an external hardware watchdog if you don't want the Wipy to hang up.

        1 Reply Last reply Reply Quote 0
        • P Offline
          Paul Thornton
          last edited by

          I presume the board has a decent stable source of power?

          Not sure why the WDT failed to reboot it. do you have any other info about what it was likely to be doing at the time?

          1 Reply Last reply Reply Quote 0
          • M Offline
            Martinnn
            last edited by

            The device was in a loop, reading data via a serial interface, reading from the pysense and sending it to AWS IoT (using the builtin module). It was powered from a USB hub with external supply.

            1 Reply Last reply Reply Quote 0
            • M Offline
              Martinnn
              last edited by

              Update: It seems I am getting the crashes only when I have my pysense/wipy connected via USB. I have around 12-15 units running in various setups; those running standalone (battery connection only) seem to do fine, those with USB fail regularly.

              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