Firmware Update Fails

[livius]

@mike632t
No, updater tool did not check if you have version already it is because you can have version already but with some error - and you can reflash it once again with same version "fixed"

your problem is that you use Linux - i am joking ;-)
I know that this is not helpful but on Windows there are no problem with this at all.

[robert-hh]

Well, I never had any problem when using Linux, with both types of updaters. I would not even consider a second to use Windows for that task.
@mike632t: Do you use the most recent updater tool, and do you have access to the site, wget tries to get the image from?

[mike632t]

@robert-hh
I used 'wget' to download the updater last night so I'm reasonably sure it is the current version.

The problem looks like the 'curl' command (see below). I did try connecting directly to my router (I normally connect from behind a firewall) but it makes no difference. Unfortunately I have no idea what the output means.

I'll try uninstalling 'curl' later which should force the updater to use 'wget' and see if that makes a difference.

Mike T.

[jmarcelino]

@mike632t

In this thread @bucknall was mentioning a problem in the Linux updater, not sure if this related.

[mike632t]

@livius
LOL - I generally find that the problem with windows is windows :-) - unfortunately I have to use it at work.

I have not used Windows at home for years, I think I have an old XP box somewhere but drivers for the USB serial interface could be a problem...

Mike T.

[livius]

@mike632t
:) :) :)

For XP you can fiund drivers too - but on XP (laptop) i have UART TTL -> USB converter and work ok
I do not know if the same will be for drivers for expansion board

[bucknall]

Thanks @jmarcelino!

I believe the Linux Firmware Updater should be working correctly now!

@mike632t I'd suggest a couple of things:

1. Ensure all the headers on the expansion board are connected
2. Try changing USB port on your computer
3. Do you have the jumper cable connected across pins GND and G23 on the expansion board? (I know it's been asked but this is normally the cause!)

[mike632t]

@bucknall

1. Yes they are
2. Tried that makes no difference
3. Yes and the initial serial communication to detect the type of device works.

Serial communication with the 'console' works on all the ports I've tried, and the script is able to communicate with the board to discover what type of device it is but it exits when it checks the contents of the temporary file that it tried to download from the web using curl.

Mike T.

[bucknall]

@mike632t Hmm odd, let me check this internally! Will get back to you ASAP!

[robmarkcole]

Is it possible to update without the USB? I only have wifi connection to my Wipy and using the iOS app failed..

[livius]

@robmarkcole
at this time no - only RS232 (or UART TTL -> USB converter)

[robmarkcole]

@livius thanks :)

[robmarkcole]

@livius I saw a youtube video yesterday where the guy used a nodeMCU to provide the UDB-sserial connection for a Lopy, is there a guide? I have a nodeMCY (bricked), raspberry pi and a particle photon available..

[robert-hh]

I would assume that they simply used the USB/Serial chip on the NondeMCU for that purpose, connecting RX-RX and TX-TX of the two devices. The nodemcu board has to be powered for that purpose. The problem is to get the TX pin of the NodeMCU to high impedance and have the NodeMCU to be silent. One guess would be to keep in in reset (pull reset low).
A similar approach is sometimes told with an Arduino.

[robmarkcole]

@robert-hh Thanks for the info, if I get it working I will make a post :)

[szatmari60]

I have the same issue with two WiPy 2.0 boards ,
( (sysname='WiPy', nodename='WiPy', release='1.6.3.b1', version='v1.8.6-463-g468b9d27 on 2017-02-16', machine='WiPy with ESP32')
and
(sysname='WiPy', nodename='WiPy', release='1.6.3.b1', version='v1.8.6-463-g468b9d27 on 2017-02-16', machine='WiPy with ESP32') ) ,
the the first one I manage to upgrade maybe a month ago !
I can connect to my boards using FTDI , I am a linux user, except this issue everything is OK!

The updater fails to connect and throw an error : "Something failed trying to connect to the device"
Can anybody help ...

[robert-hh]

Hello @szatmari60, if you get an REPL prompt using USB, then the basic communication works. Do you know, which interface is used for the REPL prompt. The same is needed for the update. The updater changed in that it fetches the image directly from the Pycom web site during update. So be sure that a connection is possible. I do not know whether mike632t finally succeeded. The was no response during the last three days. If you look in the board for the downgrade instructions, you'll see a method to upload the file locally. From these instructions you can easily guess the names of the most recent files, which are available too.

[mike632t]

@szatmari60
That seeme like the error I got before I installed the python-serial package.

[szatmari60]

Hello, and thank you!
YES I get a REPL prompt using USB (FTDI chip FT232RL), the basic communication works with Pymkr, screen, ESPlorer, I also can upload files with "ftp"
Booting process:
"""
ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0x00
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:QIO, clock div:2
load:0x3fff9010,len:8
load:0x3fff9018,len:248
load:0x40078000,len:4056
load:0x4009fc00,len:920
entry 0x4009fde4
I (1577) wifi: frc2_timer_task_hdl:3ffd4a2c, prio:22, stack:2048
I (1592) wifi: Init lldesc rx mblock:10
I (1593) wifi: Init lldesc rx ampdu len mblock:7
I (1593) wifi: Init lldesc rx ampdu entry mblock:4
I (1594) wifi: pp_task_hdl : 3ffdbb68, prio:23, stack:8192
I (1599) wifi: sleep disable
I (2588) wifi: mode : softAP (24:0a:c4:00:b4:93)
MicroPython v1.8.6-463-g468b9d27 on 2017-02-16; WiPy with ESP32
Type "help()" for more information.
">>>import os
">>>os.uname().release
">>>'1.6.3.b1'
"""
But the "uploader" cannot communicate with WiPy 2.0. I tried to run manualy on terminal "updater.py" file.
This is the result:
"""
...:~/pyupgrade$ ./bin/updater.py --port "/dev/ttyUSB0 --speed 19200 wmac
Connecting...........................................
Exception: Failed to connect to ESP32: Invalid head of packet ('\x08'), on line 161
"""
I am runnig out of ideas !!

[robert-hh]

@szatmari60 Even with the manual updater, have you installed the wire between GND and GP23, and Reset after that?