User manual

UM0036 Getting started with STVD
Doc ID 7705 Rev 11 23/385
2 Getting started with STVD
Once you have installed and launched ST Visual Develop (STVD), the following section will
provide you with information to help you get started building, debugging and programming
your application to your target microcontroller.
The following sections will explain how to:
Section 2.1: Set the toolset and path information
Section 2.2: Create a workspace with a new project
Section 2.3: Add source files (.asm, .c, .s) to your project
Section 2.4: Build your application
Section 2.5: Select and connect to your debug instrument
Section 2.6: Debug your application
Section 2.7: Program your application to your microcontroller
2.1 Set the toolset and path information
When you first open STVD, you should confirm the default toolset and path information that
will be used when building your application. STVD will automatically set path and subpath
information for standard installations of the supported toolsets. However, you should confirm
that these paths are correct for your particular installation.
Note: Even though you have specified these default settings in STVD, which are applied to all
projects using a toolset, you can still change the toolset and paths for a specific project in
the General tab of the Project Settings window (see Section 4.5: Configuring project settings
on page 84).
To change default toolset paths:
1. Select Tools > Options.
2. In the Options window click on the Toolset tab.
3. Select your toolset from the Toolset list box.
If the path is incorrect you can type the correct path in the Root Path field, or use the
browse button to locate it.
4. In the subpath fields, type the correct subpath if necessary.
These paths are relative to the toolset path in the Root Path field.
Note: For Metrowerks toolset users, some versions use the filename “prog” instead of “bin” for the
binary path.
2.2 Create a workspace with a new project
The workspace is a generic, global environment for STVD, which can contain one or more
projects and their dependencies. Projects, however, contain the specific information for
building your application including the toolset information, build configuration and target
device information. When you started debugging, the project also stores the debug context
each time you save it.