Browse Prior Art Database

(GQ) Lab Navigator Tool

IP.com Disclosure Number: IPCOM000087803D
Original Publication Date: 2005-Mar-03
Included in the Prior Art Database: 2005-Mar-03
Document File: 6 page(s) / 54K

Publishing Venue

IBM

Abstract

Lab Navigator is a GUI (Graphical User Interface) environment for the control and display of pervasive debug hardware facilities. It is intended to help users avoid omissions and conflicts in the setup of trace array hardware prior to and after running lab tests. It is also intended to be the main window seen by users when running a test station debug session.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 24% of the total text.

Page 1 of 6

(GQ) Lab Navigator Tool

Function: A GUI environment for the control and display of pervasive debug hardware facilities, Navigator is intended to help users avoid omissions and conflicts in the setup of trace array hardware prior to and after running lab tests. It lets a user run the lab tests and analyze them with tools. It is also intended to be the main window seen by users when running a test station debug session.

Lab Navigator provides:

    Test shift operating status and controls. Integration between exercisers and the base code.

Trace array setup and formatted output display

    Trigger management
Point tool invocation (edit_cnfg and checkstop analysis tools - fircheck, LFDM, RPM, logshift,etc.)

Edit cronus config (GUI for configuring/ deconfiguring chips )

General Operation:

When launched, the Lab Navigator main window appears showing separate regions for displaying :

Tools that can be invoked with a click,

    File menu to setup the session for the Trace Array Setup Tools and, Display area to show a system image (e.g., one of the Power 4 systems depending on what parameter was passed to navigator). This image appears for the different pages/tabs.

The different pages in Navigator are:

Gentrace

Muxselect
Edit Config
SDC
Run Shift List

An image of the system is displayed on separately tabbed notebook pages, one for each tool. The image includes an overlay of buttons, each representing a physical chip for which trace arrays and/or trigger controls are available for user setup. The buttons are created based on data acquired from the Cronus configuration file for the system under test. The number and letter shading per button indicates whether a chip is actually present and configured or deconfigured, as defined in the user's cronus config file. Pre placed buttons for which the actual chips are unpopulated or deconfigured in the hardware system will be grayed out and disabled.

A chip button's color indicates Trace Array Setup progress with status tracked per chip, which Navigator determines by the presence or absence of lines in the navigator.xxxx file. (The specific tool name, such as "gentrace" or "mxsl" is used in place of the xxxx extension. These navigator.xxxx files are used for inter tool communication. Users should not normally be concerned with these files.) The purpose of the color indicators

1

Page 2 of 6

is to confirm that the System's trace array and trigger/action hardware has been configured and call attention to chips for which are possibly conflicting.

Certain events, such as returning from a trace array setup tool or a user selecting View -> Re scan All Chips from the menu bar, will cause Lab Navigator to inspect the navigator.xxxx file in the directory indicated in the Session Setup dialog box. It then updates the system device display with the appropriate colors from the following four possible combinations:

(-p)# (-p)all COLOR DESCRIPTION

0 0 ivory untouched: no trigger/action set up for this chip

0 1 blue all chips of thi...