thanks I tried firstly the second option you told and it worked well.

I must have totally missed your message. I posted the firmwares on the forum some time ago for a different user in your situation, but now we have the latest firmwares published in the documentation: https://docs.pycom.io/updatefirmware/expansionboard/ Best, Gijs

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 from the future.

@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,

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