Appendix G
JUST Exploration Tool
Data Files
294
Format
Comments Comments in this file are specified by placing a # character at the beginning of the line containing the
comment. End of line comments are not currently supported.
Version Infromation The first none comment field in the cplx.ini file must start with the keyword FILE_VERSION
followed by the files version entered as a double.
Example G-15 Device Architecture File Version
FILE_VERSION <version number>
Device Entries Each valid JTAG ID for this device must have an entry in this file. Entries consist of the keyword
Device_Id followed by the device name and the unsigned long representation of the JTAG ID.
Example G-16 Device ID
##################################################################
# Device_Id <device name> <jtag id>
##################################################################
Device_Id dna1 0x14076049
If a device does not have a JTAG ID, a default ID must be provided in this file. The format of a default entry begins with
the keyword Default_Id followed by the device name and the default JTAG ID represented as a string.
The default JTAG ID string must begin with the 0x. The JUST tool looks for this these characters and strips them off to
build its device file names.
Example G-17 Default ID
##################################################################
# Device_Id <device name> <jtag id>
##################################################################
Device_Id dna1 0x14076049
End of File Marker This file must end with the keyword End_Of_File.
Link Architecture File
The link architecture file describes the possible link interconnects possible within a complex. These
connections are any that are not static within a system.
There is only one link architecture file for each complex and it must be named link.arc.
Output Data Files
JET produces both data files and log files. Other scan tools use the data files created by JET as input
information. The log file generated by JET contains information on its execution. JET output files are
described in the following sections.
Complex Configuration File
This file contains information on the systems available for test on a particular network. It is used by the
Libsdp library to direct messages from the test station to the system under test.
There is only one complex configuration file, which must be named complex.cfg. It may contain entries for
multiple complexes. JET places this file in the default scan directory /opt/scansw/data.
To Next Page
Loading...
