SILICON LABS Si-MB4002A Wireless Pro Kit Mainboard User Guide

SILICON LABS Si-MB4002A Wireless Pro Kit Mainboard

Product Information

Specifications:

• Product Name: Si-MB4002A Wireless Pro Kit Mainboard
• Manufacturer: Silicon Labs
• Compatibility: Carrier board for Silicon Labs radio boards

Mainboard Features:

• Contains sensors and peripherals
• Demonstrates capabilities of the attached radio board
• 20-pin EXP header for connecting EXP boards or I/Os on the radio board target IC

Software Support:
This document focuses on using the Pro Kit Mainboard features. For connectivity information between a Silicon Labs wireless device on a radio board and a mainboard feature, refer to the user’s guide for the specific radio board.

Product Usage Instructions

1. Hardware Overview:
   The hardware layout and block diagram provide insights into the physical structure of the mainboard.

2. Power Supply and Reset:
   Understand the power selection for the radio board, kit power, and target reset functionalities.

3. Connectivity:
   Learn about host-to-target communication, limitations, and troubleshooting methods.

4. Advanced Energy Monitor:
   Explore the introduction, code correlation, and details of the AEM circuit for energy monitoring.

5. Kit Configuration and Upgrades:
   Discover how to perform firmware upgrades to enhance the functionality of the mainboard.

6. Schematics, Assembly Drawings, and BOM:
   Access detailed schematics, assembly drawings, and Bill of Materials for reference.

FAQ:

Q: How do I connect EXP boards to the mainboard?
A: Use the 20-pin EXP header on the mainboard for connecting EXP boards or I/Os on the radio board target IC.

The Silicon Labs Pro Kit Mainboard is a carrier board for Silicon Labs radio boards.
The mainboard provides all necessary tools for application development and debugging of both the attached radio board as well as external hardware. Its features include an on-board J-Link debugger, Packet Trace Interface (PTI) support, and a Virtual COM port. The embedded Advanced Energy Monitor (AEM) can accurately measure the radio board current consumption from 0.1 µA to 495 mA with a time resolution of 100 kSps. All of these features can be accessed either through USB or Ethernet. The mainboard also contains sensors and UI peripherals for easy demonstration of some of the capabilities of an attached radio board.

MAINBOARD FEATURES

• Advanced Energy Monitor
• Packet Trace Interface
• Logic analyzer
• 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
• Joystick
• 20-pin 2.54 mm EXP header
• Breakout pads for radio board I/O
• CR2032 coin cell battery support

SOFTWARE SUPPORT

• Simplicity Studio
• Energy Profiler
• Network Analyzer

ORDERING INFORMATION

• Si-MB4002A

Introduction

The Pro Kit Mainboard is a carrier board for all Silicon Labs radio boards, featuring 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 demonstrate some of the many capabilities of the attached radio board. The mainboard also has a 20-pin EXP header which can be used for connecting EXP boards to the kit or for easy connection to I/Os on the radio board target IC.

Note:
This document explains how to use the Pro Kit Mainboard features. Information about connectivity between a Silicon Labs wireless device on a radio board and a mainboard feature is found in the user’s guide for the specific radio board.

Ordering Information
The Pro Kit mainboard is included in all Silicon Labs wireless Pro Kits. It can also be purchased stand-alone.

Table 1.1. Ordering Information

1x Battery holder for two AA batteries

1x 10-pin Mini Simplicity debug cable 1x wire harness for logic probe

2x 2×16 Dual 2.54 mm headers for breakout connectors

Getting Started
Detailed instructions for how to get started can be found on the Silicon Labs web pages: http://www.silabs.com/dev-tools.

Hardware Overview

Hardware Layout
The layout of the Wireless Pro Kit Mainboard is shown below.

Block Diagram
A block diagram of the Wireless Pro Kit is shown in the figure below.

Connectors

This chapter gives you an overview of the Wireless Pro Kit Mainboard connectivity. The placement of the connectors is shown in the figure below.

J-Link USB Connector
The J-Link USB connector is situated on the left side of the mainboard and provides access to the kit features described in Section 6. Board Controller through the USB interface. In addition to providing access to the development features of the kit, this USB connector is also the main power source for the kit powering both the board controller and the AEM as described in Section 4. Power Supply and Reset.

Ethernet Connector
The Ethernet connector is situated on the left side of the mainboard and provides access to the kit features described in Section 6. Board Controller over TCP/IP. The J-Link USB connector must be connected while using this interface to provide power to the Wireless Pro Kit as power is not supplied over the Ethernet connector.

Breakout Pads
Most of the radio board pins are routed from the radio board to breakout pads at the top and bottom edges of the Wireless Pro Kit 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 radio board map to the PINs printed on the breakout pads. To see the available functions on each, refer to the datasheet for the IC on the attached radio board.

EXP Header

• The EXP header is an angled, 20-pin header that allows the connection of peripherals or plugin boards to the kit. It is located on the right-hand side of the mainboard and contains several I/O pins that can be used with most of the radio board’s features. Additionally, the VMCU, 3V3, and 5V power rails are also exposed.
• The pin-out is standardized so commonly used peripherals, such as SPI, UART, and I2C, are available in fixed locations. The remaining pins are assigned to general-purpose IO. This allows the definition of EXP boards that can be used with most radio boards.
• The figure below shows the pin assignment of the EXP header.

Logic Analyzer Connector
The Wireless Pro Kit Mainboard includes an on-board, eight-channel logic analyzer. It enables four digital signals to be sampled and displayed in Simplicity Studio, in addition to the state of the onboard user interface LEDs and buttons. The logic analyzer is a good tool for correlating specific events to the AEM energy profile and packet trace data as these are time-synchronized and can be visualized together. The sampling rate of 100 kHz limits its use in decoding digital protocols like I2C or SPI.

The logic analyzer connector is situated on the top right side of the Wireless Pro Kit Mainboard. Four signals (channels 0-3) can be connected to the logic analyzer using this connector. The test probes can be connected to the kit itself or an external board connected to the Wireless Pro Kit Mainboard. Note that in both cases the connected signals must be digital, and the voltages referenced to ground and VMCU on the Wireless Pro Kit Mainboard. The table below gives an overview of the logic analyzer signals.

Note:
Test probes are not included with all Pro Kits. If needed, they can be obtained separately as Si-DA001A Pro Kit Mainboard Accessory Kit.

Table 3.1. Logic Analyzer Signal Description

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 radio board on the radio board. When set to “Debug OUT”, this connector allows the kit to be used as a debugger toward 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 onboard target device supports these features.

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

between target and debugger.
2| TMS / SWDIO / C2D| JTAG TMS, Serial Wire data I/O, or C2 data
4| TCK / SWCLK / C2CK| JTAG TCK, Serial Wire clock, or C2 clock
6| TDO/SWO| JTAG TDO, or Serial Wire Output
8| TDI / C2Dps| JTAG TDI or C2D pin sharing function
9| GNDDetect| Can be used by the target system for debugger presence detection.
10| RESET / C2CKps| Target CPU reset or C2CK pin-sharing function
12| TRACK| ETM trace clock pin
14| TRACED0| Trace data output pin 0
16| TRACED1| Trace data output pin 1
18| TRACED2| Trace data output pin 2
20| TRACED3| Trace data output pin 3
7, 11, 13| NC| Not connected
3, 5, 15, 17, 19| GND| Ground

Simplicity Connector
The Simplicity Connector enables advanced debugging features, such as the AEM, the virtual COM port, and the Packet Trace Interface, to be used toward an external target. The pinout is illustrated in the figure below.

Note:
The 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 mainboard to avoid adding the radio board’s current consumption to the measurements.

Table 3.3. Simplicity Connector Pin Descriptions

Mini Simplicity Connector
The Mini Simplicity Connector on the Wireless Pro Kit Mainboard offers advanced debugging features on a 10-pin connector to be used toward an external target. The Mini Simplicity Connector offers the following features:

• Serial Wire Debug (SWD) with SWO
• Packet Trace Interface (PTI)
• Virtual COM port (VCOM)
• AEM monitored the voltage rail

Note:
The current drawn from the VMCU voltage pin is included in the AEM measurements. When monitoring the current consumption of an external target with the AEM, unplug the radio board from the Wireless Pro Kit Mainboard to avoid adding the radio board’s current consumption to the measurements.

Table 3.4. Mini Simplicity Connector Pin Descriptions

the AEM when the power selection switch is in the “AEM” position.
2| GND| Ground
3| RESET| Target device reset
4| VCOM_RX| Virtual COM Rx
5| VCOM_TX| Virtual COM Tx
6| SWO| Serial Wire Output
7| STUDIO| Serial Wire Data
8| SWCLK| Serial Wire Clock
9| PTI_FRAME| Packet Trace Frame Signal
10| PTI_DATA| Packet Trace Data Signal

Note:
Mini Simplicity Connector pin-out is referenced from the device target side. I.e. VCOM_RX is output from the board controller and input to the connected device.

Power Supply and Reset

Radio Board Power Selection
The radio board on a Wireless Pro Kit can be powered by one of these sources:

• The debug USB cable
• A 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 Pro Kit Mainboard. The figure below shows how the different power sources can be selected with the slide switch.

Note:
The AEM can only measure the current consumption of the radio board when the power selection switch is in the AEM position.

AEM position:
With the switch in the AEM position, a low-noise 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.

SELF-position:
With the switch in the SELF position, the radio board can be self-powered. The typical use case is for radio boards with wireless devices with USB support, allowing a USB device application that operates as a bus-powered device.

BAT position:
With the switch in the BAT position, the VMCU rail is sourced from the CR2032 coin cell holder or the 2-pin JST connector. This is the switch position that should be used when the radio board is powered by an external power source. 1.8 V and 3.6 V instead of a coin cell. The coin cell battery is not protected from reverse current, and it is, therefore, important to remove the coin cell battery from the CR2032 socket if applying external power. With the switch in this position, no current measurements are active.

Note:
The current sourcing capabilities of a coin cell battery might be too low to supply certain wireless applications.

Kit Power
The board is designed to be powered from the debug USB port. In this case, there are normally two main contributors to its current consumption:

• VMCU – this is the target, or radio board, power domain. This is monitored by the AEM.
• 3V3 – this is the board controller power domain. This is not monitored by the AEM.

The current consumption on 3V3 is fairly deterministic and stable, typically around 250 mA. The current consumption of VMCU, on the other hand, varies widely. It depends on which radio board is attached, the application running on the radio board, and also the position of the power switch. Since the regulators on the mainboard are linear, the total current required by the kit is approximately the same as the sum of these two domains, i.e. the total current on VMCU plus 250 mA. Additionally, both the 3V3 and 5V power nets are available on the breakout pads on the EXP header, and on the radio board. These must also be taken into account if used. 3V3 is always sourced from the USB connector and 5V comes from USB when the power switch is in the AEM position.

Use a USB host or power supply and cables that can deliver at least the total amount of current required by the kit. The board can also operated without USB power. In this case, the power switch is to be set in the BAT position so the VMCU domain is powered by the coin-cell battery or through the JST PH connector. When there is no VBUS, some of the isolation circuits will be powered by VMCU, adding a couple of hundred nanoamps to the current consumption. Therefore, if one wants to do accurate measurements of the current consumption through the battery header, the board must also be powered by USB.

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 radio board device will continue to operate in the BAT mode.

AEM Power
The supply for the target power domain (VMCU) is a linear regulator integrated with the AEM described in Section 7. Advanced Energy Monitor when the power select switch is in the AEM position. The output voltage of the regulator can be adjusted between 1.8 V and 3.6 V using the admin console. The output current is limited by an overcurrent protection (OCP) function, which depends on the programmed VMCU voltage: OCP (A) ≈ VMCUSET (V) x 0.2 (A/V). Approaching or exceeding the OCP limit is not recommended as the output voltage will be pulled low, which causes a loss of function.

Target Reset
The radio board DEVICE_CLASS 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 radio board 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.

Peripherals

• The Wireless Pro Kit has a set of peripherals that showcase some of the radio board features.
• Note that most radio board I/Os routed to peripherals are also routed to the breakout pads or the EXP header, which must be taken into consideration when using these I/Os.

Push Buttons and LEDs

• The kit has two user push buttons marked BTN0 and BTN1. They are connected directly to the radio board and are debounced by RC filters with a time constant of 1 ms.
• The kit also features two yellow LEDs marked LED0 and LED1 that are controlled by GPIO pins on the radio board. The LEDs are active-high.

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 continuous refreshing is required to maintain a static image. The display interface consists of a 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 (radio board) has control of the display

Power to the display is sourced from the target application power domain when the radio board 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.

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

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

Virtual COM Port
An asynchronous serial connection to the board controller is provided for application data transfer between a host PC and the target radio board. This eliminates the need for an external serial port adapter.

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

controller when it is ready to receive more data
VCOM_RTS| Request to Send hardware flow control output, asserted by the radio board 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 Pro Kit Mainboard.

Note:
The VCOM port is only available when the board controller is powered, which requires the J-Link USB cable to be inserted.

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.

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:

• WPK> serial from config
• Usage: serial from config [–nostore] [handshake <rts/cts/tests/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.

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 a 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 the transmission of data toward 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

(VCOM_RTS) is ignored.
arts| RTS (VCOM_CTS) is driven by the board controller to halt the target from transmitting when the 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.
results| RTS (VCOM_CTS) is driven by the board controller to halt the target when buffers are full. Data is transmitted to the target device if CTS (VCOM_RTS) is asserted and halted when de-asserted.

Note:
Enabling CTS flow control without configuring the VCOM_RTS pin can result in no data being transmitted from the host to the target device.

Board Controller

Introduction
The Wireless Pro Kit 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 provides real-time energy profiling of the user application.
• The Packet Trace Interface is used in conjunction with PC software to provide detailed insight into an active radio network.
• The Virtual COM Port and Virtual UART interfaces, provide ways to transfer application data between the host PC and the target processor.
• The admin console provides the 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 upgrades.

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.

Connecting

• The admin console is available when the Wireless Pro Kit is connected to Ethernet using the Ethernet connector in the top left corner of the mainboard. 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 WPK> prompt is displayed.

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:

The help command can be used in conjunction with any top-level command to get a list of sub-commands with descriptions. For example, PTI help will print a list of all available sub-commands of PTI:

This means that running pti enable will enable packet trace.

Command Examples

PTI Configuration

• PTI config 0 February 1600000
• Configures PTI to use the “EFRUART” mode at 1.6 Mb/s.

Serial Port Configuration

• serial config from handshake enable
• Enables hardware handshake on the VCOM UART connection.

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 STK makes the VUART interface available on TCP/IP port 4900.

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.

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 the 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 the 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 so as not to instantiate the RTT connection.

Limitations

• Because the SWO connection can be disabled by the debugger at will, the target application needs 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. 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, refrain from using VUART.

Troubleshooting

operations, the host computer manually disables SWO on the target 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 was 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 replugging the USB cable.

Advanced Energy Monitor

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 radio board. 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. The Energy Profiler is available through Simplicity Studio.

Code Correlation
By using the Energy Profiler, current consumption, and voltage can be measured and linked to the actual code running on the radio board in real-time. The Energy Profiler gets its data from the board controller on the mainboard through the Advanced Energy Monitor (AEM). 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 peri-odic intervals 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.

AEM Circuit
The AEM circuit measures the current through a sense resistor inside the feedback loop of a low-dropout regulator (LDO). The output voltage of this LDO powers the radio board when the power slide switch is in the AEM position.

Note:

• The VMCU regulator feedback point is after the sense resistor to ensure that the VMCU voltage is kept constant when the output current changes. Series resistances in the current path will, however, cause some IR drop on VMCU.
• The AEM circuit only works when the kit is powered and the power switch is in the AEM position.

AEM Details
The key parameters of the AEM are summarized in the table below, with more in- depth information given in the text that follows.

Table 7.1. Advanced Energy Monitor Parameters

The AEM circuitry on the Wireless Pro Kit Mainboard is capable of measuring current signals in the range of approximately 0.1 µA to 495 mA. This is accomplished through a combination of a highly capable current sense amplifier, multiple sense resistors and gain stages, and signal processing within the kit’s board controller before the current sense signal is read by a host computer with a 100 kHz sample rate for display and/or storage. Averaging on the output data may be required to achieve sufficient accuracy in some situations, such as low currents, which can be traded for lower bandwidth. High current applications require that the regulator can supply enough current as described in Section 4.2 Kit Power.

At low currents, the current sense amplifier measures the voltage drop over a 10.5 Ω resistive path. The gain stage further amplifies this voltage with two different parallel gain settings to obtain two current ranges. The transition between these two ranges occurs around 150 µA. When the current exceeds a threshold, which is typically between 10 and 30 mA, the AEM circuitry switches from the 10.5 Ω resistive path to a 0.5 Ω sense resistor and is now capable of measuring currents up to approximately 495 mA. Should the current drop below the threshold again, the sense resistor is changed back to the 10.5 Ω resistive path and the AEM is back to using two different gain stages depending on whether the current is above or below 150 µA.

The expected typical accuracy of the AEM on the Wireless Pro Kit Mainboard is within 1 %, except for currents in the low tens of micro-amps where offset errors start to dominate. In this low current region, the expected typical accuracy is some hundred nanoamps. At kit power-up or on a power cycle, an automatic AEM calibration is performed which compensates for offset errors in the current sense amplifiers. To achieve the stated accuracy, averaging of the AEM output data is required in certain situations (typically at low currents and close to the bottom of the measurement ranges) to reduce noise. Averaging can be applied in the Energy Profiler to suit different requirements during or after the acquisition. The analog bandwidth of the measurement circuit depends on multiple factors, such as output current and capacitance on the VMCU net, and may be lower than the output data rate. Generally, higher output current and lower capacitance on VMCU give a higher analog bandwidth.

On-Board Debugger

The Wireless Pro Kit Mainboard contains an integrated debugger, which can be used to download code and debug the radio board. 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

For debugging to work properly, make sure the selected debug interface is supported by the target device. The debug connector on the board supports all three of these modes.

Host Interfaces

• The Wireless Pro Kit supports connecting to the onboard 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.

USB Interface
The USB interface is available whenever the USB connector on the left-hand side of the mainboard is connected to a computer.

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 mainboard USB connector.

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.

Debug Modes
The kit can be used in various debug modes as explained in this chapter. The on-board debugger can be used to debug the radio board on the radio board, or it can be used to debug a supported external target board using either the debug connector or the Mini Simplicity Connector. An external debugger can furthermore be used to debug the radio board on the radio board using the debug connector. Selecting the active debug mode is done in Simplicity Studio.

Debug MCU:
In this mode, the onboard debugger is connected to the radio board on the kit. To use this mode, set the debug mode to [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 using the debug connector. To use this mode, set the debug mode to [Out].

Debug IN:
In this mode, the on-board debugger is disconnected and an external debugger can be used to debug the radio board on the kit over the debug connector. To use this mode, set the debug mode to [In].

Note:
For “Debug IN” to work, the kit board controller must be powered through the debug USB connector.

Debug MINI:
In this mode, the on-board debugger can be used to debug a supported Silicon Labs device mounted on a custom board over Serial Wire Debug. Virtual COM port and Packet Trace Interface are also available in this mode. To use this mode, set the debug mode to [Mini].

Depending on the position of the mainboard power switch and the presence of the battery, the Wireless Pro Kit can supply voltage to the VMCU pin on the Simplicity connector and the Mini Simplicity connector. When using these connectors, care must be taken to avoid power conflicts with the external hardware. For more information regarding debugging external hardware see AN958: Debugging and Programming Interfaces for Custom Designs.

Debugging During Battery Operation

• When the radio board 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 GPIOs used for debugging, which are exposed on the breakout pads.

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 silabs.com/simplicity.
• In the main window of 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 these settings to open the kit configuration dialog.

Firmware Upgrades

• You can upgrade the kit firmware 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.

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 kit page on the Silicon Labs website: silabs.com.

Kit Revision History

The kit revision can be found printed on the kit packaging label, as outlined in the figure below. The revision history given in this section may not list every kit revision. Revisions with minor changes may be omitted.

Si-MB4002A Revision History

Document Revision History

Revision 1.0

• March 2024
• Initial document version.

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 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 the use of the information supplied in this document. This document does not imply or expressly grant any license to design or fabricate any integrated circuits. The products are not designed or authorized to be used within any FDA Class III devices, applications for which FDA premarket approval is required or Life Support Systems without the specific written consent of Silicon Labs. A “Life Support System” is any product or system intended to support or sustain life and/or health, which, if it fails, can be reasonably expected to result in significant personal injury or death. Silicon Labs products are not designed or authorized for military applications. Silicon Labs products shall under no circumstances be used in weapons of mass destruction including (but not limited to) nuclear, biological, or chemical weapons, or missiles capable of delivering such weapons. Silicon Labs disclaims all express and implied warranties and shall not be responsible or liable for any injuries or damages related to the use of a Silicon Labs product in such unauthorized applications.

Note:
This content may contain offensive terminology that is now obsolete. Silicon Labs is replacing these terms with inclusive language wherever possible. For more information, visit www.silabs.com/about-us/inclusive-lexicon- project.

Trademark Information
Silicon Laboratories Inc., Silicon Laboratories®, Silicon Labs®, SiLabs® and the Silicon Labs logo®, Bluegiga®, Bluegiga Logo®, EFM®, EFM32®, EFR, Ember®, Energy Micro, Energy Micro logo and combinations thereof, “the world’s most energy friendly microcontrollers”, Redpine Signals®, WiSeConnect, n-Link, ThreadArch®, EZLink®, EZRadio®, EZRadioPRO®, Gecko®, Gecko OS, Gecko OS Studio, Precision32®, Simplicity Studio®, 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
• www.silabs.com.

References

• Silicon Labs
• Simplicity Studio - Silicon Labs
• Silicon Labs
• Development Tools - Silicon Labs
• Relative Humidity and Temperature Sensors - Silicon Labs
• Simplicity Studio - Silicon Labs

Read User Manual Online (PDF format)

Download This Manual (PDF format)

Download this manual  >>