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

JUST Exploration Tool Data Files Board Lists The board list section begins with the keyword Board_List and ends with the keyword End_Board_List. Between these tags are board entries for each of the boards in the node. Board entries begin with the keyword Board followed by the board family, board type, and the board reference number. Board entries end with the keyword End_Board. Board entries contain a variable number of parameters each designated by a keyword. Each of the parameters that can be specified has default values that are used if the parameter is not present. Below is a list of the board options. • required-By default boards are consider to be not required. If a board is required, it must have an entry beginning with the keyword required followed by an upper case boolean either TRUE or FALSE. • eprom-By default boards are assumed to have serial EPROMs from which the board name and scan revision can be retrieved. If a board doesn't have an eprom then the board name, part number and scan revision must be supplied. An eprom entry begins with the keyword EPROM and is followed by a boolean indicating whether eprom data is available. If EPROM data is not available (FALSE) then the entry must specify the board name, part number, and scan revision as follows: eprom [ ] • num_scan_paths-By default a board is assumed to have no (zero) scan paths. If a board has scan paths, the number of paths on the board must be defined, using the keyword num_scan_paths followed by an unsigned integer representing the number of scan paths on the board as follows: num_scan_paths Masks By default a board is assumed to not have a presence mask. If a presence mask does exist for this board then an entry defining the mask is required. A mask entry begins with the keyword mask followed by a boolean indicating whether a mask is available. If a mask is available then the following data is also required. The bit in the mask that reflects this board, the type of mask to request (either CELL_MASK, IO_MASK, or NODE_MASK), the type of entity the mask should be sent to an that entities reference number. mask [ Dependency A dependency is a relationship between boards. There are two currently supported dependency types: CHILD and PARENT. A board that contains a child dependency depends on the board specified in the dependency to be present. A board that contains a parent dependency must be present for the board specified in the dependency to be present. During normal JET operations these dependencies are used to resolve presence issues. In interactive mode these dependencies are used to prevent invalid configurations from being created. By default, boards are considered to contain no dependencies. If a board has a dependency then an entry must be made. A dependency entry begins with the keyword dependency followed by the family, type and reference number of the board and the dependency type. dependency Example G-11 Board list Board_List Board 2 1 0 required FALSE eprom TRUE num_scan_paths 3 mask TRUE 3 IO_MASK MP 0 dependency 5 3 1 PARENT End_Board Board 5 1 5 required TRUE eprom FALSE HMIOB A5201-60005 1 num_scan_paths 1 290 Appendix G