Hello, I've just tried to update firmware of my Expansion Board v3.0 and faced the same issue. Does anyone knows how to fix it? Thanks in advance, w

@jc_serg That looks bad then. Since 3.3V is an output of the board, it means that the board is not working. Are you sure you plugged in the board in the right orientation?

well, right now I only have access to win10. Is there any solution for windows 10?

@reidfo The issue is that an unsupported band is being used by the modem and causes it to crash and reboot. It's a bit more involved but that is the gist. I got a revised firmware that appears to have resolved it. I suppose I could PM the fw. Not sure if pycom would frown upon sharing. I would expect this is resolved in the next release after 1.18.2.r3.

Ok solved using 5v as vcc nor 3.3v for the boot

@elizar I wouldn't have expected it since the Putty output looked fine, but it does appear to be issues related to poor signal quality. I took the breadboard out of the loop and attached the FTDI headers directly to the board headers with Molex cables and the flash finally took! Thanks for the suggestion!

@zahary-momchilov Yes. You can use WiFi. However it is advisable to have a generic USB/UART adapter with 3.3v output as second option. Any adapter with 3.3V output level will do. The latter sorts out most Arduinos.

@ledbelly2142 I'm very glad that you found a way. The Expansion board 2 has no firmware. Only expansion board 3 has. If the other board you used was a model 3, it could have been caused by the firmware updater, requiring multiple resets. I faintly recall something like that.

@bqpd Thank you!! I've managed to un-brick a FiPy and a GPy by following these instructions. Very much appreciated!

@elizar Thank you for confirming this!

Hi, I tried via ftp and it works perfectly. Regards

hello, I think we are talking about the same problem in another post. Regards,

@james-matthews I agree James! I got a Photon the other day from another vendor, and was up and running in 5 minutes with their app. I'm two hours into this process, after fighting to upgrade the firmware on the expansion board (never worked... according to the instructions anyway - board only waits 7s, not long enough for Windows device enumeration to work on my system, so the DFU driver failed to install every time!) Now there's the 'pycom upgrade' program, and the screenshots in the instructions aren't even close to what I'm getting, so there's half a dozen options which the instructions don't cover. Then there's this pybytes stuff - I don't even know what that is!? Absolutely hopeless.

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