Mk2 development kit technical manual - wless.ru1 x ETRX2HW Module with a Harwin 1.27mm pitch, 2x10...

Telegesis

TG-ETRX2DVKA/P-PM-01-200 1

ETRX2DVKA/P Development Kits Technical Manual 2.00

©2007 Telegesis (UK) Ltd ETRX2DVKA/P Technical Manual (Rev 2.00)

TG-ETRX2DVK-PM-01-200

ETRX2DVKA & ETRX2DVKP – TELEGESIS DEVELOPMENT KIT FOR ZIGBEE® TECHNOLOGY

TECHNICAL MANUAL

Telegesis

Telegesis




1 ETRX2DVKP Development Kit Functional Summary

Development Kit Contents

1 x ETRX2DV USB Development Board

1 x ETRX2HW Module with a Harwin 1.27mm pitch, 2x10 connector

1 x ETRX2 Module

1 x USB Cable Development Kit Features

The ETRX2DVKP is an ideal companion to the ETRX2DVKA in adding another USB development board to the prototyping environment. The additional ETRX2 module is ideally suited for integration into prototypes. The two ETRX2 development kits provide genuine quick and easy, out-of-the-box evaluation and application development, based on the Telegesis ETRX2 wireless meshing modules. They allow a simple demonstration of the capabilities of wireless meshing technology and provide a reliable platform for technology evaluation. Using the comprehensive AT style command interface and the simple-to-use Telegesis Terminal software package provided, they offer a low cost, high value introduction to ZigBee® technology. The Telegesis Terminal software – obtainable free of charge from www.telegesis.com – helps you to get started as quickly as possible and also offers visual tools for demonstration purposes.

The ETRX2DV USB Development Board

Size: 100mm x 80mm

On-board 3.3V voltage regulator

USB to serial bridge

Breakout of all pins of the ETRX2 module

4 LED‟s, 4 buttons, 2 analogue voltages and a beeper, all of which can be connected to the I/Os of the ETRX2 module

The ETRX2 Module is connected to the Development board by a 2x10, 1.27mm pitch Harwin connector

ETRX2 Module operating temperature range -400C to +850C

Suggested Applications

Technology evaluation

Application development

Proof-of-concept work

Prototyping

Customer demonstrations

Custom firmware development in conjunction with Ember development tools

The Telegesis ETRX2DVKP is a kit intended to either extend the number of nodes in a development network by another node with serial access via USB, or to be used as a standalone development tool used in conjunction with the supplied ETRX2 module (and potentially further modules) integrated into custom hardware.

http://www.telegesis.com/

Telegesis




2 ETRX2DVKA – Development Kit Functional Summary

The Telegesis ETRX2DVKA Development Kit has been designed to enable fast and simple evaluation and development of the low cost, low power, meshing solution provided by the ETRX2 modules.

Development Kit Features

The ETRX2DVKA Development kit provides genuine quick and easy, out-of-the-box construction of a working mesh network. Using the comprehensive AT Style Command Dictionary and the simple-to-use Telegesis Terminal software package provided, it should take less than an hour to set up a three-way mesh network and to begin detailed, in-depth assessment of the underlying Ember meshing technology. Included in the kit are both a full Development Board and two module carrier boards (MCB) with the following features: - 2 LEDs - 2 Buttons - On board 3.3V voltage regulator - Beeper - Light sensor - Temperature sensor These carrier boards allow you to quickly experiment with sensors and actuators and are ideal for demonstrations and prototyping. They can either be mains or battery powered. The module‟s serial interface can be accessed via pads or by plugging the MCB onto the development board, but this is not required as set-up and updates can be done over the air. Pin/Function table

I/O0 -- Button I/O1 -- Button I/O3 -- Beeper I/O5 -- Green LED I/O7 -- Red LED

Development Kit Contents

1 x ETRX2DV USB Development Board

1 x ETRX2HW Module with a Harwin 1.27mm pitch, 2x10 connector

2 x ETRX2MCB Module Carrier Boards fitted with ETRX2 Modules

2 x AA Battery Holders with leads

1 x USB Cable

The ETRX2DV USB Development Board

Size: 100mm x 80mm

On-board 3.3V voltage regulator

USB to serial bridge

Breakout of all pins of the ETRX2 module

4 LED‟s, 4 buttons, 2 analogue voltages and a beeper which can be connected to the I/O of the ETRX2 module

The ETRX2 Module is connected to the Development board by the 2x10, 1.27mm pitch Harwin surface mount header

ETRX2 Module operating temperature range -400C to +850C

Telegesis




Table of Contents

1 ETRX2DVKP DEVELOPMENT KIT FUNCTIONAL SUMMARY ............................. 2

2 ETRX2DVKA – DEVELOPMENT KIT FUNCTIONAL SUMMARY .......................... 3

3 ABSOLUTE MAXIMUM RATINGS OF THE DEVBOARD AND MCB .................... 6

4 OPERATING CONDITIONS OF THE DEVBOARD AND MCB ............................... 6

5 ELECTRICAL SPECIFICATIONS ........................................................................... 6

6 INTEROPERABILITY ............................................................................................. 6

7 OVERVIEW ............................................................................................................. 7

7.1 The Development Board ......................................................................................... 7 7.2 The Module Carrier Board (MCB) ............................................................................ 8 7.3 What is in the ETRX2DVKP box? ............................................................................ 8 7.4 What‟s in the ETRX2DVKA box? ............................................................................. 8

8 SETTING UP THE HARDWARE ............................................................................ 9

9 DRIVER INSTALLATION AND OPERATION ....................................................... 10

9.1 Windows 9x/XP/2k Driver Installation .................................................................... 10

9 DEVELOPMENT BOARD INTERFACE DESCRIPTION ....................................... 14

10 MODULE CARRIER BOARD (MCB) INTERFACE DESCRIPTION ...................... 16

11 APPLICATION SOFTWARE ................................................................................ 18

11.1 Software Set-up .................................................................................................... 18 11.2 Features of the Telegesis Terminal Application for ETRX2 ................................... 19 11.3 A Quick Start ......................................................................................................... 20 11.3.1 Network Setup ...................................................................................................... 20 11.4 Configuring Buttons for your Setup ....................................................................... 21

12 FIRMWARE UPGRADES ..................................................................................... 23

12.1 Firmware Upgrades via RS232 ............................................................................. 23 12.2 Over the Air Firmware Upgrades ........................................................................... 25 12.2.1 Cloning .................................................................................................................. 25 12.2.2 Recovering ............................................................................................................ 25 12.2.3 Recovering on the default channel ........................................................................ 25

13 DEVBOARD SCHEMATIC ................................................................................... 26

14 MODULE CARRIER BOARD SCHEMATIC ......................................................... 28

15 ETRX2 ORDERING INFORMATION .................................................................... 29

16 TRADEMARKS .................................................................................................... 30

17 DISCLAIMER ........................................................................................................ 30

18 CONTACT INFORMATION .................................................................................. 30

Telegesis




19 REFERENCES ..................................................................................................... 30

Telegesis




3 Absolute Maximum Ratings of the Devboard and MCB

Parameter Min. Max. Units Condition

Supply Voltage VDD -0.3 12 V

Voltage on any I/O pin -0.3 3.6 V

Storage Temperature range -50 150 °C

Table 1: Absolute Maximum Ratings

The absolute maximum ratings given above should under no circumstances be violated. Stress exceeding one or more of the limiting values may cause permanent damage to the device.

Caution! ESD sensitive devices. Precautions should be used when handling the device in order to prevent permanent damage.

4 Operating Conditions of the Devboard and MCB

Typical values at 5V 25°C.

Parameter Min. Typ. Max. Units Condition

Supply Voltage, VDD 4 5 6 V

Supply Current 120 mA TX with PA-Module

Operating ambient temperature range

-40 25 85 °C

Table 2. Operating Conditions

The voltage regulators used are protected against overtemperature and overcurrent.

5 Electrical Specifications See ETRX2 Product Manual

6 Interoperability

Please note that the R2xx Telegesis AT-Command line Interpreter is based on a private application profile and uses the Ember meshing and self-healing stack, so interoperability with wireless mesh networking solutions from other manufacturers is unlikely when using the default firmware. Interoperating with other solutions that use EmberZNet can be possible, but if this is a concern please contact us for advice.

Telegesis




7 Overview

The ETRX2DVKA/P development kits have been designed to allow quick evaluation and prototyping using the ETRX2 wireless mesh networking modules.

Two versions of the development kit are available, please see the functional summaries at the start of this document for full kit details. For a full evaluation of ZigBee® technology without using your own prototypes it is recommended to use more than a single development kit to set up an experimental network. The development kits are sold separately to provide the maximum flexibility for your prototyping needs.

This document is intended to describe the hardware and accompanying software of the development kits. To learn more about the usage of the ETRX2 module please refer to the following documents:

- TG-ETRX2-PM-01-xxx: ETRX2 Hardware manual - TG-ETRXn-R2xx-Commands: AT Style command dictionary for firmware R2xx - TG-ETRXn-UG-01-2xx: User Guide and how-to‟s for firmware R2xx

All our documents can be found at www.telegesis.com/support/documents.htm.

7.1 The Development Board

Figure 1: the Development board

The development board which is part of both development kits hosts a USB to serial bridge as well as voltage regulation circuitry. Furthermore it hosts a reset switch, a bootloader switch, 4 buttons, 4 LED‟s, 2 potentiometers to generate analogue input levels and a beeper, all of which can be connected to the I/Os of the module as described later in this document.

http://www.telegesis.com/support/documents.htm

Telegesis




7.2 The Module Carrier Board (MCB)

Figure 2: the MCB

7.3 What is in the ETRX2DVKP box?

- ETRX2DV Development Board - 1 x ETRX2 Module - 1 x ETRX2HW Module (with a 2x10, 1.27mm pitch SMT connector fitted) - 1 x USB Cable

7.4 What’s in the ETRX2DVKA box?

- ETRX2DV Development Board - 1 x ETRX2HW Module (with a 2x10, 1.27mm pitch SMT connector fitted) - 2 x ETRX2MCB Carrier Boards with fitted ETRX2 Modules - 2 x AA Battery Holders with leads - 1 x USB Cable

These packages contain everything you need to instantly set up an ETRX2 development platform using the enclosed modules. This approach can reduce costs significantly for applications where only a limited number of nodes are required for evaluation. If you require easy serial access to the AT-command line on two ends you should purchase two development kits, so that you can use the USB to serial bridges on two of the development boards.

The module carrier boards (of which there are two in the ETRX2DVKA) simply host a voltage regulator, two LED‟s, two buttons, a beeper, a light sensor and a temperature sensor.

The module carrier board is a cut down version of the development board and due to its small form factor is ideal to be powered using the attached battery packs and distributed in the field to evaluate mesh networking capabilities.

A 10 Way programming connector (X3) allows programming and in circuit debugging using an Ember InSight Adaptor or an Ember InSight USB programmer in case custom firmware is to be designed for the ETRX2 modules.

Telegesis




8 Setting up the Hardware

In the development kits there are three versions of the module. Both the ETRX2DVKA & P have an ETRX2HW which has an SMT connector on the bottom of the module so that it can be plugged directly into the appropriate 2x10, 1.27mm pitch receptacle on the devboard - Figure 3 & Figure 4.

Figure 3: 2x10 1.27mm SMT Connector Figure 4: 2x10 1.27mm Receptacle

Figure 5. 16 & 20-pin plugs with 16 & 20-pin sockets

Please note that earlier versions of the development kit were using a 2x8 connector instead of the 2x10 connector used on the current devboard.

In case you are using a module from a previous development kit with only a 2x8 pinheader connected to it, simply align the module so that the four unused connections point towards the antenna end of the devboard (Figure 5).

In analogy to this when connecting a module with a 10x2 pinheader to an old style development kit, just have the 4 unconnected pins sticking out at the antenna end.

The ETRX2DVKA comes supplied with 2 ETRX2 modules pre-connected to 2 ETRX2MCB carrier boards which enable you to quickly experiment with sensors and actuators and are ideal for demonstrations and prototyping. They can either be mains (via a suitable power supply) or battery powered. The module‟s serial port can be accessed via pads at the bottom of the MCB, or by plugging the MCB onto the development board as shown in Error! Reference source not found..

Telegesis




Finally a bare ETRX2 is provided with the ETRX2DVKP.

Figure 6. MCB plugged onto Devboard

9 Driver Installation and Operation

The ETRX2USB drivers obtainable from http://www.telegesis.com/ZigBee/Dsoftware.htm will generate a virtual com port allowing easy access to the serial port of the embedded ETRX2.

9.1 Windows 9x/XP/2k Driver Installation

The driver package should be unzipped into a local folder. When executing the file „PreInstaller.exe‟ prior to connecting the development kit using the provided USB cable an installer will guide you through the steps required for the driver installation. If prompted that the driver hasn‟t passed the windows logo test simply press „Continue Anyway‟.

http://www.telegesis.com/ZigBee/Dsoftware.htm

Telegesis




Figure 7. Found New Hardware Wizard

After connecting the devboard Windows® will prompt that new hardware has been found. If you have run the „PreInstaller.exe‟ windows will be able to install the driver by automatically as shown in Figure 8. In case you haven‟t run „PreInstaller.exe‟ you will have to manually point to the directory into which you have unzipped the driver.

Figure 8. Install software Automatically

If prompted that the driver hasn‟t passed the windows logo test simply press „Continue Anyway‟.

Telegesis




Figure 9. Windows Logo Test

After completing the installation of the USB device the new hardware wizard will start again in order to install the virtual com port in an identical manner.

Please note that each devboard has a unique serial number which requires the installation procedure to be repeated with every new devboard being attached to the computer. This allows multiple devboards to be used on the same computer at any one time.

In order to find out the identity/number of the virtual com port the devboard has been assigned to, please enter the Device Manager under the Windows Computer Management screen (see below) and click on the Ports (COM and LPT) section where you should find the new virtual com port. By double clicking on the entry of the virtual com port you can also change the number assigned to the virtual com port when entering the advanced setup of the device.

Telegesis




Figure 10. Device Manager

Once the correct COM port has been selected, the Telegesis Terminal software can be used to control the devboard as described in chapter 11.

Figure 11. Telegesis Terminal

Telegesis




9 Development Board Interface Description

Figure 1 shows the location of the connectors described below.

I/O breakout:

JP4 and JP5 give access to the I/O on the ETRX2 module. The individual pins are labelled on the circuit board.

Programming Connector:

The 10 way programming connector (JP1) was used to program ETRX1 modules, therefore it is not fitted on the ETRX2DVK.

An ETRX2 soldered onto the development board can be connected to an Ember InSight Adapter using X3 for programming and real time debugging of custom firmware.

Serial Port:

The serial port allows connectivity to a PC. This provides access to the command line interface and the bootloader for firmware upgrades.

Power Jumper: JP3 connects the ETRX2 module to the supply voltage. It is possible to measure the current consumption of the module across this jumper.

I/O connection: JP7 can be used to connect the I/O pins as shown in table 3. The two potentiometers can be used to vary the analogue input voltage of A/D1 and A/D2 between 0 and 1.2V.

Module connector: X2 is used to connect an ETRX2HW module using the attached 2x10 pinheader. It can also be used to connect a MCB.

Pin Devboard functionality Default

I/O0 Button4 connected



I/O3 Button1 or Buzzer Buzzer connected

I/O4 LED4 connected

I/O5 LED3 connected

I/O6 LED2 connected

I/O7 LED1 connected

A/D1 Analogue Voltage 1 connected

A/D2 Analogue Voltage 2 connected

Table 3. I/O Connectivity on development board

Reference Ground: JP7 is connected to the devboards ground plane. It can be used as a reference point when making measurements on the devboard.

Flow Control Selection: JP2 is used to connect the RTS and CTS lines used for the flow control to the host. By default flow control is disabled (see the AT command dictionary on how to enable it), so the default setting of JP2 does not connect those lines to the host as shown in Figure 12. When flow control is enabled JP2 must be set as shown in Figure 13. Please make sure the jumpers are only

Telegesis




set to this configuration in case flow control is enabled as otherwise I/Os driving against each other (via a protective resistor) will increase the current consumption.

Figure 12. No Flow Control (default) Figure 13. Flow control enabled

Telegesis




10 Module Carrier Board (MCB) Interface Description

Figure 2 shows the location of the connectors described below.

Power connector: Connect a power supply or battery pack from 4VDC to 6VDC here. The voltage is regulated down to 3.3V using a low drop voltage regulator.

RS232 Port: If required a connection to the module‟s serial port can be made via pads on the bottom of the MCB.

Pad MCB

1 3.3V

2 TXD

3 RXD

4 GND

Table 4. Serial Connectivity on MCB

where Pin 1 is the one nearest to the power connector.

Please note that to connect an MCB to a PC‟s serial port using these pads, level conversion of the RS232 signals is required via a MAX232 (or equivalent) circuit.

Alternatively the MCB can be plugged onto a devboard as shown in Error! Reference source not found. to gain access to the serial command interface.

The following table shows the connectivity of the ETRX2 module to the peripherals on board the MCB.

Pin MCB

I/O0 Button1

I/O1 Button2

I/O2 Not connected

I/O3 Beeper

I/O4 Not connected

I/O5 Green LED

I/O6 Not connected

I/O7 Red LED

A/D1 Light Sensor

A/D2 Temperature Sensor

Table 4. I/O Connectivity on MCB

JP2 can be used to disconnect A/D2 from the temperature sensor and force it to ground in order to make the ETRX2 enter bootloading mode after power-up or reset (see chapter 12). To do this place the jumper over the two pins nearest the power connector. For normal operation place the jumper so that it bridges the two pins furthest away form the power connector.

Finally X2 can be used to plug the MCB onto a development board in order to gain serial access to the module on-board the MCB. The pinout is illustrated in Figure 14 and Table 5.

Telegesis




Figure 14. X2 Pin Numbering

Pin Function

1 I/O8

2 I/O2

3 N/C

4 RESET

5 I/O1

6 I/O0

7 RXD

8 TXD

9 I/O10

10 I/O11

11 I/O9

12 N/C

13 GND

14 N/C

15 N/C

16 N/C

17 I/O6

18 N/C

19 I/O4

20 VCC

Table 5. Pinout of MCB

Telegesis




11 Application Software

The command line of the ETRX2 can be accessed using any terminal software program such as HyperTerminal®. Simply set up HyperTerminal® to connect to the appropriate com port at 19200bps, Data bits - 8, Parity - none, Stop bits - 1, Flow Control – none (ETRX2 factory default).

To speed up evaluation Telegesis provides its own Terminal Application Software program which allows enhanced functionality especially suited to the ETRX2 modules. The AT-Style commands can be issued by clicking on customisable „Command‟ buttons and all of the 64-bit serial numbers which are reporting in, are listed in a separate window. This means you will not need to input any of the 64-bit serial numbers.

For instructions on how to use the AT-Commands read the ETRX2 wireless meshing module user guide.

Figure 15. Appearance of the Telegesis Terminal Application Software

11.1 Software Set-up

After installing the Telegesis Terminal Application program the command buttons for the latest firmware R2xx will be shown at the bottom of the window. In order to use the Telegesis Terminal

Telegesis




software, select the correct COM port and the connection parameters (ETRX2 default 19200, 8 bits, no parity, no flow control) and press the connect button. These settings are automatically retained each time the software is re-started.

11.2 Features of the Telegesis Terminal Application for ETRX2

To make life easier all of the commands have been pre-defined and conveniently grouped at the bottom of the terminal window. Pressing a button (where no parameters are required) causes the corresponding command to be issued instantly. Where a parameter is required the command is shown in the Command bar and the required parameter can be entered manually. In order to issue the command from the command bar simply press the <enter> or the Send button. To see the parameters for a specific command, move and hold the mouse pointer over the chosen command button - Figure 16.

Figure 16. Screen tips for parameters

Every EUI64 number reporting in is listed in a separate window which can be opened or closed by clicking on the button labelled „Device List‟. If a device ID is required as a parameter in the command bar, simply double click on an entry in the device list and its EUI64 will be automatically transferred to the current cursor position of the command bar.

To allow for easier identification, the EUI64 IDs in the device list can be named. When right clicking on any EUI64 ID a name can be associated with the respective ID - Figure 17.

Figure 17. Device Naming

The application software also allows you to add custom command buttons and edit existing command buttons. New groups of commands can be created and command buttons can be moved between groups. To learn more about how to do this please refer to the help files of the Telegesis Terminal Software by selecting Help / Contents.

Telegesis




11.3 A Quick Start

This section gives you a quick introduction on how to get started

Power up the node connected to the PC and type AT followed by <enter>. If the communication to the module is working the module will prompt OK, if not check the USB connectivity and driver status and make sure you have connected to the correct COM port with the correct speed.

11.3.1 Network Setup

To establish a PAN network issue the AT+EN command, or alternatively press the „Establish PAN‟ button.

The local unit will now scan all available 16 channels and establish a PAN with a random PAN ID, on the quietest available one. This may take up to 16 seconds and leads to the node becoming the networks coordinator. When successful the module will prompt „JPAN:cc,PPPP‟, where cc is the channel number and PPPP is the PAN ID of the newly created PAN.

If you get an error message instead, it is likely that the module was already part of a PAN, so you will need to issue the AT+DASSL command or press the „Disas Local‟ button to leave the PAN before going back to starting a new one. In order to find out about the network status simply issue the AT+N command or press the „NWK Info‟ button.

Once the network is established, remote nodes can be powered up ready to join in. If you have serial access to remote nodes simply issue the AT+JN command or press the „Join any PAN‟ button, to join the newly established PAN. If you don‟t have serial access to the remote nodes (as is the case of the two MCBs provided with the DVKA) you will just need to wait for them to join the network automatically. By default, once every minute, all nodes (except coordinators) are set up to check whether there are any neighbours on the same PAN nearby, or if they have been orphaned. If no neighbours are found after 5 consecutive tries, the unit will leave the (deserted) PAN and try to join into a new one, once every minute.

This initial network set-up can take a few minutes, especially with no serial access to remote nodes, but once the network is set up it will remain set even after power cycles. New nodes joining will cause a prompt „NEWNODE: <EUI64>‟ on the remote side, (where <EUI64> is the unique 64 bit identifier of the device joining in) and display the JPAN message locally as described above.

Figure 18. Command Line Interactions

Telegesis




To learn more about setting up and maintaining a PAN please refer to the user guide and the AT Command Dictionary.

11.4 Configuring Buttons for your Setup

After setting up the network, press the button labelled „Configure‟ which will issue a command to scan the network causing all of the nodes in the network to report in. You will see that on discovery of a remote device its serial number is added to the device list window. In addition to this the configure functionality will build additional buttons for you to allow toggling the LEDs („LED x on‟ and „LED x off‟ in the Register Access Group) on a remote MCB as well as playing a tune on a remote devboard or MCB („Ident Node x‟ in the Test Commands Group).

By looking at the actual commands behind these new buttons it is quite easy to understand how the AT-Command interface operates. You can easily discover the basic principles of mesh networking. Simply move an MCB (or devboard) out of range (if you don‟t have enough space simply turn the transmit power down or put it behind a metal screen) and then add an MCB or devboard between the local node and the one which is out of range and you will find that the network has healed the broken link and all three nodes are accessible again.

If you have more than a single module connected to a PC try sending messages between the PCs using the Broadcast or Unicast buttons. This will begin to give you an understanding on how to integrate the ETRX2 into your application. The Telegesis Terminal Application also allows you to create custom command buttons for your individual application, just click on Commands / Add command button.

Telegesis




Figure 19. Using the buttons

For a more detailed description of the AT command interface please refer to the application notes and user guides for firmware revision R2xx.

Telegesis




12 Firmware upgrades

If required, the firmware of the ETRX2 modules can be upgraded serially as well as over the air.

12.1 Firmware Upgrades via RS232

In order to upgrade the firmware of the ETRX2 module using the serial bootloader, issue the “AT+BLOAD” command either by typing it in, or by pressing the respective button in the “Module Control” group of the Telegesis Terminal Application.

Alternatively the button labelled “Bload” can be pressed on the development board whilst the reset button is pressed and released.

After entering the bootloader, the connection parameters need to be changed to 115200bps, 8 data bits, 1 stop bit, no parity, no flow control (providing that it is not already set to these values). This is achieved by pressing the „Disconnect‟ button, changing the settings and then pressing the „Connect‟ button (if only the connection speed needs to be changed disconnecting and reconnecting is not required).

After pressing „Enter‟, the bootloader menu will be shown in the terminal window as shown in Figure 20.

Figure 20. Bootloader Menu

Telegesis




Pressing „1‟ initiates the upload of the new firmware and a number of „C‟ characters will indicate that the ETRX2 is ready to receive data. Within 60 seconds, select Tools / Transfer File… and browse for the new firmware file.

Firmware files for the ETRX2 will be in the format ETRX2_R2xxX.ebl. After checking that the protocol is set to XMODEM (128 Bytes), press the Send button and the new firmware will be downloaded as shown in Figure 21.

Figure 21. File Transfer Window

When the transfer has been completed successfully, press Enter again in order to return to the bootloader menu (shown in figure 10) and option „2„ to run the downloaded application software. If the application software has a baudrate other than 115200bps, this will need to be changed to the application baudrate as described above.

Telegesis




12.2 Over the Air Firmware Upgrades

On the ETRX2 over the air firmware upgrades became possible with revision R208X of the firmware. Upgrading is possible by cloning a local node‟s firmware to a remote node, so if a new firmware has to be introduced to the network it can be downloaded serially to a master node, which then can clone itself to one node after the other in turn given the target node is only a single hop away. Nodes with firmware R207X or older cannot receive new firmware via the AT+CLONE command, instead you must use AT+RECOVER on channel 13 as described below.

12.2.1 Cloning

In order to clone the local node‟s firmware use the command

AT+CLONE:<EUI64 of the target device>:<Target device’s password>

This will initiate the cloning process given the target node is only a single hop from the local node. After successful cloning the remote node will perform a reset and the local node will continue normal operation without reset.

12.2.2 Recovering

If the process of cloning is interrupted and fails the remote node will have incomplete firmware. In this case the remote node will remain in the bootloader and wait for a new application image. Using the command

AT+RECOVER

The local node will search for a remote node in boatload mode and clone the local firmware to that remote node.

12.2.3 Recovering on the default channel

If the target device gets reset or power cycled whilst in the bootloader, the unit will listen for new firmware files on channel 13. It is therefore required to set up a node on channel 13 and repeat the recovery action described in the previous section.

To Set up a node on channel 13 use the following commands:

AT+DASSL – leave the current network (will show an error if not currently part of a network) ATS00=0004 – Only allow channel 13 AT+EN – establish new network on channel 13

This will cause the local node to become a coordinator on channel 13.

AT+RECOVER

The local node will search for a remote node in bootload mode and clone the local firmware to that remote node.

Telegesis




13 Devboard Schematic

Telegesis




Telegesis




14 Module Carrier Board Schematic

Telegesis




15 ETRX2 Ordering Information

Table 6. Ordering Information

Ordering/Product Code Description

ETRX2

Telegesis Wireless Mesh Networking Module with Ember ZigBee® Technology:

Telegesis AT Style Command Interpreter based on

Ember‟s EmberZNet stack

Integrated 2.4GHz Antenna

No Harwin Connector

ETRX2HR

Telegesis Wireless Mesh Networking Module with Ember ZigBee® Technology:

Telegesis AT Style Command Interpreter based on

Ember‟s EmberZNet stack

Hirose U.FL Antenna Connector

No Harwin Connector

ETRX2DVKA

Telegesis Development Kit with:

1 x ETRX2HW Module with Board to Board Connector

1 x ETRX2DV Development Board

2 x ETRX2 Modules fitted onto

2 x ETRX2MCB Module Carrier Boards

1 x USB Cable

ETRX2DVKP

Telegesis Development Kit with:

1 x ETRX2HW Module with Board to Board Connector

1 x ETRX2DV Development Board

1 x ETRX2 Module

1 x USB Cable

Notes:

Customers‟ PO‟s must state the Ordering/Product Code.

There is no “blank” version of the ETRX2 Module available. All Modules carry the Telegesis AT style Command Layer based on the EmberZNet Stack. (Where customers wish to add their own firmware they can re-program the flash memory of the embedded EM250).

Please contact Telegesis if you require additional AT style commands or specific integration assistance.

Telegesis




16 Trademarks All trademarks, registered trademarks and products names are the sole property of their respective owners.

17 Disclaimer Product and Company names and logos referenced may either be trademarks or registered trademarks of their respective companies. All information is correct at time of issue. We reserve the right to make modifications and/or improvements to documentation or products without prior notification. Telegesis (UK) Ltd does not convey any license under its patent rights or assume any responsibility for the use of the described product.

18 Contact Information Website: www.telegesis.com E-mail [email protected] Telegesis (UK) Limited Marlow Business Centre 84 Station Road Marlow Bucks. SL7 1NX UK Tel: +44 (0)1628 894347 Fax: +44 (0)1628 894333

19 References Telegesis - www.telegesis.com Ember - www.ember.com

http://www.telegesis.com/

mailto:[email protected]

http://www.ember.com/

Date post:	07-Aug-2020
Category:	Documents
Upload:	others
View:	3 times
Download:	0 times

Mk2 development kit technical manual - wless.ru1 x ETRX2HW Module with a Harwin 1.27mm pitch, 2x10...

Documents