On this WEB page we shall look at customizing the SDS
graphical interface simulation tool to allow
To allow these operations to occur requires modification to
one of the three SSTEP.INI files. These SSTEP.INI
files are executed in the following order by the SDS program as
it powers up.
- SSTEP.INI file in directory SDS6.5\cmd. This
file contains standard definitions. Do not modify.!
- SSTEP.INI file in directory SDS6.5\init. This
file should include options you would like to have
operate regardless of your working directory.
- The SSTEP.INI file in the SDS Start up directory.
To avoid possible problems and unexpected
"happenings" make sure that you modify the appropriate
SSTEP.INI file and avoid having different "working
directories"
The SDS toolset has an editor that is called using the SDS
toolkit's Window | Editor option. You can customize the
SDS toolset to activate your own editor youreditor
- Customizing a Window's based editor is done as follows
- Exit the SDS toolset
- Create the file
"c:\sds6.5\init\sstep.ini" and include
the line
alias _edit 'youreditor_executable \!:2'
- Customizing a DOS based editor is done as follows
- Exit the SDS toolset
- Create the file
"c:\sds6.5\init\sstep.ini" and include
the line
alias _edit 'visible -n youreditor_executable
\!:2'
- Make sure that the path variable used with the
SDS simulator includes the path to youreditor_executable
You can now bring up youreditor by selecting the Tools
| External Editor option and selecting the file you wish to
edit. Set up your Startup
directory to your Laboratory directory for ease of use of
this tool.
Return to the top of this page.
To customize the SDS 68K toolset for assembling files use the
following procedure
- Set up your Startup
directory.
Select
the toolset option Tools | Assembler | Configure.
- You should now see a CrossCode Assembler Options
window
- In the Processor sub-window select the 68020
option. You will see the Option
sub-window values change to reflect this new option.
In the Additional
Options sub-window enter -L -m. You
will see the Option sub-window values
change to reflect these new options. Note that the
assembler option -f is automatically selected.
- In the Output sub-window you can specify
the name of the outfile (.o) from the assembly operation.
If you do not specify anything you will get a outfile
with the same prefix as the source file (thing.s will
give thing.o).
- In the sub-window below the Output
sub-window make sure the Generate full symbol and
type information option is checked.
- You can specify the file to assemble in a similar way
using the File button and associated window.
Select a 68K source file, say "e1final.s".
- You can either specify your Execution Directory
in the sub-window next to the Execution Directory
button or browse through the available directories by
clicking on the Execution Directory button.
Set the directory to your Laboratory 1 directory.
- Activate the Save button
to save these options.
You can now use the Tools | Assembler | Execute
option to assemble your file. You will see an Editor
window and an associated Error Messages window
to show the status of your assembly. Dismiss these windows when
you have made use of the information in them.
After you have performed the assembly operation, you get an Editor window
and an associated Error Messages window. If you
have any errors in the Error Messages window,
then double click on them. The SDS toolkit will
bring in the associated source file and indicate the line that is
incorrect. If you want to you can then correct the source file
(using the SDS editor) and re-assemble using the Tool |
Assembler option.
WARNING:- With the Version 6.5 toolset, if
you are editing a file and use the Tool | Assembler
option, the file you set when you configured the Assembler will
be assembled and NOT the file you are editting. Apparently (I
read the User Manual but have not tested it) with the Version 7.X
toolset, the editor will reconfigure the Assembler configuration
for the file being edited.
To customize the SDS 68K toolset for linking files use the
following procedure
- Set up your Startup
directory.
- Select the toolset option Tools | Linker | Configure.
You should now see a CrossCode Linker Options
window.
- You can either specify your memory specification file SpecFile
in the sub-window next to the SpecFile button or
browse through the available files by clicking on the SpecFile button.
Set this to the absmap.spc file in your 68K
Laboratory 1 directory.
You
should specify the output file t1final.out in
the sub-window labeled Output File.
- You can either specify your Execution Directory
in the sub-window next to the Execution Directory
button or browse through the available directories by
clicking on the Execution Directory button.
Set the directory to your 68K Laboratory 1 directory.
Click on
the Input Files button. You will see the Files
to link window appear.
- In the sub-window Chosen Files,
select files (with the mouse) and then Delete
all the files in the sub-window.
- Select the file you wish to link (t1final.o). Its
name should appear in the File Name
sub-window.
- Select ADD to
add this file into the Chosen File
sub-window.
- Dismiss the window with OK.
- You may find it useful to click on the Generate
global cross reference file if you have a large
amount of code. (Try it anyway, find out what happens.)
- Activate the Save button
to save these options.
You can now use the Tools | Linker | Execute option
to link all of your files. You will see an Editor
window and an associated Error Messages window
to show the status of your linking. Dismiss these windows when
you have made use of the information in them. Remember that the
SDS demo-kit linker is limited to handling only 3 object (.o)
files.
Return to the top of this page
Last modified: July 17, 1996 12:26 AM by M. Smith.
Copyright -- M. R. Smith