SILICON LABS UG432 BGM220P Wireless Gecko Module Starter Kit User Guide

UG432 BGM220P Wireless Gecko Module Starter Kit

UG432: BGM220P Wireless Gecko Module Starter Kit User’s Guide

A Wireless Starter Kit with the BRD4311A Radio Board is an excellent starting point to get familiar with the BGM220P Wireless Gecko PCB Module. It also provides the necessary tools for developing a Silicon Labs wireless application.

BRD4311A contains the BGM220P 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 BGM220P’s many capabilities.

This document describes how to use the BRD4311A Radio Board together with a Wire less Starter Kit Mainboard.

BRD4311A RADIO BOARD FEATURES

• BGM220P Wireless Gecko PCB Module with 512 kB Flash, 32 kB RAM. Fully integrated chip antenna, RF matching network, crystals, and decoupling capacitors (BGM220PC22HNA2).
• 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 128×128 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

• SLWSTK6103A
• SLWRB4311A

silabs.com | Building a more connected world.

Downloaded from Arrow.com.

UG432: BGM220P Wireless Gecko Module Starter Kit User’s Guide
Introduction

1. Introduction

The BGM220P Wireless 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 enables 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 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 demonstrates some of the many capabilities of the BGM220P. 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 BGM220P Wireless Gecko Module Radio Board (BRD4311A) 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

BRD4311A can be obtained as part of SLWSTK6103A Wireless Gecko Module Starter Kit or as a separate radio board, SLWRB4311A.

Table 1.1. Ordering Information

1x BRD4001A Wireless Starter Kit Mainboard
1x BRD4310A BGM220S Wireless Gecko Module Radio Board
1x BRD4311A BGM220P Wireless Gecko Module Radio Board
1x BRD8010A Debug Adapter Board
1x USB Type A to Mini-B cable
1x 10-pin flat cable for debug adapter

SLWRB4311A| BGM220P Wireless Gecko Module Radio
Board|

1x BRD4311A BGM220P Wireless 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/bluetooth-getstarted

2. Hardware Overview

2.1 Hardware Layout

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

Figure 2.1. Kit Hardware Layout

2.2 Block Diagram

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

Figure 2.2. Kit Block Diagram

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.

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.

3.3 Breakout Pads

Most pins of the BGM220P 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 BGM220P map to the pin numbers printed on the breakout pads. To see the available functions on each, refer to the data sheet for BGM220PC22HNA2.

Figure 3.2. Breakout Pad Pin Mapping

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 BGM220P Wireless
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.

Figure 3.3. EXP Header

3.4.1 EXP Header Pinout

The pin-routing on the BGM220P 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

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

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 2×10 1.27 mm straight cable instead.

Table 3.2. Debug Connector Pin Descriptions

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.

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

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.

Figure 3.6. Mini Simplicity Connector

Table 3.4. Mini Simplicity Connector Pin Descriptions

4. Power Supply and Reset

4.1 Radio Board Power Selection

The BGM220P 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.

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

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

4.3 BGM220P Reset

The BGM220P 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 BGM220P 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.

5. Peripherals

The starter kit has a set of peripherals that showcase some of the features of the BGM220P.
Note that most BGM220P I/O routed to peripherals are also routed to the breakout pads or the EXP header, which must be taken into consideration when using these.

5.1 Push Buttons and LEDs

The kit has 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 PB00, and BUTTON1 and LED1 are both connected to PB01.

To use the push buttons as inputs to the BGM220P, each button’s GPIO pin must be configured as an input. Configure the pins as outputs 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.

Figure 5.1. Buttons/LEDs

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 x 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 addressable,
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 information
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 (BGM220P) has control of the display

Power to the display is sourced from the target application power domain when the BGM220P 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 LS013B7DH03 documentation for more information on driving the display.

Figure 5.2. 128×128 Pixel Memory LCD

5.3 Serial Flash

The BRD4311A Radio Board is equipped with an 8 Mbit Macronix MX25R SPI flash that is connected directly to the BGM220P. The figure below shows how the serial flash is connected to the BGM220P.

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

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 elements, 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 3×3 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 3×3 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 (PD02) must be set high. When enabled, the sensor’s current consumption is included in the AEM measurements.

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

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 BGM220P. This eliminates the need for an external serial port adapter.

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

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.

5.5.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 associated 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.5.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.

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

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.

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

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 (VUART) interface provides a high performance application data interface that does not require additional I/O pins apart from the debug interface.
The Wireless Starter Kit makes the VUART interface available on TCP/IP port 4900.

6.2.1 Target to Host

Target to host communication utilizes the SWO-pin of the debug interface through the ITM debug peripheral. This approach allows a sleepy target device to enter all energy modes, and still wake up intermittently to send debug information. The baud rate of the SWO data is locked to 875 kHz.
VUART utilizes ITM stimulus port 0 for general purpose printing. Silicon Labs’ networking stacks utilize ITM stimulus port 8 for debug printing. The data on port 8 is encapsulated in additional framing and will also appear in the Simplicity Studio Network Analyzer.

6.2.2 Host to Target

Host to target communication utilizes SEGGER’s Real Time Transfer (RTT) technology. A full explanation of how this works can be found in J-Link/J-Trace User Guide (UM08001). Briefly summarized, RTT consists of a structure called the RTT Control Block, which is
located in RAM. This control block points to circular buffers that the debugger can write data into. The target application can then read data out of this circular buffer.
The board controller will start searching for the RTT Control Block upon receiving data on TCP/IP port 4900. If the board controller is unable to locate the RTT Control Block it will return an error message on the same connection. For the board controller to be able to
locate the RTT Control Block it has to be aligned on a 1024-byte boundary in RAM.
After initializing the RTT connection the target will only enter emulated EM2 and EM3 where the power consumption remains similar to EM1. This is because RTT utilizes the debug interface which requires use of high frequency oscillators. Energy modes EM4S and EM4H will work as normal. When debugging energy consumption it is therefore important to not send data on TCP/IP port 4900 as not to instantiate the RTT connection.

6.2.3 Limitations

• Because the SWO-connection can be disabled by the debugger at will, it is important for the target application to verify that SWO is enabled and configured before each transmission on the interface.
• After initializing host to target communication over RTT by sending data on TCP/IP port 4900 the target application will be unable to enter EM2 and EM3. This is because RTT utilizes the debug connection of the target.
• VUART might not work reliably during an active debugging session. This is because there is contention over the target’s debug interface, and the board controller will defer accessing the target until it is made available by the host debugger.
• VUART is designed with the assumption that only the board controller will access the RTT control block. If the target application uses RTT for other purposes, such as Segger SystemView, please refrain from using VUART.

6.2.4 Troubleshooting

No data received after ending a
debug session.|

After certain debugger operations the host computer manually disables SWO on the target in order to conserve power. This might cause SWO data to not appear if the target application initialized
SWO before the debugger has disconnected. Either press the RESET-button on the Wireless Starter Kit to reset the target application, or make sure that the target application verifies that SWO is enabled and configured before sending any data.

No data received after flashing
a new application.
Other issues|

Disconnect from TCP port 4900, press the RESET-button on the kit, then reconnect to 4900. If this does not fix the issue, try to restart the kit by unplugging and replunging the USB cable.

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

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.

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 BGM220P in real time.

8. On-Board Debugger

The Wireless STK Mainboard contains an integrated debugger, which can be used to download code and debug the BGM220P. 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.
UG432: BGM220P Wireless Gecko Module Starter Kit User’s Guide
On-Board Debugger silabs.

8.2 Debug Modes

To program external devices, use the debug connector to connect to a target board and set the debug mode to [Out]. The same connector
can also be used to connect an external debugger to the BGM220P 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 BGM220P on the kit.

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.

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

Figure 8.3. Debug IN

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 BGM220P is battery-powered 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, 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.

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 are shown. Click the [Change] link next to any of them to open the kit configuration dialog.

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.

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. They are also available from the Silicon Labs website and kit page.

11. Kit Revision History

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

Figure 11.1. Kit Label

11.1 SLWSTK6103A Revision history

Boards upped to BRD4310A Rev. A03 and BRD4311A Rev. A04.

A02| 6 March 2020|

Initial kit release. Includes BRD4310A Rev. A02 and BRD4311A Rev. A03.

11.2 SLWRB4311A Revision History

Initial release with BRD4311A Rev. A03.

A02| 5 March 2020|

Initial release with BRD4311A Rev. A02.

12. Document Revision History

Revision 1.0
July, 2020
• Initial document release.

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 & Community
www.silabs.com/community

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 lll devices, applications for which FDA premarket approval s 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®, Gecko OS, Gecko OS Studio, ISOmodem®, Precision32®, ProSLIC®, Simplicity Studio®, SiPHY®, Telegesis, the Telegesis Logo®, USBXpress®, Zentri,  the Zentri logo and Zentri DMS, Z-Wave®, 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. Wi-Fi is a registered trademark of the Wi-Fi Alliance. 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

Downloaded from Arrow.com.

References

• commands.net
• data.No
• Gerhard Hacker · my business home page
• Relative Humidity and Temperature Sensors - Silicon Labs

Read User Manual Online (PDF format)

Download This Manual (PDF format)

Download this manual  >>