US5611044A
Expired / Lapsed
US
⏱️ 0.0 years remaining
System and method for cross-triggering a software logic analyzer and a hardware analyzer
Assignee: Hewlett Packard Development Co LP
•
Filing: 1995-04-10
•
Granted: 1997-03-11
•
Expires: 2015-04-10
Abstract
Abstract A system and method provides software logic analysis of computer system problems. The system and method incorporates event triggering, event limiting and cross-triggering in a software event logging process. A cross-trigger port is provided to facilitate connection between the present system and an external analyzer, such as a hardware logic analyzer or an oscilloscope. An end-user controls the event logging process via a user interface that permits the end-user to write trigger and limit conditions. One embodiment of the present system and method involves the small computer system interface (SCSI) sub-system.
Inventors
- 👤 Bruce A. Lundeby
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-03 22:07
CPC Classifications
G; G06; G06F; G06F11/00; G06F11/30; G06F11/34; G06F11/3466; G06F11/22; G06F11/25
Claims Analysis
Total Claims: 16
Claim 1
Independent Claim
131 words
A software logic analyzer for aiding an end-user in the analysis of software problems occurring in a software process residing in a computer system, the analyzer comprising: an event log; a kernel log machine, the kernel log machine collects at least one predetermined log point located within the software process, the kernel log machine places said at least one predetermined log point in the event log; a kernel log machine interface, connected to the kernel log machine, the interface provides the end-user a capability to control the kernel log machine; decoding means for transforming the event log from a first format to a second format; and a cross-trigger port having first and second ends, the first end connected to the kernel log machine, the second end connected to an external analyzer.
Claim 2
Dependent Claim
131 words
A software logic analyzer for aiding an end-user in the analysis of software problems occurring in a software process residing in a computer system, the analyzer comprising: an event log; a kernel log machine, the kernel log machine collects at least one predetermined log point located within the software process, the kernel log machine places said at least one predetermined log point in the event log; a kernel log machine interface, connected to the kernel log machine, the interface provides the end-user a capability to control the kernel log machine; decoding means for transforming the event log from a first format to a second format; and a cross-trigger port having first and second ends, the first end connected to the kernel log machine, the second end connected to an external analyzer.
Claim 3
Dependent Claim
15 words
The software logic analyzer as recited in claim 1, wherein the cross-trigger port is bi-directional.
Claim 4
Dependent Claim
22 words
The software logic analyzer as recited in claim 2, wherein the cross-trigger port resides within an I/O interface of the computer system.
Claim 5
Dependent Claim
37 words
The software logic analyzer as recited in claim 3, wherein the cross-trigger port can be configured as a trigger input port, the trigger input port providing the external analyzer a capability to arm the software logic analyzer.
Claim 6
Dependent Claim
37 words
The software logic analyzer as recited in claim 3, wherein the cross-trigger port can be configured as a trigger input port, the trigger input port providing the external analyzer a capability to trigger the software logic analyzer.
Claim 7
Dependent Claim
40 words
The software logic analyzer as recited in claim 3, wherein the cross-trigger port can be configured as a trigger output port, the trigger output port providing the software logic analyzer a capability to send a message to the external analyzer.
Claim 8
Dependent Claim
19 words
The software logic analyzer as recited in claim 3, wherein the external logic analyzer is a hardware logic analyzer.
Claim 9
Dependent Claim
17 words
The software logic analyzer as recited in claim 3, wherein the external logic analyzer is an oscilloscope.
Claim 10
Dependent Claim
30 words
The software logic analyzer as recited in claim 3, wherein the kernel log machine is located in a first area of memory, the first area being inaccessible by the end-user.
Claim 11
Dependent Claim
17 words
The software logic analyzer as recited in claim 9, wherein the I/O interface comprises a SCSI interface.
Claim 12
Dependent Claim
34 words
The software logic analyzer as recited in claim 10, wherein the SCSI drive is controlled by the software process, the at least one predetermined log point indicative of a sub-process of the SCSI interface.
Claim 13
Independent Claim
79 words
A method for software logic analysis of problems occurring in a software process, the method comprising the steps of: (a) starting an analyzer function to collect data located in the software process upon encountering a predetermined log point located within the software process, the analyzer function having an operation state; (b) determining whether an external trigger condition has been satisfied; and (c) saving a first predetermined log point in an event log when the external trigger condition is satisfied.
Claim 14
Independent Claim
79 words
A method for software logic analysis of problems occurring in a software process, the method comprising the steps of: (a) starting an analyzer function to collect data located in the software process upon encountering a predetermined log point located within the software process, the analyzer function having an operation state; (b) determining whether an external trigger condition has been satisfied; and (c) saving a first predetermined log point in an event log when the external trigger condition is satisfied.
Claim 15
Dependent Claim
62 words
The method as recited in claim 12, wherein step (b) further comprises the steps of: (b1) determining whether the operation state is equal to ARMED; (b2) determining, if the operation state is equal to ARMED, whether the external trigger condition has been satisfied; and (b3) resetting the operation state equal to NOT -- ARMED if the external trigger condition has been satisfied.
Claim 16
Dependent Claim
81 words
The method as recited in claim 13, further comprising the steps of: (d) determining, if the operation state is not equal to ARMED after step (b1), whether an internal trigger condition is present; (e) determining, if the internal trigger condition is present, whether the internal trigger condition has been satisfied; (f) setting the operation state of the analyzer function equal to TRIGGERED if the internal trigger condition has been satisfied; (g) saving a second predetermined log point in an event log.
References Cited (Backward Citations)
US5265254A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2000-03-10 | 2000-09-09 | 2001-03-11 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2004-03-10 | 2004-09-09 | 2005-03-11 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2008-03-10 | 2008-09-09 | 2009-03-11 | $7700.00 | Window Closed / Lapsed |