ULINKPRO Keil, ULINKPRO Datasheet - Page 56

• Manufacturer Part Number: ULINKPRO
• Description: KIT DEBUG/TRACE UNIT HIGH SPEED
• Manufacturer: Keil
• Type: In-Circuit, Real-Time Debugger/Programmerr

Specifications of ULINKPRO

• Contents: Module
• For Use With/related Products: ARM7, ARM9, Cortex
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant

Getting Started: Creating Applications with µVision
Chapter 5. Using µVision
The µVision IDE is, for most developers, the easiest way to create embedded
system programs. This chapter describes commonly used µVision features and
explains how to use them.
General Remarks and Concepts
Before we start to describe how to use µVision, some general remarks, common
to many screens
our continuous effort to deliver best-in-class development tools, supporting you
in your daily work, µVision has been built to resemble the look-and-feel of
widespread applications. This approach decreases your learning curve, such that
you may start to work with µVision right away.
Based on the concept of windows:
and several microcontroller architectures to resemble the main feature, sometimes the special
feature, of that topic. The same window, dialog, or tab category will look slightly different for
other microcontroller architectures.
1
The screenshots presented in the next chapters have been taken from different example programs
µVision windows can be re-arranged, tiled, and attached to other screen areas
or windows respectively
It is possible to drag and drop windows, objects, and variables
A Context Menu, invoked through the right mouse button, is provided for
most objects
You can use keyboard shortcuts and define your own shortcuts
You can use the abundant features of a modern editor
Menu items and Toolbar buttons are grayed out when not available in the
current context
Graphical symbols are used to resemble options, to mark unsaved changes, or
reveal objects not included into the project
Status Bars display context-driven information
You can associate µVision to third-party tools
1
and to the behavior of the development tool, are presented. In
55