@Arkaik In the list of commits, you have to go back to an entry with the title "Bump to version 1.4.0.b1". There you find the fingerprint. It's not a long way. In you first port you mentioned 1.4.0b1. But now you mention 1.0.4b1. About esp-idf. Do use the version indicated by the pycom web site.Try to checkout the most recent version before the date of the wipy firmwar you are using. That might get a little bit of a trial & error game.

@jmarcelino that fixed it. I can now upload my own firmware. Your fix of increasing the stack and putting listining mode in PASSIVE doesn't help though :-(. I'll see if I can go deeper into the scanning part. thanks for all the help Rolf

@jmarcelino Thank you.

@jmarcelino '1.6.12.b1'

@Ralph It seems there's a new bug. (almost) Every time I click the "Sync" button all the files get uploaded. Also I notice something that looks like a piece of checksum being printed like this: >>> Syncing project (main folder)... >>> >>> [1/12] Writing file communication.py c8474829a403c5fefb5e339b"]] [2/12] Writing file config.py [3/12] Writing file globals.py [...etc...] [12/12] Writing file utils.py Synchronizing done, resetting board... EDIT: Also, "Run" command on a file doesn't update the file on the flash, resulting in a strange behaviour if the current file is also present in the flash. Editing the script and running it seems to use the classes from the file on the flash memory, and the "top level" instructions from the editor file :/ EDIT2: Now the "Sync" end with an error. I rebooted the board, the PC and updated the firmware.... >>> Syncing project (main folder)...   >>> >>> [1/13] Writing file communication.py [2/13] Writing file config.py Synchronizing failed: Write failed. Please reboot your device manually.    EDIT3: Fixed with the new release

The latest firmware, 1.6.12.b1 has fixed this issue for machine.reset(). Typing CTRL-D in Pymakr still causes a crash but that is manageable by testing for machine.SOFT_RESET before attempting to set up Sigfox and if true, do a machine.reset() or machine.deepsleep(1) first.

Short of doing a reset, I don't see any way to avoid this scenario currently. I'm not at the point of being able to update my device remotely yet, but warning lights are already flashing in my brain over this becoming an issue.

@mrainone @daniel Behavior confirmed. I added a few print statements between the lines to see where it fails. Sometimes it passed through the script, sometimes it just stalled, sometimes I get an guru mediation error. In case of failure, it happened at the statement: sd = SD() Pasting the scripts into REPL always works. The core dump starts with (calling for saint Daniel): /Users/danicampora/Code/Pycom/esp-idf-2017-03-12/components/freertos/./queue.c:1444 (xQueueGenericReceive)- assert failed! abort() was called at PC 0x40085501 Guru Meditation Error: Core 0 panic'ed (abort) Backtrace: 0x40008155:0x3ffc5670 0x40007d16:0x3ffc5690 0x40125065:0x3ffc56d0 0x4019e230:0x3ffc5700 0x401977b4:0x3ffc5720 0x40197ba6:0x3ffc5770 0x400e0ee0:0x3ffc57a0 0x400df756:0x3ffc57f0 0x400f2b8e:0x3ffc5830 0x400eace0:0x3ffc5850 0x400f62e8:0x3ffc5870 0x400ee697:0x3ffc5910 0x400eace0:0x3ffc5990 0x400eb776:0x3ffc59b0 0x400f3d46:0x3ffc5a40 0x400f40b5:0x3ffc5a70 0x400eb602:0x3ffc5b50 0x400f65d4:0x3ffc5b90 0x400ee697:0x3ffc5c30 0x400eace0:0x3ffc5cb0 0x400ead09:0x3ffc5cd0 0x400d8c38:0x3ffc5cf0 0x400d8eb3:0x3ffc5d80 0x400d7f76:0x3ffc5dc0 ================= CORE DUMP START ================= YCgAAAwAAABsAQAA 6D38P7BV/D9QX/w/ wFT8P/Be/D8ubAAA7Dr8P+w6/D/oPfw/5Dr8PxQAAAAMf/s/DH/7P+g9/D8AAAAA BQAAAFQ//D9NaWNyb1B5AAAAAAAAAAAAAAAAAFBf/D8AAAAAIQAGAAUAAAABAAAA AAAAAMhm/D8AAAAAAAAAAAAAAAC4MPs/IDH7P4gx+z8AAAAAAAAAAAEAAAAAAAAA iKNCPwAAAABIHQBAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAA== KYEIgFWBAEA2BwYAFn0AgHBW/D97AAAAewAAABAAAAD/////AAAAAOv///9UOfw/ AQAAACQAAAAkAAAACAAAAP////8AAAAA/////wUAAAABAAAAAAAAAODCAED2wgBA AAAAAAgAAAD/////aBAIQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

@robert-hh Thank you. I will work on that advice.

Unplugged it one more time. Plugged it back in and hit the reset button. Then selected Com 4 and it worked. Thank you so much for your help. If I still had hair I would have pulled a few more strands out!

@beyonlo I found the solution with wireshark. I was testing the web page with chrome. Chrome is a litle bit buggy to test single threaded web servers. It does a pre-connection without sending any data in order to be ready for next request.

@livius thanks again Bookmarked ... Stephane A.

@Lokefar firmware blinking blue indicate that all is ok firmware state red indicate problem.. than changing "defaults" firmware colors are not avaiable