Table of Contents
Advertisement
Chapter 8: Using the Emulator with a Debugger
Using the Software Development Systems debugger
performs this initialization. However, when SingleStep resets the
target, it immediately places the processor in debug mode. Any
initialization code which may exist on the target board has not been
run.
SingleStep provides a way for target initialization to occur without
running application code through the use of the "_config" alias. _config
is used to define a list of commands that will be used to initialize the
target after a reset. The _config alias should be defined in the sstep.ini
file (in the "cmd" directory) and will point to a file of type .cfg which
contains the actual initialization commands.
SingleStep provides some workspace files for some standard targets.
These files will setup various registers in order to initialize these
targets. The files can be found in the init directory and are as follows:
• EST SBC 360 - est360.wsp
• Motorola 332 EVS revision a – 332evs_a.wsp
• Motorola 332 EVS revision b – 332evs_b.wsp
• Motorola 340 EVS – 340evs.wsp
• Nohau Trg-332 – trg332.wsp
• Vesta SBC332 – vesta332,wsp
Loading one of these workspace files followed by opening the Debug
Dialog from the File Menu and setting the File and Connection options
then clicking OK will create a corresponding .cfg file in the cmd
directory. This file will store the values of the items shown in the Target
Configuration tab. You may wish to edit these values before clicking OK
and saving them to a .cfg file.
Solutions for CPU32
195
- Quick Links:
- Overview
Hide quick links:
Advertisement
Table of Contents
