C8051T60x-DK
C8051T60
X
D
EVELOPMENT
K
IT
U
SER
’
S
G
U I D E
1. Kit Contents
The C8051T60x Development Kit contains the following items:
C8051T600 Main Board
C8051T600 SOIC Socket Daughter Board for programming SOIC devices
C8051T600 Emulation Daughter Board with C8051F300 installed
(5) C8051T600-GS Samples
C8051T60x Development Kit Quick-Start Guide
Silicon Laboratories IDE and Product Information CD-ROM. CD content includes:
Laboratories Integrated Development Environment (IDE)
Evaluation Version of Keil 8051 Development Tools (macro assembler, linker, ‘C’ Compiler)
Source code examples and register definition files
Documentation
Silicon
AC to DC Universal Power Adapter
USB Cable
RS-232 Cable
Also available for purchase separately is a C8051T600 QFN Socket Daughter Board for programming QFN
devices.
2. About the Daughter Boards
The C8051T60x Development Kit includes two daughter boards: an Emulation Daughter Board (EDB) and an
SOIC Socket Daughter Board (SOIC-DB). The EDB has a C8051F300 device installed, which is a Flash-based
device that can be used for the majority of C8051T60x code development. The SOIC-DB and the QFN-DB
(available separately) are intended to allow both the programming of multiple C8051T60x devices, as well as
system-level debugging of these devices. Once a C8051T60x device has been programmed, it cannot be erased,
so it is advisable to use the C8051F300 for the majority of code development. Refer to Application Note “AN280:
Differences Between the C8051F300 and the C8051T60x Device Family” for more details on how the C8051F300
can be used to develop code for the C8051T60x device family.
3. Hardware Setup
Refer to Figure 1 for a diagram of the hardware configuration.
1. Attach the desired daughter board to the main board at connectors P1 and P2.
2. If using the SOIC Socket daughter board or the QFN Socket daughter board, place the device to be
programmed into the socket.
3. Connect the AC to DC Power Adapter to connector P3 on the main board.
4. Connect the main board to a PC running the Silicon Laboratories IDE using the USB Cable.
Notes:
Use the
Reset
icon in the IDE to reset the target when connected during a debug session.
Remove power from the main board and remove the USB cable before removing a daughter board from the
main board. Connecting or disconnecting a daughter board when the power adapter or USB cable are
connected can damage the main board, the daughter board, or the socketed device.
Likewise, remove power from the main board and remove the USB cable before removing a C8051T60x device
from the socket. Inserting or removing a device from the socket when the power adapter or USB cable are
connected can damage the main board, the daughter board, or the socketed device.
Rev. 0.1 1/07
Copyright © 2007 by Silicon Laboratories
C8051T60x-DK
C8051T60x-DK
RESET
J7
R13
SILICON LABS
www.silabs.com
P3
P1
C8051T600 EDB
J8
D7
J10
AC Adapter
D4
PWR
J1
USB Cable
F300
P2
DEBUG
J3
D2
SW1
D1
P0.6
P0.3
J2
Figure 1. Hardware Setup (Emulation Daughter Board Shown)
4. Software Setup
The included CD-ROM contains the Silicon Laboratories Integrated Development Environment (IDE), Keil software
8051 tools 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
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.
5. Silicon Laboratories Integrated Development Environment
The Silicon Laboratories IDE integrates a source-code editor, source-level debugger and in-system Flash
programmer. The use of third-party compilers and assemblers is also supported. This development kit includes an
evaluation version of the Keil Software A51 macro assembler, BL51 linker and C51 ‘C’ compiler. These tools can
be used from within the Silicon Laboratories IDE.
5.1. System Requirements
The Silicon Laboratories IDE requirements:
Pentium-class host PC running Windows 2000 or Windows XP.
One available USB port.
64 MB RAM and 40 MB free HD space recommended.
5.2. Assembler and Linker
A full-version Keil A51 macro assembler and BL51 banking linker are included with the development kit and are
installed during IDE installation. The complete assembler and linker reference manual can be found under the
Help
menu in the IDE or in the “SiLabs\MCU\hlp” directory (A51.pdf).
2
Rev. 0.1
C8051T60x-DK
5.3. Evaluation C51 ‘C’ Compiler
An evaluation version of the Keil C51 ‘C’ compiler is included with the development kit and is installed during IDE
installation. The evaluation version of the C51 compiler is the same as the full professional version except code
size is limited to 4 kB and the floating point library is not included. The C51 compiler reference manual can be
found under the
Help
menu in the IDE or in the “SiLabs\MCU\hlp” directory (C51.pdf).
5.4. Using the Keil Software 8051 Tools with the Silicon Laboratories IDE
To perform source-level debugging with the IDE, you must configure the Keil 8051 tools to generate an absolute
object file in the OMF-51 format with object extensions and debug records enabled. You may build the OMF-51
absolute object file by calling the Keil 8051 tools at the command line (e.g. batch file or make file) or by using the
project manager built into the IDE. The default configuration when using the Silicon Laboratories IDE project
manager enables object extension and debug record generation. Refer to Application Note “AN104:
Integrating
Keil 8051 Tools Into the Silicon Labs IDE”
in the “SiLabs\MCU\Documentation\Appnotes” directory on the CD-
ROM for additional information on using the Keil 8051 tools with the Silicon Laboratories IDE.
To build an absolute object file using the Silicon Laboratories IDE project manager, you must first create a project.
A project consists of a set of files, IDE configuration, debug views, and a target build configuration (list of files and
tool configurations used as input to the assembler, compiler, and linker when building an output object file).
The following sections illustrate the steps necessary to manually create a project with one or more source files,
build a program and download the program to the target in preparation for debugging. (The IDE will automatically
create a single-file project using the currently open and active source file if you select
Build/Make Project
before a
project is defined.)
5.4.1. Creating a New Project
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 pre-defined
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.
Rev. 0.1
3
C8051T60x-DK
5.4.2. Building and Downloading the Program for Debugging
1. Once all source files have been added to the target build, 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.
2. Before connecting to the target device, several connection options may need to be set. Open the
Connection Options
window by selecting
Options
Connection Options...
in the IDE menu. First, select
the “USB Debug Adapter” option. The USB Debug circuitry is integrated onto the C8051T60x main board.
Next, the correct “Debug Interface” must be selected. C8051T60x Family devices and the C8051F300 all use
Silicon Labs “C2” 2-wire debug interface. Once all the selections are made, click the
OK
button to close the
window.
3. Click the
Connect
button in the toolbar or select
Debug
Connect
from the menu to connect to the device.
4. 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.
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 Project
As...
from the menu. Create a new name for the project and click on
Save.
6. Example Source Code
Example source code and register definition files are provided in the “SiLabs\MCU\Examples\C8051T60x”
directory during IDE installation. These files may be used as a template for code development.
6.1. Register Definition Files
Register definition files
C8051T600.inc, C8051T600_defs.h
and
compiler_defs.h
define all SFR registers and bit-
addressable control/status bits. They are installed into the “SiLabs\MCU\Examples\C8051T60x” directory during
IDE installation. The register and bit names are identical to those used in the C8051T60x datasheet. The register
definition files are also installed in the default search path used by the Keil Software 8051 tools. Therefore, when
using the Keil 8051 tools included with the development kit (A51, C51), it is not necessary to copy a register
definition file to each project’s file directory.
6.2. Blinking LED Example
The example source files
blink.asm
and
blinky.c
show examples of several basic C8051T60x 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 C8051T600 main board about ten times a second using the interrupt handler
with a timer.
4
Rev. 0.1
C8051T60x-DK
7. Development Boards
The C8051T60x Development Kit includes a main board which interfaces to various daughter boards. The
“C8051T600 Emulation Daughter Board” contains a C8051F300 device to be used for preliminary software
development. The socketed C8051T600 daughter boards allow programming and evaluation of the actual
C8051T60x family of devices. Numerous input/output (I/O) connections are provided on the main board to facilitate
prototyping. Refer to Figure 2 for the locations of the various connectors on the main board. Figure 3, Figure 4 and
Figure 5 show the available daughter boards that can be used with the C8051T600 main board.
P1, P2
P3
J1
J2
J3
J6
J7
J8
J10
Daughter board connection (Daughter boards are plugged into the P1 and P2 connectors for
evaluation and programming)
Power connector (accepts input from 7.5 to 15 VDC unregulated power adapter)
USB Debug connector
RS-232 connector
LED/Switch/RS-232 connection block
Analog I/O terminal block
Connects potentiometer to P0.1
Direct device pin connection block
VPP supply connection (used when programming OTP devices)
RESET
J6
J7
R13
SILICON LABS
www.silabs.com
P3
P1
J8
C20
R18
R12
D7
J10
D4
PWR
J1
P2
DEBUG
J3
D2
SW1
D1
P0.6
P0.3
J2
Figure 2. C8051T600 Main Board (Included in Kit)
Rev. 0.1
5