Silicon Laboratories UDP C8051F390 User manual

Rev. 0.2 2/14 Copyright © 2014 by Silicon Laboratories C8051F39x
C8051F39x/F37x
UDP C8051F390/F370 MCU CARD USER’SGUIDE
1. Introduction
The Unified Development Platform (UDP) provides a development and demonstration platform for Silicon
Laboratories microcontrollers and the Silicon Laboratories software tools, including the Silicon Laboratories
Integrated Development Environment (IDE).
Note: The C8051F39x/F37x family has two MCU cards, one for the C8051F39x devices and one for the C8051F37x devices.
The information in this document applies to both sets of hardware, and the examples (with the exception of the
EEPROM) will run on both.
Figure 1. Unified Development Platform
2. Relevant Documents
This document provides a hardware overview for the Unified Development Platform (UDP) system UDP
C8051F390/F370 MCU Card. Additional information on the UDP system can be found in the documents listed in
this section.
Motherboard User’s Guide: The UDP Motherboard User’s Guide contains information on the motherboard
features and can be found at www.silabs.com.
Card User’s Guides: The UDP MCU Card and Radio Card User’s Guides can be found at www.silabs.com.

C8051F39x/F37x
2 Rev. 0.2
3. Hardware Setup
3.1. Using the MCU Card Alone
Refer to Figure 2 for a diagram of the hardware configuration when using the MCU card without a UDP
motherboard.
1. Connect the USB Debug Adapter to the 2x5 debug connector on the MCU card with the 10-pin ribbon
cable.
2. Connect one end of the USB cable to the USB connector on the USB Debug Adapter.
3. Connect the other end of the USB cable to a USB Port on the PC.
4. Move the SW1 switch to the VREG position.
5. Connect the 9 V DC adapter to P1.
Notes:
Use the Reset button in the IDE to reset the target when connected using a USB Debug Adapter.
Remove power from the MCU card and the USB Debug Adapter before connecting or disconnecting the
ribbon cable from the MCU card. Connecting or disconnecting the cable when the devices have power can
damage the device and/or the USB Debug Adapter.
Figure 2. Hardware Setup Using the MCU Card Alone
USB Debug Adapter
USB
Connectivity
Power
Adapter (P1)
VDD
Selection
Switch

C8051F39x/F37x
Rev. 0.2 3
3.2. Using the MCU Card with the UDP Motherboard
Refer to Figure 3 for a diagram of the hardware configuration when using the MCU card with a UDP motherboard.
1. Connect the MCU card to the UDP motherboard slot.
2. (Optional) Connect the I/O card to the UDP motherboard slot.
3. (Optional) Connect a radio card to the radio card slot in the UDP motherboard.
4. (Optional) Connect an EZLink card to the EZLink card slot in the UDP motherboard.
5. Connect the USB Debug Adapter to the 2x5 debug connector on the MCU card with the 10-pin ribbon
cable.
6. Connect one end of the USB cable to the USB connector on the USB Debug Adapter.
7. Connect the other end of the USB cable to a USB Port on the PC.
8. Connect the ac/dc power adapter to power jack J20 on the UDP motherboard. The board can also be
powered from the J16 USB or J1 mini USB connectors.
9. Move the SW1 switch on the MCU card to the UDP MB position.
10. Move the S3 power switch on the UDP motherboard to the ON position.
Notes:
Use the Reset button in the IDE to reset the target when connected using a USB Debug Adapter.
Remove power from the target board and the USB Debug Adapter before connecting or disconnecting the
ribbon cable from the target board. Connecting or disconnecting the cable when the devices have power
can damage the device and/or the USB Debug Adapter.
The MCU card can be used alone without the motherboard. However, the motherboard must be powered if
an MCU card is connected.
Figure 3. Hardware Setup Using the Unified Development Platform
USB Debug Adapter
Power
Adapter
(J20)
USB
Connector
(J16)
VDD
Selection
Switch

C8051F39x/F37x
4 Rev. 0.2
4. Software Setup
Simplicity Studio greatly reduces development time and complexity with Silicon Labs EFM32 and 8051 MCU
products by providing a high-powered IDE, tools for hardware configuration, and links to helpful resources, all in
one place.
Once Simplicity Studio is installed, the application itself can be used to install additional software and
documentation components to aid in the development and evaluation process.
Figure 4. Simplicity Studio
The following Simplicity Studio components are required for the C8051F390 Development Kit:
8051 Products Part Support
Simplicity Developer Platform
Download and install Simplicity Studio from www.silabs.com/8bit-software or www.silabs.com/simplicity-studio.
Once installed, run Simplicity Studio by selecting StartSilicon LabsSimplicity StudioSimplicity Studio
from the start menu or clicking the Simplicity Studio shortcut on the desktop. Follow the instructions to install the
software and click Simplicity IDE to launch the IDE.
The first time the project creation wizard runs, the Setup Environment wizard will guide the user through the
process of configuring the build tools and SDK selection.
In the Part Selection step of the wizard, select from the list of installed parts only the parts to use during
development. Choosing parts and families in this step affects the displayed or filtered parts in the later device
selection menus. Choose the C8051F39x family by checking the C8051F39x/37x check box. Modify the part
selection at any time by accessing the Part Management dialog from the WindowPreferencesSimplicity
StudioPart Management menu item.
Simplicity Studio can detect if certain toolchains are not activated. If the Licensing Helper is displayed after
completing the Setup Environment wizard, follow the instructions to activate the toolchain.

C8051F39x/F37x
Rev. 0.2 5
4.1. Running Blinky
Each project has its own source files, target configuration, SDK configuration, and build configurations such as the
Debug and Release build configurations. The IDE can be used to manage multiple projects in a collection called a
workspace. Workspace settings are applied globally to all projects within the workspace. This can include settings
such as key bindings, window preferences, and code style and formatting options. Project actions, such as build
and debug are context sensitive. For example, the user must select a project in the Project Explorer view in order
to build that project.
To create a project based on the Blinky example:
1. Click the Simplicity IDE tile from the Simplicity Studio home screen.
2. Click the Create new project link from the welcome screen or go to FileNewSilicon Labs MCU
Project.
3. In the Kit drop-down, select C8051F390 Development Kit, in the Part drop-down, select C8051F390, and
in the SDK drop-down, select the desired SDK. Click Next.
4. Select Example and click Next.
5. Under C8051F390 Development Kit in the Blinky folder, select F39x-37x Blinky and click Finish.
6. Click on the project in the Project Explorer and click Build, the hammer icon in the top bar. Alternatively,
go to ProjectBuild Project.
7. Click Debug to download the project to the hardware and start a debug session.
8. Press the Resume button to start the code running. The LED should blink.
9. Press the Suspend button to stop the code.
10. Press the Reset the device button to reset the target MCU.
11. Press the Disconnect button to return to the development perspective.
4.2. Simplicity Studio Help
Simplicity Studio includes detailed help information and device documentation within the tool. The help contains
descriptions for each dialog window. To view the documentation for a dialog, click the question mark icon in the
window:
This will open a pane specific to the dialog with additional details.
The documentation within the tool can also be viewed by going to HelpHelp Contents or HelpSearch.

C8051F39x/F37x
6 Rev. 0.2
4.3. Legacy 8-bit IDE
Note: Using the Simplicity Studio tools with the C8051F390 Development Kit is recommended. See section 4. "Software
Setup‚" on page 4 for more information.
Download the 8-bit software from the website (www.silabs.com/8bit-software) or use the provided installer on the
CD-ROM to install the software tools for the C8051F39x devices. After installation, examples can be found in
...\Examples\C8051F39x_37x in the installation directory. At a minimum, the C8051F390 DK requires:
Silicon Labs IDE—Software enabling initial evaluation, development, and debugging.
Configuration Wizard 2—Initialization code generation software for the C8051F39x devices.
Keil C51 Tools—Keil 8051 Compiler/Assembler/Linker toolchain.
CP210x Drivers—Virtual COM Port (VCP) drivers for the CP210x COM interface. More information on this
installation process can be found in Section 4.4.
Other software available includes:
Keil µVision Driver—Driver for the Keil µVision IDE that enables development and debugging on
C8051Fxxx MCUs.
Flash Programming Utilities and MCU Production Programmer—Programming utilities for the
production line. More information on the available programming options can be found on the website:
http://www.silabs.com/products/mcu/Pages/ProgrammingOptions.aspx.
ToolStick Development Tools—Software and examples for the ToolStick development platform. More
information on this platform can be found at www.silabs.com/toolstick.
The development kit includes the latest version of the C51 Keil 8051 toolset. This toolset is initially limited to a code
size of 2 kB and programs start at code address 0x0800. After registration, the code size limit is removed entirely
and programs will start at code address 0x0000.
To register the Keil toolset:
1. Find the Product Serial Number printed on the CD-ROM. If you no longer have this serial number,
register on the Silicon Labs website (www.silabs.com/8bit-software) to obtain the serial number.
2. Open the Keil µVision4 IDE from the installation directory with administrative privileges.
3. Select FileLicense Management to open the License Management window.
Figure 5. Keil µVision4 IDE License Management Window
4. Click on the Get LIC via Internet... button to open the Obtaining a License IDE Code (LIC) window.
5. Press OK to open a browser window to the Keil website. If the window doesn’t open, navigate to

C8051F39x/F37x
Rev. 0.2 7
www.keil.com/license/install.htm.
6. Enter the Silicon Labs Product Serial Number printed on the CD-ROM, along with any additional required
information.
7. Once the form is complete, click the Submit button. An email will be sent to the provided email address
with the license activation code.
8. Copy the License ID Code (LIC) from the email.
9. Paste the LIC into the New License ID Code (LIC) text box at the bottom of the License Management
window in µVision4.
10. Press the Add LIC button. The window should now list the PK51 Prof. Developers Kit for Silabs as a
licensed product.
11. Click the Close button.
4.4. CP210x USB to UART VCP Driver Installation
The MCU Card includes a Silicon Labs CP210x USB-to-UART Bridge Controller. Device drivers for the CP210x
need to be installed before the PC software can communicate with the MCU through the UART interface. Use the
drivers included CD-ROM or download the latest drivers from the website (www.silabs.com/interface-software).
1. If using the CD-ROM, the CP210x Drivers option will launch the appropriate driver installer. If downloading
the driver package from the website, unzip the files to a location and run the appropriate installer for the
system (x86 or x64).
2. Accept the license agreement and follow the steps to install the driver on the system. The installer will let
you know when your system is up to date. The driver files included in this installation have been certified by
Microsoft.
3. To complete the installation process, connect the included USB cable between the host computer and the
COM PORT USB connector (J5) on the MCU Card. Windows will automatically finish the driver installation.
Information windows will pop up from the taskbar to show the installation progress.
4. If needed, the driver files can be uninstalled by selecting Windows Driver Package—Silicon
Laboratories... option in the Programs and Features window.

C8051F39x/F37x
8 Rev. 0.2
5. UDP C8051F390/F370 MCU Card Overview
The C8051F39x/F37x MCU cards enable application development on the C8051F390 or C8051F370 MCU. The
card connects to the MCU Card expansion slot on the UDP motherboard and provides complete access to the
MCU resources. Each expansion board has a unique ID that can be read out of an EEPROM or MCU on the board,
which enables software tools to recognize the connected hardware and automatically select the appropriate
firmware image. The target MCU card can also be detached from the UDP and used alone as a development or
demonstration tool.
Figure 6 shows the C8051F390 MCU card.
Figure 6. C8051F39x UDP MCU Card
Figure 7 highlights some of the features of the UDP C8051F390/F370 MCU Card.

C8051F39x/F37x
Rev. 0.2 9
Figure 7. UDP C8051F390/F370 MCU Card
Debug Connector
9 V Wall Adapter
Connector
Reset Push-Button
VDD Selection
Switch
Potentiometer
Terminal Block
USB Connector
Push-Button
LED

C8051F39x/F37x
10 Rev. 0.2
5.1. VDD Selection Switch (SW1)
The UDP C8051F390/F370 MCU Card has two power options. The VDD selector switch (SW1) selects the power
source for the C8051F39x/F37x VDD supply pin and the supply for the external peripheral circuits, VDD2.
The left VREG position selects the output of the on-board 3.3 V regulator (U5) for VDD and VDD2. This is the
primary supply option for development. The on-board regulator has multiple 5 V and 9 V power sources connected
via Schottky diodes to the regulator input. The highest voltage power source will supply power to the regulator.
The power sources for the on-board regulator (U1) are as follows:
9 V DC Wall Adapter power receptacle (P1).
USB receptacle (P2).
10-pin Debug connector (J2).
The UDP MB position on the VDD selector selects the UDP motherboard programmable supply (PWR_VDD_OUT)
as the power source. Use this position when using the programmable power supply under software control. The
UDP motherboard bulk 3.3 V supply (UDP_PWR_3.3V_BULK) supplies VDD2.
The VDD voltage is available on the J1 header. Ground is accessible at various test points on the MCU card, such
as header J3, J4, and J5. Use these test points to power the board from an external lab power supply. When using
a lab supply, the VDD selector switch should be in the UDP MB position with the MCU card disconnected from the
UDP motherboard.
The MCU card facilitates measurement of the MCU supply current by removing the R1 0 resistor and placing a
current meter in series with the two terminals of the J1 header.
5.2. Push-Button Switches and LEDs (SW3, D7)
The UDP C8051F390/F370 MCU Card has one push-button switch. Connect to switch to port pin P1.0 by placing a
shorting block on J8: SW - P1.0. The switch is normally open and pulls the pin voltage to ground when pressed.
Port pin P1.1 connects to one LED: D7 when a shorting block is placed on J8: LED - P1.1. The LEDs connect to
VDD2 through a current limiting resistor.
5.3. Debug Header (J2)
The standard 10-pin debug header supports the Silicon Labs USB Debug Adapter. This connector provides a C2
debug connection to C8051F39x/F37x. The USB Debug Adapter supports two types of debug connections: C2 and
JTAG. When using this MCU card with the Silicon Labs IDE, select C2 in the connection options dialog before
connecting.
The USB Debug Adapter also provides a 5 V power source that can power the regulator. When powering the MCU
from the debug connector, the SW1 switch must be in the VREG position. Additionally, select the Power Target
after Disconnect check box in the Silicon Labs IDE connections options dialog to ensure the MCU always has
power.
5.4. Reset Button (SW2)
The reset push-button switch is in the lower-right corner. Pushing this button will always reset the MCU. Note that
pushing this button while the IDE is connected to the MCU will result in the IDE disconnecting from the target.

C8051F39x/F37x
Rev. 0.2 11
5.5. UART VCP Connection Options
The MCU card features a USB virtual COM port (VCP) UART connection via the USB connector (P2). The VCP
connection uses the CP2102 USB-to-UART bridge chip.
The UART pins on the target MCU either connect to the CP2102 USB-to-UART bridge chip or to the UDP
motherboard. The MCU card has level translators with enable pins that normally route the UART connections to
the on-board USB-to-UART bridge chip. However, the UDP motherboard can drive the enable pins to route the
UART connections to the UDP motherboard instead of the on-board USB-to-UART bridge chip. There are two
enable signals: one with a default pull-down (UART_VCP_EN) and one with a default pull-up (UART_SYS_EN).
When using the UART with either the on-board USB-to-UART bridge or the UDP motherboard, install shorting
blocks on header J14 to connect P0.4 to MCU_TX and P0.5 to MCU_RX.
If desired, install shorting blocks for hardware handshaking on P0.6 and P0.7 on the J14 header. Hardware
handshaking is not required for most applications. Firmware must implement hardware handshaking on the target
MCU using P0.6 and P0.7.
5.6. Potentiometer (R36)
The potentiometer is available on P0.7 when a shorting block is placed on J13. To enable the potentiometer, place
a shorting block on J12 to connect the top terminal of the potentiometer to VDD2.
5.7. Screw Terminal (TB1)
The MCU card includes a 5-position screw terminal connection capable of accepting large wires in the field. P0.6,
P0.1/IDAC0, P0.2/IDAC1, ground, and P0.0/VREF are available.
Before the VREF output can be observed on TB1, place a shorting block on J9 which connects P0.0/VREF to
4.7 µF and 0.1 µF decoupling capacitors.
Before the IDAC0 output can be observed on TB1 with an oscilliscope, place a shorting block on J10 which
connects P0.1/IDAC0 to a 1 kresistor to ground.
Before the IDAC1 output can be observed on TB1 with an oscilliscope, place a shorting block on J11 which
connects P1.2/IDAC1 to a 1 kresistor to ground.
5.8. Port Pin Headers (J3-J5)
All of the MCU port pins are available on the 0.100 inch headers.
Shorting blocks are placed on J6 and J7, connecting pins P0.2 and P0.3 to the P0.2 and P0.3 headers on J3. Pin
P0.2 and P0.3 can also connect to an external oscillator circuit. When using an external oscillator driver circuit,
remove the shorting block on J6 and J7.

C8051F39x/F37x
12 Rev. 0.2
5.9. C8051F39x Board Default and Optional Connections
The C8051F39x MCU card has many default and optional connections for use with the UDP motherboard. The
default connections have shorting jumpers consisting of a 402 resistor footprint with solder connecting the two
pads. To disconnect a default connection, remove the solder between the pads. To reconnect, install a 0 402
resistor or connect the two pads with solder. The optional connections are non-populated (no-pop) resistor
footprints. To connect, install a 0 402 resistor or connect the two pads with solder.
Table 1 shows a summary of the default and optional connections for each pin. Further explanation of the UDP
motherboard signals can be found in Section 6.2.
Table 1. MCU Pin Functions
MCU Pin MCU Card Function
(via shorting blocks) UDP Motherboard Signal (via 402 resistor footprint)
Default Optional Default Optional
P0.0/VREF VREF
P0.1/IDAC0 IDAC0
P0.2/XTAL1 EXT_INT0
P0.3/XTAL2 EXT_INT1
P0.4/TX TX
P0.5/RX RX
P0.6 CTS
P0.7 Potentiometer RTS
P1.0
P1.1 CLKOUT0/SYSCLK
P1.2/IDAC1 IDAC1
P1.3 PCA_CEX0, SPI_SL-
CK_A
P1.4 SPI_MISO_A,
PCA_CEX1
P1.5 PCA_CEX2, SPI_-
MOSI_A
P1.6 SPI_NSS0_A, PCA
P1.7 SMBUS0_SDA, T0
P2.0 SMBUS0_SCL, T1,
ADC_IN0
P2.1 CP_OUT_A,
ADC_IN3
P2.2 CP_OUT_A_A,
ADC_IN2
P2.3 ADC_IN1 SMBUS_SDA_EZR
P2.4 SMBUS_SCL_EZR

C8051F39x/F37x
Rev. 0.2 13
5.9.1. P0.2 and P0.3
By default, pins P0.2 and P0.3 connect to the EXT_INT0 and EXT_INT1 signals respectively on the UDP
motherboard. To disconnect these signals, remove the solder on the R13 and R14 footprint resistors.
5.9.2. P1.1
By default, pin P1.1 connects to the CLKOUT0/SYSCLK signal on the UDP motherboard. To disconnect this signal,
remove the solder on the R15 foot resistor.
5.9.3. P1.7 and 2.0
By default, pins P1.7 and P2.0 connect to the SMBUS0_SDA and SMBUS0_SCL signals respectively on the UDP
motherboard. To disconnect these signals, remove the solder on the R24 and R26 footprint resistors.
By default, pins P1.7 and P2.0 also connect to the T0 and T1 signals respectively on the UDP motherboard. To
disconnect these signals, remove the solder on the R25 and R27 footprint resistors.
By default, P2.0 also connects to the ADC_IN0 signal on the UDP motherboard. To disconnect this signal, remove
the solder on the R28 foot resistor.
5.9.4. P2.1 and R2.2
By default, pins P2.1 and P2.2 connect to the CP_OUT_A and CP_OUT_A_A signals respectively on the UDP
motherboard. To disconnect these signals, remove the solder on the R29 and R31 footprint resistors.
By default, pins P2.1 and P2.2 also connect to the ADC_IN3 and ADC_IN2 signals respectively on the UDP
motherboard. To disconnect these signals, remove the solder on the R30 and R32 footprint resistors.
5.9.5. P2.3 and R2.4
By default, pins P2.2 and P2.4 do not connect to the SMBUS_SDA_EZR and SMBUS_SCL_EZR signals
respectively on the UDP motherboard. To connect these signals, solder the R33 and R35 footprint resistors.
By default, pin P1.0 connects to the ADC_IN1 signal on the UDP motherboard. To disconnect this signal, remove
the solder on the R34 foot resistor.

C8051F39x/F37x
14 Rev. 0.2
6. Using the C8051F39x with the UDP Motherboard
6.1. VBAT Selector Switch
When used with the UDP motherboard, the motherboard can power the C8051F39x MCU card. With the VBAT
selector switch in the VREG position, the motherboard powers the regulator on the card. With the VBAT selector
switch in the UDP position, the UDP motherboard powers VBAT directly. This position supports software control of
the variable voltage power supply and current measurements.
The S1 switch on the UDP motherboard selects between the fixed or programmable voltage. The variable supply is
controlled by the C8051F384 board control MCU through the U1 digital potentiometer. Use the fixed supply when
the variable supply is not under software control.
6.2. MCU Card Header Connections
The C8051F39x MCU card has four connectors with 100 pins each. These 400 pins are directly tied to the UDP
motherboard and I/O cards. These signals are named and designed to support a wide variety of features and
applications, and the UDP C8051F390/F370 MCU Card card implements a subset of these connections.
The MCU cards and I/O cards are designed so that a maximum number of functions are shared between each
card. This allows a particular type of I/O card to be shared amongst all MCU cards that connect to the same
signals.
The MCU card slot includes the following components:
J1 MCU card connector H1
J2 MCU card connector H2
J3 MCU card connector H3
J4 MCU card connector H4
The C8051F39x MCU card implements the signals described in Table 3, Table 4, Table 5, and Table 6 in the
Appendix.

C8051F39x/F37x
Rev. 0.2 15
6.3. Shorting Blocks: Factory Defaults
The UDP C8051F390/F370 MCU Card comes from the factory with pre-installed shorting blocks on several
headers. Figure 8 shows the positions of the factory default shorting blocks.
Figure 8. Shorting Blocks: Factory Defaults
Shorting blocks are installed on J14 to connect P0.4 to MCU_TX and P0.5 to MCU_RX.

C8051F39x/F37x
16 Rev. 0.2
7. Schematics
Figure 9. C8051F39x UDP MCU Card Schematic (1 of 6)

C8051F39x/F37x
Rev. 0.2 17
Figure 10. C8051F39x UDP MCU Card Schematic (2 of 6)

C8051F39x/F37x
18 Rev. 0.2
Figure 11. C8051F39x UDP MCU Card Schematic (3 of 6)

C8051F39x/F37x
Rev. 0.2 19
Figure 12. C8051F39x UDP MCU Card Schematic (4 of 6)

C8051F39x/F37x
20 Rev. 0.2
Figure 13. C8051F39x UDP MCU Card Schematic (5 of 6)