Download complete version

CHAPTER 6. DEVELOPMENT
6.2. DEVELOPMENT TOOLS
mainly used for qualitative analysis and to limited extend to quantitative
analysis. Some data is copied to text files via this copy and paste procedure, this enabled analysis of data carried out in a Matlab environment.
The program is however quite simple to users familiar with older software types. There is only a limited variety of possible options. So very
fast any frequent user will have visited almost any corner of the simulator.
Because of the fact that a simulation of a 20 msecs DSP process, takes close
to 2 minutes, you get a natural feeling of where the time consuming code
is.
Screen environment
The visible area on the DOS screen is only the usual 80 × 25 characters.
This limits the amount of windows visible at the same time. By default,
there is the COMMAND, MEMORY, DISASSEMBLY and CPU window
shown, but a lot of others are possible. The windows are easily modified in
size and placement by use of the mouse. However, it is an old interface that
do not permit modifications that is usually present in all other newer MSWindows based software. Some unlucky usage of window displacements,
leads to scrambling of the screen and a restart is necessary.
The windows available are described in the subsections following. There
is a large number of possible commands that can be written in the command
window, for further study of those see [10]. Some of the most important
ones will, however, be covered here.
Command window
The most important window is the COMMAND window. From this window
all the other window parameters can be controlled. If nothing is done to
deliberately make another window text sensitive, one can always write a
command even if another window is active (highlighted). The command will
be written in a DOS like prompt and when ENTER is hit, the command
is performed. Former commands and answers can be found by scrolling
upwards in the COMMAND window.
To load a compiled and liked file the load FILE command is used. If
this is done from the start there is no need of resetting, if however a reset is
needed then reset, is written at the prompt. In the same way a restart can
be written if a debugging session needs to be restarted. Another helpful
command is ba ADDRESS, which puts a breakpoint at the address following the command. The address can be both a label(ex. main) or a 32-bit
physical address(ex. 0x002ff800). The list of breakpoints is found by invoking bl. To open another memory window surveying a memory section
100