Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!usc!sdd.hp.com!hplabs!hpfcso!hpldola!hp-lsd!rick
From: rick@hp-lsd.COS.HP.COM (Rick Nygaard)
Newsgroups: comp.realtime
Subject: Re: Technical Details (was Re: Measuring timing of Realtime Systems)
Message-ID: <15630010@hp-lsd.COS.HP.COM>
Date: 31 Aug 90 14:25:53 GMT
References: <182@srchtec.UUCP>
Organization: HP Logic Systems Division - ColoSpgs, CO
Lines: 30

> For example, define event A and event B.  Then, set the analyzer to trigger
> whenever B occurs > 200 usecs after A.

The HP 64620 State Analyzer, when configured with the 20 channel range/overview
board, supports this measurement, and other more general "range time trigger"
measurements.  This analyzer is an optional part of the 64000 emulation system.

Unfortunately, the measurement setup is somewhat obscure.**  The following is
from memory.  The manual (or softkeys) should be consulted for the precise
syntax:

  show trace_specification                         # bring up the trace spec
  overview on time                                 # turn on overview machine
  window one enable address A disable address B    # define interval
  overview enable window one                       # apply interval to overview
  overview event 1 range 200 usec or_more          # define time range
  trigger on overview event 1                      # trigger when in range
  execute                                          # start measurement
  show trace_list                                  # bring up the results

Trigger will occur on the bus cycle containing address B when the time
interval from A to B is 200 usec or longer.  Five time ranges, plus an
"everything else" bucket may be defined.  Thus, triggering in the "notches"
between a set of acceptable time ranges is also possible.

Rick Nygaard
HP, Logic Systems Division


** Yes, I know this is an understatement.