HP Integrity Superdome SX1000 User Guide, Sixth Edition - HP Integrity Superdo - Page 303
Board Architecture File, Format, JUST Exploration Tool
View all HP Integrity Superdome SX1000 manuals
Add to My Manuals
Save this manual to your list of manuals |
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