C8051Txxx Development Kit Quick-Start Guide
Product information CD-ROM includes:
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.
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 jum p er pair on J6, as shown in Figu re 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 devic e.
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 devic e.
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 14.
The included CD-ROM contains the Silicon Laboratories Integrated Development Environment (IDE), 8051
evaluation toolset, Virtual COM Port drivers for the CP210x USB to UART Bridge, and additional documentation.
Insert the CD-ROM into your PC's CD-ROM drive. An installer will automatically launch, allowing you to install the
IDE software or read documentation by clicking buttons on the installation panel. If the installer does not
automatically start when you insert the CD-ROM, run autorun.exe, which is found in the root directory of the CD-
ROM. Refer to the ReleaseNotes.txt file on the CD-ROM for the latest information regarding the CD contents.
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. Click on the “Install Development Tools” button on the installation utility's startup screen.
2. In the Kit Selection box that appears, choose the C8051T620-DK or C8051T622-DK development kit from the
list of options.
3. In the next screen, choose “Components to be Installed”. 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 on the CD-ROM.
4. 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 di rectory is C:\SiLabs\MCU\CP210x.
2. The final window will give an option to install the driver on the target system. Select the “Launch the CP210x
VCP Driver Installer” option if you are ready to install the driver.
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.
Rev. 0.43
C8051T620/2-DK
5. Software Overview
The following software is necessary to build a project, download code to, and communicate with the target
microcontroller.
Other useful software that is provided on the development kit CD and the Silicon Labs Downloads website
( 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 in the documentation section of the Development
Kit CD or on the Silicon Labs web site (http://www.silabs.com/appnotes) . See Table 1 for a list of supported toolsets
and associated application notes.
Table 1. Supported Third Party 8051 Toolsets
ToolsetApplication 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”
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
3. Browse to the C:\SiLabs\MCU\Examples\C8051T620_1_T320_3\Blinky or SiLabs\MCU\Exam-ples\C8051T622_3_T326_7\Blinky directory (default) and select the T620_Blinky_C.wsp pr
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 toolb ar or
selecting Project
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
5. Before connecting to the target device, several connection optio ns may need to be set. Open th e Connec-tion Options window by selecting Options
“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 button to close the window.
Open Project to open an existing project.
Build/Make Project from the menu.
Rebuild All from the menu.
Connection Options... in the IDE menu. First, select the
4Rev. 0.4
C8051T620/2-DK
6. Click the Connect button in the toolbar or select DebugConnect from the menu to connect to the
device.
7. Download the project to the target by clicking the DownloadCode 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
build process, the IDE will not attempt the download.
8. Click on the Go button (green circle) in the toolbar or by selecting Debug
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 projec t. Once ste ps 1–5 in this se ction are co mplete, c ontinue with Step 3
from Section 5.2.1.
1. Select Project
2. Select File
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 grou p name and cho ose 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 Projectect As... from the menu. Create a new name for the project and click on Save.
New Project to open a new project and reset all configuration settings to default.
New File to open an editor window. Create your source file(s) and save the file(s) with a rec-
T arget Build Configurat ion dialog. If errors occur during the
Go from the menu to start run-
Save Proj-
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
Rev. 0.45
C8051T620/2-DK
The Configuration Wizard utility helps accelerate development by automatically generating initialization source
code to configure and enable the on-chip resour ces needed b y most design project s. In just a few steps, th e 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 on the
kit CD and from the downloads webpage: www.silabs.com/mcudownloads.
5.4. Keil uVision2, uVision3, and uV ision4 Silicon La boratories 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 on
the kit CD and from the downloads webpage: www.silabs.com/mcudownloads.
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 Uti lities. The MCU Production Pro grammer is inst alled with the IDE to the
directory, C:\Silabs\MCU\Utilities\Production Programmer\ (default). The Flash Programming Utilities can be
optionally installed from the CD 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 softwareconfigurable purposes. The ToolStick Terminal software is available on the downloads webpage: www.silabs.com/
mcudownloads.
6Rev. 0.4
C8051T620/2-DK
6. Example Source Code
Example source code and register definition files are provided by default in the
SiLabs\MCU\Examples\C8051T620_1_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_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_T320-3 or
C8051T620-23_T326-27 dat a 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 C 8051T62x functions. Thes e include disabling the watchdog timer (WDT), c onfiguring
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.
Rev. 0.47
C8051T620/2-DK
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 connec tors. 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, P2Daughter board connection
P3Power connector that accepts input from 7.5 to 15 V dc unregulated power adapter
P4USB connector for UART to USB communications interface
P5USB Debug interface connector
J1Analog I/O terminal block
J2Port 0 header
J3Port 1 header
J4Port 2 header
J5Port 3 header with access to VDD and GND
J6Power supply selection header (See "7.3. Power Supply Headers (J6 and J7)" on page 14)
J7Power supply enable header that connects power source selecte d on J6 to the board's main
power supply net
J8Communications interface control signal header
J9Connects port pins to the switches labeled “SW1” and “SW2”
J10Connects port pins to the LEDs labeled “LED1” and “LED2”
J11Communications interface data signal header
J12Connects potentiometer to the port pin, P2.5
J13Additional connections to ground
J14Connects an external VREF from J1 to P0.7
J15VPP supply connection used when programming EPROM devices