HP Integrity Superdome SX1000 User Guide, Sixth Edition - HP Integrity Superdo - Page 306

Output Data Files, Format, Link Architecture File, Complex Configuration File

Get HP Integrity Superdome SX1000 PDF manuals and user guides View all HP Integrity Superdome SX1000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 306 highlights

JUST Exploration Tool Data Files 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 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

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
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
.