Crossware

Table of Contents        Previous topic       Next topic       

Getting Started->Running a Simulation

If the program file contains information on the line numbers of your source code, the Simulator will automatically configure itself in source mode.  If you started the simulator with the step into command, the simulator will run and will not stop until it reaches the first instruction for which there is an associated source file line number.

If the program file does not contain any line numbers, the simulator will configure itself in disassembly mode.  If you started the simulator with the step into command, the disassembly window will open and the simulator will be ready to run from the start address.

Once a program has been loaded into the simulator and started in the above manner, it can be run using the go, step into, step over, step out and trace commands.  All of these can be selected from the  Simulate menu, by clicking on the relevant toolbar button or by pressing the relevant accelerator keys.

It you use the go command, then you will not see anything happen except that the highlights on the toolbar will change.  Only when you halt the program or if it automatically stops at a breakpoint will the status bar and any open windows be updated. (However, disabled breakpoints can be used to cause an update of the display when running in response to the go command.)

If you use the trace command, then all windows and the status bar will be updated continuously as execution proceeds.

If you use the step into, step over or step out commands, then the windows and status bar will be updated after these commands have been carried out.