close
OpenRTLS
OpenRTLS
Search

Software:UpdateManually

Contents

Firmware Recovery

To update the RTLS software manually on the Master, Anchor and Tags, special software is needed. This is only provided to selected customers.

MAKE SURE YOU HAVE INSTALLED openocd-0.10.0 on your system !!!

Each Master contains a unique certificate which is used to access securely the OpenRTLS provisioning server. The same certificate should be reflashed (written) onto the Master.

All Anchors have the same firmware. They can be erased safely without loosing anything.

The Tag has calibration values stored in the AntBoot environment. Reflashing the Tag could remove the calibration data.

Connecting the device

All devices (Master, anchor and Tag) have a special 10-pins female JTAG/serial debug connector on the PCB. The programmer can be fitted onto this black connector. Make sure the GND pin is aligned.

File:Anchor programmer.jpeg

This programmer is a USB to JTAG/serial converter (2 channels). It has a micro-USB receptacle on it, 10-pins male connector and a reset button.

MS-Windows

FTDI based

After connecting it to a MS-Windows PC, some drivers could be needed:

Download FTDI drivers

After the drivers are installed, in the Device Manager the JTAG device (channel A) should be visible under "Universal Serial Bus controllers". The serial port under "Ports".

Connect a terminal (hyperterminal or puTTY) to this COM port.

Set the connection parameters to 115200, 8N1

ATMEL based

After connecting it to a MS-Windows PC, the programmer should pop up as serial port and HID device.

Connect a terminal (hyperterminal or puTTY) to this COM port.

Set the connection parameters to 115200, 8N1

Linux

FTDI based

On Linux the drivers are pre-loaded.

After connecting the programmer via a USB cable the device should be visible via the following command:

$ lsusb
Bus 002 Device 038: ID 0403:6010 Future Technology Devices International, Ltd FT2232C Dual USB-UART/FIFO IC

The following devices should exist:

/dev/ttyUSB0
/dev/ttyUSB1

Connect a terminal (e.g. picocom) to the serial device:

$ picocom -b 115200 /dev/ttyUSB1
ATMEL based

Instead of /dev/ttyUSB1 use /dev/ttyACM0

Master

Linux:

$ unzip v18xxyyzz.xip
$ cd v18xxyyzz/scripts
$ PRG=zzz ./reflash-oc8r-master.sh

For zzz fill in "jtag" for FTDI based programmers, and "swd" for ATMEL based programmers


MS-Windows:

C:\> unzip v18xxyyzz.xip
C:\> cd v18xxyyzz/scripts
C:\> reflash-master-full-zzz.bat


For zzz fill in "jtag" for FTDI based programmers, and "swd" for ATMEL based programmers

Follow the shell output and when finished, watch the terminal output to check if the Master starts up with the new firmware. The master will be only running the firmware loader and will accept DHCP. You can now upload the firmware using the python script in the root, or using the GUI applications as you would do normally.

Anchor

Open a command prompt or shell and start flashing:

Linux:

$ unzip v18xxyyzz.xip
$ cd v18xxyyzz/scripts
$ PRG=zzz ./reflash-oc8r-anchor.sh

for zzz fill in "jtag" for FTDI based programmers, and "swd" for ATMEL based programmers

MS-Windows:

C:\> unzip v18xxyyzz.xip
C:\> cd v18xxyyzz/scripts
C:\> reflash-anchor-full-zzz.bat

for zzz fill in "jtag" for FTDI based programmers, and "swd" for ATMEL based programmers

Follow the shell output and when finished, watch the terminal output to check if the Anchor starts up with the new firmware. The anchor will be only running the firmware loader and will update over the air as usual.

Tag

Open a command prompt or shell and start flashing:

Linux:

$ unzip v18xxyyzz.xip
$ cd v18xxyyzz/scripts
$ PRG=zzz ./reflash-tag-full.sh ../binaries/tagkiwi-antboot-ota-fwup.bin

for zzz fill in "jtag" for FTDI based programmers, and "swd" for ATMEL based programmers

MS-Windows:

C:\> unzip v18xxyyzz.xip
C:\> cd v18xxyyzz/scripts
C:\> reflash-master-full-zzz.bat

for zzz fill in "jtag" for FTDI based programmers, and "swd" for ATMEL based programmers

Follow the shell output and when finished, watch the terminal output to check if the Tag starts up with the new firmware.

Links

General information about OpenOCD:

For troubleshooting, check the following:

Good place to download ready-made binaries of the latest OpenOCD