
Appendix H
JUST Exploration Tool
Data Files
226
#################################################################
# Connection <ID> <lookup> <loopback> <type> <brd ref des> <cable ref des>
#<PN> <name>
#################################################################
Connection1 0 FALSE IO J5005T P1 A5201-63037_0001 CELL0_REO_IN
Connection1 1 TRUE IO J5033T P1 A5201-63037_0001 CELL1_REO_IN
End_Primary
End_Link_Type
End_Of_File
Device Architecture File
The device architecture file lists valid JTAG IDs for a device based on the device name. If a device does not
have a JTAG ID, then a default ID entry must be included in this file. The file must exist for each device name
present in the board architecture file. Its file name has the form
dev_<device name>.arc
. and is named by
placing the prefix
dev_
in front of the device name and ending it with the suffix
.arc
.
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 H-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 H-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.
Содержание 9000 Superdome
Страница 8: ...Contents 8 ...
Страница 9: ...9 Preface ...
Страница 21: ...21 IEC 60417 IEC 335 1 ISO 3864 IEC 617 2 International Symbols ...
Страница 22: ...22 Figure 9 Superdome Declaration of Conformity Page 1 ...
Страница 23: ...23 Figure 10 Superdome Declaration of Conformity Page 2 ...
Страница 24: ...24 ...
Страница 32: ...Chapter 1 Introduction Installation Warranty 8 ...
Страница 130: ...Chapter 4 Verifying and Booting Superdome Enabling iCOD 106 ...
Страница 146: ...Chapter 6 Troubleshooting and Installation Related Tasks Installing a PCI I O Card While the Cell is Off 122 ...
Страница 154: ...Chapter 7 No Boot Disk Superdome Installations Installing the Superdome Operating System From Available Media 130 ...
Страница 172: ...Appendix A hp Server rx2600 Support Management Station Configuring the SMS 148 ...
Страница 184: ...Appendix C Superdome LAN Interconnect Diagram 160 ...
Страница 193: ...Appendix F 169 F A180 Support Management Station ...
Страница 230: ...Appendix G Connecting Multiple SPU Cabinets Connecting Cables 206 ...
Страница 256: ...Appendix H JUST Exploration Tool Error Conditions 232 ...