@balefire I agree - the PyCom user experience is terrible. So many gaps in the documentation, the main effort is reverse engineering what to do from everyone's failures - no clear "how to" guidance that is actually accurate / complete. Its a shame - gut feel; pycom could have been a game changer, but will die a slow death due to too closely guarded "secrets" which only serve to hinder the developers and product users.

Hi @agotsis, Please check this post for more info about this issue. Hope this helps!

@sympatron Can you try this link please? https://xykon.pycom.nl/s/M8braq020b9gInb Internet and China don't work well together... There isn't really documentation for the new format yet because it's not yet been officially released. If you do manage to download the firmware updater you'd be the first person outside Pycom to actually use it. And as I said before it's still experimental and I'm aware of some issues with it such as the otadata partition definition missing, so please don't try to modify the script2 file in a firmware package. I'm still in China this week and things tend to get more and more hectic towards the end of the trip so I likely won't be able to do any work on the firmware updater until I'm back in Eindhoven.

I came across this "bytesdfu-util: Error sending completion packet" error today when attempting to upgrade a Pycom Expansionboard 3.1 connected to an Ubuntu 18.04 LTS. Running ls -la /dev showed that the serialport had restricted access, so a quick fix was: sudoedit /etc/udev/rules.d/50-myusb.rules and insert the following: KERNEL=="ttyUSB[0-9]*",MODE="0666" KERNEL=="ttyACM[0-9]*",MODE="0666" then sudo reboot After rebooting the firmware upgrade worked great (holding the s1 button when connecting the USB-cable; releasing s1 after one second; then running dfu-util within a few seconds). sudo su - dfu-util -D /home/user/Download/expansion31_0.0.11.dfu

@sympatron said in New beta firmware updater 1.15.2.b0: Just wanted to help with bug fixing/spotting Which is very much appreciated and reason I started releasing development versions in the first place :)

@clementdecaux Not only is there no USB support directly on the LoPy (I guess you connected to the UART lines), but additionally USB is 5V while the LoPy only supports 3.3V...

@xykon said in New Firmware Updater version 1.15.1: @bmarkus Win32:Evo-gen [Susp] is a broad classification used by the Avast Behavior Monitor feature for software that exhibits suspicious behavior categorized as potentially malicious. The Behavior Monitoring feature observes the behavior of processes as they run programs. The firmware updater connects to the Internet. That is considered "suspicious" for some anti-virus applications. Thanks for the details. However it is a bit strange,a s I'm frequently installing programs connecting to the net during installation and have never seen such message from my AVAST. Anyhow, I will ad it as an exception.

@sukandar Thanks a lot. It seems the serial communication is working. Can you please try the following two commands next: cd "/Applications/Pycom Firmware Update.app/Contents/MacOS" "Pycom Firmware Update" -v This will open the firmware updater (please follow the same steps as before) but during the update it should print some text in the terminal window. Please send the output in the terminal window along with the wireless Mac address from the previous command and a link to this forum post to support@pycom.io Thanks a lot.

Perfect, thanks. This gives me what I need until it can be dealt with on your end. I have filed the ticket.

@xykon Works now with the new 1.14.2. Thank you!

EDIT: This issue should now be fixed in the latest version 1.14.2 but I'm leaving these instructions here for now in case the issue is still not 100% resolved. If you are prompted for a Pybytes token even though you selected "stable" as the firmware type: Please post your OS type (Mac, Windows (32/64bit), Linux) and exact version here. Then please use the following firmware updater: MacOS Windows Linux Please ignore the message about an upgrade being available.

It just happened to me too :-( Yesterday it worked, and today it doesn't.

I just struggled through getting the Expansion Board V3.0r to support updating a fipy and had similar issues. In the end it required a manual jumper between P2 and GND (even though the board is supposed handle this automatically) and turning off the high-speed and Pysense options. Having said that, the first one I upgraded I used an external USB to serial interface and it worked first time.

@buw I'm surprised that made a difference, I have nearly always upgraded Pysense boards with a module on. But whatever works for you!

Hi, Yes, the way the Pytrack/Pysense/Deepsleep shield sleep works is that they disconnect the power from the module, sensors etc entirely. In the case of the Pysense and Pytrack the USB is also de-initialised meaning you will lose the serial connection, this can make talking to the device difficult if it does not wake up for long The Pytrack/Pysense/Deepsleep shield sleep is a a "deep" sleep rather than a regular sleep. Once you use this, when the module wakes up it will be like it was rebooted. Pycom board do not currently support machine.sleep although this is being investigated. The way this differs from the machine.deepsleep is that this uses external hardware and powers off everything on the board, not just the ESP32 processor. You can still use machine.deepsleep if you desire but note that on the WiPy2, LoPy and SiPy, due to an issue with the way the voltage regulator is connected the deepsleep current draw will be quite high (15mA) If you connect P12 to 3.3v with a jumper cable and wait for the device to wake from sleep you will see the on-board LED blink orange. Once this happens you can disconnect the cable. The device will now "safe boot". This prevents the device from running boot.py and main.py and therefore the code putting the device to sleep. The best way to stay informed of firmware updates is to use the forums subscribe feature for the announcements forum. We will always post in there when a new firmware is released

@stefan85e That is correct, the 1.17.0.b1 upgrade is for the LoPy. You do not need to ever upgrade firmware for the expansion board 2

I have tried the firmware update on Windows 10 and windows 7 and the update stays stuck on "Please wait. Reading information about the board ..." Last week Xylon sent a *.tar.gz file which I was able to update the firmware using the CLI tool. Could you please provide the same. Thanks.

anyone reading this. please refer to: Problem joining TTN in Australia with OTAA using a LoPy 4 post on the LoPy section of the forum. The solution to this issue seems to be to restrict the channels of the AU915 regional settings.