To update the firmware on the Pysense/Pytrack/Pyscan/Expansion Board v3, please see the following instructions. The firmware of Pysense/Pytrack/Pyscan/Expansion Board v3 can be updated via the USB port using the terminal tool,
There is currently no firmware update released for the new Pytrack 2.0 X and Pysense 2.0 X. Please do not try to flash these boards with firmware released for the old Version 1 hardware revision. The hardware revision is printed on the bottom of the shield.
The latest firmware DFU file can be downloaded from the links below:
Make sure to choose the correct firmware version for your expansion board. both 3.0 and 3.1 versions have version numbers in the silkscreen on the back of the board. See the image below for examples highlighted in Red
While in the normal, application mode, the Pysense/Pytrack/Pyscan/Expansion Board v3 require a Serial USB CDC driver, in DFU, bootloader mode, the DFU driver is required. Below, the USB Product ID is depicted for each case.
|Board||DFU bootloader (update mode)||Application firmware (normal mode)|
|Expansion Board v3||
Note: USB Vendor ID is always
$ brew install dfu-util
port install libusb dfu-util
Ubuntu or Debian:
$ sudo apt-get install dfu-util
$ sudo yum install dfu-util
$ sudo pacman -Sy dfu-util
To uploaded the latest DFU firmware to the Pytrack/Pysense, first install the DFU drivers to the host computer. Open Zadig and select
libusbK as the driver.
To install the drivers, the Pytrack/Pysense board must be in DFU-mode:
“Install Driverbutton immediately. If the driver was unsuccessful, repeat from step 1.
0xF014_for Pytrack or
Open the command prompt and navigate to the directory where the DFU-util and the firmware was downloaded (must be in same directory). Repeat the procedure to get the board in DFU-mode and run the command below but replace
X.X.X with the firmware version and replace Pysense with Pytrack if it is the Pytrack that is to be updated (e.g:
dfu-util-static.exe -D pysense_X.X.X.dfu
If the update was successful, a message,“Done!” should appear in the bottom of the command prompt.
Double-check Serial USB (CDC) driver is installed in Application mode: if, by mistake, the
libusbk driver was installed while the USB ID is the Application mode (
0xF013 for Pytrack or
0xF012 for Pysense), then the
Serial USB (CDC) driver has to be installed for application mode. This will allow Windows to allocate a COM port, which is required for REPL console.
To enter update mode follow these steps:
$ dfu-util -D pytrack_0.0.8.dfu
You might need to run
sudo. In that case, you will need to enter your password.
An output, similar to the one below, will appear upon successful installation:
dfu-util 0.9 Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc. Copyright 2010-2016 Tormod Volden and Stefan Schmidt This program is Free Software and has ABSOLUTELY NO WARRANTY Please report bugs to http://sourceforge.net/p/dfu-util/tickets/ Match vendor ID from file: 04d8 Match product ID from file: f014 Opening DFU capable USB device... ID 04d8:f014 Run-time device DFU version 0100 Claiming USB DFU Runtime Interface... Determining device status: state = dfuIDLE, status = 0 dfu-util: WARNING: Runtime device already in DFU state ?!? Claiming USB DFU Interface... Setting Alternate Setting #0 ... Determining device status: state = dfuIDLE, status = 0 dfuIDLE, continuing DFU mode device DFU version 0100 Device returned transfer size 64 Copying data from PC to DFU device Download [=========================] 100% 16384 bytes Download done. state(2) = dfuIDLE, status(0) = No error condition is present Done!
lsusb command, the Pytrack/Pysense device should be visible in both normal and bootloader modes.
For exemple, a Pytrack board is visible as either:
Bus 020 Device 004: ID 04d8:f014 Microchip Technology Inc. Application Specific Device
f014is USB PID), active just for 7-8 seconds, if the reset button was just pressed before plugging USB connector.
Bus 020 Device 005: ID 04d8:f013 Microchip Technology Inc. Pytrack Serial: Pyabcde0
f013is USB PID), this means the bootloader verified application partition and it boot-up correctly.