@robert-hh Thanks will try and come back to you,

We will be releasing the firmware update packages soon, here: https://github.com/pycom/pycom-micropython-sigfox/releases They are not currently uploaded there yet but we plan on making them available there to make OTA updates easier. It is important to note you must update via USB at least once with a new device in order to be provided with mac address, sigfox PAC etc.

@seb It's my bad. I have missed that service was listening just on localhost, that's why I was not able to receive any file.

@gnm Glad to hear it finally worked :) I hope the rest of the getting-started experience will be smoother but don't hesitate to let us know if you need anything further.

Hi @xykon thanks for the info and quick response :-) ... I've not really studied udev rules on my Linux mint machines. However adding dialout did not effect the behavior of 'cutecom'. Changing the read write permissions on the USB device survives reboot. I'm sure if I have a different device take USB0 then I will be stuck again. Any info on how files are copied to and from the device or is anyone in the community looking at a plugin for pycharm? Great stuff - keep up the good work... :-) Kind regards, Nicholas.

Just updated to latest version and exactly the same issue again...

Hi @naveen, Sorry I'm late to the party here, but I believe that the PyMakr is the "expansion board". Take a look at the back of your PyMakr and it should say Expansionboard v2.X or v3.X. You should be able to update firmware using your PyMakr and this tutorial. https://docs.pycom.io/gettingstarted/installation/firmwaretool.html Hope this helps!

@xykon Thanks Xykon. Yes, I connected a wire between 23 and GND before plugging it in and flashing. I think if there are thermal issues affecting all Fipys and its a known issue you should slap a sticky note or something on the site. I mean all the Fipys just went out recently. t.pirk and myself can't be the only ones noticing this. Should we not use the Fipys until a fix is available? I don't want to damage my units.

@crumble There is no USB stack on the *Py devices. They are connecetd by UART0 of the ESP32 through an USB/UART bridge chip. The driver for that chip used to make problems, but mostly on OS X.

@pyoneer It's mostly a matter of timing. Too early and the device is not yet up. Too late and the Pysense has exited DFU mode and booted normally. IIRC the window is about 7 seconds.

You cannot use the pycom updater for a Wipy 1.x. These have to be updated via OTA. Images and instructions are on the micopython.org web site. There is also the forum for that product.

Oops the answer was to reboot after installing those drivers and now it appears to work. :)

Ok..it works again using /dev/cu.usbmodemP* device. That confused me...usually its always a tty. Thanks a lot!!

Solved it. I used the pycom upgrader 1.1.1.b2 to downgrade to FW 1.6.0.b1. Afterwards, the upgrade to 1.7.5.b2 worked seemlessly.

This worked for me:

@Bryan Hello Bryan, you also asked on the micropython.org board, which is the right forum for your problem. I placed an answer there, which may fix your issue.

@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

I spent a great deal of time getting this to work on a Mac: Power off the board and put the jumper on Install the FTDIUSBSerialDriver_v...dmg Run this in the terminal: kextstat -b com.FTDI.driver.FTDIUSBSerialDriver you may have to run it a few times to get an output like this: Index Refs Address Size Wired Name (Version) UUID <Linked Against> 91 0 0xffffff7f80e43000 0x7000 0x7000 com.FTDI.driver.FTDIUSBSerialDriver (2.4.2) E16D9540-AF63-36AD-94C4-B1164FBD6078 <90 42 5 4 3 1> After that, reboot your machine. Once up, run the Pycom Firmware Update again. This time you'll see another port eg. /dev/cu.usbserial-DQ00DQIT Select the serial port and click 'continue' This time it'll run the whole process to update your firmware.

@robert-hh Unfortunately deep sleep hasn't been implemented in the latest version I can use (1.6.3). I will try to implement it myself later today though.

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!