Unhandled interrupt 30 on cpu 0! with lastest firmware

[Gomez]

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

[seb]

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

[fyber]

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

[Gomez]

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.

[fyber]

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

[fyber]

Tried 1.12.0_915 and it flashes successfully.

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

[fyber]

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.

[seb]

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

[mphasize]

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!

[seb]

@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.

[mphasize]

@seb Just tried 1.15.0.b1 and the first 2 tries where successful. Thanks!