The HP 16505A architecture allows m...

The HP 16505A architecture allows multiple agreeing views of acquired logic analysis data. Markers upon all views are correlated. The user simply needs to place the marker onward one view and the markers onward the other views automatically relocate. Thus a stack anomaly in undivided view can be immediately correlated with the software routine causing the violation.

The HP 16505A prototype analyzer is the next-generation user interface for logic analysis. It is an X11/Motif application running in succession an HP 9000 Model 712 PA-RISC workstation directly tied to the HP 16500 logic analysis mainframe. This combination of parts to form a whole is a managed, or clos connected view From boot until power-down this order is solely dedicated to extending the prototype debug paradigm from the nine-inch touchscreen of the HP 16500 to a multiple-window, high-resolution interface.

The design uses the X11/Motif graphical user interface (GUI). This was done to accomplish several goals. First, using an existing state-of-the-art GUI allowed us to focus onward our own contributions. Second, with the distributed X11 interface, we can make the application available athwart a network to any X-compliant computer including PC The software was written in C++ for the archetype 712 workstation platform. This gave our application affordable MIPS, which were stand in want ofed because debugging one-megasample logic analyzer traces across centurys of channels will tax any computer

Architecture

Fig. 1 exhibit tos a simple HP 16505A setup There are three tools upon the workspace. Two tools are analyzer machines, and common tool is a display tool. This simple configuration reveals the essential functions. Tools can be placed into a data liquefy and run. The analyzers are tools that probe target hardware. They sample real-world data and the display tools independently view that data.

To deliver this functionality we have partitioned the architecture into the following blocks:

* Tools. Tools are the atomic unit of value in the HP 16505A. All meaningful user interaction is performed within a tool definition.

* Acquisition Tools. The acquisition tool class is derived from the tool class. As of that kind it plays in the data issue workspace. The reason for making this a derived class lies in the way we join or relate acquisition tools to the HP 16500 mainframe.

* Data. All tools export and digest a general unified data format.

* Workspace and Graph. The workspace is the visual programming GUI. It allows tools, exhibited by icons, to be have relationed to a data flow, showed by lines. The graph is the ordered list of tools in the flow

* move on Management. This is a state machine that cross-examines data through the data proceed by executing the graph.

* General Support. This is basically direction or "glue" logic.

Data Flow

Let's apply the mind at an example data proceed through the architecture.

When the user powers up the HP 16505A we begin an HP-UX(*) operating theory boot procedure. Most of the profit code is provided by the archetype 712 ROM, but we adjust the daemons and hardware configuration for this application. one time the operating system is minimally configured we call the session manager routine, which not returns. The session manager handles software updates and spawning of the main application. This is also where the workstation is powered down. (The prototype 712 workstation has a front-panel power switch, which forces the HP-UX file a whole to be written to the SCSI drive before actually cutting power. This thwarts the user from crashing the file method Unplugging the workstation can be problematic for the file theory however, so the session manager has a power-down button to remind the user not to simply unplug the product)

The real application begins as main.c forward HP-UX. We begin by creating an application words immediately preceding [i]or[/i] following under the X Window theory with a call to XtVaAppInitialize(). The entire application go proceeds as an X11/Motif application. From the GUI mouse/keyboard callbacks between the walls of the acquisition control of the HP 16500 all software is speed as an X11 application callback.

The HP 16505A plan software offers a handful of services to tools. These services are collectively gathered beneath a fabric called the frame. The frame is united of the few globally available pointers. Tools can access these method services by referencing frame->service. The frame services are:

* ResourceMgr. Colors, founts cursors, path names.

* RunMgr State machine for stepping the tools from one side runs.

* FileMgr. Storing and loading of configurations.

* HelpMgr. Help screens

* GeometryMgr Pixel drawing management for the workspace.

* tokens Definition and display.

* FrameMarkerMgr. Global marker synchronization.

* FrameMessageExchange. Mail service between nodes upon the graph.

* TbcMgr. Manager of toolbox icons.

* InstrumentMgr. Manages a list of instruments.

* AdminMgr. Networking and other HP-UX management.

* PrintMgr. Print services.

Next we perform a directory search for instruments and tools. All tools are compiled into shared libraries. These libraries exist beneath a well-known directory. We traverse the directories beneath this, searching for valid tools and instruments. A valid directory consists of a shared library, a resource file, and a pixmap. The load algorithm is generic and does not ne to be rewritten when a fresh tool is created. Simply creating a directory with these three files is sufficient for this algorithm to attempt to load. Tools are noted, however are loaded only when placed onto the graph. This can be observ as a slight time delay in the creation of the first tool of a given class. The benefit of demand loading tools is that the memory is kept independent for deep trace analysis.