Firmware upgrade troubleshooting - checklist/procedure

[rskoniec]

@livius said in Firmware upgrade troubleshooting - checklist:

@rskoniec
you can somehow merge this post:
https://forum.pycom.io/post/2655

Good tip! Done! :)

[rskoniec]

@mmarkvoort said in Firmware upgrade troubleshooting - checklist:

I don't know if it is relevant but when i wanted to update/connect through USB I had to install the USB driver manually. Mine called FTDI driver where VCP or D2XX are types of drivers. With one of the two it said it was installed but still i coudn't update/connect.

But you were trying to update using Expansion Board USB or xPy board + USB2TTL serial converter?

[dClaus]

For Lopy "Connecting ......... Failure !"
see post https://forum.pycom.io/post/4518

between 3 and 4 : use the RESET buttom on the Lopy

;-)

[rskoniec]

@dClaus One more time - thanx! It's already updated. :)

[mmarkvoort]

@rskoniec
Update using Expansion Board USB.

[bucknall]

@jmarcelino This is going into Docs with the next update :)

[rskoniec]

@bucknall said in Firmware upgrade troubleshooting - checklist:

@jmarcelino This is going into Docs with the next update :)

Nice! :)

[rskoniec]

@mmarkvoort said in Firmware upgrade troubleshooting - checklist:

@rskoniec
Update using Expansion Board USB.

OK. In a free time (I hope this weekend) I'll grab a fresh install Windows machine and try to investigate FTDI driver issue.

[Frida]

On linux remember to update/place a file in: /etc/udev/rules.d

I have these in my: 45-espruino.rules, then you don't have to use sudo su

# To go in /etc/udev/rules.d/
# Makes Espruino's serial port accessible to non-SU users, and stops the Modem Manager trying to enumerate it
ATTRS{idProduct}=="5740", ATTRS{idVendor}=="0483", ENV{ID_MM_DEVICE_IGNORE}="1", MODE="0666", GROUP="plugdev"
# Nordic kits
ATTRS{idProduct}=="1015", ATTRS{idVendor}=="1366", ENV{ID_MM_DEVICE_IGNORE}="1", MODE="0666", GROUP="plugdev"
# Microbit
ATTRS{idProduct}=="0204", ATTRS{idVendor}=="0d28", ENV{ID_MM_DEVICE_IGNORE}="1", MODE="0666", GROUP="plugdev"
# Propeller
ATTRS{idProduct}=="6001", ATTRS{idVendor}=="0403", ENV{ID_MM_DEVICE_IGNORE}="1", MODE="0666", GROUP="plugdev"
# Pycom
ATTRS{idProduct}=="6015", ATTRS{idVendor}=="0403", ENV{ID_MM_DEVICE_IGNORE}="1", MODE="0666", GROUP="plugdev"

[rskoniec]

@Frida Thanx for sharing! Updated!

[rskoniec]

@mmarkvoort said in Firmware upgrade troubleshooting - checklist/procedure:

I don't know if it is relevant but when i wanted to update/connect through USB I had to install the USB driver manually. Mine called FTDI driver where VCP or D2XX are types of drivers. With one of the two it said it was installed but still i coudn't update/connect.

OK, I took my notebook with Windows 10 Pro x64 with internet access and plug LoPy on Expansion Board to it for the very first time.
Here is Device Manager just after connection:

After about 30 seconds Windows Auto Update mechanism has done all the job:

As you can see it is pretty straightforward - at least on Windows 10.
What OS are you using?

[mmarkvoort]

@rskoniec

Aah thanks for the update. Really fast!!

Now that u mention that windows installs the update automatic, I remember that I disabled windows update on my windows 10... that explans a lot! How stupid...

Sorry for wasting your time, but thanks for the fast answer and for trying it out.

[maamar]

@rskoniec thank you
I did my updated

[rskoniec]

@mmarkvoort @maamar You welcome. :o)

[yunying]

Thank a lot.
Reply just for feedback.

Make sure your jumper at "TX"

[colinza]

I had issues trying to update my wipy 2.0 with a standard TTL serial programmer I use for Arduino. For some reason the low baud rate update in the software selects 38400 but the WiPy sold with old broken firmware has it set to 115200 which isn't even an option through the firmware update tool.

To change this you can edit C:\Program Files (x86)\Pycom\Pycom Firmware Update\Upgrader\bin\updater.py and set "SLOW_BAUD_RATE=115200". Then the firmware updater works just fine.

[daniel 0]

One should also check that all of the jumpers have tight connections. I couldn't get communication to work with my expansion board until I replaced the jumpers provided with new ones as the originals were quite loose.

[philwilkinson]

I stress the need to reset LoPy boards after they have been connected to pc by data USB cable, and before you try to run the upgrade....

[on4aa]

Unfortunately, this is currently not working for upgrading a module through either the Pysense or Pytrack boards using any GNU/Linux distribution.