@misterlisty Crash dumps contain some state about the device and running code at the point it had an error. with the right tools and source code you can see what was happening on the device when it crashed and try and locate the source of the error. Im not sure we have all the tooling to diagnose a crash dump public. Let me confirm with the team and check I could be wrong.

I found, that the problem only exist, while the Lopy is in time.sleep(). Can someone confirm this? Cheers, Thomas

I was able to upload it by not safe booting, but it would be nice to be able to boot in safe mode with this.

@jmarcelino @robert-hh Thank you for the inputs guys! This is what solved the issue for me, I thoroughly debugged the functions written in sensors.py file. There were some errors in the newly implemented functions which I corrected and then things started working fine!

@xykon Thanks. Even if I'm a little bit self-confident, please give it a second thought and a second test.

Hi @JVGD, thanks for reporting this. Looking at the error message, I'm wondering if you can check if the folder '~/.atom/packages/pymakr' is in lower case, not uppercase as 'Pymakr'? There was a change from uppercase to lowercase a couple of versions ago, but in some cases the uppercase version stayed in some atom cache or config file, causing issues like this... If it's in uppercase, please try to un-install and install the latest version of Pymakr (1.2.7). Some more suggestions to solve the issue were discussed here: https://github.com/pycom/pymakr-atom/issues/53

@aimette You can set up your own firmware build environment from the repository at https://github.com/pycom/pycom-micropython-sigfox, which in addition to changing the frequency allows you to embed your Python code into the flash, if it solid.

@seb bolded text Thank you your valuable information