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

    Unhandled interrupt 30 on cpu 0! with lastest firmware

    Scheduled Pinned Locked Moved Firmware
    sigfoxfipybug
    14 Posts 4 Posters 2.6k Views 4 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.
    • G Offline
      Gomez
      last edited by

      Hi,
      after the last upgrade of firmware (MicroPython v1.8.6-849-86da809 on 2018-01-17; FiPy with ESP32) in my Fipy board, running this few line of code ( working in the previosuly version of FW ):

      from network import Sigfox
      import socket
      sigfox = Sigfox(mode=Sigfox.SIGFOX, rcz=Sigfox.RCZ1)
      s = socket.socket(socket.AF_SIGFOX, socket.SOCK_RAW)
      s.setblocking(True)
      s.setsockopt(socket.SOL_SIGFOX, socket.SO_RX, False)

      when i send the command ( over REPL ) s.send(byte([1,2,3])) the Fipy hangs completely and don't receive any other command over serial or after a while send this message infinitly:

      Unhandled interrupt 30 on cpu 0!

      Any suggestion please? Thanks in advance, Andrea

      1 Reply Last reply Reply Quote 0
      • sebS Offline
        seb
        last edited by seb

        Hi,

        Thanks for reporting this, we are already aware of the issue and it will be fixed in the next firmware release that should be available soon. In the mean time I can suggest rebooting your FiPy, the issue seems to be intermittent and won't always occur. Another option would be to downgrade your firmware until the new one is available.

        1 Reply Last reply Reply Quote 0
        • G Offline
          Gomez
          last edited by

          Thank you for your fast response. Rebooting anyway don't solve the problem, even if you don't have the unhandled interrupt error, you cannot send Sigfox message. Best regards, Andrea

          1 Reply Last reply Reply Quote 0
          • G Offline
            Gomez
            last edited by

            Where can I found a previous working firmware ( than the actualu one 1.8.6-849-86da809 ) ? I downgraded to the one I found in this topic but Sigfox connection doesn't works even if s.send() reply me with the correct number of bytes sent.
            https://forum.pycom.io/topic/517/downgrading-firmware-advanced-users
            Thanks,
            Andrea

            1 Reply Last reply Reply Quote 0
            • sebS Offline
              seb
              last edited by

              The previous FiPy firmware can be downloaded here:

              For 868 MHz: https://software.pycom.io/downloads/FiPy_868-1.13.0.b1.tar.gz
              For 915 MHz: https://software.pycom.io/downloads/FiPy_915-1.13.0.b1.tar.gz

              1 Reply Last reply Reply Quote 0
              • F Offline
                fyber
                last edited by

                Flashing that firmware does not seem to work. The flashing tool returns 1 and the board is softbricked until you flash something else.

                1 Reply Last reply Reply Quote 0
                • G Offline
                  Gomez
                  last edited by

                  I had success on downgrade with the tool provided in the post https://forum.pycom.io/topic/517/downgrading-firmware-advanced-users and the firmware download link provided in this one. Sigfox is working again. Windows 10 + Fipy + Expansion board + FW_868.

                  1 Reply Last reply Reply Quote 0
                  • F Offline
                    fyber
                    last edited by

                    I used the same tool - MacOS + Fipy + Pysense + FW_915 - returns 1.

                    1 Reply Last reply Reply Quote 0
                    • F Offline
                      fyber
                      last edited by

                      Tried 1.12.0_915 and it flashes successfully.

                      It still doesn't work even though s.send() gives the correct # of bytes.

                      1 Reply Last reply Reply Quote 0
                      • F Offline
                        fyber
                        last edited by

                        1.13.0 started working for some reason

                        from network import Sigfox
                        import socket
                        sigfox = Sigfox(mode=Sigfox.SIGFOX, rcz=Sigfox.RCZ2)
                        s = socket.socket(socket.AF_SIGFOX, socket.SOCK_RAW)
                        s.setblocking(True)
                        s.setsockopt(socket.SOL_SIGFOX, socket.SO_RX, False)
                        s.send("hi")
                        2
                        os.uname()
                        (sysname='FiPy', nodename='FiPy', release='1.13.0.b1', version='v1.8.6-849-656704e on 2018-01-10', machine='FiPy with ESP32', lorawan='1.0.0', sigfox='1.0.1')

                        Still no luck, nothing shows up on sigfox backend.

                        1 Reply Last reply Reply Quote 0
                        • sebS Offline
                          seb
                          last edited by

                          Have you tried to disengage the sequence number from the sigfox back end, this often resolves sigfox issues.

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

                            Seeing the same issues here. Even after downgrading the firmware to 1.13.0.b1 and then uploading a bit of code that is calling the Sigfox example as a function, I got the unhandled interrupt 30.

                            Any idea what's causing it or when the fix will be available? Thanks!

                            sebS 1 Reply Last reply Reply Quote 0
                            • sebS Offline
                              seb @mphasize
                              last edited by

                              @mphasize Have you tried the latest firmware that was released yesterday: https://forum.pycom.io/topic/2541/new-firmware-release-v1-15-0-b1

                              This should hopefully fix the issue, if it does not, please report back.

                              M 1 Reply Last reply Reply Quote 0
                              • M Offline
                                mphasize @seb
                                last edited by

                                @seb Just tried 1.15.0.b1 and the first 2 tries where successful. 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