Silicon Laboratories EM34 Series User manual

UG113
Rev 0.1 Copyright © 2015 by Silicon Laboratories UG113
EM34X DEVELOPMENT KIT USER’S GUIDE
Contents
1About This Guide............................................................................................................................................ 4
1.1 Purpose................................................................................................................................................... 4
1.2 Audience.................................................................................................................................................. 4
1.3 Documentation Conventions..................................................................................................................... 4
2Introducing the EM34x Development Kit.......................................................................................................... 4
2.1 Overview.................................................................................................................................................. 4
2.2 Development Kit Contents........................................................................................................................ 5
2.3 Hardware Requirements .......................................................................................................................... 5
2.4 Software Requirements............................................................................................................................ 5
2.5 Hardware................................................................................................................................................. 5
2.6 Software .................................................................................................................................................. 6
2.7 Documentation......................................................................................................................................... 6
2.8 Before You Begin..................................................................................................................................... 7
3Development Kit Components......................................................................................................................... 7
3.1 Overview.................................................................................................................................................. 7
3.2 Hardware................................................................................................................................................. 8
3.2.1 EM341 Remote Control..................................................................................................................... 8
3.2.2 EM35x Breakout Board ....................................................................................................................10
3.2.3 EM34x Modules ...............................................................................................................................11
3.2.4 Debug Adapter (ISA3)......................................................................................................................12
3.3 Acceptable Power Sources for Normal Operation....................................................................................12
3.3.1 USB Power Supply with Adapters.....................................................................................................13
3.4 Software .................................................................................................................................................13
3.4.1 Network Stack..................................................................................................................................13
3.4.2 Hardware Abstraction Layer.............................................................................................................13
3.4.3 Sample Applications.........................................................................................................................14
3.4.4 Ember Desktop ................................................................................................................................15
4Setting up Hardware Components..................................................................................................................16
4.1 Overview.................................................................................................................................................16
4.2 EM34x Radio Communications Module (RCM)........................................................................................16

UG113
2 Rev. 0.1
4.3 Hardware Connections............................................................................................................................16
4.4 Connecting the Breakout Board and RCM...............................................................................................17
4.5 Breakout Board Power Configurations.....................................................................................................17
4.6 Breakout Board Serial Configurations......................................................................................................19
4.7 Common Hardware Configurations..........................................................................................................19
4.8 Connecting the RF Cable to the RCM......................................................................................................24
5Installing the Software....................................................................................................................................25
5.1 Overview.................................................................................................................................................25
5.2 Installing the Ember Stack.......................................................................................................................25
5.3 Installing Ember Desktop.........................................................................................................................25
5.4 Installing IAR Embedded Workbench for ARM.........................................................................................25
5.5 Installing the Debug Adapter (ISA3) Utilities ............................................................................................25
5.6 Installing FTDI USB Drivers.....................................................................................................................26
6Using the Debug Adapter (ISA3)....................................................................................................................26
6.1 Overview.................................................................................................................................................26
6.2 Connectivity and Power...........................................................................................................................26
6.3 Ethernet Settings ....................................................................................................................................27
6.4 Using the Admin Interface over USB .......................................................................................................27
6.5 Using the Admin Interface over Ethernet .................................................................................................27
6.6 Using the Serial Ports..............................................................................................................................28
6.7 Updating the Firmware............................................................................................................................28
7Debug Adapter (ISA3) Commands .................................................................................................................29
7.1 Syntax Conventions................................................................................................................................29
7.2 Entering Commands ...............................................................................................................................29
7.3 Command List.........................................................................................................................................29
7.3.1 button...............................................................................................................................................29
7.3.2 debug...............................................................................................................................................30
7.3.3 config...............................................................................................................................................30
7.3.4 connections......................................................................................................................................30
7.3.5 help..................................................................................................................................................30
7.3.6 hostname.........................................................................................................................................31
7.3.7 ip......................................................................................................................................................31
7.3.8 port ..................................................................................................................................................31
7.3.9 power...............................................................................................................................................31
7.3.10 reset ................................................................................................................................................32

UG113
Rev. 0.1 3
7.3.11 usbaddr............................................................................................................................................32
7.3.12 version.............................................................................................................................................32
8Software Tools Overview................................................................................................................................33
8.1 Running the remote control sample application........................................................................................33
8.2 Programming your Application on the EM34x..........................................................................................35
8.3 Programming Manufacturing Tokens.......................................................................................................36
8.3.1 Programming Certificates & Installation Codes.................................................................................36
8.4 Using the Debugger in IAR Embedded Workbench with an Ember Debug Adapter (ISA3).......................36

UG113
4 Rev. 0.1
1 About This Guide
1.1 Purpose
This document describes the EM34x Development Kit and explains how to set up its hardware and use the Ember
Debug Adapter (ISA3). For information on developing and debugging applications with Ember Desktop, see its on-
line HTML help.
See section 2.7, Documentation, for a list of other EM3xx documents of interest.
1.2 Audience
This document is intended for embedded software and hardware engineers who are responsible for developing
wireless applications with the ZigBee Remote Control (ZRC) Development Kit. This document assumes that the
reader has a solid understanding of embedded systems design and programming in the C language. Experience
with networking and radio frequency systems is useful but not expected.
1.3 Documentation Conventions
Notation
Meaning
Example
Italics Identifies on-screen software menu
options. Connect
UPPERCASE Identifies a keyboard key. ENTER
Right-angle bracket Delimits a series of software program
menu options to be clicked. Open > Save
Courier Identifies software code and, in body text,
variables. void Main(String[] argv)
the buffer variable
Courier Italics
Identifies a variable name.
ipAddress
2 Introducing the EM34x Development Kit
2.1 Overview
The EM34x Development Kit is used for evaluation and application design and development. The Development Kit
contains a variety of hardware for quickly creating a prototype of the customer’s hardware, EmberZNet, Silicon
Labs' implementation of the ZigBee ZRC stack software specification, and various development tools that enable
the development of the customer’s application software.
EmberZNet runs on top of an IEEE 802.15.4-compliant radio and link layer software. Combined with the powerful
IEEE 802.15.4 compliant EM34x radios, the EmberZNet network stack provides complete networking services from
the physical layer up to a reliable application profile support layer. The stack produces ZRC networks that are
reliable, flexible, secure, and easy to use.
EmberZNet provides a common Application Programming Interface (API) that utilizes the underlying layers. This
API provides support for the following layers of the Open System Interconnection Reference Model (OSI Model):
•PHY: radio control
•MAC: medium access
•NETWORK: routing, association
•APPLICATION: Application Profile Support for reliable message delivery
The Development Kit includes Ember Desktop, which facilitates application development and debugging. The
Debug Adapter (ISA3) incorporates Power-over-Ethernet (PoE) capability, which can simplify node deployment in

UG113
Rev. 0.1 5
the test environment. The Breakout Board provides a direct connection for debugging customer-designed
hardware, while the remote control provides a low cost, form factor reference design. For detailed information
about the EM35x Breakout Board, see document TS6, EM35xx Breakout Board Technical Specification.
2.2 Development Kit Contents
Table 1 summarizes the components and the specified count for each component in the EM34x Development Kit.
Table 1. EM34x Development Kit Components
Component
EM34x Development Kit
EM341 Remote Control 1
Debug Adapter (ISA3) 1
EM35x Breakout Board 1
EM34x Modules
4
Data Emulation Interface (DEI) Cable 1
Packet Trace Port Cable 1
Radio Frequency Cable 1
EM34x Quick Start Guide 1
AA Batteries 2
Ethernet Cable 1
USB Cable
1
USB Power Brick 1
2.3 Hardware Requirements
•PC with Ethernet connectivity
•Network hub with DHCP server
2.4 Software Requirements
•Microsoft Windows XP or Windows 7
•Java, version 1.6 or later
•Adobe Acrobat Reader (available free from http://get.adobe.com/reader/)
2.5 Hardware
•Remote Control provides a low cost, single-sided, form factor reference design. The remote is programmable
via the Packet Trace connector and Debug Adapter (ISA3). It provides an ideal solution to quickly prototype
and develop a fully functioning ZRC remote control application
•Breakout Board serves as a test bed for network hardware and applications. The Breakout Board will have an
associated EM34x Module, which can be deployed as a node within a network application. The Breakout Board
connects with a Debug Adapter (ISA3) through two communication links: the Packet Trace Port and the DEI
Port. This allows the Breakout Board’s EM34x Module to interface with Ember Desktop through the Debug
Adapter (ISA3)’s Packet Trace Port and its wired Ethernet connection. These interconnections are described
later in this chapter. The Breakout Board also has a prototype breadboard area for application-specific
hardware development.
•EM34x modules contain the EM34x System-on-Chip (SoC) solution providing a complete radio and
microcontroller solution. The kit includes both EM341 (ZRC Controller) and EM346 (ZRC Target) module
variants.

UG113
6 Rev. 0.1
•Debug Adapter (ISA3) connects a Breakout Board to the Ethernet. The adapter transmits network data
collected through its Packet Trace Port and conveys it over its Ethernet connection to Ember Desktop. It also
picks up any messages or new software that is addressed to the Breakout Board.
The Packet Trace Port is a cabled communication link between the Debug Adapter (ISA3) and the EM34x Module
mounted on the Breakout Board. It can also be used to program the remote control.
•Packet Trace Port Cable connects Debug Adapter (ISA3) to a Breakout Board.
•USB Power Supply with Adapters power the Breakout Board and/or Debug Adapter (ISA3) from wall socket.
•Ethernet Cable connects the Debug Adapter (ISA3) to an Ethernet subnet.
•Data Emulation Interface (DEI) cable provides a peripheral interface connection between the Debug Adapter
(ISA3) and Breakout Board. The DEI cable supports UART functionality.
2.6 Software
After registering for ZigBee software access on the Silicon Labs technical support portal, the software components
can be obtained online through the “Software Releases” tab. Refer to the QSG100 for information on downloading
the latest version of the software via Silicon Labs’ technical support portal, https://siliconlabs.force.com.
•Ember Desktop
•EmberZNet
•ISA3 Utilities (drivers and executables to manage the Debug Adapter (ISA3)
•IAR Embedded Workbench for ARM
Licenses and support are provided separately and can be obtained from IAR Systems at http://www.iar.com.
Note: The appropriate IAR Embedded Workbench version varies with the revision of EmberZNet. Check the
release notes to verify which IAR compiler version you should use.
2.7 Documentation
QSG100, the EM34x Development Kit Quick-Start Guide,is shipped with the EM34x Development Kit. All other
documented listed below are available from Silicon Labs’ website (www.silabs.com) via the Search toolbar as
Adobe PDF files or as on-line HTML help:
•The Ember Application Development Fundamentals series (UG103)
•Testing and Debugging Applications for the Ember EM2xx and EM35xx Platforms (UG104)
•Advanced Application Programming with the Stack and HAL APIs (UG105)
•EM35x Breakout Board Technical Specification (TS6)
•EM3xx Module Technical Specification (TS8)
•Ember Debug Adapter (ISA3) Technical Specification (TS7)
•EM341 Remote Control Reference Design
•EM341, EM342 and EM346 Data Sheet
•Ember Desktop on-line HTML help
•Application notes (various)

UG113
Rev. 0.1 7
2.8 Before You Begin
The EM34x Development Kit is designed only for the operating conditions and interfaces specified in documents
TS7, Debug Adapter (ISA3) Technical Specification, TS6, EM35x Breakout Board Technical Specification, and
TS8, EM3xx Module Technical Specification. Any modifications or alterations to the hardware are liable to cause
irreparable damage to the EM34x Development Kit, and shall render its warranty null and void.
If you wish to use the EM34x Development Kit in a non-standard fashion, consult with Silicon Labs Customer
Support or Sales before starting custom development. This is especially true if you are embarking on an aggressive
development cycle, plan to use custom hardware, or wish to use alternate software configuration files, images, or
hardware configurations. Contact us and describe your plan, so we can help you minimize the risk of delays in your
development cycle.
3 Development Kit Components
3.1 Overview
Figure 1 shows the key components in the EM34x Series Development Kit.
Figure 1. EM34x Series Development Kit
This chapter describes the hardware and software components in the EM34x Series Development Kit.

UG113
8 Rev. 0.1
3.2 Hardware
The EM34x Series Development Kit development board set has four major hardware components:
•EM341 Remote Control
•EM35x Breakout Board
•EM34x Modules
•Debug Adapter (ISA3)
The EM34x Series Development Kit also includes the following components:
•USB Power Adapter
•Miscellaneous Cables (Ethernet, USB, DEI, Packet Trace Port, and RF Coax)
3.2.1 EM341 Remote Control
The Remote Control has the following features:
•47 buttons
•Bi-color backlit Power button
•Packet Trace connector (under battery cover)
•Powered by 2x AAA batteries
The case is secured by 8 locking tabs (see figure for approximate location). Care should be taken if opening the
case as the tabs may break. The remote must be in the case for the batteries and keyboard to function properly.

UG113
Rev. 0.1 9
Figure 2. Remote Control
For information about the Remote Control, see the reference design files at
http://www.silabs.com/products/wireless/zigbee/Pages/zigbee-reference-designs.aspx

UG113
10 Rev. 0.1
3.2.2 EM35x Breakout Board
Figure 3. EM35x Breakout Board
The Breakout Board (Figure 3) has the following components:
•External power supply connectors
•One DB-9 serial port connector for RS-232 serial communication
•One USB connector for EM35x SC1 virtual COM port serial communication
•One header with TTL-compliant UART signals for EM35x SC1 SPI serial communication
•A buzzer, two buttons, two LEDs, and a temperature sensor for application development purposes
•Hardware reset buttons for the EM34x module
•Prototype or bread-boarding area (28 x 20, 0.1” pitch array) for application-specific hardware development
•One data emulation interface connector
For detailed information about the Breakout Board, see document TS6, the EM35x Breakout Board Technical
Specification.

UG113
Rev. 0.1 11
3.2.3 EM34x Modules
The EM34x Series Development Kit Module pictured in Figure 4 is used together with the Development Kit
Breakout Board to prototype customer hardware, and to develop and debug application software. Its low-power
design represents a good starting point for your own product design.
Figure 4. EM35x Breakout Board with EM34x Module installed
The EM34x Module includes these components:
•The Ember EM34x SoC (IEEE 802.15.4-compliant, 2.4 GHz radio transceiver with ARM®Cortex-M3
microcontroller).
•All off-chip components required for optimum SoC performance
•Two LEDs
•Packet Trace Port connector
For detailed information about the modules, see document TS8, the EM3xx Module Technical Specification.
Once you move away from the EM3xxx Module and toward application-specific hardware, refer to the extensive
Ember reference design library at http://www.silabs.com/products/wireless/zigbee/Pages/zigbee-reference-
designs.aspx. Each reference design provides a schematic, Bill of Materials (BOM), characterization data, and
layout files. They are designed and delivered in a manner that reduces both time to market and hardware
implementation risk. For assistance in locating the best design for your needs, contact support at
www.silabs.com/zigbee-support.
EM34x Module

UG113
12 Rev. 0.1
3.2.4 Debug Adapter (ISA3)
The Debug Adapter (ISA3) provides an efficient and configurable debug interface to the Development Kit Breakout
Board for processing emulation and debug commands. It also provides an interface to Ember Desktop for
monitoring and managing network data.
The Debug Adapter (ISA3) has the following components:
•Debug Port interface to the Breakout Board’s Extended Debug Interface Connector
•Packet Trace Port interface to the radio communication module, providing programming and debugging
services
•TCP/IP 10/100 Ethernet interface with Power-over-Ethernet functionality
•USB Interface
3.3 Acceptable Power Sources for Normal Operation
Table 2 lists all of the components and the acceptable combinations of power sources that yield normal operation
for the EM35x Breakout Board. Potential power sources include the following:
•Power-Over-Ethernet (PoE) Switch
•USB cable
•Connected to PC
•Connected to USB Power Supply with Adapters
•Power over Packet Trace Port on Debug Adapter (ISA3) (the target power select switch on the front panel must
be set to Int (Internal)).
•From RCM dedicated power
•External dc adapter (not supplied with the Development Kit)
Table 2. Safe Combination of Operating Power
PoE External DC
Packet
Trace Port
USB
Breakout
Board
Debug Adapter (ISA3) X N/A N/A X N/A
EM34x Module N/A N/A X1N/A X
EM35x Breakout Board N/A X2X3X N/A
Notes:
1. Power is sourced from the Debug Adapter (ISA3) to the RCM module using the Packet Trace Port cable
connected to the Debug Adapter (ISA3) with its target power select switch set to Int (Internal).
2. External dc power between 4 V and 20 V can be connected to clip leads J1 (+) and J32 (-) on the EM35x
Breakout Board.
3. Power is sourced from the Debug Adapter (ISA3) to the EM35x Breakout Board using the Packet Trace
Port cable connected to the Debug Adapter (ISA3) with its target power select switch set to Int
(Internal).

UG113
Rev. 0.1 13
3.3.1 USB Power Supply with Adapters
The USB power adapter (Figure 5) is a linear regulated wall plug power supply with 5 V dc at 1 A regulated output.
It has a USB type-B connector for connecting power via a USB cable to the USB port of the Debug Adapter (ISA3)
or Breakout Board. Four interchangeable snap-in input plugs are provided with various port configurations suitable
for various locales: North America, Europe, United Kingdom, and Australia.
Figure 2. USB Power Supply with Interchangeable AC Adapters
3.4 Software
The EM34x Development Kit provides customers with access to the following software components:
•Network Stack
•Hardware Abstraction Layer
•Ember Application Framework with sample scenarios
•Ember Desktop
3.4.1 Network Stack
The EmberZNet provides an advanced implementation of the ZigBee Remote Control 2.0 specification. ZigBee
Remote Control provides a global standard for advanced RF remotes that removes line-of-sight restrictions while
also delivering two-way communication and longer range
3.4.2 Hardware Abstraction Layer
The hardware abstraction layer (HAL) acts as a conduit between the network stack and the node processor and
radio. Separating network stack functionality from the specific hardware implementation enables easy portability.
HAL code is provided as a combination of pre-built libraries for complex, stack-critical functionality and C source
code that you can alter in order to customize, extend, or reduce device functionality across various hardware
platforms.

UG113
14 Rev. 0.1
3.4.3 Sample Applications
The Ember ZNET ZRC software contains sample applications. These demonstrate aspects of the ZRC stac kbased
on the ZRC 2.0 specification. Silicon Labs provides an IAR project and workspace file for each application as well
as a S.37 binary file. Table 4 lists the sample applications that are in the current distribution. All applications are in
the app directory.
Table 3. Development Kit Sample Applications
Application name Directory Description
ZRC 2.0 Controller ZRC
The ZRC2.0 controller application demonstrates basic ZRC network
functionality and ZRC2.0 application functionality. This application acts
as a generic remote control. It utilizes the ZRC Profile plugin to provide
core application-level ZRC functionality and the ZRC GDP and ZRC2.0
plugins to provide ZRC2.0-specific behavior.
ZRC 2.0 Target ZRC
The ZRC2.0 target application demonstrates basic ZRC network
functionality and ZRC2.0 application functionality. This application acts
as a generic target device. It utilizes the ZRC Profile plugin to provide
core application-level ZRC functionality and the ZRC GDP and ZRC2.0
plugins to provide ZRC2.0-specific behavior.
The target will automatically start the network. The controller is responsible for initiating pairing to an existing
network. The controller application will disable its receiver automatically to conserve power. This is representative
of a sleepy device that is generally a transmit-only device that acts when directed by the user (i.e., a button press).
The controller application is allowed to pair to two targets, i.e., a set-top box (STB) and a TV target. The target
application acts as either a STB or a TV target and can accept up to maximum 5 pairings.
Pressing and holding the PAIR button and then pressing the STB button on the controller will cause the device to
initiate the binding process to discover, pair and validate with a target.
Note: When remote control is connected to the Ember Adapter (ISA3), the controller firmware will auto-remap some
key-matrix GPIO pins for debugging and some buttons will not be available. The key combination for pairing when
debugging are changed as shown below:
•Press SETUP + TV keys to bind to the TV target
•Press SETUP + STB keys to bind to the STB target
The ZRC GDP and ZRC ZRC2.0 plugins manage discovery, pairing, and validation and notify the application when
binding completes. If the binding completes successfully, the controller can begin sending actions to the target.
Pressing the STB or the TV button switches the controller to STB or TV mode accordingly. Buttons pressed in STB
mode will be sent to the STB target and buttons pressed in TV mode will be sent to the TV. Depending on the
mode, either an RF or IR signal will be generated. Some keys (such as power) may send both an RF command
and an IR command.
When actions are sent, the ZRC ZRC2.0 plugin will keep track of timing in order to automatically repeat actions for
keys that are held down.
The target provides feedback by playing tunes. A rising two-tone tune indicates a successful operation while a
falling two-tone tune indicates a failure. A brief tone indicates that the device has performed a long-running action
and is waiting for a result.
All application code is contained in the ZRC-callbacks.c files within each application directory.

UG113
Rev. 0.1 15
3.4.4 Ember Desktop
Ember Desktop is a graphical tool incorporating a Network Analyzer utility that manages the Development Kit
hardware and displays network and node activity in real time (see Figure 6). It provides a rich and flexible interface
to Ember-embedded networks, which helps you develop and debug new network applications.
Ember Desktop includes these features:
•Ember AppBuilder, a tool for generating ZigBee-compliant applications, made up of the Ember application
framework and a graphical tool for configuring the included source code. Ember AppBuilder gives you an
interface for turning on or off embedded clusters and features in the code compiled into a finished application.
•An Integrated Development Environment (IDE) with multiple editor panes that provide tiered views of network
activity, letting you drill down from a high-level map of node interactions to the details of each packet.
•Customizable filters that let you specify exactly which network activities to display.
•Log files that save captured data, so you can step through transactions and events for detailed analysis.
•A file browser that lets you easily upload new applications to any connected node.
An Adapters view shown in Figure 6 allows you to interact with the Debug Adapter (ISA3) and RCM to download
new firmware, reset, and manage each of the devices.
Figure 3. Ember Desktop
For detailed information about Ember Desktop, refer to Ember Desktop’s on-line HTML help.

UG113
16 Rev. 0.1
4 Setting up Hardware Components
4.1 Overview
This chapter contains the following sections:
•EM34x Radio Communications Module (RCM)
•Hardware Connections
•Connecting the Breakout Board and RCM
•Breakout Board Power Configurations
•Breakout Board Serial Configurations
•Common Hardware Configurations
•Connecting the RF Cable to the RCM
4.2 EM34x Radio Communications Module (RCM)
The EM34x Series Development Kit contains various types of EM34x Radio Communications Modules designed by
Silicon Labs’ partner, California Eastern Laboratories (CEL). These modules contain either the EM341 or EM346 IC
and are configured to use either the PCB antenna or the on-board RF connector (U.FL). These configuration
options are noted in the Module Product Label, as shown the example label in Figure 7. This label can be found on
the bottom of the module. The top line contains the Silicon Labs Part Number, while the bottom line contains the
Module Serial Number. The Module Serial Number is also listed in the Hardware Identification List attached to your
Quick Start Guide. You can determine the EUI-64 of each module based on this list.
Figure 4. Module Product Serial Number Label
The module shipped already installed on the Breakout Board is module variant EM346-MOD-ANT-C. All other
module variants are contained in the EM34x Development Kit. Refer to Table 5 for configuration comparisons of the
modules included in your development kit.
Table 4. Module Product Variant Matrix
Silicon Labs Part
Number CEL Part Number
Silicon
Labs
Product
Number IC Antenna or Connector PA or non-PA
Qty
Included
in Kit
EM341-MOD-ANT-C ZICM341SP0-1-SL 0740 EM341 Antenna Non-PA 1
EM341-MOD-RF-C ZICM341SP0-1C-SL 0741 EM341 Connector Non-PA 1
EM346-MOD-ANT-C ZICM346SP0-1-SL 0742 EM346 Antenna Non-PA 1
EM346-MOD-RF-C ZICM346SP0-1C-SL 0743 EM346 Connector Non-PA 1
4.3 Hardware Connections
To avoid communication problems, verify that the radio communication module is firmly seated in its Breakout
Board connector, and its Packet Trace Port cable is properly seated.

UG113
Rev. 0.1 17
4.4 Connecting the Breakout Board and RCM
Refer to document EM34x Quick Start Guide, included in your development kit for detailed step-by-step instructions
for setting up your hardware.
CAUTION: Observe electrostatic discharge (ESD) precautions when removing, handling, or replacing RF
communication modules.
To remove the radio communication module:
Carefully pull the RCM away from the Breakout Board.
To attach the radio communication module:
Align the radio communication module to its footprint outline on the Breakout Board, and then press it into place.
Make sure that the RCM sits firmly in its mating connector.
To attach the Debug Adapter (ISA3):
1. Plug the Packet Trace Port cable into the Debug Adapter (ISA3).
2. Plug one end of the Packet Trace Port cable into the 10-pin Packet Trace Port (J31) on the Breakout
Board, and the other end into the Debug Adapter (ISA3). If desired, the Packet Trace Port cable may be
connected directly to the RCM instead of the Breakout Board, but the Breakout Board connector allows for
straight cable paths and more convenient swapping of modules.
3. Verify that the Debug Adapter (ISA3)’s Target Power Select switch is set to Int (Internal).
To remove the Debug Adapter (ISA3):
1. Unplug the Packet Trace Port cable from the Breakout Board (or radio communication module).
2. Unplug the Packet Trace Port cable from the Debug Adapter (ISA3).
4.5 Breakout Board Power Configurations
The Breakout Board may be powered in one of four ways:
•Breakout Board Power Supplied by Debug Adapter (ISA3) (Figure 8): The default configuration is to supply
power via the Debug Adapter (ISA3) and Packet Trace Port cable. Ensure the power switch on the Debug
Adapter (ISA3) is in the INT (Internal) position. The power supply of the Debug Adapter (ISA3) is also controlled
via the admin interface. You may need to connect to the admin port of the Debug Adapter (ISA3) and issue the
“power on” command. No external power supply should be connected to the Breakout Board when supplying
power from the Debug Adapter (ISA3). The power supply jumper on the Breakout Board should be in the

UG113
18 Rev. 0.1
horizontal position, connecting V_ISA to the center pin. The V_ISA LED (DS3) will illuminate when power is
applied.
Figure 5. Breakout Board Power Supplied by Debug Adapter (ISA3)
•Breakout Board Power Supplied by USB (Figure 9): The Breakout Board may also be powered through the
USB connector (J5), either using a USB cable plugged in to the USB power adapter included in the
development kit, or by connecting it to your PC. The power supply jumper on the Breakout Board should be in
the lower vertical position, connecting V_REG to the center pin. The V_FTDI LED (DS2) will illuminate when
power is applied. When powering the Breakout Board in this way, ensure the power switch on the Debug
Adapter (ISA3) is in the EXT (External) position.
Figure 6. Breakout Board Power Supplied by USB (J5)
•Breakout Board Power Supplied by DC Jumpers (Figure 10): The Breakout Board may also be powered by an
external power source that provides 4-20 V dc. The power supply should be connected to jumpers J1 (+

UG113
Rev. 0.1 19
supply) and J32 (ground). The power supply jumper on the Breakout Board should be in the lower vertical
position, connecting V_REG to the center pin. The VIN LED (DS1) will illuminate when power is applied. When
powering the Breakout Board in this way, ensure the power switch on the Debug Adapter (ISA3) is in the EXT
(External) position.
Figure 7. Breakout Board Power Supplied by DC Jumpers
4.6 Breakout Board Serial Configurations
Serial connectivity to the Breakout Board can be made in a number of ways. The default configuration of your
development kit will match your expected usage scenario.
•To use the pass-through UART feature of the Debug Adapter (ISA3):Plug the larger 12-pin DEI cable into
the DEI header on the Breakout Board and the connector on the Debug Adapter (ISA3). Ensure that jumpers
are installed across the 8th (PB2) and 10th (PB1) rows of headers next to the DEI port on the Breakout Board to
pass the UART RX and TX signals through. The serial port selection jumpers between the USB and DB-9
connectors should be removed, or placed on their center pins. Connection to the UART pass-through port can
then be made using either of the two options below:
a. Connect to the Debug Adapter (ISA3) using Ember Desktop. Launch the console. Choose the Serial 1
tab.
b. Run a terminal application (for example, Microsoft Telnet Client, HyperTerminal, PuTTY). Connect to
port 4901 on the Debug Adapter (ISA3).
•To use the RS-232 interface: Connect a serial cable to the DB-9 connector on the Breakout Board. Ensure the
four jumpers above the DB-9 connector are positioned towards the DB-9 connector to send the UART signals
to the RS-232 transceiver, and remove the jumpers from the row of headers next to the DEI port or make sure
the DEI cable is disconnected.
•To use the USB interface: Install the FTDI USB drivers as described in Section 5.6, Installing FTDI USB
Drivers, and connect a USB cable to J5 of the Breakout Board and to your PC. Ensure the four jumpers above
the DB-9 connector are positioned towards the USB connector to send the UART signals to the FTDI chip, and
remove the jumpers from the row of headers next to the DEI port or make sure the DEI cable is disconnected.
4.7 Common Hardware Configurations
Common configurations of the Breakout Board and Debug Adapter (ISA3) can be seen in Figure 13, Figure 14,
Figure 15 and Figure 16.

UG113
20 Rev. 0.1
Figure 8. Debug Adapter (ISA3) Supplying Power; Pass-through UART Being Used for Serial
Communication