User manual

UM0036 Your STVD graphical environment
Doc ID 7705 Rev 11 71/385
– Start.log– Contains the target debug and STVD version information. Old
information is overwritten with the most recent, each time you enter a debug
session (Debug>Start Debugging).
– error.log– Contains information about errors that are specific to your debug
instrument. This information is cleared each time you enter a debug session
(Debug>Start Debugging).
– downloader.log– Contains information regarding the last update of your debug
instrument's firmware.
Figure 53. Generate Information File for Support window
3. In the Add File to Archive field, specify any additional files that you would like to add to
the archive.
4. Click on OK to retrieve the logs and place them in the archive.
You can mail this file to your support representative, who will use it to help you resolve
your problem.
3.10 Migrating old workspaces (STVD7 2.5.4 and prior versions)
When building ST7 applications with STVD7 prior to version 3.0, the command line options,
include files, and library path names used by your toolset were contained in a makefile
(.mak). STVD no longer relies on the makefile, which you had to write for previous versions.
Instead it offers a graphical interface that allows you to quickly and easily apply and change
build options, in addition to storing those options as build configurations.
To benefit fully from STVD’s new build features, you must manually transfer the build
configuration (options, paths) from the makefile used by your old workspace (.wsp) to the
build settings interface for your project (.stp), which is contained in a new workspace
format (.stw).
As an expedient, STVD also allows you to automatically create a new workspace (.stw)
from the makefile that you used with your old workspace (.wsp). This permits a rapid
migration, however, you will not be able to take advantage of the full range of STVD’s new
build features. Ta bl e 2 5 outlines the advantages and drawbacks of these two migration
methods.