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

Board Architecture File, Format, JUST Exploration Tool

Page 303 highlights

mask FALSE dependency 2 1 0 CHILD End_Board End_Board_List JUST Exploration Tool Data Files The Path List The next section of Node Architecture FIle defines the scan paths in the node. Each of the nodes scan paths are composed of one or more scan paths on the board defined in the board list. The path list begins with the keyword Path_List and ends with the keyword End_Path_List. Between these tags are the individual path definitions for the node. Path Entries A path entry defines the boards and there scan paths that make up this node level scan path. A path entry begins with the keyword Path followed by the paths reference number. A path entry ends with the keyword End_Path. Between these tags are board entries for each board composing the path. Board Entries A board entry in a path begins with the keyword board followed by the family, type, and reference number of the board and the path on the board that is to be used. These entries must be in order of how they appear on the path through the node as follows: board Example G-12 Path Entry Path_List Path 1 board 2 1 0 2 board 3 2 6 0 End_Path Path 2 board 5 1 1 1 board 3 2 6 2 End_Path End_Path_List End of File Marker This file must end with the keyword End_Of_File. Board Architecture File The Board Archiritecture File describes the scan paths and link connections present on the board. It lists the devices present on each board scan path along with there name, and removal information. It also has a section that lists the connections present on the board for links. A board architecture file must exist for each board part number/scan revision. Its file name has the form brd__.arc. This file is named using the prefix brd_ followed by the board name and scan revision separated by an underscore and ending 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 Information 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-13 Board Architecture File Version FILE_VERSION Appendix G 291

  • 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
291
mask
FALSE
dependency 2
1
0
CHILD
End_Board
End_Board_List
The Path List
The next section of Node Architecture FIle defines the scan paths in the node. Each of the nodes scan
paths are composed of one or more scan paths on the board defined in the board list. The path list begins with the keyword
Path_List
and ends with the keyword
End_Path_List
. Between these tags are the individual path definitions for the
node.
Path Entries
A path entry defines the boards and there scan paths that make up this node level scan path. A path entry
begins with the keyword
Path
followed by the paths reference number. A path entry ends with the keyword
End_Path
.
Between these tags are board entries for each board composing the path.
Board Entries
A board entry in a path begins with the keyword
board
followed by the family, type, and reference
number of the board and the path on the board that is to be used. These entries must be in order of how they appear on
the path through the node as follows:
board <board family> <board type> <board reference num> <board path num>
Example G-12
Path Entry
Path_List
Path 1
board
2
1
0
2
board
3
2
6
0
End_Path
Path 2
board
5
1
1
1
board
3
2
6
2
End_Path
End_Path_List
End of File Marker
This file must end with the keyword
End_Of_File
.
Board Architecture File
The Board Archiritecture File describes the scan paths and link connections present on the board. It lists the
devices present on each board scan path along with there name, and removal information. It also has a
section that lists the connections present on the board for links.
A board architecture file must exist for each board part number/scan revision. Its file name has the form
brd_<board part number>_<scan revision>.arc
. This file is named using the prefix
brd_
followed by the
board name and scan revision separated by an underscore and ending 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 Information
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-13
Board Architecture File Version
FILE_VERSION <version number>