Document name IP-DECT – Software Upgrade Author  Simon Smith Publish Date 01/09/2021 Version  1.0

 

 

1. Version Information 

 

 

Date Author Update Information  Version 01/09/2021 Simon Smith Initial

1.0

20/10/2021 Simon Smith Improved Images
Improved version branch information for the different levels of software.

1.01

03/02/2023 Simon Smith 6.10 software added

1.02

 

 

2. Document Purpose & History

 

This document describes the steps to upgrade GDC800 products, 130DB, 110H and 150DH to version 480.

 

The Software Download

The new 610 software download includes 610 Software for all components. All components are Version 610 Branch 1, except the GDC800R repeater which is 530 branch 2,  and the 130DB which is 610 Branch 101.

All intermediate software versions for older GDC800 installations are also included in the zip to allow older GDC800 installations to be upgraded to 480.

 

The Directory Structure of firmware has been included under the “FwuPath” folder. This document assumes you place the “FwuPath” folder from the zip  into the “C:” directory. This makes the root used for the TFTP server, “C:”. 

 

IP DECT Software Downloads can be found here. 

Setting up the TFTP Server Software

These instructions include screenshots from TFTPD64, as illustration. Similar steps can be taken in other TFTP servers, such as SolarWinds.

 

Our directory to be server is the “FwuPath” directory in C:.

 

Run TFTPD64 or TFPTD32 as Administrator. Choose Settings and in the General Tab, untick all services except for TFTP Server (you should avoid running a 2nd DHCP server on your customer’s network).

 

 
  

 

Change to the TFTP Server configuration tab. In here we will change the “Base Directory” to “C:”, where we have the “FwuPath” folder. The download of handset firmware can be very slow, to avoid timeouts, we need to increase the “Timeouts (Seconds)” from 3 to 10. 

 

 
 

 

In TFTPD main window, change the interface to the interface with the IP Address you are using for the IP-DECT network.

 

Graphical user interface, text, application Description automatically generated  
 

How the Base Requests Files to be Served

The most common reason that TFTP requests from the base fail to retrieve a file is a mismatch between the directory structure served by the TFTP Server, and the file requested by the product.

 

The product will request the file using the following TFTP path structure:

 

<prefix>/<product_dir>/<model_id>/<modelid>_v<major_version>_b<minor_version>.fwu

 

Where:

<prefix> is the value we place in the firmware path box, in the Firmware Upgrade page.

 

<product_dir> and <model_id> are hard coded into the specific devices.

 

<major_version> is the version we place in the “Required Version” Field. The version is padded on the left with “0” to 4 digits.

 

<minor_version> is the version we place in the “Required Branch” field. The branch is padded on the left with “0” to 4 digits.

 

The <product_dir> and <model_id> for the different products are given below. 

 

Product

Product Dir

Model ID

110DH

8430

8430

130DB

Electra

9430

150DH

8830

8830

GDC800B

Electra

Electra

GDC800B Version 440

Electra

8660

GDC800H

8630

8630

GDC800R

DECT4024

DECT4024

 

The <product_dir> and <model_id> for the different products are given above. 

 

The TFTP Server maps the requests to the root directory and changes the path to Windows compatible (the “/” become “”).

 

Example:

When Upgrading a GDC800B to version 480 branch 8, with a prefix of “FwuPath”, and the TFTP Server serving C: as its base directory. The following steps happen.

 

  1. The GDC800B Base requests the file /FwuPath/Electra/Electra_v0480_b0008.fwu.
  2. The Server changes the path seperators to “”.
  3. The server prefixes the base directory.
  4. The TFTP Server will look to serve the file C:FwuPathElectraElectra_v0480_b0008.fwu.

In TFTPD64, there is a Log tab. Here you can see the file requested by the product, and if the TFTP64 Server saw the request, and could find the file.

  • No incoming request.
    • Ensure you are on the same subnet as the Base. TFTP requires ALG/Helpers somewhere along the path to work through NAT.
    • Ensure the Save and Start button has been pushed.
    • Turn off any Firewall on the PC temporarily whilst the TFTP download takes place.
  • Incoming Request, but file not served.
    • Check the file exists. Check if the filename exists under the Base Directory, in the folders described by the path. 

Upgrade Steps

When upgrading the firmware for a customer follow the steps below.

Older GDC800 firmware only tracked required version, and no minor version, and the update page was slightly different.

Newer firmware includes a minor version number, the branch number. This must match the version the TFPT server will serve.

 

When upgrading the firmware for a customer use the following steps. 

 

  1. Set the Firmware update server, to the address where TFTPD is running, and Firmware path to FwuPath.
            On older versions of s/w you may need to click save/start update 

    On older versions of software, you may get the below screen and need to press Save/Start Update button at this stage before continuing


     

  2. Upgrade the Base. Set the Required version to the major version number for example 480, the branch to the minor version if there is a branch field, and press Save/Start.
     
     
  3. Change the Base Required version/branch to 0/0, if you are not upgrading handsets or repeaters press Save/Start Update now.
  4. If the upgrade type is Full, upgrade Handsets. The same note about major and minor version numbers apply.
     
     
    1. Handsets must be in their charger to upgrade. Do not remove whilst update is occurring.
    2. As handset upgrade, there status on the Extensions menu will change.
      A % – upgrade is in progress.
      Verify % – the firware is being checked before burning to Flash.
      Complete – The handset has been updated.
      off – The handset is not being updated.
       
       
  5. Change the Handset Required version/branch to 0/0. If there are no repeaters to update, press Save/Start now.
  6. If the upgrade type is Full, upgrade Repeaters. The same note about major and minor versions apply, For 480 firmware, branch version is 5, not 8. 
     

GDC 800

If you are running 440 software the steps above outline the process.

 

For older software, the update page behaves differently, these differences and the next version you must update to are detailed below.

GDC 800 (1323)

You must upgrade GDC 800 Version 1323 to 1324, before installing newer software. The update page is different on this version: 

  1. You need to explicitly tell the page to update all bases for multi-cell.
  2. Ony Required Version (1324) is used, not branch number.

GDC 800 (From Intermediate Version 1324)

We need to upgrade to intermediate version 1400. The upgrade page is the same as the version 1323, so configure to update the version to 1400.

 

 
 

GDC 800 (From Intermediate Version 1400)

We must upgrade to Version 440 Branch 4. You should also upgrade handsets and repeaters to 440,  before upgrading to 480. The upgrade page on this version is the same as 440 and 480.

 

Upgrade the base

 

 
 

 

Upgrade the Handsets

 

  
 

 

Upgrading the Repeaters (Needed from Intermediate Version 1400)

 

Upgrade the Repeaters, until version 440, repeaters used a different version scheme to the other products. We are upgrading to version 41, branch 1 – this becomes version 440. After this, when you upgrade to 480, the numbering scheme changes from 2 digit to 3 digit, with the version 480 branch 5.

 

  
 

GDC 800 (Intermediate Version 1400)

Follow the process at the beginning of the document to upgrade bases, hnadsets and repeaters to 480.

130DB

The 130DB Base station,110DH handset and 150DH handsets shipped with a minimum of 440 software. Follow the process at the beginning of the document to upgrade bases, hnadsets and repeaters to 480. 

 

Upgrade Path Summary

The download includes all previous versions required to upgrade from Version 1323 to 480, or from anywhere in between.

The steps above are summarised in the table below.

 

From Version

GDC800B Upgrade To

130DB Upgrade To

Upgrade Type

1323

800B: 1324

800R: 41 branch 1 (440 Eqiv)

N/A

Intermediate

1324

800B: 1400

800R: 41 branch 1 (440 Eqiv)

N/A

Intermediate

1400

800B: 440 branch 4

800H: 440 branch 4

800R: 41 branch 1 (440 Eqiv)

N/A

Full

440

800B: 480 branch 8

800H: 480 branch 8

800R: 480 branch 5

110DH: 480 branch 8

130DH: 480 branch 8

150DH: 480 branch 8

130DB: 480 branch 8

Full

480

 

800B: 610 branch 1

800H: 610 branch 1

800R: 530 branch 5

110DH: 610 branch 1

130DH: 610 branch 1

150DH: 610 branch 1

130DB: 610 branch 101

Full