UG110
Rev 1.0 Copyright © 2015 by Sili con Laboratories UG110
EMBER® EM35X DEVELOPMENT KIT USER GUIDE
This document describes the Em ber EM35x Dev elopment K it and explains how to set up it s hardware and use the
Debug Adapter ( ISA3). This revision also incl udes i nstr uc tions to get started developi ng applic ations usi ng the
EmberZNet PRO stack and for debugging appli c ations using Nodetest. For inf ormation about dev eloping
applications with other stac k s and prot oc ols, see QSG105, Getting Started wit h S ilic on Labs Wireles s Network
Software, and the help and documentati on included with your developm ent environment. For software installation
instr uc ti ons, see the stac k ’s release notes.
New in This Revision
Content r eor ganized. Updated to reflect kit updates and terminology changes.
Contents
1 About T his Guide ............................................................................................................................................ 4
1.1 Purpose ................................................................................................................................................... 4
1.2 Audience .................................................................................................................................................. 4
1.3 Documentation Conv entions..................................................................................................................... 4
2 Intr oduc ing the EM35x Development Kit .......................................................................................................... 4
2.1 Overview .................................................................................................................................................. 4
2.2 Support .................................................................................................................................................... 5
2.3 Documentation ......................................................................................................................................... 5
2.4 Hardwar e Requirements .......................................................................................................................... 5
2.5 Before You Begi n ..................................................................................................................................... 5
3 Development Kit Hardware Components ......................................................................................................... 6
3.1 Overview .................................................................................................................................................. 6
3.2 EM35x Breakout Board ............................................................................................................................ 7
3.3 EM 35x M odule ......................................................................................................................................... 8
3.4 Debug Adapter (ISA3) .............................................................................................................................. 9
3.5 O ther Kit Components .............................................................................................................................. 9
4 Accept able Power Sour c es for Normal Operation ............................................................................................ 9
4.1 Power-Over-Ethernet (PoE) Switch .........................................................................................................10
4.2 USB P ower Supply wit h Adapter s ............................................................................................................11
5 Setti ng up Har dware Components ..................................................................................................................13
5.1 Overview .................................................................................................................................................13
5.2 EM 35x Radio Communications Module (RCM) ........................................................................................13
UG110
2 Rev. 1.0
5.3 Connecti ng the Breakout B oar d and RCM ...............................................................................................14
5.4 Br eak out Board P ower Configurations .....................................................................................................15
5.5 Br eak out Board S eri al Configurat ions ......................................................................................................18
5.6 Common Har dware Configurations ..........................................................................................................19
5.7 Connecti ng the RF Cable to the RCM ......................................................................................................23
6 Using the Debug Adapter (ISA3) ....................................................................................................................24
6.1 Overview .................................................................................................................................................24
6.2 Connectivity and Power ...........................................................................................................................24
6.3 Et her net Settings ....................................................................................................................................24
6.4 Using the Admin Interfac e ov er USB .......................................................................................................25
6.5 Using the Admin Interfac e ov er Ether net .................................................................................................25
6.6 Using the Serial Ports..............................................................................................................................25
6.7 Updating the Firmw are ............................................................................................................................26
7 Debug Adapter ( ISA3) Commands .................................................................................................................26
7.1 Sy ntax Conventions ................................................................................................................................26
7.2 Entering Commands ...............................................................................................................................26
7.3 Command List .........................................................................................................................................27
7.3.1 button...............................................................................................................................................27
7.3.2 debug...............................................................................................................................................27
7.3.3 config ...............................................................................................................................................28
7.3.4 connections ......................................................................................................................................28
7.3.5 help ..................................................................................................................................................28
7.3.6 hostname .........................................................................................................................................28
7.3.7 ip......................................................................................................................................................28
7.3.8 port ..................................................................................................................................................29
7.3.9 power ...............................................................................................................................................29
7.3.10 reset ................................................................................................................................................29
7.3.11 usbaddr ............................................................................................................................................29
7.3.12 version .............................................................................................................................................30
8 Soft ware Tools Overview................................................................................................................................31
8.1 Using the EM35x Nodetest Application ....................................................................................................31
8.2 Running a Pack et Er r or Test ...................................................................................................................31
8.3 T esting Deep Sleep Cur r ent ....................................................................................................................32
8.4 Exam ple of Openi ng, Building, and Programming an Applicati on Buil der Scenario Applic ation for
EmberZNet PRO ...............................................................................................................................................34
8.5 Programming your Applicati on on the EM 35x ..........................................................................................35
UG110
4 Rev. 1.0
1 About This Guide
1.1 Purpose
This document describes the Em ber EM35x Dev elopment K it and explains how to set up it s hardware and use the
Debug Adapt er ( ISA3).
1.2 Audience
This document is i ntended f or em bedded soft ware and hardware engineers who are responsible for developi ng
wireless applicati ons with the Ember EM35x Devel opment K it. This document assumes that the r eader has a solid
understandi ng of embedded system s design and progr am m ing in the C language. Experience with networking and
radi o frequency systems i s usef ul but not expect ed.
1.3 Document ation Conventions
Notation Meaning Example
Italics I dentifies on-screen software menu
options. Connect
UPPERCASE Identifies a k eybo ard key. ENTER
Right-angle bracket Deli mits a series of software p r ogram
menu options to be clic ked. Open > Save
Courier Identifies software code and, in body text,
variables. void Main(String[ ] argv)
the buffer va riable
Courier Italics Identifies a va r iable name. ipAddress
Bold-underline Id entifies a lin k to a different section of
th e do cument Documentation
2 Introducing the EM35x Development Kit
2.1 Overview
The EM35x Developm ent Kit is used for applic ation design and devel opm ent. The Development Kit contai ns a
v ari ety of hardware for quic k ly c r eating a hardware prototype, links to Sili c on Labs stack software such as
EmberZNet or Silicon Labs Thread, and vari ous tools that enable the development of your appli c ation software.
In general, Silicon Labs’ stacks provide a co mmon API (Application Programming Interface) that supports the
following l ay er s of the OSI model (Open Sy stem Interconnection Ref er enc e M odel).
• PHY: radio contr ol
• MAC: medium access
• LINK: route discover y
• NETWORK: routi ng, associat ion
• APPLICATION: Application profile support for re liable mess age delivery
For example, the EmberZNet stac k is used to build ZigBee PRO-based appli c ations. Applicati ons that are built on
this stack benefit from the follow ing features:
• PHY and MAC lay er s comply with the IE E E 802.15.4-2003 standard
• LINK and NETW ORK lay er s comply with the l atest ZigBee PRO specification
• The APS l ay er provides the int erfac e to the applic ation for data transfer and managem ent, inc luding
rel iable transport and binding.
UG110
Rev. 1.0 5
The Development Kit includes a devel opm ent environment, such as Ember Desktop, which facilitates application
dev elopment and debugging. A compiler, such as IAR-EWARM, is also one of the kit ’s sof tware components.
Debug Adapter s (I S A 3s) incorpor ate Power-over-Ethernet ( P oE ) capabi lity, which can simplify node deployment in
the t est env ironm ent. Breakout Boards provide a direct connection for debuggi ng c ustomer-desi gned har dware . For
more information, see document TS6, the EM35x Breakout Board T ec hnic al S pec ificat ion.
2.2 Support
Once y ou r ec eiv e y our development kit, register to downl oad developm ent software on Silic on Labs’ tec hnical
support por tal, https://www.silabs.com/support/Pages/default.aspx. Use the support por tal to contac t Customer
Support for any questions you might hav e duri ng the developm ent process.
2.3 Documentation
QSG101, EM35x Development K it Quick Start Guide, is shipped with the EM35x Devel opm ent Kit. The stac k
installer provi des a documentation index (i n doc um entation/index.htm and also l inked from a Start Menu entr y ) that
contains link s to doc um entation loc ations and brief descri ptions of each document’s purpose. Documents are also
available through the support port al as Adobe PDF files.
2.4 Hardware Requirements
To use the EM 35x Development Kit y ou will need:
• PC with Ethernet connectivit y
• Network hub with DHCP server
2.5 Before You Begin
The EM35x Developm ent Kit is desi gned only for the operating c onditi ons and i nterfaces specif ied in documents
TS7, the Debug Adapter (ISA3) Technical Specification, TS6, the EM35x Breakout B oar d Technic al S pec ificat ion,
and TS8, the EM3x Module T ec hnic al S pec ificat ion. Any modific ations or alt erations to the hardware are l iable to
cause irreparable damage to the EM35x Development Ki t, and shal l r ender its warrant y null and void.
If y ou wish to use the EM35x Development Ki t in a non-standard fashion, c onsul t with Sili c on Labs Customer
Support or S ales before star ting custom dev elopm ent. This is especially true if you are em bar ki ng on an aggr essive
dev elopment cy cl e, plan to use custom har dware, or wish to use al ternat e software configuration files, images, or
hardware confi gur ations. Contac t us and describe your plan, so we can hel p y ou mi nim iz e the risk of delay s in your
dev elopment cy cl e.
UG110
6 Rev. 1.0
3 Development Kit Hardware Components
3.1 Overview
Figure 1 sho ws the components i n the EM35x Series Devel opm ent Kit.
Figure 1. EM35x Series Development Kit
The invent ory of development kit components is inc luded in the development kit’s Quick Start G uide ( UG101). This
section describes the use for eac h of t he maj or components.
The EM35x Developm ent Kit development board set has thr ee major hardware components:
• EM35x Breakout Board
• EM35x Module
• Debug Adapter ( ISA3)
The EM35x Developm ent Kit also includes the following components:
• US-to-Multinational AC Plug Power Adapter Ki t
• Power-Over-Ethernet (PoE) Swi t ch
• USB Power Adapter s
• Miscellaneous Cables (USB, DEI , Packe t Trace Port, and RF Coax )
UG110
Rev. 1.0 7
3.2 EM35x Breakout Board
Figure 2. EM35x Breakout Board
The Breakout Board (Figure 2) serves as test beds for network hardware and applicati ons. E ac h B r eak out Board
has an associ ated EM35x Module, whic h c an be deployed as a node wit hin a network applic ation. E ac h Breakout
Board connec ts with a Debug Adapt er ( ISA3) thr ough two communicati on link s: the Packet Trace Port and the DEI
Port. This allows the Br eak out Board’s EM35x M odule to interface wi th the developm ent environm ent t hr ough the
Debug Adapter ( ISA3) ’s Pack et T r ac e Port and its wi r ed E thernet c onnec tion. The Breakout B oar d also has a
prototype breadboar d ar ea for applicati on-specif ic har dware development.
The Breakout Board has the following component s:
• Exter nal power supply connec tors
• One DB-9 seri al por t connec tor f or RS-232 seri al c ommunication
• One USB connector for EM35x SC1 virtual COM port serial c ommunicati on
• One USB connect or for EM358x USB virtual COM port seri al communicati on
• One header wit h TT L-c om pliant UART signals for EM35x SC1 SPI serial communication
• A buzzer, two buttons, two LEDs, and a tem per ature sensor f or application development pur poses
• Exter nal serial flash for application bootloader pur pose s (via eit her EM35x SC1 or SC2)
• Hardware reset but tons f or the EM35x module
UG110
8 Rev. 1.0
• Prototype or bread-boarding area (28 x 20, 0.1” pitch array) for application-specific hardware developm ent
• One data emulation int erface connector
For detailed inform at i on about the Break out Board, see document TS6, the EM35x Breakout Board Technical
Specification.
3.3 EM35x Module
The EM35x Module (Figure 3) contains the Ember EM35x System-on-Chip (SoC) solution p roviding a complete
radio and microcont roller solution. All m odul es are pin-compati bl e, and they can be directly attached to a Breakout
Board. The kit includes both EM357 and E M 3588 m odule variants.
The EM35x module is used together with the Development Kit Breakout Board to prot otype customer hardwar e,
and to develop and debug application software. Its low-power de sign represents a good st art i ng point for your own
product design.
Figure 3. EM35x Breakou t Board with EM35x Module Installed
The EM35x Modul e i ncludes these components:
• The Ember EM35x SoC (IEEE 802.15.4-compliant, 2. 4 GHz radio transceiver wit h ARM® Cortex-M3
microcontroller).
• All off-chip components req ui red for optimum SoC perf ormance
• Two LEDs
• Packet Trace Port connector
EM35x Module
UG110
Rev. 1.0 9
For detailed information about the modules, see document TS8, the EM3x Module Technical Specif icat i on.
Once you move away f rom the EM35x Module and toward application-specific hardware, refer to the extensive
reference design li brary available through the Silicon Labs support portal. Each reference design provi des a
schematic, Bill of Materials (BOM), characterization dat a, and layout files. They are designed and delive red in a
manner that redu ces both time to market and hardware implementation risk. For assista nce in locating the best
design for your needs, contact Customer Support.
3.4 Debug Adapter (ISA3)
A Debug Adapter (ISA3) connects a Breakout B oard to the Ethernet. Each adapter transmits network data
collected through i ts Packet Trace Port and conveys it over its Ethernet connection to the dev el opm ent
environment. It also picks up any messages or new software that is addressed to this Breakout B oard. The ISA3
functions as a source-level debugger fo r E M 3x devices, providing single-stepping and brea kpoint support via IAR
EWARM.
The Debug Adapter (ISA3) provides an efficient and configurabl e debu g interfa ce t o t he EM35x Development K i t
Breakout Board for processing emulation and debug commands. It also provides an interface to the development
environment for moni t oring and managing net work data.
The Debug Adapter (ISA3) has the following compon ents:
• Debug Port interface t o the Breakout Board’s Ex tended Debug Interface Connector
• Packet Trace Port interface to the radio communi cat ion module, providing programming and debu ggi ng
services
• TCP/IP 10/100 Ethernet interface with Power-over-Et hernet functionality
• USB Interface
The Packet Trace Port is a cabled communicati on l i nk between the Debug Adapter (ISA3) and the E M 35x Module
mounted on the Breakout Board.
3.5 Other Kit Components
• Packet Trace Port Cables connect each Debug Adapter (ISA3 ) to a Breakout Board.
• AAA Battery Pack attaches to a Breakout B oard and enables deployment of battery-operated nodes.
• USB Power Supply with Adapters power Breakout Board s and / or Debug Adapters (IS A3s) from wall
sockets.
• Ethernet Cables conne ct Debug Adapters (ISA3s ) t o an E thernet subnet and the PoE Switch to your PC
or network.
• Data Emulatio n Interface (DEI) cables provide a peripheral i nt erface connection between the Debug
Adapter (ISA3) and Breakout Board. The DE I cable supports UAR T functionality.
4 Acceptable Power Sources for Normal Operation
Table 1 lists all of the components and the ac ceptable combinations of power sources that yi eld normal operation.
Potential power sour ces include the following:
• Power-Over-Ethernet (PoE) Switch
• AAA battery pack (3 VDC)
• USB cable
• Connected to PC
• Connected to USB Power Supply with Adapters
UG110
10 Rev. 1.0
• Power over Packet Trace Port on Debug Adapter (IS A3) (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 1. Safe Combination of Operating Power
PoE External DC A AA Batt ery
Pack Packet
Trace Port USB Breakout
Board
Debug Adapter (ISA3) X N/A N/A N/A X N/A
EM35x Module N/A N/A N/A X1 N/A X
EM35x Breakout Board N/A X2 X X3 X N/A
4.1 Power-Over-Ethernet (PoE) Switch
The EM35x Devel opm ent Kit contains a NETGEAR 8-port P ower-over-Ethernet (PoE) switch that supplies power to
a Debug Adapter (ISA3) over a standard TIA/EIA-568 category 5 cable. The Debug Adapt er (ISA3) can, in turn,
supply power to an EM35x Breakout Board and t he M odul e that is mounted on i t . Thus, you can place Breakout
Boards wherever an Et hernet cable connectio n i s av ailable.
The dc operating power for data terminal units is fed throu gh unused pairs 7/8 and 4/5. For more informati on about
the NETGEAR switch, see its online technical specifications.
The NETGEAR PoE Switch that is supplied in the EM35x Develop m ent Kit is certified by S i li con Labs. If you wish to
use a different PoE switch, consult Customer Support.
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 switc h set to Int (Internal).
2 External dc power betw een 4 V and 20 V can be connected to clip lea d s J1 (+) and J32 (-) on the EM35xx 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).
UG110
Rev. 1.0 11
The US-to-Multinat i onal AC Plug Power Adapter Kit (Figure 4) is a set of three power adapters for use with the
NETGEAR PoE S witch. These three interc hangeable plugs are provided with various port configurations suitabl e
for North America, Europe, the United Kingdom, and Australia.
Figure 4. US-to-Multinational AC Plug Power Adapter Kit
4.2 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 t he US B port of the Debug Adapter (ISA3)
UG110
12 Rev. 1.0
or Breakout Board. Four interchangeable snap-in input plugs are provided with various p ort configurations suit able
for North America, Europe, the United Kingdom , and Australia.
Figure 5. USB Power Supply with Interchangeable AC Adapters
UG110
Rev. 1.0 13
5 Setting up Hardware Com ponents
5.1 Overview
This chapter contains the following sections:
• EM35x Radio Communications Module ( RCM)
• Hardware Connect ions
• Connecting the Breakout Board and RCM
• Breakout Board Pow er Configurations
• Breakout Board Serial Configurations
• Common Hardware C onfigurations
• Connecting the RF Cable to the RCM
5.2 EM35x Radio Communications Module (RCM)
The EM35x Devel opm ent Kit contains various types of EM35x RCMs designed by S i l icon Labs’ partner, California
Eastern Laboratories (CEL). These modules contain either the E M357 or EM3588 IC and are configured to use
either the PCB antenna or the on-board RF connector (U.FL). Some module variants also include a power
amplifier. These configuration options are noted in t he Module Product Label, as shown the exam ple label in
Figure 6. This label can be found on the bottom of the module. The top line contains the Silicon Labs Part Nu m ber,
while the bottom line contains the Module Serial Number. The Module Serial Number is als o l i st ed i n the Hardware
Identification List attach ed to the QS G101, EM35x Development Kit Quick Start Guide. You can deter m ine the EUI-
64 of each module based on this list.
Figure 6. Module Product Seri al Number Label
UG110
14 Rev. 1.0
The modules shipped already installed on Breakout Boards are module variant EM3588-M-AN-C. Other module
variants are cont ained in the Module Variety Pack. Refer to Table 2 for configuration comparisons of the modules
included in your development kit.
Table 2. Module Product V ari ant Matrix
Silicon Labs Part Number CEL Part Number
Silicon
Labs
Product
Number IC
Antenna
or
Connector PA or
non-PA
Qty
Included
in Kit
EM357-MOD-ANT-C ZICM357SP0-1-SL 0730 EM357 Antenna Non-PA 1
EM357-MOD-RF-C ZICM357SP0-1C-SL 0731 EM357 Connector Non-PA 1
EM357-MOD-LR-RF-C ZICM357SP2-1C-SL 0732 EM357 Connector PA 1
EM357-MOD-LR-ANT-C ZICM357SP2-1-SL 0733 EM357 Antenna PA 1
EM3588-M-AN-C ZICM3588SP0-1-SL 0734 EM3588 Antenna Non-PA 3
EM3588-M-RF-C ZICM3588SP0-1C-SL 0735 EM3588 Connector Non-PA 1
EM3588-MLR-RF-C ZICM3588SP2-1C-SL 0736 EM3588 Connector PA 1
EM3588-MLR-AN-C ZICM3588SP2-1-SL 0737 EM3588 Antenna PA 0
5.3 Connecting the Breakout Boar d and RC M
Refer to document QSG101, EM35x Develo pment Kit Quick Start Guide, included in the development kit, for
detailed step-by-step in st ructions for setti ng up your hardware.
Two hardware modules attach to the EM35x Breakout Board:
• Radio Communic ation Module (RCM)
• Debug Adapter (ISA 3)
CAUTION: Observe electrostati c discharge (ESD) precautions when removing, handling, or replacing RF
communication m odules.
To attach the radio communication module:
Align the radio comm unication module to its footprint outline on the Breakout Board, and then press it into place. To
avoid communication problems, verify that each RCM is firmly seated in its Breakout Board connector, and its
Packet Trace Port cable is properly seated.
To remove the radio communicatio n m odul e:
Carefully pull the RCM away from the Breakout B oard.
To attach the Debug Ada pter (ISA3):
1. Plug the Packet Trace Port cable into the Debug A dapter (ISA3).
2. Plug one end of the Packet Trace Port cabl e i nt o t he 10-pin Packet Trace Port (J 31) on the Breakout
Board, and the other en d i nto the Debug Adapter (ISA3). If desired, the Packet Trace Port cable may be
connected directly to the RCM instead of the B reakout Board, but the Breakout Board connector all ows for
straight cable paths and more convenient swapping of modules.
3. Verify that the Debug Adapter (ISA3)’s Target Power Select swit ch is set to Int (Internal).
To remove the Debug Adapter (ISA3):
1. Unplug the Packet Trace P ort cable from the Breakout Board (or RCM).
2. Unplug the Packet Trace Port cable from the Debug Adapt er (I SA3).
UG110
Rev. 1.0 15
5.4 Breakout Board Power Configurat ions
The Breakout Board may be powered in one of five ways:
• Breakout Board Pow er Supplied by Debug Adapter (ISA3) (Figure 7): The def aul t configuration is t o supply
power via the Debug A dapter (ISA3) and Packet Tra ce Port cable. Ensure the power switch on the Debug
Adapter (ISA3) is in t he I NT (Internal) position. T he power supply of the Debug Adapter (ISA3) is al so
controlled via t he adm i n i nt erface. You may need to connect to the admin port of t he 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 (IS A3). The power supply jumper on the
Breakout Board should be in the horizontal positi on, connecting V_ISA to the center pin. The V_ISA LED
(DS3) will illu m i nate when power is appli ed.
Figure 7. Breakout Board Power Supplied by Debug Adapter (ISA3)
• Breakout Board Pow er Supplied by USB (Figu re 8): 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 o n the Breakout Board should
be in the lower vertical position, connecti ng V _RE G to the center pin. The V_FTDI LED (DS2) will
UG110
16 Rev. 1.0
illuminate when power is applied. When powering the Breakout Board in this way, ensure the p ower switch
on the Debug Adapter (ISA3) is in the EX T (E xternal) position.
Figure 8. Breakout Board Power Supplied by USB (J5)
• Breakout Board Pow er Supplied by DC Jumpers (Figure 9): The Br eakout 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
(+ supply) and J32 (ground). The power supply jumper on the Breakout Board should be i n the lower
vertical position, connecting V_REG t o the center pin. The VIN LE D (DS1) will illuminat e 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 9. Breakout Board Power Supplied by DC Jumpers
UG110
Rev. 1.0 17
• Breakout Board Pow er Supplied by Battery Connector (Figure 10): The Breakout Board may also be
powered via the battery connector (J8), using the supplied battery pack and 2x A A A batteries. The power
supply jumper should be in the upper vertical posit ion, connecting V_BA T T to the center pin. The V_BAT
LED (DS5) will il l um inate when power is applie d. When powering the Brea kout B oard i n this way, ensure
the power switch on the Debug Adapter (IS A3) is in the EXT (External) position.
Figure 10. Breakout Board Power Supplied by Battery Connector
• Figure 11. Break out Board Power Supplied by EM3588 USB (J39) (Figure 11): Fi nal ly, the Breakout Board
may also be powered t hrough the EM3588 USB connector (J39), either u sing a USB cable plugged in to
the USB power adapter included in the development kit, or by connecting it to your PC. The p ower supply
jumper on the Break out B oard should be in the lower v ert i cal position, connecti ng V_REG to the center
UG110
18 Rev. 1.0
pin. The V_EM358 LE D (D S8) will illuminate when po wer is applied. When powe ring the Breakout Board
in this way, ensure t he power switch on the Debug A dapter (ISA3) is in the EXT (External) position.
Figure 11. Breakout Board Power Supplied by EM3588 USB (J3 9)
The V_MOD LED (DS4) on t he Breakout Board will also ill uminate to indicate that power is properly ap pl ied
to the board and the RCM.
5.5 Breakout Board Serial Configur ations
Serial connectivity to the Breakout Board can be made in a number of way s. The default configurat i on of your
development kit will m atch your expected usa ge scenario.
• To use the pass-thro ugh UART feature of the Debug Adapter (ISA3): Plu g the larger 12-pin DEI cable
into the DEI header on t he 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 n ext 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 cente r pins. Connection to the UART
pass-through port can then be made using eit her of the two options belo w:
a. Connect to the Debug Adapter (ISA3) using the development environment. Laun ch t he console.
Choose the Serial 1 tab.
b. Run a terminal application (for example, Microsoft Telnet Client , HyperTerminal, PuTTY). Connect to
port 4901 on the Deb ug Adapter (ISA3).
• To use the RS-232 interface: Connect a serial cable to the DB-9 conne ct or on the Breakout Board.
Ensure the four jum pers above the DB-9 connector are positioned towards the DB-9 connector to send the
UG110
Rev. 1.0 19
UART signals to the RS-232 transceiver, and remove the jumper s f rom t he row of headers next to the DEI
port or make sure the DEI cable is disconnected.
• To use the USB interface: Install the FTDI US B drivers as described in the stack release not es, and
connect a USB cable to J5 of the Breakout Board and to your PC. Ensure the four jumpers abo ve the DB-
9 connector are posit i oned towards the USB connector to send the UART signals to the FTDI chip, an d
remove the jumpers f rom the row of headers next to the DEI port or make su re the DEI cable is
disconnected.
• To use the EM358x USB interface: Install the Silicon Labs USB drivers as described in the stack release
notes, and connect a US B cable to J39 of the Breako ut Board and to your PC. Ensu re t he USB_EN
jumper J40 to the lef t of the J39 USB connector is po sitioned on the top 2 pins (U SB position).
5.6 Common Hardware Configurations
Common configurat i ons of the Breakout Board and Debug Adapter (ISA3) can be seen in Figure 12, Figure 13,
Figure 14, Figure 15, and Figure 16.
Figure 12. Debug Adapter (IS A3) Supplying Power; Pass-through UART Being Used for Serial
Communication
UG110
20 Rev. 1.0
Figure 13. Debug Adapter (IS A3) Supplying Power; RS-232 Seri al Com munication
Figure 14. Power Supplied V ia USB Connector; Pass-through UART B ei ng Used for Communication
UG110
Rev. 1.0 21
Figure 15. Debug Adapter (IS A3) Supplying Power; FTDI Serial <-> USB Converter Used for Communication
UG110
22 Rev. 1.0
Figure 16. Debug Adapter (IS A3) Supplying Power; EM358x USB Used for Communi cation
UG110
Rev. 1.0 23
5.7 Connecting the RF Cable to the RCM
As detailed in Table 2, depending on the confi guration of the module, some RCMs include a PCB antenna while
others include an RF connector (type U.FL) w here an external antenna c an be connected via an RF adapter cable.
See Figure 17 for an example of a module with a PCB antenna. The RF connector may al s o be used as a
connection to test equipment. The development kit contains an RF adapter cable (type U.FL) t hat plugs into the RF
Connector on these modules. See Figure 18 for an example of a m odul e with this RF connector.
Figure 17. Module with PCB Antenna
Figure 18. Module with U.FL RF Connector
RF Connector
UG110
24 Rev. 1.0
6 Using the Debug Ada pter (ISA3)
6.1 Overview
The Debug Adapter (ISA3) provides an Ethernet connection to EM35x devices. Y ou can use the Debug Adapter
(ISA3) to perform the following t asks:
• Program and debug using Serial Wire or JTAG.
• Monitor packets se nt and received by the radio.
• Send and receive serial port data.
• Send and receive debugging data.
• Turn power on and off.
• Control reset, boot l oader and GPIO signal s.
6.2 Connectivity and Power
All the features of the Debug Adapter (ISA3) are available via the Et hernet connection. The Debug Adapter (ISA3)
can also be connected to a PC via USB to change the Ethernet settings.
When connected via USB, the Debug Adapter (I S A3) will also be powe red v i a USB. It should be connected to a
powered USB hub, or port on your PC that is capabl e of supplying full power t o connected devices.
When connected via Ethernet, the Debug A dapt er (I SA3) may be powered i n one of two ways:
1. Using an Ethernet switch that supplies Power Over Et hernet (P oE).
2. Using a USB pow er s uppl y.
The Debug Adapter (ISA3) will also supply power to the co nnected EM35x device when the power swit ch is in the
INT (Internal) position. I f the connected EM35x device has its own power supply, ensure the power switch is kept in
the EXT (External) position.
You can connect vi a Ethernet to the ports li st ed i n Table 3 using either t he Silicon Labs development environment
or a terminal applicati on (for example, Micr osoft Telnet Client, HyperTerminal, or PuTTY).
Table 3. Debug Adapter (ISA3) Ports
Port Use
4900 Virtual s erial port on EM35x via Packet Trace Port cable.
4901 Physic al serial port on EM35x v ia D ata Emulation Interface cable.
4902 or 23 Admin interface.
6.3 Ethernet Settings
By default, Debug Adapters (ISA3)s are configured t o get an IP address via D HC P. They are assigned hostnames
of EM-ISA3-00, EM-ISA3-01, etc. You can use the development environment to discov er the Debug Adapters
(ISA3) on the network and see thei r I P addresses.
If you are unable to use DHCP, the ISA3 Ethernet configuration may be changed using the ad m in interface over
USB as described in section 6.4, Using the Admin Interface over USB. The following ex am ple changes the
settings to a static IP address of 192.168.1.100 with a netmas k of 255.255.255.0 and a gat eway of 192.168.1.1.
>em3xx_isa.exe --admin "ip static 192.168.1.100 255.255.255.0 192.168.1.1"
em3xx_isa version 1.0.9
DLL version 1.0.13, compiled Aug 19 2009 19:42:00
Success: ip: (after reboot) Static 192.168.1.100 255.255.255.0 192.168.1.1
UG110
Rev. 1.0 25
>em3xx_isa.exe --admin "ip dhcp off"
em3xx_isa version 1.0.9
DLL version 1.0.13, compiled Aug 19 2009 19:42:00
Success: ip: (after reboot) DHCP off
You must reset the ISA3 after this configurati on change either by power cycling the device or with the reset
command.
You can change the hostname to make it more descriptive or to avoid conf l icts if Debug Adapt ers (ISA3)s from
multiple development kits are connected to the same network. To ch ange t he hostname, use the admin c ommand
hostname set <hostname>.
6.4 Using the Admin Interface over USB
1. Connect the Deb ug Adapter (ISA3) to the PC using USB. Only co nnect one Debug Adapte r (ISA3) at a
time by USB.
2. Run em3xx_isa.ex e with the --admin option.
3. Configure the Debug Adapter (ISA3) u sing the commands des cribed in Section 7, Debug Adapter (ISA3)
Commands.
6.5 Using the Admin Interface over Ethernet
1. Connect the Deb ug Adapter (ISA3) to the network using Ethernet.
2. Connect to the admi n port on the Debug Adapt er (I S A3) using either Ember Desktop or a terminal
application:
• Connect to the Deb ug A dapter (ISA3) using Em ber Desktop. Launch t he console. Choose the Admin
tab
OR
• Run a terminal application (e.g., Microsoft Telnet Client, Hy perTerminal, PuTTY ). Connect to port 4902
or 23 on the Debug Adapter (ISA3).
3. Configure the Debug Adapter (ISA3) u sing the commands des cribed in Section 7, Debug Adapter (ISA3)
Commands.
6.6 Using the Serial Ports
Connect to port 4900 o r 4901 on the Debug Ada pt er (ISA3) using either Ember Desktop or a terminal a pplication.
Port 4900 connects t o t he virtual serial port on the EM35x via the Packet Trace Port cable. The virtual seri al port
has no baud rate or other settings.
Port 4901 connects t o t he physical serial port on the EM35x via the Data Em ulation Interface (DEI) cable. The
default settings ar e 115200 baud, 8-n-1 (8 dat a bi ts, no parity bit, 1 stop bi t). To change the defaul t settings, use
the port admin command. For example, for 19200 baud, 8-n-1, use the command port 1 19200 8-n-1.
UG110
26 Rev. 1.0
6.7 Updating the Firmw are
Periodically, Sil i con Labs provides updat ed firmware for the Debug Adapter (ISA3). You can perform the update
using em3xx_isa.exe or em3xx_load.exe. Both utilities automatically update the firmware to t he latest version each
time they run.
To update a Debug Adapter (ISA3) over USB, run em3xx_isa.exe with no options. For ex ample:
>em3xx_isa.exe
em3xx_isa version 1.0.9
DLL version 1.0.13, compiled Aug 19 2009 19:42:00
Updating firmware: Ember InSight Adapter V1 compiled May 26 2009 13:47:00 V0.2b4
Replacing firmware: Ember InSight Adapter V1 compiled Feb 26 2009 21:54:00
... Firmware update successful. CRC=8DA7
Waiting for new firmware to boot
New firmware booted successfully
To update a Debug Adapter (ISA3) over Ethernet, run em3xx_isa. exe with the --ip option. For example:
>em3xx_isa.exe --ip 192.168.1.100
em3xx_isa version 1.0.9
DLL version 1.0.13, compiled Aug 19 2009 19:42:00
Connecting to IP address 192.168.1.100
Updating firmware: Ember InSight Adapter V1 compiled May 26 2009 13:47:00 V0.2b4
Replacing firmware: Ember InSight Adapter V1 compiled Feb 26 2009 21:54:00
... Firmware update successful. CRC=8DA7
Waiting for new firmware to boot
New firmware booted successfully
7 Debug Adapter (ISA3) Commands
7.1 Syntax Conventions
Element Meaning Example
Literal A command or argument that is ent er ed exactly as shown. hostname r ead
Variable An argument that is entered as the desired value for that
variable. hostname set hostname
[ | ] An argument chosen from a list. [on|off]
7.2 Entering Commands
• Commands can be entered over USB (see Section 6.4, Using the Admi n I nterface over USB) or
Ethernet (see Secti on 6.5, Using th e Admin Interface over Ethernet).
• Commands are not c ase sensitive.
• Arguments are separated with a single spa ce.
• Backspace can be u sed t o correct mistakes.
UG110
Rev. 1.0 27
7.3 Command List
• button
• config
• connections
• debug
• help
• hostname
• ip
• port
• power
• reset
• usbaddr
• version
7.3.1 button
button [0|1] [press|release]
Description
Simulates button 0 or 1 on the Breakout Board being pressed or releas ed.
The Data Emulation I nterface cable must be connected.
Example
button 1 press
7.3.2 debug
debug [on|off|disable]
Description
Turns BackChannel Debug on (the default), off (for sleepy devices), or disable (for read-protected devices). With no
arguments specified, it prints the current debu g st at us.
Examples
debug
debug off
debug disable
UG110
28 Rev. 1.0
7.3.3 config
config
Description
Displays the configuration of the Debug Adapt er (ISA3):
• hostname and static I P settings
• IP mode (static or DHCP) and current IP sett i ngs
• serial port sett i ngs
• firmware version
• serial number and Et hernet MAC address
• type, EUI and board nam e of the attached EM35x device
You can also view the configuration using Ember Desktop.
7.3.4 connections
connections
Description
Displays active and inactive TCP connections across the various Et hernet ports of the ISA 3.
7.3.5 help
help
Description
Displays a list of all Debug Adapter (ISA3) commands.
7.3.6 hostname
hostname set hostname
hostname read
Description
Sets or displays the host name of the Debug Adapter (ISA3).
The Debug Adapter (ISA3) must be reset for a change to take effect.
You can also view the hostname using Ember Desktop.
Example
hostname set mydevice3
7.3.7 ip
ip static ipaddress netmask gateway
ip dhcp [on|off]
Description
Sets the static IP address, netmask and gateway. These are only used when DHCP is turned off.
Turns DHCP on or off.
The Debug Adapter (ISA3) must be reset for a change t o t ake ef fect.
UG110
Rev. 1.0 29
Examples
ip static 192.168.1.100 255.255.255.0 192.168.1.1
ip dhcp off
7.3.8 port
port 1
port 1 baud
port 1 baud [5|6|7|8]-[n|o|e]-[1|2]
Description
Displays the configuration of the serial port.
Sets the baud rate, dat a bits (5, 6, 7 or 8), parity (no ne, odd or even) and stop bits (1 or 2).
Examples
port 1
port 1 57600
port 1 115200 8-n-1
7.3.9 power
power [on|off|read]
Description
Turns the power to the attached EM35x device on or off. Displays t he current power setting.
You can also turn the power on and off using Ember Desktop.
Example
power on
7.3.10 reset
reset
reset adapter
reset host [hold]
Description
Resets the attache d EM35x device if no arguments are specified
Resets the Debug Adapter (ISA3) when “adapter” argument is specified.
Resets the host MCU (if using the EM35x NCP Host Breakout B oard and DEI cable is conne ct ed to ISA3),
optionally holding t he host MCU in reset state if “hold” is specified.
You can also reset the device using Ember Desktop.
7.3.11 usbaddr
usbaddr read
usbaddr set [0|1|2|3|FF]
Description
Displays the USB address configuration of a specific Debug Adapter (I S A3).
Sets the USB addre ss configuration, range is 0-3 or FF (default).
UG110
30 Rev. 1.0
The Debug Adapter (ISA3) must be reset for a change to take effect. See document AN717, Programming Options
for the EM35xx Platform, for step by step instructions on setting the address of a Debug Adapter (ISA3).
7.3.12 version
version
Description
Displays the firmware version of the Debug Adapter (ISA3).
You can also view the v ersion using Ember Desktop.
UG110
Rev. 1.0 31
8 Software Tools Overview
8.1 Using the EM35x Nodetest Appl ication
The Nodetest application supports a command parser and prov ides results in a consistent , easy-to-parse format.
The Nodetest applic at i on i s pre-programmed on to the Radio Communicat ion Modules (RCMs) includ ed with your
EM35x Development Kit. The pre-built application images are also located in the {stack installation
directory}\app\nodetest folder, and S37 files used to create these HEX f i l es can b e f ound in t he chip-specific
build\nodetest-XXX di rectories.
You may communicat e with the serial interface of the Nodetest appli cat i on using the methods descri bed i n Section
6, Using the Debug Adapter (ISA3). A command line interface is supported on both the Vi rtual UART (“Serial 0”
tab in the Ember Desktop Console view) and the P hysical UART (“Serial 1” tab in the Ember Desktop Console
view). If using the Physical UART, ensure that the serial port i s co nfigured for 115200 baud, 8 data bits, No parity,
and 1 stop bit. By default the Debug Adapter (IS A3) is configured in this way, but it can be adjusted in this manner:
• Connect to the admin i nterface of the Debug A dapter (ISA3).
• Issue the baud rate configuration comment for the pass-through UART (port 1): port 1 115200
The Nodetest applic at i on provides on-line hel p about the available c om mands that can be viewed by executing the
command “help”. A l l i nput parameters to Nodetest are specified in hexadecimal without a “0x” prefix.
8.2 Running a Packet Error Test
A typical usage scenario for the Nodet est application is mea surement of Packet Error Rate (PER). PER is defined
in 802.15.4 as the percentage of transmitt ed packets that are not detected correctly. The Nod etest application
provides two commands "rx" and "tx" that are designed to interoperat e with each other across two nodes running
this application or with the "receive" and "transmit" commands f rom the legacy Rangete st application used in earlier
releases of the EM250 and EM260 platforms.
PER measurement pr ocedure:
1. Load the Nodetest appl ication on two EM35x nodes.
2. Set the radio t o the desired channel on both nodes with the "setchannel n" command where "n" is the
desired channel number in hex.
3. Issue the "rx" command on the first node.
4. Issue the "tx a" command on the second node. (This command will transmit 10 (hex a) packets of the form
required for PER analy sis. For actual PER analy sis, send 1000 or more packet s.)
UG110
32 Rev. 1.0
5. Observe the P E R result in the third column of the "rx" command out put, for example4:
> rx
{{(rx)} test start ('e'nd)}
#{{(rx)}
{num} {seq} {per} {lqi} {rssi}{gain} {status} {time} {length}}
{ { 1} { 1} { 0} {0x00} {-22} {0x31} {0x4000} {0x000F3716} {0x12} }
{ { 2} { 2} { 0} {0x00} {-22} {0x31} {0x4000} {0x000F9FE6} {0x12} }
{ { 3} { 3} { 0} {0x00} {-22} {0x31} {0x4000} {0x000008B6} {0x12} }
{ { 4} { 4} { 0} {0x00} {-22} {0x31} {0x4000} {0x00007186} {0x12} }
{ { 5} { 5} { 0} {0x00} {-22} {0x31} {0x4000} {0x0000DA57} {0x12} }
{ { 6} { 6} { 0} {0x00} {-22} {0x31} {0x4000} {0x00014327} {0x12} }
{ { 7} { 7} { 0} {0x00} {-22} {0x31} {0x4000} {0x0001ABF6} {0x12} }
{ { 8} { 8} { 0} {0x00} {-22} {0x31} {0x4000} {0x000214C6} {0x12} }
{ { 9} { 9} { 0} {0x00} {-22} {0x31} {0x4000} {0x00027D96} {0x12} }
{ { 10} { 10} { 0} {0x00} {-22} {0x31} {0x4000} {0x0002E666} {0x12} }
{{(rx)} test end}
>
To end the rx test, press the 'e' key. To reset the rx test statistics, end and restart the rx test.
8.3 Testing Deep Sleep Current
• Deep sleep current ca n be easily measured using the Nodetest applicat ion running on a Breakout Board.
Deep sleep current ca n only be measured when po wer is supplied to the board f rom a source other than
the Debug Adapter (I S A3). The buffer logic on t he Debug Adapter (ISA3) consum es extra current which
will not allow for accu rat e measurements.
• If a Debug Adapter (ISA3) is connected to the B reakout Board, then t he Deb ug Adapt er (ISA 3)' s Target
Power Select Swit ch should be switched t o EXT (External) so that the Debug A dapter (ISA3) is not
supplying power.
• Supply power through t he USB jack (J5), the dc jack, or the AAA Battery Pack. (The USB jack (J5) is
recommended and reviewed in these test step s because it is the simplest.)
• Rotate the VIN_SELE CTOR jumper (J2/J3) on the Breakout Board to the V_REG position (pins 2 and 3). If
power is supplied properly and all four power/LED jumpers (J2/J3, J4, J6, and J7) in the upper left corner
of the board are installed, then only the red V_ US B LE D and the green V_MOD LED will be illuminated.
• To properly measure current, remove the V_M OD jumper (J6) from t he B reakout Board. This ensures that
the green V_MOD LED is not being driven. I f supplying voltage through the J8 battery connector, also
remove J7 so the V_BATT LED DS5 is not driven.
• Remove the V_MOD_EN jumper (J4) from t he Breakout Board to take cur rent measurements. Then,
connect an ammet er in place of the jumper.
• If using EM35x Breakout Board revision B0 or later, remove the DataFlash jumpers at J33-J38 to isolate
the DataFlash IC from the rest of the circuit.
• If using EM35x Breakout Board revision C0 and later, confirm t he USB enable (USB_EN) jum per at J40 is
configured for S C2 (s hort i ng jumper across bott om 2 pins) and not USB.
4 This example may show different length packets than you see.
UG110
Rev. 1.0 33
These jumper sett ings can be seen in Figure 19.
Figure 19. Jumper setting for De ep S l eep Curr ent Testing
• Given an RCM programmed with Nodetest, execute the "shutdown" command:
> shutdown
Will wake from GPIO activity on the following port pins:
Port B, pin 6.
Port C, pin 6.
Entering SLEEPMODE_POWERDOWN via halSleep...
• Once the node is asleep, disconnect the Packet Trace Port cable, the DEI cable, t he RS-232 cable, and
remove all four UA RT jumpers (J22, J24, J25, and J26) from the Breakout B oard between the USB and
RS-232 connector s to obtain the lowest curre nt settings. All other jumpers may remain instal l ed.
UG110
34 Rev. 1.0
• Waking up is accomplished via either act i vity on the SerialWire deb ugger or pressing BUTTON0 or
BUTTON1.
To measure deep slee p while the Packet Trac e Port cable is still attached, issue the "swjdisabl e 1" command in
Nodetest to disable the SerialWire/JTAG port, and place the S WJ pins in a low current state. While the SWJ is
disabled, the Packet Trace Port/debugger will not be functional until ei t her the command "swjdisable 0" is issued or
the chip resets.
8.4 Example of Opening, Building, and Programming an Application Builder Scenario
Application for EmberZNet PRO
Follow these steps to create, open, build, and program the HA Light scenario application as included with
EmberZNet. If you are working with other protocols, see QSG1 05, Getting Started with Si li con Labs Wireless
Networking Software, for similar instructions.
1. Open Ember Desktop.
2. From the menus, choose File > New > Application Framework Configuration.
3. Choose “ZCL Application Framework V2 ”, and click Next.
4. Choose the stack installation upon whi ch you’d like to base your application, such as “EmberZNet 5.3 GA
EM35X”, and click N ext.
5. Choose “Start from a selected sample appl ication:”, and click on “HaSampleLight”. Then click Next.
6. Enter a name for y our application, such as “MyLi ght ”, and click Finish.
7. Optional: Ma ke any desired changes to your appl ication configurat ion
8. Click the Generate button in the top right corner of the AppBuilder user interface.
9. If prompted to overwrite the callbacks. c file, make sure to leav e this option unselected ( don’ t overwrite).
10. After the generat i on results are display ed, click OK. Note the locati on of the EWW file, such as
C:\Users\{username}\Ember\EmberZNet5.3.0\EM35x\app\builder\MyLight\MyLight.eww
11. Open the EWW file for your application, such as MyLight.eww, in IAR Embedded Workbench for A RM
(EWARM). This can be done by either double clicking the MyLight.eww file (located in the
”app\builder\{appName}” subdirectory within your EmberZNet installation) or fro m i nside of EWARM using
File > Open > Workspace and navigating to the MyLight.eww file.
12. Select Project > Make (F7) from inside of EWARM.
13. After making the project, the firmware file used for programmi ng is found at
”{EmberZNet_Install_Dir}\build\MyLight\MyLight.ebl” (an ap pl ication image in Em ber bootloader file format)
14. To program this fi l e to the node, connect y our Debug Adapter (ISA3) to the chip and your computer (this
example assumes the Debug Adapter (ISA3) is connected via USB . See the next section for how t o
program if the Debug Adapter (ISA3) is connected via Ethernet.
15. Open a command line of your choice (such a s DOS or cygwin).
16. Navigate to the dire ct ory where the MyLight.ebl file was built.
17. Invoke the com m and " em3xx_load.exe" without any build option s. Thi s will ensure that em3xx_l oad.exe
can be found in your path and will cause em3x x_load.exe to print it s on-line help menu.
18. To download the EBL file to the EM357 chip, invoke the command "em3xx_l oad.exe MyLight.ebl". (Note
that this application also requires that you load bootloader firmware to the chip. This must be done before
the application firmware will run. Bootloader firmware can be f ound as *.s37 files within t he
tool/bootloader-em357 or bootloader-em351 directory within your stack installation and is loaded in a
manner similar to that of the *.ebl file above. I f bootloader firmware is not already present on the chip
when the application is loaded, em3xx_load wil l display a warning about a “bootloading and a pplication
mismatch”.)
19. Download will compl ete when em3xx_load prints the string "Run (b y toggling nRESET)".
UG110
Rev. 1.0 35
8.5 Programming your Application on the EM35x
Programming EM35x flash is accomplished with the e m 3xx_load.exe utility, either via the Windows C om m and
Prompt or via the Upload Application action in Ember Desktop’s Adapters view. The em3xx_load uti l ity is included
as part of the Debug Adapter (ISA3) Utilities Installer, in the “bin” subdirectory..
A complete summary of em3xx_load functi onality with brief desc riptions of each option c an be found in
em3xx_load's own help menu. Invoking " em3xx_load.exe" wit hout opt i ons or invoking "em3xx_load.exe --help" will
print this help menu. More information ab out using Ember Desktop to upload application can b e f ound in the online
help for Ember Deskt op.
The most common u sage of em3xx_load is to simpl y program flash. em3xx_l oad takes the S37 specific version of
Motorola S-record file formats, and the se files use the .s37 extension. If you are using a bootloader, em3xx_load
can also load a .ebl file, which is a proprietary, binary file format designed for appli cati ons that use an Ember
Bootloader.
Given an S37 file call ed " file.s37", the most ba sic command for programming flash is simply:
em3xx_load.exe file.s37
Em3xx_load will then print out the versions it i s using, the devices it is connected to, the steps it is perf orming, and
programming prog ress. By default, the last st ep em3xx_load perform s is to run the chip by toggli ng the nRESET
pin.
By default, em3x x_load.exe assumes the Debug Adapter (ISA3) is connected via USB when no other options are
given. If the Debug Adapter (ISA3) is connected via Ethernet, use the --ip option t o specify the IP address or
hostname of the Debug Adapter (ISA3) to be used. Given a Debug Adapter (ISA 3) with an IP address of
123.123.123.123, programming can be accomplished with the command:
em3XX_load.exe --ip 123.123.123.123 file.s37
8.6 Programming Manufacturi ng Tokens
The em3xx_load utility has the ability to program m anufacturing tokens much like the em2xx_patch tool di d. In the
case of the EM357, these tokens are contained in t he Customer Information Block (CIB). For more inf ormation on
using the em3xx _l oad utility, refer to document UG107, EM35x Utilities Guide. For more infor m at i on about CIB
tokens and how to program them, refer to document AN710, Brin ging Up Custom Device s f or the EM35x Platform.
Certificates and installation codes can be programmed using the sam e em 3xx_load tool that is us ed to program
other tokens. There is a separate application note which describ es the process in detail. F or more information, see
document AN708, S etting Manufacturin g Cert i f i cates and Installation Codes.
8.7 Using the Debugger in IAR Embedded Workbench with a Debug Adapter (ISA3)
1. Start IAR Embedded Workbench. Open the workspace (*.eww).
2. Select Project > Options. Select the Debugger > J-Link/J-Trace category. Select the Con nection tab.
3. Select TCP/IP Communication and enter the IP address of the Debug Adapter (ISA3). Click OK.
4. Embedded Workbench is not able to program the flash on the EM35x. Every time the project is re-built,
you must manually l oad i t ont o t he EM35x (using em3xx_load.exe) befor e st arting a debug session.
5. Once the correct im age has been loaded onto the EM35x, select Project > Debug without Downloading to
start the debug se ssi on.
UG110
36 Rev. 1.0
CONTACT INFORMATION
Silicon Laboratories Inc.
400 West Cesar C havez
Austin, T X 787 01
Tel: 1+(512) 416-8500
Fax: 1+(512) 416-9669
Toll Free: 1+(877) 444-3032
For addition al information please visit the Silicon Labs Technical Support page:
http://www.silabs.com/support/Pages/default.aspx
Patent Notice
Silicon Labs invests in research and development to help our customers differentiate in the market with innovative low-power, small size,
analog-intensive mixed-signal solutions. Silicon Labs' extensive patent portfolio is a testament to our unique approach and world-class
engineering team.
The information in this document is believed to be accurate in all respects at the time of publication but is subject to change without notice.
Silicon Laboratories assumes no responsibility for errors and omissions, and disclaims responsibility for any consequences resulting from the
use of information included herein. Additionally, Silicon Laboratories assumes no responsibility for the functioning of undescribed features or
parameters. Silicon Laboratories reserves the right to make changes without further notice. Silicon Laboratories makes no warranty,
representation or guarantee regarding the suitability of its products for any particular purpose, nor does Silicon Laboratories assume any liability
arising out of the application or use of any product or circuit, and specifically disclaims any and all liability, including without limitation
consequential or incidental damages. Silicon Laboratories products are not designed, intended, or authorized for use in applications intended to
support or sustain life, or for any other application in which the failure of the Silicon Laboratories product could create a situation where personal
injury or death may occur. Should Buyer purchase or use Silicon Laboratories products for any such unintended or unauthorized application,
Buyer shall indemnify and hold Silicon Laboratories harmless against all claims and damages.
Silicon Laboratories, Silicon Labs, and Ember are registered trademarks of Silicon Laboratories Inc.
Other products or brandnames mentioned herein are trademarks or registered trademarks of their respective holders.
