Datasheet

ADuC836
–68–
ADuC836
–69–
QUICKSTART DEVELOPMENT SYSTEM
The QuickStart Development System is a full featured, low cost
development tool suite supporting the ADuC836. The system
consists of the following PC based (Windows
®
compatible) hard-
ware and software development tools:
Hardware: ADuC836 Evaluation Board
and Serial Port Cable
Code Development: 8051 Assembler
Code Functionality: ADSIM, Windows
MicroConverter Code
Simulator
In-Circuit Code Download: Serial Downloader
In-Circuit Debugger/Emulator: Serial Port/Single Pin
Debugger/Emulator with
Assembly and C Source
Debug
Miscellaneous Other: CD-ROM Documentation
and Two Additional
Prototype Devices
Figure 67 shows the typical components of a QuickStart Devel-
opment System while Figure 68 shows a typical debug session. A
brief description of some of the software tools components in the
QuickStart Development System follows.
Figure 67. Components of the QuickStart Development
System
Download—In Circuit Downloader
The Serial Downloader is a software program that allows the user
to serially download an assembled program (Intel Hex format le)
to the on-chip program Flash memory via the serial COM1 port on
a standard PC. Application Note uC004 details this serial download
protocol and is available from www.analog.com/microconverter.
Debugger/Emulator—In-Circuit Debugger/Emulator
The Debugger/Emulator is a Windows application that allows the
user to debug code execution on silicon using the MicroConverter
UART serial port or via a single pin to provide nonintrusive
debug. The debugger provides access to all on-chip peripherals
during a typical debug session, including single-step and multiple
break-point code execution control. C source and assembly level
debug are both possible with the emulator.
ADSIM—Windows Simulator
The Simulator is a Windows application that fully simulates the
MicroConverter functionality including ADC and DAC periph-
erals. The simulator provides an easy-to-use, intuitive, interface to
the MicroConverter functionality and integrates many standard
debug features including multiple breakpoints, single stepping,
and code execution trace capability. This tool can be used both
as a tutorial guide to the part as well as an efcient way to prove
code functionality before moving to a hardware platform.
Figure 68. Typical Debug Session
REV. A
REV. A