The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Sep. 24, 1991
Filed:
Dec. 30, 1988
John D Hansen, Colorado Springs, CO (US);
Arnold S Berger, Colorado Springs, CO (US);
Lewis S Kootstra, Colorado Springs, CO (US);
Beth V Jones, Colorado Springs, CO (US);
Stan W Bowlin, Colorado Springs, CO (US);
William Fleck, Colorado Springs, CO (US);
Hewlett Packard Company, , US;
Abstract
A system for coordinating the measurement activity of a plurality of emulators and their associated internal analyzers uses a bus with three signal lines. A READY signal is set false by any emulator that initiates a break (a transition from running user code to running a monitor). The READY signal is set false by the breaking emulator at the very beginning of its break, without waiting for the resumption of the monitor program. The false ready signal is detected immediately by the other emulators, which then break in sympathy. The READY signal is further used to restart all emulators in unsion. The emulator that initiated the break remains running its monitor, while the others start their monitors, determine that they did not cause the break, and then in anticipation of a restart, essentially suspend their monitors and prepare to start running user code. As each emulator becomes ready it releases the READY signal. As the last emulator becomes ready, it too releases READY, which then goes true. At this all emulators complete their escape from their monitors (which for each of them amounts to just an instruction fetch, or so) and resume execution of their user code. A four-state state machine in each emulator assists in this, and is in part, advanced through its states by transitions in the READY signal. The four states correspond to: running the monitor, ready to start executing user code, executing user code, and invoking the monitor. A TRIGGER signal is available to allow analyzers to trigger other analyzers, or to cause an emulator to break. An EXECUTE signal is available to allow a single command issued to any emulator to cause target system starts from preselected initial conditions.