Silicon Laboratories C8051T622 User manual

Rev. 0.5 7/12 Copyright © 2012 by Silicon Laboratories C8051T620/2-DK
C8051T620/2-DK
C8051T620/2 DEVELOPMENT KIT USER’SGUIDE
1. Kit Contents
The C8051T620 and C8051T622 Development Kits contain the following items:
C8051T62x Motherboard
C8051T62x Emulation Daughter Board with C8051F34A installed
Socket Daughter Board (one of the following):
C8051T620DK: C8051T62x QFN 32-pin
C8051T622DK: C8051T622 QFN 24-pin
Device samples (one of the following):
C8051T620DK: C8051T620-GM (Qty: 10) and C8051T626-B-GM (Qty: 10)
C8051T622DK: C8051T622-GM (Qty: 10)
C8051Txxx Development Kit Quick-Start Guide
Quick Start Guide includes steps to download the following development software and documentation (these
instructions can also be found in this document. See “4. Software Installation” on page 3.):
• Silicon Laboratories Integrated Development Environment (IDE)
• Evaluation version of 8051 development tools (macro assembler, linker, C compiler)
• Source code examples and register definition files
• Documentation
AC-to-DC universal power adapter
Two USB cables
2. About the Daughter Boards
The C8051T620 and C8051T622 Development Kits include an Emulation Daughter Board (EDB) and a QFN
Socket Daughter Board (QFN-DB). The EDB has an installed C8051F34A device, which is a Flash-based device
that can be used for the majority of C8051T62x/32x code development. The QFN-DB is intended to allow both
programming and system-level debugging of C8051T62x/32x devices directly.
A C8051T62x/32x device cannot be erased once it has been programmed; so, it is advisable to use the
C8051F34A for the majority of code development. Refer to “AN368: Differences between the C8051F34A and the
C8051T62x and C8051T32x Device Families” for more details on how the C8051F34A can be used to develop
code for the C8051T62x/32x device families. Application notes can be found on the Silicon Labs web site:
www.silabs.com/appnotes
Not Recommended for New Designs

C8051T620/2-DK
2 Rev. 0.5
3. Hardware Setup
See Figure 1 for a diagram of the hardware configuration.
1. Attach the desired daughter board to the motherboard at connectors P1 and P2.
2. If using the QFN Socket Daughter Board, place the device to be programmed into the socket.
3. Place shorting blocks on J7 and the +3VD-VDD_PWR jumper pair on J6, as shown in Figure 1.
4. Connect the motherboard’s P5 USB connector to a PC running the Silicon Laboratories IDE using the USB
Cable.
5. Connect the ac-to-dc power adapter to connector P3 on the motherboard.
Notes:
1. Use the Reset icon in the IDE to reset the target when connected during a debug session.
2. Remove power from the motherboard and remove the USB cable before removing a daughter board from the
motherboard. Connecting or disconnecting a daughter board when the power adapter or USB cable are connected can
damage the motherboard, the daughter board, or the socketed device.
3. Remove power from the motherboard and remove the USB cable before removing a C8051T62x/32x device from the
socket. Inserting or removing a device from the socket when the power adapter or USB cable are connected can
damage the motherboard, the daughter board, or the socketed device.
4. The above hardware setup instructions configure the development system to be powered through the onboard 3.3 V
regulator. For other power options, see "7.3. Power Supply Headers (J6 and J7)" on page 15.
Figure 1. Hardware Setup (Emulation Daughter Board)
P3
SILICON LABS
www.silabs.com
RESET
J15
J7
USB ACTIVE J5
J14
SW1
J12 J13
J1
DEBUG
PWR
RUN
VDD_PWR
VDD_PWR
VDD_PWR
VDD_PWR
+3VD
VDD_EXT
VDD_DEBUG
VDD_COMM
J6
P2
P1 J2
SW2
J3
J4
USB ACTIVE
LED1
PWR
D10 D11 D12
R8
U2
CP2103 U1
F326
STOP
LED1
J10 P2.2
P0.6
LED2
P2.3
P1.2
SW1
J9 P2.0
P0.1
SW2
P2.1
P1.0
C8051T62x-MB
LED2
VPP
P5
P4
J8 CTS_DEBUG
P1.1 P1.2
RTS_COMM CTS_COMM
RTS_DEBUG
J11 TX_DEBUG
P0.4 P0.5
RX_COMM TX_COMM
RX_DEBUG
J1 AC Adapter
USB Cable
Place shorting blocks on
J7 and J6 as shown.
U1
F34A
VREGIN
VREGIN
VBUS
VDD
P3
SILICON LABS
www.silabs.com
C8051T62x EDB
Not Recommended for New Designs

C8051T620/2-DK
Rev. 0.5 3
4. Software Installation
All the latest software tools and documentation can be downloaded from www.silabs.com/mcudownloads.
The Silicon Labs 8-bit Development Tools download package available on that web page includes the Silicon
Laboratories Integrated Development Environment (IDE), 8051 evaluation toolset, Virtual COM Port drivers for the
CP210x USB to UART Bridge, and additional documentation. Download the package and install the components
by following the on-screen instructions.
4.1. System Requirements
The following are the system requirements necessary to run the debug and programming tools:
Pentium-class host PC running Microsoft Windows 2000 or newer.
One available USB port.
4.2. Development Tools Installation
To install the IDE, utilities, and code examples, perform the following steps:
1. Run the Silicon Labs 8-bit Development Tools installer downloaded from www.silabs.com/mcudownloads.
2. In the screen titled “Select Installation Packages”, the Silicon Labs IDE, 8051 Evaluation Toolset and CP210x
Virtual COM Port drivers will be checked by default. The programs necessary to download and debug on the
MCU are the Silicon Labs IDE and the 8051 Evaluation Toolset. The CP210x Drivers are necessary to use the
UART capabilities of the target board. See “4.3. CP210x USB to UART VCP Driver Installation” for more
information about installing the CP210x drivers. See “5. Software Overview” for an overview of all applicable
software included in the web download.
3. Installers selected in Step 3 will execute in sequence, prompting the user as they install programs,
documentation, and drivers.
4.3. CP210x USB to UART VCP Driver Installation
The C8051T62x Motherboard includes a Silicon Laboratories CP2103 USB-to-UART Bridge Controller. Device
drivers for the CP2103 need to be installed before PC software, such as HyperTerminal, can communicate with the
board over the USB connection. If the “Install CP210x Drivers” option was selected during installation, this will
launch a driver “unpacker” utility.
1. Follow the steps to copy the driver files to the desired location. The default directory is C:\SiLabs\MCU\CP210x.
2. The final window of this installer will provide an option to install the driver on the target system. Select the
“Launch the CP210x VCP Driver Installer” option in that window if you are ready to install the driver. You do not
need to have the motherboard's USB connector plugged into the PC's USB port for this step.
3. If selected, the driver installer will now launch, providing an option to specify the driver installation location. After
pressing the “Install” button, the installer will search your system for copies of previously installed CP210x
Virtual COM Port drivers. It will let you know when your system is up-to-date. The driver files included in this
installation have been certified by Microsoft.
4. If the “Launch the CP210x VCP Driver Installer” option was not selected in Step 3, the installer can be found in
the location specified in Step 2 (by default, C:\SiLabs\MCU\CP210x\Windows). At this location, run
CP210xVCPInstaller.exe.
5. To complete the installation process, connect the included USB cable between the host computer and the
COMM USB connector (P4) on the C8051T62x Motherboard. Windows will automatically finish the driver
installation. Information windows will pop up from the taskbar to show the installation progress.
6. If needed, the driver files can be uninstalled by selecting the “Silicon Laboratories CP210x USB to UART Bridge
(Driver Removal)” option in the “Add or Remove Programs” window.
Not Recommended for New Designs

C8051T620/2-DK
4 Rev. 0.5
5. Software Overview
The following software is necessary to build a project, download code to, and communicate with the target
microcontroller.
8051 Evaluation Toolset
Silicon Labs Integrated Development Environment (IDE)
Other useful software included in the Silicon Labs 8-bit Development Tools package from the Silicon Labs
Downloads web site ( www.silabs.com/mcudownloads) includes:
Configuration Wizard 2
Keil µVision2, µVision3, and µVision4 Drivers
MCU Production Programmer and Flash Programming Utilities
5.1. 8051 Evaluation Toolset
The Silicon Labs IDE has native support for many third-party 8051 toolsets. Included with this kit is an 8051
evaluation assembler, compiler, and linker. For further information on the tools, including limitations, see the
corresponding application note. Application notes can be found on the Silicon Labs web site (http://
www.silabs.com/appnotes). See Table 1 for a list of supported toolsets and associated application notes.
5.2. Silicon Labs IDE
The Silicon Labs IDE integrates a source-code editor, source-level debugger, and in-system programmer. The
following sections discuss how to open an example project in the IDE, build the source code, and download it to the
target device.
5.2.1. Running the T620_Blinky or T622_Blinky example program
The T620_Blinky or T622_Blinky example program blinks an LED on the target board.
1. Open the Silicon Labs IDE from the Start menu.
2. Select ProjectOpen Project to open an existing project.
3. Browse to the C:\SiLabs\MCU\Examples\C8051T620_1_6_7_T320_3\Blinky or SiLabs\MCU\Exam-
ples\C8051T622_3_T326_7\Blinky directory (default) and select the T620_Blinky_C.wsp or
T622_Blinky_C.wsp project file. Click Open.
4. Once the project is open, build the project by clicking on the Build/Make Project button in the toolbar or
selecting ProjectBuild/Make Project from the menu.
Note: After the project has been built the first time, the Build/Make Project command will only build the
files that have been changed since the previous build. To rebuild all files and project dependencies, click
on the Rebuild All button in the toolbar or select ProjectRebuild All from the menu.
5. Before connecting to the target device, several connection options may need to be set. Open the Connec-
tion Options window by selecting OptionsConnection Options... in the IDE menu. First, select the
“USB Debug Adapter” option. Next, the correct “Debug Interface” must be selected. C8051T62x/32x
devices use Silicon Labs “C2” 2-wire debug interface. Once all the selections are made, click the OK but-
ton to close the window.
Table 1. Supported Third Party 8051 Toolsets
Toolset Application Note
Keil “AN104: Integrating Keil 8051 Tools into the Silicon Labs IDE”
Raisonance “AN125: Integrating Raisonance 8051 Tools into the Silicon Labs IDE”
Tasking “AN126: Integrating Tasking 8051 Tools into the Silicon Labs IDE”
HI-TECH “AN140: Integrating Hi-TECH 8051 Tools into the Silicon Labs IDE”
SDCC “AN198: Integrating SDCC 8051 Tools into the Silicon Labs IDE”
IAR “AN236: Integrating IAR 8051 Tools into the Silicon Labs IDE”
Not Recommended for New Designs

C8051T620/2-DK
Rev. 0.5 5
6. Click the Connect button in the toolbar or select DebugConnect from the menu to connect to the
device.
7. Download the project to the target by clicking the Download Code button in the toolbar.
Note: To enable automatic downloading if the program build is successful, select Enable Automatic Con-
nect/Download after Build in the ProjectTarget Build Configuration dialog. If errors occur during the
build process, the IDE will not attempt the download.
8. Click on the Go button (green circle) in the toolbar or by selecting DebugGo from the menu to start run-
ning the firmware. The LED on the target board will start blinking.
5.2.2. Creating a New Project
Use the following steps to create a new project. Once steps 1–5 in this section are complete, continue with Step 3
from Section 5.2.1.
1. Select ProjectNew Project to open a new project and reset all configuration settings to default.
2. Select FileNew File to open an editor window. Create your source file(s) and save the file(s) with a rec-
ognized extension, such as .c, .h, or .asm, to enable color syntax highlighting.
3. Right-click on “New Project” in the Project Window. Select Add files to project. Select files in the file
browser and click Open. Continue adding files until all project files have been added.
4. For each of the files in the Project Window that you want assembled, compiled, and linked into the target
build, right-click on the file name and select Add file to build. Each file will be assembled or compiled as
appropriate (based on file extension) and linked into the build of the absolute object file.
Note: If a project contains a large number of files, the “Group” feature of the IDE can be used to organize.
Right-click on “New Project” in the Project Window. Select Add Groups to project. Add predefined groups
or add customized groups. Right-click on the group name and choose Add file to group. Select files to be
added. Continue adding files until all project files have been added.
5. Save the project when finished with the debug session to preserve the current target build configuration,
editor settings, and the location of all open debug views. To save the project, select ProjectSave Proj-
ect As... from the menu. Create a new name for the project and click on Save.
Not Recommended for New Designs

C8051T620/2-DK
6 Rev. 0.5
5.3. Configuration Wizard 2
Configuration Wizard 2 is a code generation tool for all Silicon Laboratories devices. Code is generated through the
use of dialog boxes for each device peripheral as shown in Figure 2.
Figure 2. Configuration Wizard 2 Utility
The Configuration Wizard utility helps accelerate development by automatically generating initialization source
code to configure and enable the on-chip resources needed by most design projects. In just a few steps, the wizard
creates complete startup code for a specific Silicon Laboratories MCU. The program is configurable to provide the
output in C or assembly language.
For more information, refer to the Configuration Wizard 2 help available under the Help menu in Configuration
Wizard 2 or refer to the Configuration Wizard 2 documentation. Documentation and software are available from the
downloads webpage: www.silabs.com/mcudownloads.
5.4. Keil uVision2, uVision3, and uVision4 Silicon Laboratories Drivers
As an alternative to the Silicon Laboratories IDE, the µVision debug driver allows the Keil µVision2, µVision3, and
µVision4 IDEs to communicate with Silicon Laboratories’ on-chip debug logic. In-system Flash memory
programming integrated into the driver allows for rapid updating of target code. The µVision2, µVision3, and
µVision4 IDEs can be used to start and stop program execution, set breakpoints, check variables, inspect and
modify memory contents, and single-step through programs running on the actual target hardware.
For more information, refer to the µVision driver documentation. The documentation and software are available
from the downloads webpage: www.silabs.com/mcudownloads.
Not Recommended for New Designs

C8051T620/2-DK
Rev. 0.5 7
5.5. Programming Utilities
The Silicon Labs IDE is the primary tool for downloading firmware to the MCU during development. There are two
software programming tools that are intended for use during prototyping or in the field: the MCU Production
Programmer and the Flash Programming Utilities. The MCU Production Programmer is installed with the IDE to the
directory, C:\Silabs\MCU\Utilities\Production Programmer\ (default). The Flash Programming Utilities can be
optionally installed from the web installer, and are installed to C:\Silabs\MCU\Utilities\FLASH Programming\
(default).
5.6. ToolStick Terminal
The onboard debug circuitry provides both an in-system programming and debugging interface and a
communications interface to the target microcontroller's UART. The ToolStick Terminal software can access the
debug hardware's communications path and provides a terminal-like interface on the PC. Note that for concurrent
debugging and UART communications, the CP2103 USB-to-UART bridge is also included onboard.
In addition to the standard terminal functions (Send File, Receive File, Change Baud Rate), two GPIO pins on the
target microcontroller can be controlled using the terminal for either RTS/CTS handshaking or software-
configurable purposes. The ToolStick Terminal software is available on the downloads webpage: www.silabs.com/
mcudownloads.
Not Recommended for New Designs

C8051T620/2-DK
8 Rev. 0.5
6. Example Source Code
Example source code and register definition files are provided by default in the
SiLabs\MCU\Examples\C8051T620_1_6_7_T320_3 or SiLabs\MCU\Examples\C8051T622_3_T326_7 directory
during IDE installation. These files may be used as a template for code development.
6.1. Register Definition Files
Register definition files C8051T620.inc, C8051T622.inc, C8051T620_defs.h, C8051T622_defs.h,and
compiler_defs.h define all SFR registers and bit-addressable control/status bits. They are installed by default into
the SiLabs\MCU\Examples\C8051T620_1_6_7_T320_3 or SiLabs\MCU\Examples\C8051T622_3_T326_7
directory during IDE installation. The register and bit names are identical to those used in the C8051T620-21-26-
27_T320-3 or C8051T622-23_T326-27 data sheet.
6.2. Blinking LED Example
The example source files T620_Blinky.asm and T620_Blinky.c or T622_Blinky.asm and T622_Blinky.c show
examples of several basic C8051T62x functions. These include disabling the watchdog timer (WDT), configuring
the Port I/O crossbar, configuring a timer for an interrupt routine, initializing the system clock, and configuring a
GPIO port. When compiled/assembled and linked, these programs flash the green LED on the C8051T62x
Motherboard about five times a second using the interrupt handler with a timer.
Not Recommended for New Designs

C8051T620/2-DK
Rev. 0.5 9
7. Development Boards
The C8051T620/2 Development Kit includes a motherboard that interfaces to various daughter boards. The
C8051T62x Emulation Daughter Board contains a C8051F34A device to be used for preliminary software
development. The C8051T620 Socket Daughter Board and C8051T622 Socket Daughter Board allow
programming and evaluation of the actual C8051T62x devices. Numerous input/output (I/O) connections are
provided on the motherboard to facilitate prototyping. Figure 3 shows the C8051T62x Motherboard and indicates
locations for various I/O connectors. Figure 4 shows the factory default shorting block positions. Figures 5, 6, and 7
show the available C8051T62x daughter boards. Figures 8, 9, 10, and 11 show the available C8051T32x daughter
boards.
P1, P2 Daughter board connection
P3 Power connector that accepts input from 7.5 to 15 V dc unregulated power adapter
P4 USB connector for UART to USB communications interface
P5 USB Debug interface connector
J1 Analog I/O terminal block
J2 Port 0 header
J3 Port 1 header
J4 Port 2 header
J5 Port 3 header with access to VDD and GND
J6 Power supply selection header (See "7.3. Power Supply Headers (J6 and J7)" on page 15)
J7 Power supply enable header that connects power source selected on J6 to the board's main
power supply net
J8 Communications interface control signal header
J9 Connects port pins to the switches labeled “SW1” and “SW2”
J10 Connects port pins to the LEDs labeled “LED1” and “LED2”
J11 Communications interface data signal header
J12 Connects potentiometer to the port pin, P2.5
J13 Additional connections to ground
J14 Connects an external VREF from J1 to P0.7
J15 VPP supply connection used when programming EPROM devices
Not Recommended for New Designs

C8051T620/2-DK
10 Rev. 0.5
Figure 3. C8051T62x Motherboard
Figure 4. C8051T62x Motherboard Default Shorting Block Positions
P3
SILICON LABS
www.silabs.com
RESET
J15
J7
USB ACTIVE J5
J14
SW1
J12 J13
J1
DEBUG
PWR
RUN
VDD_PWR
VDD_PWR
VDD_PWR
VDD_PWR
+3VD
VDD_EXT
VDD_DEBUG
VDD_COMM
J6
P2
P1 J2
SW2
J3
J4
USB ACTIVE
LED1
PWR
D10 D11 D12
R8
U2
CP2103 U1
F326
STOP
LED1
J10 P2.2
P0.6
LED2
P2.3
P1.2
SW1
J9 P2.0
P0.1
SW2
P2.1
P1.0
C8051T62x-MB
LED2
VPP
P5
P4
J8 CTS_DEBUG
P1.1 P1.2
RTS_COMM CTS_COMM
RTS_DEBUG
J11 TX_DEBUG
P0.4 P0.5
RX_COMM TX_COMM
RX_DEBUG
P3
SILICON LABS
www.silabs.com
RESET
J15
J7
USB ACTIVE J5
J14
SW1
J12 J13
J1
DEBUG
PWR
RUN
VDD_PWR
VDD_PWR
VDD_PWR
VDD_PWR
+3VD
VDD_EXT
VDD_DEBUG
VDD_COMM
J6
P2
P1 J2
SW2
J3
J4
USB ACTIVE
LED1
PWR
D10 D11 D12
R8
U2
CP2103 U1
F326
STOP
LED1
J10 P2.2
P0.6
LED2
P2.3
P1.2
SW1
J9 P2.0
P0.1
SW2
P2.1
P1.0
C8051T62x-MB
LED2
VPP
P5
P4
J8 CTS_DEBUG
P1.1 P1.2
RTS_COMM CTS_COMM
RTS_DEBUG
J11 TX_DEBUG
P0.4 P0.5
RX_COMM TX_COMM
RX_DEBUG
Not Recommended for New Designs