SLWRB4306C - SILICON LABS - Datasheet.Live

UG340: MGM13P02 Mighty Gecko Module

Radio Board User's Guide

A Wireless Starter Kit with the BRD4306C Radio Board is an ex-

cellent starting point to get familiar with the MGM13P Mighty

Gecko Module. It also provides the necessary tools for developing

a Silicon Labs wireless application.

BRD4306C contains the MGM13P02 Module, and it is a plug-in board for the Wireless

Starter Kit Mainboard.

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 MGM13P's many capa-

bilities.

This document describes how to use the BRD4306C Radio Board together with a Wire-

less Starter Kit Mainboard.

BRD4306C RADIO BOARD FEATURES

• MGM13P Mighty Gecko Module with 512

kB Flash, 64 kB RAM. Fully integrated

chip antenna, RF matching network,

crystals, and decoupling

(MGM13P02F512GA-V2).

• 8 Mbit low-power serial flash for over-the-

air upgrades.

WIRELESS STK MAINBOARD FEATURES

• Advanced Energy Monitor

• Packet Trace Interface

• 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 Module I/O

• CR2032 coin cell battery support

SOFTWARE SUPPORT

• Simplicity Studio™

• Energy Profiler

• Network Analyzer

ORDERING INFORMATION

• SLWRB4306C

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 ..............................9

3.4.1 EXP Header Pinout ..........................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 MGM13P Reset .............................15

5. Peripherals ............................... 16

5.1 Push Buttons and LEDs ..........................16

5.2 Memory LCD-TFT Display..........................17

5.3 Serial Flash ..............................18

5.4 Si7021 Relative Humidity and Temperature Sensor .................19

5.5 Virtual COM Port .............................20

5.5.1 Host Interfaces ...........................21

5.5.2 Serial Configuration ..........................21

5.5.3 Hardware Handshake .........................22

6. Board Controller ............................. 23

6.1 Admin Console .............................23

6.1.1 Connecting .............................23

6.1.2 Built-in Help ............................23

6.1.3 Command Examples .........................24

6.2 Virtual UART ..............................24

7. Advanced Energy Monitor ......................... 25

silabs.com | Building a more connected world. Rev. 1.1 | 2

7.1 Introduction...............................25

7.2 Theory of Operation ............................25

7.3 AEM Accuracy and Performance .......................26

7.4 Usage ................................26

8. On-Board Debugger ............................ 27

8.1 Host Interfaces .............................27

8.1.1 USB Interface ............................27

8.1.2 Ethernet Interface ..........................27

8.1.3 Serial Number Identification .......................27

8.2 Debug Modes ..............................28

8.3 Debugging During Battery Operation ......................29

9. Kit Configuration and Upgrades ....................... 30

9.1 Firmware Upgrades ............................30

10. Schematics, Assembly Drawings, and BOM .................. 31

11. Kit Revision History ........................... 32

11.1 SLWRB4306C Revision History .......................32

12. Document Revision History ........................ 33

silabs.com | Building a more connected world. Rev. 1.1 | 3

1. Introduction

The MGM13P02 Mighty Gecko Module 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 ena-

bles programming and debugging on the target device over USB or Ethernet. The Advanced Energy Monitor (AEM) offers real-time

current and voltage monitoring. A virtual COM port interface (VCOM) provides an easy-to-use serial port connection over USB or Ether-

net. 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 demonstrates some of the many capabilities of the

MGM13P02. 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 MGM13P02 Mighty Gecko Module Radio Board (BRD4306C) is

combined with a Wireless STK Mainboard. The combination of these two boards is hereby referred to as a Wireless Starter Kit (Wire-

less STK).

1.2 Ordering Information

BRD4306C can be obtained as a separate radio board, SLWRB4306C. The radio board is intended to be used together with a Wireless

STK Mainboard that can be obtained with any Silicon Labs Wireless Starter Kit.

Table 1.1. Ordering Information

Part Number Description Contents

SLWRB4306C MGM13P02 Mighty Gecko Module Radio Board 1x BRD4306C MGM13P02 Mighty Gecko Module

Radio Board

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-efr32mg

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

Introduction

silabs.com | Building a more connected world. Rev. 1.1 | 4

2. Hardware Overview

2.1 Hardware Layout

The layout of the MGM13P02 Mighty Gecko Module Wireless Starter Kit is shown in the figure below.

MGM13P02

Module

Radio Board

Breakout pads

1.28" Memory-LCD Display

Ultra-low power

128 x 128 pixel resolution

SPI interface

Ethernet RJ-45

J-Link Debugger

Virtual COM port

Packet Trace

Advanced Energy Monitoring

USB Mini-B

J-Link Debugger

Virtual COM port

Packet Trace

Advanced Energy Monitoring

Coin Cell Holder

CR2032 Battery

Power Select Switch

BAT / USB / AEM

2x User Push Buttons 2x User LEDs

Simplicity Connector

Virtual COM port

Packet Trace

Advanced Energy Monitoring

Debug Connector

ARM Coresight 19-pin

OUT: External targets

IN: External debug probes

Reset Button

Si7021

Relative Temperature &

Humidity Sensor

EXP Header

Expansion board connector

Figure 2.1. Kit Hardware Layout

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

Hardware Overview

silabs.com | Building a more connected world. Rev. 1.1 | 5

2.2 Block Diagram

An overview of the MGM13P02 Mighty Gecko Module Wireless Starter Kit is shown in the figure below.

Wireless STK Mainboard

USB Mini-B

Connector

RJ-45 Ethernet

Connector

Debug

UART

Packet Trace

AEM

Debug

UART

ETM Trace

Packet Trace

AEM

Debug

UART

Packet Trace

AEM

Simplicity

Connector

Debug

Connector

Board

Controller

Multiplexer

OUT

MCU

MGM13P

Module

GPIO

EXP

Header

User Buttons

& LEDs

GPIO

128 x 128 pixel

Memory LCD

I2C Si7021

Temperature

& Humidity

Sensor

SPI 8 Mbit

MX25R

Serial Flash

Figure 2.2. Kit Block Diagram

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

Hardware Overview

silabs.com | Building a more connected world. Rev. 1.1 | 6

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.

Simplicity

Connector

Debug

Connector

GND

P25

P24

P27

P26

P29

P28

P31

P30

P33

P32

P35

P34

P37

P36

P39

P38

P41

P40

P43

P42

P45

P44

GND

Radio Board

Connectors

EXP Header

GND

VMCU

P11

P10

P13

P12

P15

P14

P17

P16

P19

P18

P21

P20

GND

P23

P22

VRF

3V3

Ethernet

Connector

J-Link USB

Connector

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

Please note that 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.

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

Connectors

silabs.com | Building a more connected world. Rev. 1.1 | 7

3.3 Breakout Pads

Most pins of the MGM13P are routed from the radio board to breakout pads at the top and bottom edges of the Wireless STK Main-

board. 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

MGM13P maps to the pin numbers printed on the breakout pads. To see the available functions on each, refer to the data sheet for

MGM13P02F512GA-V2.

GND

VMCU

P23 / PD15 / DISP_ENABLE / SENSOR_ENABLE

P21 / PD14 / DISP_SCS

P19 / PD13 / DISP_EXTCOMIN

P17 / NC

GND

P15 / NC

P13 / PC10 / EXP16 / I2C_SDA

P11 / PA1 / EXP14 / VCOM_RX

P9 / PA0 / EXP12 / VCOM_TX

P7 / PC9 / EXP10

P5 / PC8 / EXP8 / FLASH_SCLK / DISP_SCLK

P3 / PC7 / EXP6 / FLASH_MISO

P1 / PC6 / EXP4 / FLASH_MOSI / DISP_SI

VRF

GND

VMCU

PTI_SYNC / PB13 / P22

VCOM_ENABLE / PA5 / P20

FLASH_SCS / PA4 / P18

NC / P16

GND

NC / P14

I2C_SCL / EXP15 / PC11 / P12

DBG_TDI / EXP13 / PF3 / P10

EXP11 / NC / P8

EXP9 / PF5 / P6

EXP7 / PF4 / P4

VCOM_RTS / EXP5 / PA3 / P2

VCOM_CTS / EXP3 / PA2 / P0

VRF

J101

GNDGND

5V5V

NCNC

P45 / NCNC / P44

P43 / NCNC / P42

P41 / NCNC / P40

3V33V3

P39 / NCNC / P38

P37 / PD15 / DISP_ENABLE / SENSOR_ENABLENC / P36

P35 / NCNC / P34

P33 / PF7 / BUTTON1_LED1NC / P32

P31 / PF6 / BUTTON0_LED0NC / P30

P29 / PF2 / DBG_TDO_SWONC / P28

P27 / PF1 / DBG_TMS_SWDIONC / P26

P25 / PF0 / DBG_TCK_SWCLKPTI_DATA / PB11 / P24

GNDGND

J102

Figure 3.2. Breakout Pad Pin Mapping

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

Connectors

silabs.com | Building a more connected world. Rev. 1.1 | 8

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 loca-

ted 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 MGM13P Mighty

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 availa-

ble 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.

1516

20 19

VMCU

SPI_MOSI / PC6

SPI_MISO / PC7

SPI_SCK / PC8

SPI_CS / PC9

UART_TX / PA0

UART_RX / PA1

I2C_SDA / PC10

3V3

GND

PA2 / GPIO

PA3 / GPIO

PF4 / GPIO

PF5 / GPIO

PF3 / GPIO

PC11 / I2C_SCL

BOARD_ID_SDA

BOARD_ID_SCL

Reserved (Board Identification)

MGM13P I/O Pin

Figure 3.3. EXP Header

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

Connectors

silabs.com | Building a more connected world. Rev. 1.1 | 9

3.4.1 EXP Header Pinout

The pin-routing on the MGM13P 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 PC10 I2C_SDA SENSOR_I2C_SDA I2C0_SDA #15

14 PA1 UART_RX VCOM_RX USART0_RX #0

12 PA0 UART_TX VCOM_TX USART0_TX #0

10 PC9 SPI_CS USART1_CS #11

8 PC8 SPI_SCLK FLASH_SCLK, DISP_SCLK USART1_CLK #11

6 PC7 SPI_MISO FLASH_MISO USART1_RX #11

4 PC6 SPI_MOSI FLASH_MOSI, DISP_SI USART1_TX #11

2 VMCU MGM13P voltage domain, included in AEM measurements.

19 BOARD_ID_SDA Connected to the board controller for identification of add-on boards.

17 BOARD_ID_SCL Connected to the board controller for identification of add-on boards.

15 PC11 I2C_SCL SENSOR_I2C_SCL I2C0_SCL #15

13 PF3 GPIO DBG_TDI

11 NC

9 PF5 GPIO

7 PF4 GPIO

5 PA3 GPIO VCOM_RTS

3 PA2 GPIO VCOM_CTS

1 GND Ground

Note: Pin PF3 is used for DBG_TDI in JTAG mode only. When Serial Wire Debugging is used, PF3 can be used for other purposes.

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

Connectors

silabs.com | Building a more connected world. Rev. 1.1 | 10

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 MGM13P 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 "De-

bug 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.

1 2

13 14

15 16

17 18

2019

TMS / SWDIO / C2D

TCK / SWCLK / C2CK

TDO / SWO

TDI / C2Dps

TRACECLK

TRACED0

TRACED1

TRACED2

TRACED3

RESET / C2CKps

GND

VTARGET

Cable Detect

Figure 3.4. Debug Connector

Note: The pinout matches the pinout of an ARM Cortex Debug+ETM connector, but these are not fully compatible as 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 JTAG test mode select, Serial Wire data, or C2 data

4 TCK / SWCLK / C2CK JTAG test clock, Serial Wire clock, or C2 clock

6 TDO/SWO JTAG test data out or Serial Wire Output

8 TDI / C2Dps JTAG test data in or C2D "pin sharing" function

10 RESET / C2CKps Target device reset or C2CK "pin sharing" function

12 TRACECLK Not connected

14 TRACED0 Not connected

16 TRACED1 Not connected

18 TRACED2 Not connected

20 TRACED3 Not connected

9 Cable detect Connect to ground

11, 13 NC Not connected

3, 5, 15, 17, 19 GND Ground

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

Connectors

silabs.com | Building a more connected world. Rev. 1.1 | 11

3.6 Simplicity Connector

The Simplicity Connector enables the advanced debugging features, such as the AEM, the virtual COM port and the Packet Trace Inter-

face, to be used towards an external target. The pinout is illustrated in the figure below.

VMCU 1

33V3

GND

BOARD_ID_SCL

BOARD_ID_SDA

2VCOM_TX

4VCOM_RX

6VCOM_CTS

8VCOM_RTS

10 PTI0_SYNC

12 PTI0_DATA

14 PTI0_CLK

16 PTI1_SYNC

18 PTI1_DATA

20 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. To

monitor 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 Description

1 VMCU 3.3 V power rail, monitored by the AEM

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 Ground

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

Connectors

silabs.com | Building a more connected world. Rev. 1.1 | 12

3.7 Debug Adapter

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 1

RST

VCOM_TX

PTI_FRAME

SWDIO

2GND

4VCOM_RX

6SWO

8SWCLK

10 PTI_DATA

Figure 3.6. Mini Simplicity Connector

Table 3.4. Mini Simplicity Connector Pin Descriptions

Pin Number Function Description

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 Serial Wire Output

7 SWDIO Serial Wire Data

8 SWCLK Serial Wire Clock

9 PTI_FRAME Packet Trace Frame Signal

10 PTI_DATA Packet Trace Data Signal

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

Connectors

silabs.com | Building a more connected world. Rev. 1.1 | 13

4. Power Supply and Reset

4.1 Radio Board Power Selection

The MGM13P 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)

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.

VMCU

AEM

USB

BAT

USB Mini-B

Connector

Advanced

Energy

Monitor

3 V Lithium Battery

(CR2032)

BAT

USB

AEM

LDO

MGM13P

5 V 3.3 V

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. BRD4306C

does not contain an USB regulator, and setting the switch in the USB postition will cause the MGM13P 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 MGM13P when the power selection switch is in the AEM position.

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

Power Supply and Reset

silabs.com | Building a more connected world. Rev. 1.1 | 14

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 MGM13P device will continue to operate in the USB and BAT modes.

4.3 MGM13P Reset

The MGM13P Module 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 MGM13P 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.

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

Power Supply and Reset

silabs.com | Building a more connected world. Rev. 1.1 | 15

5. Peripherals

The starter kit has a set of peripherals that showcase some of the features of the MGM13P.

Be aware that most MGM13P I/O routed to peripherals are also routed to the breakout pads. This must be taken into consideration

when using the breakout pads for your application.

5.1 Push Buttons and LEDs

The kit features two user push buttons, marked PB0 (BUTTON0) and PB1 (BUTTON1), and two yellow LEDs, marked LED0 and LED1.

BUTTON0 and LED0 share the connection to GPIO pin PF6, and BUTTON1 and LED1 are both connected to PF7.

To use the push buttons as inputs to the MGM13P, each button's GPIO pin must be configured as an input. Configure the pins as out-

puts to control the LEDs. Note that LEDs are connected to GPIO pins in an active-low configuration.

The push buttons are debounced by RC filters with a time constant of 1 ms.

User Buttons

& LEDs

UIF_BUTTON0_LED0

UIF_BUTTON1_LED1

PF6 (GPIO)

PF7 (GPIO)

MGM13P

Figure 5.1. Buttons/LEDs

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

Peripherals

silabs.com | Building a more connected world. Rev. 1.1 | 16

5.2 Memory LCD-TFT Display

A 1.28-inch SHARP Memory LCD-TFT is available on the kit to enable interactive applications to be developed. The display has a high

resolution of 128 by 128 pixels, and consumes very little power. It is a reflective monochrome display, so each pixel can only be light or

dark, and no backlight is needed in normal daylight conditions. Data sent to the display is stored in the pixels on the glass, which means

no continous refreshing is required to maintain a static image.

The display interface consists of an SPI-compatible serial interface and some extra control signals. Pixels are not individually addressa-

ble, instead data is sent to the display one line (128 bits) at a time.

The Memory LCD-TFT display is shared with the kit's board controller, allowing the board controller application to display useful infor-

mation when the user application is not using the display. The user application always controls ownership of the display with the

DISP_ENABLE signal:

• DISP_ENABLE = LOW: The board controller has control of the display

• DISP_ENABLE = HIGH: The user application (MGM13P) has control of the display

Power to the display is sourced from the target application power domain when the MGM13P controls the display, and from the board

controller's power domain when the DISP_ENABLE line is low. Data is clocked in on DISP_SI when DISP_CS is high, and the clock is

sent on DISP_SCLK. The maximum supported clock speed is 1.1 MHz.

DISP_EXTCOMIN is the "COM Inversion" line. It must be pulsed periodically to prevent static build-up in the display itself. Refer to the

display application information for details on driving the display:

http://www.sharpmemorylcd.com/1-28-inch-memory-lcd.html

PC8 (US1_CLK #11)

PC6 (US1_TX #11)

PD14 (US1_CS #19)

PD13 (GPIO)

PD15 (GPIO)

MGM13P

0: Board Controller controls display

1: MGM13P controls display

Figure 5.2. 128x128 Pixel Memory LCD

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

Peripherals

silabs.com | Building a more connected world. Rev. 1.1 | 17

5.3 Serial Flash

The BRD4306C Radio Board is equipped with an 8 Mbit Macronix MX25R SPI flash that is connected directly to the MGM13P. The

figure below shows how the serial flash is connected to the MGM13P.

PC8 (US1_CLK#11)

PC6 (US1_TX#11)

PC7 (US1_RX#11)

PA4 (US1_CS#1)

MGM13P

MX25R8035F

SCLK

MOSI

MISO

SCS

VMCU

VDD

8 Mbit

Figure 5.3. Radio Board Serial Flash

The MX25R series are ultra low power serial flash devices, so there is no need for a separate enable switch to keep current consump-

tion down. However, it is important that the flash is always put in deep power down mode when not used. This is done by issuing a

command over the SPI interface. In deep power down, the MX25R typically adds approximately 100 nA to the radio board current con-

sumption.

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

Peripherals

silabs.com | Building a more connected world. Rev. 1.1 | 18

5.4 Si7021 Relative Humidity and Temperature Sensor

The Si7021 I2C relative humidity and temperature sensor is a monolithic CMOS IC integrating humidity and temperature sensor ele-

ments, an analog-to-digital converter, signal processing, calibration data, and an I2C Interface. The patented use of industry-standard,

low-K polymeric dielectrics for sensing humidity enables the construction of low-power, monolithic CMOS Sensor ICs with low drift and

hysteresis, and excellent long term stability.

The humidity and temperature sensors are factory-calibrated and the calibration data is stored in the on-chip non-volatile memory. This

ensures that the sensors are fully interchangeable, with no recalibration or software changes required.

The Si7021 is available in a 3x3 mm DFN package and is reflow solderable. It can be used as a hardware- and software-compatible

drop-in upgrade for existing RH/ temperature sensors in 3x3 mm DFN-6 packages, featuring precision sensing over a wider range and

lower power consumption. The optional factory-installed cover offers a low profile, convenient means of protecting the sensor during

assembly (e.g., reflow soldering) and throughout the life of the product, excluding liquids (hydrophobic/oleophobic) and particulates.

The Si7021 offers an accurate, low-power, factory-calibrated digital solution ideal for measuring humidity, dew-point, and temperature,

in applications ranging from HVAC/R and asset tracking to industrial and consumer platforms.

The I2C bus used for the Si7021 is shared with the EXP header. The temperature sensor is normally isolated from the I2C line. To use

the sensor, SENSOR_ENABLE (PD15) must be set high. When enabled, the sensor's current consumption is included in the AEM

measurements.

SENSOR_ENABLE

Si7021

Temperature

& Humidity

Sensor

0: I2C lines are isolated, sensor is not powered

1: Sensor is powered and connected

PC11 (I2C0_SCL #15)

PC10 (I2C0_SDA #15)

PD15

SENSOR_I2C_SDA

SENSOR_I2C_SCL

VMCU

VDD

SCL

SDA

MGM13P

Figure 5.4. Si7021 Relative Humidity and Temperature Sensor

Refer to the Silicon Labs web pages for more information: http://www.silabs.com/humidity-sensors

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

Peripherals

silabs.com | Building a more connected world. Rev. 1.1 | 19

5.5 Virtual COM Port

An asynchronous serial connection to the board controller is provided for application data transfer between a host PC and the target

MGM13P. This eliminates the need for an external serial port adapter.

VCOM_ENABLE

PA0 (US0_TX#0)

PA1 (US0_RX#0)

PA5 (GPIO)

VCOM_RX

VCOM_TX

Board

Controller

MGM13P

USB Host

Isolation & Level Shift

PA2 (US0_CTS#30)

PA3 (US0_RTS#30)

VCOM_CTS

VCOM_RTS

ETH

Figure 5.5. 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 MGM13P to the board controller

VCOM_RX Receive data from the board controller to the MGM13P

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 MGM13P 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.

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

Peripherals

silabs.com | Building a more connected world. Rev. 1.1 | 20

5.5.1 Host Interfaces

Data sent to the board controller through the VCOM interface is available in two different ways to the user. At the same time, data can

be sent to the target device using these interfaces:

• 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. Some examples of device names that can be as-

sosiated with the kit:

• JLink CDC UART Port (COM5) on Windows hosts

• /dev/cu.usbmodem1411 on macOS

• /dev/ttyACM0 on Linux

Note that these are only examples of what the device might show up as, and the actual assignment depends on the operating system,

and how many devices are or have been connected previously. Data sent by the target device into the VCOM interface can be read

from this port, and data written to this port is transmitted to the traget 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.5.2 Serial Configuration

By default, the VCOM serial port is configured to use 115200 8N1, with flow control disabled/ignored. (115.2 Kbit/s, 8 databits, 1 stop

bit). 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.

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

Peripherals

silabs.com | Building a more connected world. Rev. 1.1 | 21

5.5.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 form the target device and input to the board controller. The board control-

ler 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. Please 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, and 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: Please note that enabling CTS flow control without configuring the VCOM_RTS pin can result in no data being transmitted from

the host to the target device.

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

Peripherals

silabs.com | Building a more connected world. Rev. 1.1 | 22

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 house-keeping 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 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 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 exam-

ple, 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.

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

Board Controller

silabs.com | Building a more connected world. Rev. 1.1 | 23

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 uses Serial Wire Output (SWO) to get

appliaction 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.

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

Board Controller

silabs.com | Building a more connected world. Rev. 1.1 | 24

7. Advanced Energy Monitor

7.1 Introduction

Any embedded developer seeking to make his 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 MGM13P. There are multiple features in the profiler soft-

ware that allows 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 Advanced Energy Monitor (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 alomst 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 appli-

cation'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.

MGM13P

LDO

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.

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

Advanced Energy Monitor

silabs.com | Building a more connected world. Rev. 1.1 | 25

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 MGM13P in

realtime.

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

Advanced Energy Monitor

silabs.com | Building a more connected world. Rev. 1.1 | 26

8. On-Board Debugger

The Wireless STK Mainboard contains an integrated debugger, which can be used to download code and debug the MGM13P. In addi-

tion 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 con-

nector 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 dis-

covery 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 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 nor-

mally on the form 44xxxxxxx.

The J-Link serial number is normally printed at the bottom of the kit LCD display.

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

On-Board Debugger

silabs.com | Building a more connected world. Rev. 1.1 | 27

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 MGM13P Module 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 MGM13P on the kit.

RADIO BOARD

Board

Controller

USB

Host

Computer

DEBUG HEADER

External

Hardware

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.

Board

Controller

USB

Host

Computer

DEBUG HEADER

External

Hardware

RADIO BOARD

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 MGM13P

on the kit.

Board

Controller

USB

Host

Computer

DEBUG HEADER

External Debug Probe

RADIO BOARD

Figure 8.3. Debug IN

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

On-Board Debugger

silabs.com | Building a more connected world. Rev. 1.1 | 28

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 MGM13P 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.

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

On-Board Debugger

silabs.com | Building a more connected world. Rev. 1.1 | 29

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 adapt-

er 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.

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

Kit Configuration and Upgrades

silabs.com | Building a more connected world. Rev. 1.1 | 30

10. Schematics, Assembly Drawings, and BOM

Schematics, assembly drawings, and bill of materials (BOM) are available through Simplicity Studio when the kit documentation pack-

age has been installed.

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

Schematics, Assembly Drawings, and BOM

silabs.com | Building a more connected world. Rev. 1.1 | 31

11. Kit Revision History

The kit revision can be found printed on the kit packaging label, as outlined in the figure below.

SLWRB4306C

MGM13P02 Mighty Gecko Module Radio Board

124802042

22-11-17

A00

Figure 11.1. Kit Label

11.1 SLWRB4306C Revision History

Kit Revision Released Description

A00 22 November 2017 Initial release.

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

Kit Revision History

silabs.com | Building a more connected world. Rev. 1.1 | 32

12. Document Revision History

Revision 1.1

March 2018

• Added more information to section 5.5 Virtual COM Port.

Revision 1.0

February 2018

• Initial document release.

UG340: MGM13P02 Mighty Gecko Module Radio Board User's Guide

Document Revision History

silabs.com | Building a more connected world. Rev. 1.1 | 33

http://www.silabs.com

Silicon Laboratories Inc.

400 West Cesar Chavez

Austin, TX 78701

USA

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 and limitation to product information, specifications, and descriptions herein, and does not give warranties as to the accuracy or completeness of the included

information. Silicon Labs shall have no liability for the consequences of use of the information supplied herein. This document does not imply or express copyright licenses granted

hereunder to design or fabricate any integrated circuits. The products are not designed or authorized to be used within any Life Support System 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.

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®, Micrium, Precision32®, ProSLIC®, Simplicity Studio®, SiPHY®, Telegesis, the Telegesis Logo®, USBXpress®, Zentri 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.