5-2
Configuration Data and the Configuration Utility
Table 5.1
Configuration Utility Files
File Name
Description
config.exe
The main configuration program (the first element of the firmware)
provided by LSI Logic. It displays the questions one at a time,
beginning with general questions and progressing to more detailed
questions about desired MPIO/MPLED pin assignments for the
enclosure environment.
bootload.hex
The second element of the firmware provided by LSI Logic. This file
contains the bootloader, which is used only if the designer selects the
download option addressed in the first question of the configuration
utility.
loader.hex
The hex output of
config.exe.
The designer concatenates this file
with the
bootload.hex
firmware binary file into a file called
boot
.
hex
(or whatever the designer wishes to call this file), which is
the image that is placed on the TWS memory device and downloaded
to the LSI53C040. Refer to
Section 5.3, “After Running the
Configuration Utility,” page 5-21
about using DOS commands to
concatenate files.
safte.hex
The third element of the firmware provided by LSI Logic. This file is an
Intel hex file which contains the SAF-TE firmware.
config.hex
The hex output of
config.exe.
The designer concatenates this file
with the
safte.hex
firmware binary file into a file called
safcon
.
hex
, (or whatever the designer wishes to call this file), which
is the image that is placed on the TWS memory device and
downloaded to the LSI53C040. Refer to
Section 5.3, “After Running the
Configuration Utility,” page 5-21
about using DOS commands to
concatenate files.
myinput
.txt
The designer can create this file with a text editor using the answers
from the questions asked in the configuration program. After this file is
first created, the designer can change some of the values submitted to
the configuration program, by editing this file and running it, instead of
manually stepping through all of the questions in
config.exe
. Just
run
config.exe
again, redirecting the input to the configuration utility
to a file called
myinput
.txt,
and redirecting the output of the
configuration utility to a file called
myinput
.log
using the DOS
command:
config<
myinput
.txt>
myinput
.log
.
myinput
.log
When the file
myinput.txt
is used in the DOS command:
config<
myinput
.txt>
myinput
.log
, the resulting file
(
myinput
.log
) contains a summary of all the questions answered, as
well as a summary of any errors in the input file. When the program
runs to completion, the
myinput.log
file also contains a summary of
the data structure sizes and the Enclosure ID field.