Silicon Labs UG374 User's Guide

Silicon Labs UG374 User's Guide
UG374: EFR32ZG14 Zen Gecko
Wireless Starter Kit User's Guide
A Wireless Starter Kit with the BRD4201A Radio Board is an excellent starting point to get familiar with the EFR32 Zen Gecko ZWave® Wireless System-on-Chip. It also provides the necessary
tools for developing a Silicon Labs Z-Wave gateway application.
BRD4201A is a plug-in board for the Wireless Starter Kit Mainboard. It is a complete reference design for the EFR32ZG14 Wireless SoC, realizing the matching network with an
Integrated Passive Device (IPD). The board features an SMA connector for RF connection, or a PCB antenna that can be selected by moving a 0 Ω resistor.
The Wireless Starter Kit Mainboard contains an on-board J-Link debugger with a Packet
Trace Interface and a virtual COM port, enabling application development and debugging
the attached radio board as well as external hardware. The mainboard also contains
sensors and peripherals for easy demonstration of some of the EFR32's many capabilities.
This document describes how to use the BRD4201A Radio Board together with a Wireless Starter Kit Mainboard.
BRD4201A RADIO BOARD FEATURES
• EFR32 Zen Gecko Wireless SoC with 256
kB Flash, 32 kB RAM.
(EFR32ZG14P231F256GM32)
• SMA antenna connector (863-925 MHz)
• Optional PCB antenna
• RF matching network with switchable
SAW filters for EU, HK, and US frequency
bands
WIRELESS STK MAINBOARD FEATURES
• Advanced Energy Monitor
• Virtual COM port
• SEGGER J-Link on-board debugger
• External device debugging
• Ethernet and USB connectivity
• Silicon Labs Si7021 relative humidity and
temperature sensor
• Low Power 128x128 pixel Memory LCD
• User LEDs / pushbuttons
• 20-pin 2.54 mm EXP header
• Breakout pads for Wireless SoC I/O
• CR2032 coin cell battery support
SOFTWARE SUPPORT
• Simplicity Studio™
• Energy Profiler
• iOS and Android applications
ORDERING INFORMATION
• SLWRB4201A
silabs.com | Building a more connected world.
Rev. 1.1
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1 Radio Boards .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 4
1.2 Ordering Information
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 4
1.3 Getting Started
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 4
.
.
2. Hardware Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1 Hardware Layout .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 5
2.2 Block Diagram.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 6
.
3. Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.1 J-Link USB Connector .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 7
3.2 Ethernet Connector .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 7
3.3 Breakout Pads
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 8
3.4 EXP Header . . . . .
3.4.1 EXP Header Pinout .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 9
.10
3.5 Debug Connector.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.11
3.6 Simplicity Connector.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.12
3.7 Debug Adapter
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.13
4. Power Supply and Reset . . . . . . . . . . . . . . . . . . . . . . . . . .
14
.
.
4.1 Radio Board Power Selection
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.14
4.2 Board Controller Power.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.15
4.3 EFR32 Reset .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.15
5. Peripherals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16
.
.
.
5.1 Push Buttons and LEDs
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.16
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.17
.18
.18
.19
6. Board Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
20
5.2 Virtual COM Port . . . .
5.2.1 Host Interfaces . .
5.2.2 Serial Configuration .
5.2.3 Hardware Handshake
6.1 Admin Console . . . .
6.1.1 Connecting . . . .
6.1.2 Built-in Help . . .
6.1.3 Command Examples
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.20
.20
.20
.21
6.2 Virtual UART .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.21
. . . . . . . . . . . . . . . . . . . . . . . . .
22
.
.
.
7. Advanced Energy Monitor
7.1 Introduction.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.22
7.2 Theory of Operation .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.22
7.3 AEM Accuracy and Performance
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.23
silabs.com | Building a more connected world.
Rev. 1.1 | 2
7.4 Usage
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.23
8. On-Board Debugger . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24
8.1 Host Interfaces . . . . . .
8.1.1 USB Interface . . . . .
8.1.2 Ethernet Interface . . .
8.1.3 Serial Number Identification
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.24
.24
.24
.24
8.2 Debug Modes .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.25
8.3 Debugging During Battery Operation .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.26
9. Kit Configuration and Upgrades . . . . . . . . . . . . . . . . . . . . . . .
27
.
.
9.1 Firmware Upgrades .
.
.
.
.
.
.
.
.
.
.27
10. Schematics, Assembly Drawings, and BOM . . . . . . . . . . . . . . . . . .
28
11. Kit Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . .
29
11.1 SLWRB4201A Revision History
12. Document Revision History
silabs.com | Building a more connected world.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.29
. . . . . . . . . . . . . . . . . . . . . . . .
30
Rev. 1.1 | 3
UG374: EFR32ZG14 Zen Gecko Wireless Starter Kit User's Guide
Introduction
1. Introduction
The EFR32ZG14 Zen Gecko Wireless SoC is featured on a radio board that plugs directly into a Wireless Starter Kit (WSTK) Mainboard. The mainboard features several tools for easy evaluation and development of wireless applications. An on-board J-Link debugger enables programming and debugging on the target device over USB or Ethernet. The Advanced Energy Monitor (AEM) offers realtime current and voltage monitoring. A virtual COM port interface (VCOM) provides an easy-to-use serial port connection over USB or
Ethernet. The Packet Trace Interface (PTI) offers invaluable debug information about transmitted and received packets in wireless links.
All debug functionality, including AEM, VCOM, and PTI, can also be used towards external target hardware instead of the attached radio board.
To further enhance its usability, the mainboard contains sensors and peripherals that demonstrate some of the many capabilities of the
EFR32ZG14. A 20-pin expansion header (EXP header) is also provided that allows connection of expansion boards (EXP boards) to
the kit.
1.1 Radio Boards
A Wireless Starter Kit consists of one or more mainboards and radio boards that plug into the mainboard. Different radio boards are
available, each featuring different Silicon Labs devices with different operating frequency bands.
Since the mainboard is designed to work with all different radio boards, the actual pin mapping from a device pin to a mainboard feature
is done on the radio board. This means that each radio board has its own pin mapping to the Wireless Starter Kit features, such as
buttons, LEDs, the display, the EXP header and the breakout pads. Because this pin mapping is different for every radio board, it is
important that the correct document be consulted which shows the kit features in context of the radio board plugged in.
This document explains how to use the Wireless Starter Kit when the EFR32ZG14 Radio Board (BRD4201A) is combined with a Wireless STK Mainboard. The combination of these two boards is hereby referred to as a Wireless Starter Kit (Wireless STK).
1.2 Ordering Information
BRD4201A can be obtained as a separate radio board, SLWRB4201A.
Table 1.1. Ordering Information
Part Number
Description
Contents
SLWRB4201A
EFR32ZG14 Zen Gecko Radio Board
1x BRD4201A EFR32ZG14 Zen Gecko Radio Board
1x RW Badland SMAMFL SKIRT SMA Antenna
1.3 Getting Started
Detailed instructions for how to get started can be found on the Silicon Labs web pages:
http://www.silabs.com/start-efr32zg
silabs.com | Building a more connected world.
Rev. 1.1 | 4
UG374: EFR32ZG14 Zen Gecko Wireless Starter Kit User's Guide
Hardware Overview
2. Hardware Overview
2.1 Hardware Layout
The layout of the EFR32ZG14 Wireless Starter Kit is shown in the figure below.
Radio Board Breakout Pads
Plug-in Radio Board
On-board USB and
Ethernet J-Link
Debugger
Si7021 Humidity and
Temperature Sensor
USB-serial-port
Packet-trace
Advanced Energy
Monitoring
EXP-header for
expansion boards
Battery or
USB power
Ultra-low power 128x128
pixel memory LCD,
buttons and LEDs
ARM Coresight 19-pin
trace/debug header
Serial-port, packet trace and Advanced
Energy Monitoring header
Figure 2.1. Kit Hardware Layout
silabs.com | Building a more connected world.
Rev. 1.1 | 5
UG374: EFR32ZG14 Zen Gecko Wireless Starter Kit User's Guide
Hardware Overview
2.2 Block Diagram
An overview of the EFR32ZG14 Wireless Starter Kit is shown in the figure below.
Wireless STK Mainboard
USB Mini-B
Connector
Debug
AEM
UART
UART
Multiplexer
AEM
Debug
IN
Debug
Connector
MCU
Packet Trace
O
U
T
Simplicity
Connector
Packet Trace
Board
Controller
RJ-45 Ethernet
Connector
EXP
Header
User Buttons
& LEDs
Debug
Packet Trace
AEM
UART
ETM Trace
GPIO
GPIO
EFR32ZG14
Wireless SoC
Figure 2.2. Kit Block Diagram
silabs.com | Building a more connected world.
Rev. 1.1 | 6
UG374: EFR32ZG14 Zen Gecko Wireless Starter Kit User's Guide
Connectors
3. Connectors
This chapter gives you an overview of the Wireless STK Mainboard connectivity. The placement of the connectors are shown in the
figure below.
3
3V V3
3
D
N D
G GN
C
N NC
5 4
P4 P4
3 2
P4 P4
1 0
P4 P4
9 8
P3 P3
7 6
P3 P3
5 4
P3 P3
3 2
P3 P3
1 0
P3 P3
9 8
P2 P2
7 6
P2 P2
5 4
P2 P2
D
N D
G GN 5V
5V
Ethernet
Connector
Ra
Co dio B
nn
ec oard
tor
s
EX
PH
J-Link USB
Connector
Simplicity
Connector
ea
de
r
Debug
Connector
F F
VR R
V
D
N D
G GN
3 2
P2 P2
1 0
P2 P2
9 8
P1 P1
7 6
P1 P1
5 4
P1 P1
3 2
P1 P1
1 0
P1 P1
P9 P8
P7 P6
P5 P4
P3 P2
P1 P0
D
N D
G GN
U
C U
VM MC
V
Figure 3.1. Mainboard Connector Layout
3.1 J-Link USB Connector
The J-Link USB connector is situated on the left side of the Wireless Starter Kit Mainboard. Most of the kit's development features are
supported through this USB interface when connected to a host computer, including:
• Debugging and programming of the target device using the on-board J-Link debugger
• Communication with the target device over the virtual COM port using USB-CDC
• Accurate current profiling using the AEM
In addition to providing access to development features of the kit, this USB connector is also the main power source for the kit. USB 5V
from this connector powers the board controller and the AEM. It is recommended that the USB host be able to supply at least 500 mA
to this connector, although the actual current required will vary depending on the application.
3.2 Ethernet Connector
The Ethernet connector provides access to all of the Wireless Starter Kit's development features over TCP/IP. The Ethernet interface
provides some additional development features to the user. Supported features include:
•
•
•
•
•
•
Debugging and programming of the target device using the on-board J-Link debugger
Communication with the target device over the virtual COM port using TCP/IP socket 4901
"VUART" communication with the target device over the debug SWD/SWO interface using TCP/IP socket 4900
Accurate current profiling using the AEM
Real-time radio packet and network analysis using the Packet Trace Interface
Access to advanced configuration options using the admin console over TCP/IP socket 4902
Note: The Wireless Starter Kit cannot be powered using the Ethernet connector, so in order to use this interface, the USB connector
must be used to provide power to the board.
silabs.com | Building a more connected world.
Rev. 1.1 | 7
UG374: EFR32ZG14 Zen Gecko Wireless Starter Kit User's Guide
Connectors
3.3 Breakout Pads
Most pins of the EFR32 are routed from the radio board to breakout pads at the top and bottom edges of the Wireless STK Mainboard.
A 2.54 mm pitch pin header can be soldered on for easy access to the pins. The figure below shows you how the pins of the EFR32
map to the pin numbers printed on the breakout pads. To see the available functions on each, refer to the data sheet for
EFR32ZG14P231F256GM32.
J101
VMCU
GND
P1 / NC / EXP4
P3 / NC / EXP6
P5 / NC / EXP8
P7 / NC / EXP10
P9 / PA0 / EXP12 / VCOM_TX
P11 / PA1 / EXP14 / VCOM_RX
P13 / PC11 / EXP16 / I2C_SDA
P15 / NC
P17 / NC
P19 / NC
P21 / NC
P23 / NC
GND
VRF
VMCU
GND
EXP3 / NC / P0
EXP5 / NC / P2
EXP7 / NC / P4
EXP9 / NC / P6
EXP11 / NC / P8
DBG_TDI / EXP13 / PF3 / P10
I2C_SCL / EXP15 / PC10 / P12
NC / P14
NC / P16
BUTTON1 / PB11 / P18
PTI_DATA / PB12 / P20
PTI_SYNC / PB13 / P22
GND
VRF
J102
5V
GND
DBG_TCK_SWCLK / PF0 / P24
DBG_TMS_SWDIO / PF1 / P26
DBG_TDO_SWO / PF2 / P28
NC / P30
NC / P32
NC / P34
NC / P36
NC / P38
NC / P40
NC / P42
NC / P44
NC
GND
3V3
5V
GND
P25 / NC
P27 / PB14 / SAW1
P29 / PB15 / SAW2
P31 / PD13 / LED0
P33 / PD14 / VCOM_ENABLE
P35 / PD15 / BUTTON0
P37 / NC
P39 / NC
P41 / NC
P43 / NC
P45 / NC
NC
GND
3V3
Figure 3.2. Breakout Pad Pin Mapping
silabs.com | Building a more connected world.
Rev. 1.1 | 8
UG374: EFR32ZG14 Zen Gecko Wireless Starter Kit User's Guide
Connectors
3.4 EXP Header
The EXP header is an angled 20-pin expansion header provided to allow connection of peripherals or plugin boards to the kit. It is located on the right-hand side of the mainboard, and it contains a number of I/O pins that can be used with most of the EFR32 Zen Gecko's
features. Additionally, the VMCU, 3V3, and 5V power rails are also exported.
The connector follows a standard which ensures that commonly used peripherals, such as an SPI, a UART, and an I2C bus, are available on fixed locations in the connector. The rest of the pins are used for general purpose IO. This allows the definition of expansion
boards (EXP boards) that can plug into a number of different Silicon Labs Starter Kits.
The figure below shows the pin assignment of the EXP header. Because of limitations in the number of available GPIO pins, some of
the EXP header pins are shared with kit features.
3V3
5V
I2C_SDA / PC11
UART_RX / PA1
UART_TX / PA0
NC
NC
NC
NC
VMCU
20
18
16
14
12
10
8
6
4
2
19
17
15
13
11
9
7
5
3
1
BOARD_ID_SDA
BOARD_ID_SCL
PC10 / I2C_SCL
PF3 / GPIO
NC
NC
NC
NC
NC
GND
EFR32ZG14 I/O Pin
Reserved (Board Identification)
Figure 3.3. EXP Header
silabs.com | Building a more connected world.
Rev. 1.1 | 9
UG374: EFR32ZG14 Zen Gecko Wireless Starter Kit User's Guide
Connectors
3.4.1 EXP Header Pinout
The pin-routing on the EFR32 is very flexible, so most peripherals can be routed to any pin. However, many pins are shared between
the EXP header and other functions on the Wireless STK Mainboard. The table below includes an overview of the mainboard features
that share pins with the EXP header.
Table 3.1. EXP Header Pinout
Pin
Connection
EXP Header Function
Shared Feature
Peripheral Mapping
20
3V3
Board controller supply
18
5V
Board USB voltage
16
PC11
I2C_SDA
-
I2C0_SDA #16
14
PA1
UART_RX
VCOM_RX
USART0_RX #0
12
PA0
UART_TX
VCOM_TX
USART0_TX #0
10
NC
SPI_CS
8
NC
SPI_SCLK
6
NC
SPI_MISO
4
NC
SPI_MOSI
2
VMCU
19
BOARD_ID_SDA
Connected to board controller for identification of add-on boards.
17
BOARD_ID_SCL
Connected to board controller for identification of add-on boards.
15
PC10
13
EFR32 voltage domain, included in AEM measurements.
I2C_SCL
-
PF3
GPIO
DBG_TDI
11
NC
GPIO
9
NC
GPIO
7
NC
GPIO
5
NC
GPIO
3
NC
GPIO
1
GND
I2C0_SCL #14
Ground
Note: Pin PF3 is used for DBG_TDI in JTAG mode only. When the Serial Wire Debugging interface (SWD) is used, PF3 can be used
for other purposes.
silabs.com | Building a more connected world.
Rev. 1.1 | 10
UG374: EFR32ZG14 Zen Gecko Wireless Starter Kit User's Guide
Connectors
3.5 Debug Connector
The debug connector serves multiple purposes based on the "debug mode" setting which can be configured in Simplicity Studio. When
the debug mode is set to "Debug IN", the debug connector can be used to connect an external debugger to the EFR32 on the radio
board. When set to "Debug OUT", this connector allows the kit to be used as a debugger towards an external target. When set to "Debug MCU" (default), the connector is isolated from both the on-board debugger and the radio board target device.
Because this connector is electronically switched between the different operating modes, it can only be used when the board controller
is powered (i.e., J-Link USB cable connected). If debug access to the target device is required when the board controller is unpowered,
connect directly to the appropriate breakout pins.
The pinout of the connector follows that of the standard ARM Cortex Debug+ETM 19-pin connector. The pinout is described in detail
below. Even though the connector has support for both JTAG and ETM Trace, it does not necessarily mean that the kit or the on-board
target device supports this.
VTARGET
GND
GND
NC
Cable Detect
NC
NC
GND
GND
GND
1
3
5
7
9
11
13
15
17
19
2
4
6
8
10
12
14
16
18
20
TMS / SWDIO / C2D
TCK / SWCLK / C2CK
TDO / SWO
TDI / C2Dps
RESET / C2CKps
NC
NC
NC
NC
NC
Figure 3.4. Debug Connector
Note: The pinout matches the pinout of an ARM Cortex Debug+ETM connector, but these are not fully compatible because pin 7 is
physically removed from the Cortex Debug+ETM connector. Some cables have a small plug that prevent them from being used when
this pin is present. If this is the case, remove the plug or use a standard 2x10 1.27 mm straight cable instead.
Table 3.2. Debug Connector Pin Descriptions
Pin Number(s)
Function
Description
1
VTARGET
Target reference voltage. Used for shifting logical signal levels between target and
debugger.
2
TMS / SDWIO / C2D
4
JTAG test mode select, Serial Wire data, or C2 data
TCK / SWCLK / C2CK JTAG test clock, Serial Wire clock, or C2 clock
6
TDO/SWO
8
TDI / C2Dps
10
RESET / C2CKps
12
TRACECLK
Not connected
14
TRACED0
Not connected
16
TRACED1
Not connected
18
TRACED2
Not connected
20
TRACED3
Not connected
9
Cable detect
11, 13
NC
3, 5, 15, 17, 19
GND
silabs.com | Building a more connected world.
JTAG test data out or Serial Wire Output
JTAG test data in or C2D "pin sharing" function
Target device reset or C2CK "pin sharing" function
Connect to ground
Not connected
Ground
Rev. 1.1 | 11
UG374: EFR32ZG14 Zen Gecko Wireless Starter Kit User's Guide
Connectors
3.6 Simplicity Connector
The Simplicity Connector enables the advanced debugging features, such as the AEM, the virtual COM port, and the Packet Trace
Interface, to be used towards an external target. The pinout is illustrated in the figure below.
VMCU
3V3
5V
GND
GND
GND
GND
GND
BOARD_ID_SCL
BOARD_ID_SDA
1
3
5
7
9
11
13
15
17
19
2 VCOM_TX
4 VCOM_RX
6
8
10
12
14
16
18
20
VCOM_CTS
VCOM_RTS
PTI0_SYNC
PTI0_DATA
PTI0_CLK
PTI1_SYNC
PTI1_DATA
PTI1_CLK
Figure 3.5. Simplicity Connector
Note: Current drawn from the VMCU voltage pin is included in the AEM measurements, while the 3V3 and 5V voltage pins are not.
When monitoring the current consumption of an external target with the AEM, unplug the radio board from the Wireless STK Mainboard
to avoid adding the radio board current consumption to the measurements.
Table 3.3. Simplicity Connector Pin Descriptions
Pin Number(s)
Function
1
VMCU
3
3V3
3.3 V power rail
5
5V
5 V power rail
2
VCOM_TX
Virtual COM Tx
4
VCOM_RX
Virtual COM Rx
6
VCOM_CTS
Virtual COM CTS
8
VCOM_RTS
Virtual COM RTS
10
PTI0_SYNC
Packet Trace 0 Sync
12
PTI0_DATA
Packet Trace 0 Data
14
PTI0_CLK
Packet Trace 0 Clock
16
PTI1_SYNC
Packet Trace 1 Sync
18
PTI1_DATA
Packet Trace 1 Data
20
PTI1_CLK
Packet Trace 1 Clock
17
BOARD_ID_SCL
Board ID SCL
19
BOARD_ID_SDA
Board ID SDA
7, 9, 11, 13, 15
GND
silabs.com | Building a more connected world.
Description
3.3 V power rail, monitored by the AEM
Ground
Rev. 1.1 | 12
UG374: EFR32ZG14 Zen Gecko Wireless Starter Kit User's Guide
Connectors
3.7 Debug Adapter
The BRD8010A STK/WSTK Debug Adapter is an adapter board which plugs directly into the debug connector and the Simplicity Connector on the mainboard. It combines selected functionality from the two connectors to a smaller footprint 10-pin connector, which is
more suitable for space constrained designs.
For versatility, the debug adapter features three different 10-pin debug connectors:
• Silicon Labs Mini Simplicity Connector
• ARM Cortex 10-pin Debug Connector
• Silicon Labs ISA3 Packet Trace
The ARM Cortex 10-pin Debug Connector follows the standard Cortex pinout defined by ARM and allows the Starter Kit to be used to
debug hardware designs that use this connector.
The ISA3 connector follows the same pinout as the Packet Trace connector found on the Silicon Labs Ember Debug Adapter (ISA3).
This allows the Starter Kit to be used to debug hardware designs that use this connector.
The Mini Simplicity Connector is designed to offer advanced debug features from the Starter Kit on a 10-pin connector:
• Serial Wire Debug (SWD) with SWO
• Packet Trace Interface (PTI)
• Virtual COM port (VCOM)
• AEM monitored voltage rail
Note: Packet Trace is only available on Wireless STK Mainboards. MCU Starter Kits do not support Packet Trace.
VAEM
RST
VCOM_TX
SWDIO
PTI_FRAME
1
3
5
7
9
2
4
6
8
10
GND
VCOM_RX
SWO
SWCLK
PTI_DATA
Figure 3.6. Mini Simplicity Connector
Table 3.4. Mini Simplicity Connector Pin Descriptions
Pin Number
Function
1
VAEM
Target voltage on the debugged application. Supplied and monitored by the AEM
when power selection switch is in the "AEM" position.
2
GND
Ground
3
RST
Reset
4
VCOM_RX
Virtual COM Rx
5
VCOM_TX
Virtual COM Tx
6
SWO
7
SWDIO
Serial Wire Data
8
SWCLK
Serial Wire Clock
9
PTI_FRAME
10
PTI_DATA
silabs.com | Building a more connected world.
Description
Serial Wire Output
Packet Trace Frame Signal
Packet Trace Data Signal
Rev. 1.1 | 13
UG374: EFR32ZG14 Zen Gecko Wireless Starter Kit User's Guide
Power Supply and Reset
4. Power Supply and Reset
4.1 Radio Board Power Selection
The EFR32 on a Wireless Starter Kit can be powered by one of these sources:
• The debug USB cable
• A 3 V coin cell battery
• A USB regulator on the radio board (for devices with USB support only)
BA
T
U
SB
AE
M
The power source for the radio board is selected with the slide switch in the lower left corner of the Wireless STK Mainboard. The figure
below shows how the different power sources can be selected with the slide switch.
USB Mini-B
Connector
5V
LDO
3.3 V
Advanced
Energy
Monitor
AEM
USB
VMCU
BAT
EFR32ZG14
3 V Lithium Battery
(CR2032)
Figure 4.1. Power Switch
With the switch in the AEM position, a low noise 3.3 V LDO on the mainboard is used to power the radio board. This LDO is again
powered from the debug USB cable. The AEM is now also connected in series, allowing accurate high speed current measurements
and energy debugging/profiling.
With the switch in the USB position, radio boards with USB-support can be powered by a regulator on the radio board itself. BRD4201A
does not contain a USB regulator, and setting the switch in the USB postition will cause the EFR32 to be unpowered.
Finally, with the switch in the BAT position, a 20 mm coin cell battery in the CR2032 socket can be used to power the device. With the
switch in this position, no current measurements are active. This is the recommended switch position when powering the radio board
with an external power source.
Note: The current sourcing capabilities of a coin cell battery might be too low to supply certain wireless applications.
Note: The AEM can only measure the current consumption of the EFR32 when the power selection switch is in the AEM position.
silabs.com | Building a more connected world.
Rev. 1.1 | 14
UG374: EFR32ZG14 Zen Gecko Wireless Starter Kit User's Guide
Power Supply and Reset
4.2 Board Controller Power
The board controller is responsible for important features, such as the debugger and the AEM, and is powered exclusively through the
USB port in the top left corner of the board. This part of the kit resides on a separate power domain, so a different power source can be
selected for the target device while retaining debugging functionality. This power domain is also isolated to prevent current leakage from
the target power domain when power to the board controller is removed.
The board controller power domain is not influenced by the position of the power switch.
The kit has been carefully designed to keep the board controller and the target power domains isolated from each other as one of them
powers down. This ensures that the target EFR32 device will continue to operate in the USB and BAT modes.
4.3 EFR32 Reset
The EFR32 Wireless SoC can be reset by a few different sources:
• A user pressing the RESET button
• The on-board debugger pulling the #RESET pin low
• An external debugger pulling the #RESET pin low
In addition to the reset sources mentioned above, a reset to the EFR32 will also be issued during board controller boot-up. This means
that removing power to the board controller (unplugging the J-Link USB cable) will not generate a reset, but plugging the cable back in
will, as the board controller boots up.
silabs.com | Building a more connected world.
Rev. 1.1 | 15
UG374: EFR32ZG14 Zen Gecko Wireless Starter Kit User's Guide
Peripherals
5. Peripherals
The starter kit has a set of peripherals that showcase some of the features of the EFR32.
Be aware that most EFR32 I/O routed to peripherals are also routed to the breakout pads or the EXP header. This must be taken into
consideration when using these.
5.1 Push Buttons and LEDs
The kit has two user push buttons marked PB0 and PB1. They are connected directly to the EFR32 and are debounced by RC filters
with a time constant of 1 ms. The buttons are connected to pins PD15 and PB11.
The kit also features two yellow LEDs marked LED0 and LED1 that are controlled by GPIO pins on the EFR32. The LEDs are connected to pins PD13 and PF3 in an active-high configuration.
PD13 (GPIO)
UIF_LED0
PF3 (GPIO)
UIF_LED1
PD15 (GPIO)
UIF_PB0
PB11 (GPIO)
UIF_PB1
User Buttons
& LEDs
EFR32ZG14
Figure 5.1. Buttons and LEDs
silabs.com | Building a more connected world.
Rev. 1.1 | 16
UG374: EFR32ZG14 Zen Gecko Wireless Starter Kit User's Guide
Peripherals
5.2 Virtual COM Port
An asynchronous serial connection to the board controller is provided for application data transfer between a host PC and the target
EFR32. This eliminates the need for an external serial port adapter.
Isolation & Level Shift
PA0 (US0_TX#0)
PA1 (US0_RX#0)
NC
VCOM_TX
VCOM_RX
VCOM_CTS
Board
Controller
USB
or
ETH
Host
PC
VCOM_RTS
NC
PD14 (GPIO)
VCOM_ENABLE
EFR32ZG14
Figure 5.2. Virtual COM Port Interface
The virtual COM port consists of a physical UART between the target device and the board controller, and a logical function in the
board controller that makes the serial port available to the host PC over USB or Ethernet. The UART interface consists of four pins and
an enable signal.
Table 5.1. Virtual COM Port Interface Pins
Signal
Description
VCOM_TX
Transmit data from the EFR32 to the board controller
VCOM_RX
Receive data from the board controller to the EFR32
VCOM_CTS
Clear to Send hardware flow control input, asserted by the board controller when it is ready to receive more data
VCOM_RTS
Request to Send hardware flow control output, asserted by the EFR32 when it is ready to receive more data
VCOM_ENABLE Enables the VCOM interface, allowing data to pass through to the board controller.
The parameters of the serial port, such as baud rate or flow control, can be configured using the admin console. The default settings
depend on which radio board is used with the Wireless STK Mainboard.
Note: The VCOM port is only available when the board controller is powered, which requires the J-Link USB cable to be inserted.
silabs.com | Building a more connected world.
Rev. 1.1 | 17
UG374: EFR32ZG14 Zen Gecko Wireless Starter Kit User's Guide
Peripherals
5.2.1 Host Interfaces
Data can be exchanged between the board controller and the target device through the VCOM interface, which is then available to the
user in two different ways:
• Virtual COM port using a standard USB-CDC driver
• TCP/IP by connecting to the Wireless STK on TCP/IP port 4901 with a Telnet client
When connecting via USB, the device should automatically show up as a COM port. The actual device name that is associcated with
the kit depends on the operating system and how many devices are or have been connected previously. The following are examples of
what the device might show up as:
• JLink CDC UART Port (COM5) on Windows hosts
• /dev/cu.usbmodem1411 on macOS
• /dev/ttyACM0 on Linux
Data sent by the target device into the VCOM interface can be read from the COM port, and data written to the port is transmitted to the
target device. Connecting to the Wireless STK on port 4901 gives access to the same data over TCP/IP. Data written into the VCOM
interface by the target device can be read from the socket, and data written into the socket is transmitted to the target device.
Note: Only one of these interfaces can be used at the same time, with the TCP/IP socket taking priority. This means that if a socket is
connected to port 4901, no data can be sent or received on the USB COM port.
5.2.2 Serial Configuration
By default, the VCOM serial port is configured to use 115200 8N1 (115.2 kbit/s, 8 data bits, 1 stop bit), with flow control disabled/ignored. The configuration can be changed using the admin console:
WSTK> serial vcom config
Usage: serial vcom config [--nostore] [handshake <rts/cts/rtscts/disable/auto>] [speed <9600,921600>]
Using this command, the baud rate can be configured between 9600 and 921600 bit/s, and hardware handshake can be enabled or
disabled on either or both flow control pins.
silabs.com | Building a more connected world.
Rev. 1.1 | 18
UG374: EFR32ZG14 Zen Gecko Wireless Starter Kit User's Guide
Peripherals
5.2.3 Hardware Handshake
The VCOM peripheral supports basic RTS/CTS flow control.
VCOM_CTS (target clear to send) is a signal that is output from the board controller and input to the target device. The board controller
de-asserts this pin whenever its input buffer is full and it is unable to accept more data from the target device. If hardware handshake is
enabled in the target firmware, its UART peripheral will halt when data is not being consumed by the host. This implements end-to-end
flow control for data moving from the target device to the host.
VCOM_CTS is connected to the RTS pin on the board controller and is enabled by setting handshake to either RTS or RTSCTS using
the "serial vcom config" command.
VCOM_RTS (target request to send) is a signal that is output from the target device and input to the board controller. The board controller will halt transmission of data towards the target if the target device de-asserts this signal. This gives the target firmware a means to
hold off incoming data until it can be processed. Note that de-asserting RTS will not abort the byte currently being transmitted, so the
target firmware must be able to accept at least one more character after RTS is de-asserted.
VCOM_RTS is connected to the CTS pin of the board controller. It is enabled by setting handshake to either CTS or RTSCTS using the
"serial vcom config" command in the admin console. If CTS flow control is disabled, the state of VCOM_RTS will be ignored and data
will be transmitted to the target device anyway.
Table 5.2. Hardware Handshake Configuration
Mode
Description
disabled
RTS (VCOM_CTS) is not driven by the board controller and CTS (VCOM_RTS) is ignored.
rts
RTS (VCOM_CTS) is driven by the board controller to halt target from transmitting when input buffer is full. CTS
(VCOM_RTS) is ignored.
cts
RTS (VCOM_CTS) is not driven by the board controller. Data is transmitted to the target device if CTS
(VCOM_RTS) is asserted, and halted when de-asserted.
rtscts
RTS (VCOM_CTS) is driven by the board controller to halt target when buffers are full. Data is transmitted to the
target device if CTS (VCOM_RTS) is asserted, and halted when de-asserted.
Note: Enabling CTS flow control without configuring the VCOM_RTS pin can result in no data being transmitted from the host to the
target device.
silabs.com | Building a more connected world.
Rev. 1.1 | 19
UG374: EFR32ZG14 Zen Gecko Wireless Starter Kit User's Guide
Board Controller
6. Board Controller
The Wireless STK Mainboard contains a dedicated microcontroller for some of the advanced kit features provided. This microcontroller
is referred to as the board controller and is not programmable by the user. The board controller acts as an interface between the host
PC and the target device on the radio board, as well as handling some housekeeping functions on the board.
Some of the kit features actively managed by the board controller are:
•
•
•
•
The on-board debugger, which can flash and debug both on-board and external targets
The Advanced Energy Monitor, which provides real-time energy profiling of the user application
The Packet Trace Interface, which is used in conjunction with PC software to provide detailed insight into an active radio network
The Virtual COM Port and Virtual UART interfaces, which provide ways to transfer application data between the host PC and the
target processor
• The admin console, which provides configuration of the various board features
Silicon Labs publishes updates to the board controller firmware in the form of firmware upgrade packages. These updates may enable
new features or fix issues. See Section 9.1 Firmware Upgrades for details on firmware upgrade.
6.1 Admin Console
The admin console is a command line interface to the board controller on the kit. It provides functionality for configuring the kit behavior
and retreiving configuration and operational parameters.
6.1.1 Connecting
The Wireless Starter Kit must be connected to Ethernet using the Ethernet connector in the top left corner of the mainboard for the
admin console to be available. See Section 8.1.2 Ethernet Interface for details on the Ethernet connectivity.
Connect to the admin console by opening a telnet connection to the kit's IP address, port number 4902.
When successfully connected, a WSTK> prompt is displayed.
6.1.2 Built-in Help
The admin console has a built-in help system which is accessed by the help command. The help command will print a list of all top
level commands:
WSTK> help
*************** Root commands ****************
aem
AEM commands
[ calibrate, current, dump, ... ]
boardid
Commands for board ID probe.
[ list, probe ]
dbg
Debug interface status and control
[ info, mode,]
dch
Datachannel control and info commands
[ info ]
discovery
Discovery service commands.
net
Network commands.
[ dnslookup, geoprobe, ip ]
pti
Packet trace interface status and control
[ config, disable, dump, ... ]
quit
Exit from shell
sys
System commands
[ nickname, reset, scratch, ... ]
target
Target commands.
[ button, flashwrite, go, ... ]
time
Time Service commands
[ client, server ]
user
User management functions
[ login,]
The help command can be used in conjunction with any top level command to get a list of sub-commands with description. For example, pti help will print a list of all available sub-commands of pti:
WSTK> pti help
*************** pti commands ****************
config
Configure packet trace
disable
Disable packet trace
dump
Dump PTI packets to the console as they come
enable
Enable packet trace
info
Packet trace state information
This means that running pti enable will enable packet trace.
silabs.com | Building a more connected world.
Rev. 1.1 | 20
UG374: EFR32ZG14 Zen Gecko Wireless Starter Kit User's Guide
Board Controller
6.1.3 Command Examples
PTI Configuration
pti config 0 efruart 1600000
Configures PTI to use the "EFRUART" mode at 1.6 Mb/s.
Serial Port Configuration
serial config vcom handshake enable
Enables hardware handshake on the VCOM UART connection.
6.2 Virtual UART
The Virtual UART interface provides a high performance application data interface that does not require any additional I/O pins apart
from the debug interface. It is based on SEGGER's Real Time Transfer (RTT) technology, and it uses the Serial Wire Output (SWO) pin
to get application data from the device and a shared memory interface to send data to the target application.
The Wireless Starter Kit makes the Virtual UART interface available on TCP/IP port 4900.
silabs.com | Building a more connected world.
Rev. 1.1 | 21
UG374: EFR32ZG14 Zen Gecko Wireless Starter Kit User's Guide
Advanced Energy Monitor
7. Advanced Energy Monitor
7.1 Introduction
Any embedded developer seeking to make their embedded code spend as little energy as the underlying architecture supports needs
tools to easily and quickly discover inefficiencies in the running application. This is what the Simplicity Energy Profiler is designed to do.
In real-time, the Energy Profiler will graph and log current as a function of time while correlating this to the actual target application code
running on the EFR32. There are multiple features in the profiler software that allow for easy analysis, such as markers and statistics on
selected regions of the current graph or aggregate energy usage by different parts of the application.
7.2 Theory of Operation
The AEM circuitry on the board is capable of measuring current signals in the range of 0.1 µA to 95 mA, which is a dynamic range of
almost 120 dB. It can do this while maintaining approximately 10 kHz of current signal bandwidth. This is accomplished through a combination of a highly capable current sense amplifier, multiple gain stages, and signal processing within the kit's board controller before
the current sense signal is read by a host computer for display and/or storage.
The current sense amplifier measures the voltage drop over a small series resistor, and the gain stage further amplifies this voltage with
two different gain settings to obtain two current ranges. The transition between these two ranges occurs around 250 µA.
The current signal is combined with the target processor's Program Counter (PC) sampling by utilizing a feature of the ARM CoreSight
debug architecture. The Instrumentation Trace Macrocell (ITM) block can be programmed to sample the MCU's PC at periodic intervals
(50 kHz) and output these over SWO pin ARM devices. When these two data streams are fused and correlated with the running application's memory map, an accurate statistical profile can be built that shows the energy profile of the running application in real-time.
At kit power-up or on a power-cycle, an automatic AEM calibration is performed. This calibration compensates for any offset errors in
the current sense amplifiers.
LDO
EFR32ZG14
Peripherals
AEM
Processing
Figure 7.1. Advanced Energy Monitor
Note: The 3.3 V regulator feedback point is after the 2.35 Ω sense resistor to ensure that the VMCU voltage is kept constant when the
output current changes. Maximum recommended output current is 300 mA.
silabs.com | Building a more connected world.
Rev. 1.1 | 22
UG374: EFR32ZG14 Zen Gecko Wireless Starter Kit User's Guide
Advanced Energy Monitor
7.3 AEM Accuracy and Performance
The AEM is capable of measuring currents in the range of 0.1 µA to 95 mA. For currents above 250 µA, the AEM is accurate within 0.1
mA. When measuring currents below 250 µA, the accuracy increases to 1 µA. Even though the absolute accuracy is 1 µA in the sub
250 µA range, the AEM is able to detect changes in the current consumption as small as 100 nA.
The AEM current sampling rate is 10 kHz.
Note: The AEM circuitry only works when the kit is powered and the power switch is in the AEM position.
7.4 Usage
The AEM data is collected by the board controller and can be displayed by the Energy Profiler, available through Simplicity Studio. By
using the Energy Profiler, current consumption and voltage can be measured and linked to the actual code running on the EFR32 in
realtime.
silabs.com | Building a more connected world.
Rev. 1.1 | 23
UG374: EFR32ZG14 Zen Gecko Wireless Starter Kit User's Guide
On-Board Debugger
8. On-Board Debugger
The Wireless STK Mainboard contains an integrated debugger, which can be used to download code and debug the EFR32. In addition
to programming a target on a plug-in radio board, the debugger can also be used to program and debug external Silicon Labs EFM32,
EFM8, EZR32, and EFR32 devices connected through the debug connector.
The debugger supports three different debug interfaces for Silicon Labs devices:
• Serial Wire Debug is supported by all EFM32, EFR32, and EZR32 devices
• JTAG is supported by EFR32 and some EFM32 devices
• C2 Debug is supported by EFM8 devices
In order for debugging to work properly, make sure that the selected debug interface is supported by the target device. The debug connector on the board supports all three of these modes.
8.1 Host Interfaces
The Wireless Starter Kit supports connecting to the on-board debugger using either Ethernet or USB.
Many tools support connecting to a debugger using either USB or Ethernet. When connected over USB, the kit is identified by its J-Link
serial number. When connected over Ethernet, the kit is normally identified by its IP address. Some tools also support using the serial
number when connecting over Ethernet; however, this typically requires the computer and the kit to be on the same subnet for the discovery protocol (using UDP broadcast packets) to work.
8.1.1 USB Interface
The USB interface is available whenever the USB Mini-B connector on the left-hand side of the mainboard is connected to a computer.
8.1.2 Ethernet Interface
The Ethernet interface is available when the mainboard Ethernet connector in the top left corner is connected to a network. Normally,
the kit will receive an IP address from a local DHCP server, and the IP address is printed on the LCD display. If your network does not
have a DHCP server, you need to connect to the kit via USB and set the IP address manually using Simplicity Studio, Simplicity
Commander, or J-Link Configurator.
For the Ethernet connectivity to work, the kit must still be powered through the USB Mini-B connector. See Section 4.2 Board Controller
Power for details.
8.1.3 Serial Number Identification
All Silicon Labs kits have a unique J-Link serial number which identifies the kit to PC applications. This number is 9 digits and is normally on the form 44xxxxxxx.
The J-Link serial number is normally printed at the bottom of the kit LCD display.
silabs.com | Building a more connected world.
Rev. 1.1 | 24
UG374: EFR32ZG14 Zen Gecko Wireless Starter Kit User's Guide
On-Board Debugger
8.2 Debug Modes
Programming external devices is done by connecting to a target board through the provided debug connector and by setting the debug
mode to [Out]. The same connector can also be used to connect an external debugger to the EFR32 Wireless SoC on the kit by setting
debug mode to [In].
Selecting the active debug mode is done in Simplicity Studio.
Debug MCU: In this mode, the on-board debugger is connected to the EFR32 on the kit.
Host
Computer
USB
Board
Controller
RADIO BOARD
External
Hardware
DEBUG HEADER
Figure 8.1. Debug MCU
Debug OUT: In this mode, the on-board debugger can be used to debug a supported Silicon Labs device mounted on a custom board.
Host
Computer
USB
Board
Controller
RADIO BOARD
External
Hardware
DEBUG HEADER
Figure 8.2. Debug OUT
Debug IN: In this mode, the on-board debugger is disconnected, and an external debugger can be connected to debug the EFR32 on
the kit.
Host
Computer
USB
Board
Controller
RADIO BOARD
External Debug Probe
DEBUG HEADER
Figure 8.3. Debug IN
silabs.com | Building a more connected world.
Rev. 1.1 | 25
UG374: EFR32ZG14 Zen Gecko Wireless Starter Kit User's Guide
On-Board Debugger
Note: For "Debug IN" to work, the kit board controller must be powered through the Debug USB connector.
8.3 Debugging During Battery Operation
When the EFR32 is powered by battery and the J-Link USB is still connected, the on-board debug functionality is available. If the USB
power is disconnected, the Debug IN mode will stop working.
If debug access is required when the target is running off another energy source, such as a battery, and the board controller is powered
down, the user should make direct connections to the GPIO used for debugging. This can be done by connecting to the appropriate
pins of the breakout pads. Some Silicon Labs kits provide a dedicated pin header for this purpose.
silabs.com | Building a more connected world.
Rev. 1.1 | 26
UG374: EFR32ZG14 Zen Gecko Wireless Starter Kit User's Guide
Kit Configuration and Upgrades
9. Kit Configuration and Upgrades
The kit configuration dialog in Simplicity Studio allows you to change the J-Link adapter debug mode, upgrade its firmware, and change
other configuration settings. To download Simplicity Studio, go to http://www.silabs.com/simplicity.
In the main window of the Simplicity Studio's Launcher perspective, the debug mode and firmware version of the selected J-Link adapter is shown. Click the [Change] link next to any of them to open the kit configuration dialog.
Figure 9.1. Simplicity Studio Kit Information
Figure 9.2. Kit Configuration Dialog
9.1 Firmware Upgrades
Upgrading the kit firmware is done through Simplicity Studio. Simplicity Studio will automatically check for new updates on startup.
You can also use the kit configuration dialog for manual upgrades. Click the [Browse] button in the [Update Adapter] section to select
the correct file ending in .emz. Then, click the [Install Package] button.
silabs.com | Building a more connected world.
Rev. 1.1 | 27
UG374: EFR32ZG14 Zen Gecko Wireless Starter Kit User's Guide
Schematics, Assembly Drawings, and BOM
10. Schematics, Assembly Drawings, and BOM
Schematics, assembly drawings, and bill of materials (BOM) are available through Simplicity Studio when the kit documentation package has been installed.
silabs.com | Building a more connected world.
Rev. 1.1 | 28
UG374: EFR32ZG14 Zen Gecko Wireless Starter Kit User's Guide
Kit Revision History
11. Kit Revision History
The kit revision can be found printed on the kit packaging label, as outlined in the figure below.
EFR32ZG14 Zen Gecko Radio Board
SLWRB4201A
10-10-18
124802042
A00
Figure 11.1. Kit Label
11.1 SLWRB4201A Revision History
Kit Revision
Released
Description
A00
10 October 2018
Initial release.
silabs.com | Building a more connected world.
Rev. 1.1 | 29
UG374: EFR32ZG14 Zen Gecko Wireless Starter Kit User's Guide
Document Revision History
12. Document Revision History
Revision 1.1
February 2019
• Minor editorial changes.
Revision 1.0
November 2018
• Initial document version.
silabs.com | Building a more connected world.
Rev. 1.1 | 30
Simplicity Studio
One-click access to MCU and
wireless tools, documentation,
software, source code libraries &
more. Available for Windows,
Mac and Linux!
IoT Portfolio
www.silabs.com/IoT
SW/HW
www.silabs.com/simplicity
Quality
www.silabs.com/quality
Support and Community
community.silabs.com
Disclaimer
Silicon Labs intends to provide customers with the latest, accurate, and in-depth documentation of all peripherals and modules available for system and software implementers using or
intending to use the Silicon Labs products. Characterization data, available modules and peripherals, memory sizes and memory addresses refer to each specific device, and "Typical"
parameters provided can and do vary in different applications. Application examples described herein are for illustrative purposes only. Silicon Labs reserves the right to make changes
without further notice to the product information, specifications, and descriptions herein, and does not give warranties as to the accuracy or completeness of the included information.
Without prior notification, Silicon Labs may update product firmware during the manufacturing process for security or reliability reasons. Such changes will not alter the specifications or the
performance of the product. Silicon Labs shall have no liability for the consequences of use of the information supplied in this document. This document does not imply or expressly grant
any license to design or fabricate any integrated circuits. The products are not designed or authorized to be used within any FDA Class III devices, applications for which FDA premarket
approval is required or Life Support Systems without the specific written consent of Silicon Labs. A "Life Support System" is any product or system intended to support or sustain life and/or
health, which, if it fails, can be reasonably expected to result in significant personal injury or death. Silicon Labs products are not designed or authorized for military applications. Silicon
Labs products shall under no circumstances be used in weapons of mass destruction including (but not limited to) nuclear, biological or chemical weapons, or missiles capable of delivering
such weapons. Silicon Labs disclaims all express and implied warranties and shall not be responsible or liable for any injuries or damages related to use of a Silicon Labs product in such
unauthorized applications.
Trademark Information
Silicon Laboratories Inc.® , Silicon Laboratories®, Silicon Labs®, SiLabs® and the Silicon Labs logo®, Bluegiga®, Bluegiga Logo®, Clockbuilder®, CMEMS®, DSPLL®, EFM®, EFM32®,
EFR, Ember®, Energy Micro, Energy Micro logo and combinations thereof, "the world’s most energy friendly microcontrollers", Ember®, EZLink®, EZRadio®, EZRadioPRO®, Gecko®,
ISOmodem®, Precision32®, ProSLIC®, Simplicity Studio®, SiPHY®, Telegesis, the Telegesis Logo®, USBXpress® and others are trademarks or registered trademarks of Silicon Labs.
ARM, CORTEX, Cortex-M3 and THUMB are trademarks or registered trademarks of ARM Holdings. Keil is a registered trademark of ARM Limited. All other products or brand names
mentioned herein are trademarks of their respective holders.
Silicon Laboratories Inc.
400 West Cesar Chavez
Austin, TX 78701
USA
http://www.silabs.com
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement