Instructions for upgrading Pytrack / LoPy

[hjl]

Hi, I am trying to find a way to update the firmware for the Pytrack & LoPy, but I can't seem to find any documentation. Any ideas? I don't have a expansion board.

The updated doesn't seem to work and the DFU-UTIL returns success, but I still get a 1.0.0.1b version by using os.uname()...

[jcaron]

@hjl note that there are two different firmwares:

• one in the Pytrack (which you upgrade with dfu-util)
• another one in the LoPy (which you upgrade with the Pycom Firmware Upgrade software)

[hjl]

Hi jcaron,

Thanks for your reply. Unfortunately no luck with both methods. I used the jumper cable correctly but it keeps giving me an error:

And the dfu-util shows a success, but after using the os.uname() i still see the 1.0.0.1b version coming up.

Can't see what I am missing.

[jcaron]

@hjl The version returned by os.uname() is that of the LoPy firmware.

dfu-util upgrades the Pytrack firmware. You can see that version using read_fw_version() in the Pytrack library.

If you have issues upgrading the LoPy firmware, you can try unchecking the "high-speed transfer". Did you select the right serial port?

I never managed upgrading with the GUI upgrader on macOS myself. What I do:

• reboot the board with P23-GND connection

• check that it's indeed in upgrade mode with:

  esptool.py --port /dev/cu.usbmodemPy343431 --after no_reset read_mac
  

• download firmware from https://software.pycom.io/downloads/LoPy_868-1.7.8.b1.tar.gz

• upgrade with:

  python2.7 /Applications/Pycom\ Firmware\ Update.app/Contents/Resources/src/bin/updater.py -s 57600 -t LoPy_868-1.7.8.b1.tar.gz -p /dev/cu.usbmodemPy343431
  

• reboot

Once you are on a firmware version >=1.7.7 you can use FTP to upgrade, it's much easier.

[hjl]

Thanks for your help so far. Seems to have no luck with that either, I have the jumper in the 4th pin on the left side and the 2nd pin on the right (USB conn on top). Should be OK, right?

Unchecking high-speed transfer didn't work either. Do I need to install some additional driver for my mac? I have the newer one with the USB-C ports.

[jmarcelino]

@hjl
Out of curiosity how are you placing a jumper while the LoPy mounted on the Pytrack? Seems really difficult to me, I have had to use test clips to do it.

[jcaron]

@hjl just to be sure, you do have that jumper while you power on the board, right?

[hjl]

Yes, thanks.. I was confused about the expansion board and 'jumpers' assuming I first was updating the Pytrack itself without connecting the LoPy. So! Almost there I guess.. :) But still;

Any last tricks?

[bucknall]

Hi @hjl,

We'll be releasing an update for our firmware update tool (later this month) that will automatically let you update via the pytrack/pysense.

For the time being, you can try this method to update the lopy via the Pytrack -

1. Open the Firmware Update Tool and set the speed to low speed.
2. Ensure that GND and P2 (G23) are connected
3. Reset the LoPy (press the reset button on the LoPy)

It's a little difficult to do at the moment so we're planning to make it easier but with a bit of practice, this method does work!

Thanks,

Alex

[jmarcelino]

@hjl
That means the LoPy is not in firmware update mode.

You do need to start it (power up or reset) mounted on the Pytrack and with the P23-GND connection in place.

On the Pytrack that is difficult because you either need to precariously "touch" the a bit of wire to the pins (risking a short-circuit), use test "grabber" clips to grab onto the pins which not everyone has, or place the LoPy on a breadboard and then run jumper wires between the pins on the Pytrack to the corresponding LoPy pins on the breadboard (just 5V power, GND, P0 and P1 should be enough)

[hjl]

I use the 'grabbers'. The Pycom Updater doesn't seem to work unfortunately. And now I can confirm that I am in the right mode:

And I have some progress:

But the monitor gives this:

So I think something went wrong while upgrading?

[jcaron]

@hjl using the same method but at 57600 usually works for me. Not sure if that makes any difference.

[hjl]

@hjl Tried different rates as well..!

[hjl]

@bucknall The preconfigured serial port in the updater tools doesn't match my serial port.

cu.
tty.

difference...? I connect with an adapter through a USB-C port.

[hjl]

@hjl @bucknall @jmarcelino any ideas?

[jmarcelino]

@hjl
You usually get a cu. and tty. port on macOS (actually it's a BSD thing, so the same for FreeBSD and other *nixes) they should be effectively the same thing other than historical differences.

To be honest I never managed to upgrade the firmware using the Pytrack on high or low speed - neither worked - but I haven't tried in latest Pytrack firmware.

[bucknall]

Hi @hjl,

Apologies for the slow reply, I've been out of office for the last few days.

I've just tried the update procedure with a Pysense and LoPy, without any problems. I'll try it again with a Pytrack but the firmware is practically identical for the two shields.

Have you updates the firmware on your Pytrack Shield? If you're using an older version of the firmware then this might be preventing you from updating.

Thanks,

Alex

[hjl]

@bucknall Hi, I've use the dfu-util to upgrade it with the 0.0.4 version and that seemed to be going OK..

[hjl]

@bucknall But still experiencing upgrade problems for the lopy..

[bucknall]

Hi @hjl,

What seems to be the issue? Is it still not going in firmware upgrade mode?