Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Partitioning VLSI Functions Into Stages for a Knowledge Base

IP.com Disclosure Number: IPCOM000102597D
Original Publication Date: 1990-Dec-01
Included in the Prior Art Database: 2005-Mar-17
Document File: 3 page(s) / 79K

Publishing Venue

IBM

Related People

Barrett, KL: AUTHOR [+3]

Abstract

Disclosed is a concept of partitioning all functions/faults of a VLSI design into stages in knowledge bases which are used for generating implementation verification programs.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 53% of the total text.

Partitioning VLSI Functions Into Stages for a Knowledge Base

       Disclosed is a concept of partitioning all
functions/faults of a VLSI design into stages in knowledge bases
which are used for generating implementation verification programs.

      As the user interface accesses the function unit, it needs to
know how to perform the function.  Therefore, some form of knowledge
must be attached to the function, i.e., via a frame-based data
structure, or a slot.  The representation must take into account the
fact that different functions can execute concurrently.  And,
finally, as the system design becomes more stable, many functions may
be assumed to work correctly and they should not have to be checked
for correctness every time they are used.

      Based on the above criteria, the "HOW TO PERFORM" property of
all functions in the function KB is organized as four slots: SET_UP,
TRIGGER, CHECK_DONE and CHECK_RESULTS.
      EVENTS:

      Set of procedures that are recursively defined.  The lowest
level of these procedures are assembly code or IVPMAC (REXX) code.
      ARG_LIST:

      List of all arguments needed for this function.  The user must
provide or accept default values for each argument.  Arguments are
properties of this object (event).
      SET_UP:

      Procedure to set up an event, get it ready.  This step is just
one step short of kicking-off this event.
      TRIGGER:

      Procedure to kick-off the event.
      CHECK_DONE:

      Procedure to verify that the event compl...