Table of Contents
Previous topic Next topic
The Embedded Development Studio automatically detects the presence of the simulator/debugger by looking for a file called sim.dll located in the directory:
where <installation directory> is the directory into which the complete package is installed.
Therefore sim.dll must remain in this directory and must not be renamed. The installer will normally look after placing the simulator in the appropriate directory. The simulator/debugger remains inactive until an ARM project is created and/or opened. Once such a project is open, the Embedded Development Studio:
Normally, at this point, the simulator/debugger will place an additional toolbar on the Embedded Development Studio workspace.
- activates the simulator/debugger
- places an additional Simulate or Debug item on the menu bar and
- instructs the simulator/debugger to initialise itself.
If the project type is for an executable program or stand-alone simulator/debugger (as opposed to a library) the Go, Step Into and Trace commands will be active on the Simulate or Debug menu. If the cursor is located in a source file window, the Step to Cursor and Set Breakpoint at Cursor commands will also be active. When any of Go, Step Into, Trace and Step to Cursor commands are used, the Embedded Development Studio will check that the ARM program exists and is up-to-date and instruct the simulator/debugger to load it. As well as loading the ARM program, the simulator/debugger will update the menu bar and status bar of the Embedded Development Studio. The Build and Simulate or Debug menu bar items of the Embedded Development Studio will be removed and replaced with Simulate or Debug, Peripherals and Options menu bar items from the simulator/debugger. The simulator/debugger will also add additional items to the View and Windows menus. After loading the program and updating the Embedded Development Studio, the simulator/debugger will open and position any simulator/debugger specific windows that were open when it last loaded this same program.
Persistent data specific to the simulator/debugger is stored in the same directory as the program file and with the same file name as the program but with a .ARS, ARE and ARD extensions.
The simulator/debugger will also retrieve any non-source level breakpoints and other information from this file. (Source level breakpoints are stored in the Embedded Development Studio's .XWS file.)
Once the simulator/debugger has loaded the ARM program, initialised itself and updated the Embedded Development Studio, the Embedded Development Studio will transfer further information to it.
All source level information will be transferred. The simulator/debugger will set a breakpoint at the program address corresponding to the source line. If there is not an exact match between the source line and a program address, the breakpoint will be positioned at the nearest following source line. If there is no appropriate following source line, the breakpoint will be disabled.