US7096440B2 - Methods and systems for automatic verification of specification document to hardware design - Google Patents
Methods and systems for automatic verification of specification document to hardware design Download PDFInfo
- Publication number
- US7096440B2 US7096440B2 US10/624,347 US62434703A US7096440B2 US 7096440 B2 US7096440 B2 US 7096440B2 US 62434703 A US62434703 A US 62434703A US 7096440 B2 US7096440 B2 US 7096440B2
- Authority
- US
- United States
- Prior art keywords
- hardware
- document
- database
- hardware device
- predefined elements
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Lifetime, expires
Links
- 238000000034 method Methods 0.000 title claims abstract description 44
- 238000013461 design Methods 0.000 title claims abstract description 43
- 238000012795 verification Methods 0.000 title description 26
- 238000012360 testing method Methods 0.000 claims description 38
- 230000015654 memory Effects 0.000 claims description 31
- 230000006870 function Effects 0.000 claims description 23
- 230000004044 response Effects 0.000 claims description 4
- 238000004088 simulation Methods 0.000 description 10
- 230000008569 process Effects 0.000 description 8
- 238000012942 design verification Methods 0.000 description 6
- 238000012545 processing Methods 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 230000006399 behavior Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 239000013598 vector Substances 0.000 description 3
- 101100136092 Drosophila melanogaster peng gene Proteins 0.000 description 2
- 101100096985 Mus musculus Strc gene Proteins 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 102000000850 Proto-Oncogene Proteins c-rel Human genes 0.000 description 1
- 108010001859 Proto-Oncogene Proteins c-rel Proteins 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 230000002860 competitive effect Effects 0.000 description 1
- 230000000295 complement effect Effects 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2284—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing by power-on test, e.g. power-on self test [POST]
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01R—MEASURING ELECTRIC VARIABLES; MEASURING MAGNETIC VARIABLES
- G01R31/00—Arrangements for testing electric properties; Arrangements for locating electric faults; Arrangements for electrical testing characterised by what is being tested not provided for elsewhere
- G01R31/28—Testing of electronic circuits, e.g. by signal tracer
- G01R31/317—Testing of digital circuits
- G01R31/3181—Functional testing
- G01R31/3183—Generation of test inputs, e.g. test vectors, patterns or sequences
- G01R31/318342—Generation of test inputs, e.g. test vectors, patterns or sequences by preliminary fault modelling, e.g. analysis, simulation
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01R—MEASURING ELECTRIC VARIABLES; MEASURING MAGNETIC VARIABLES
- G01R31/00—Arrangements for testing electric properties; Arrangements for locating electric faults; Arrangements for electrical testing characterised by what is being tested not provided for elsewhere
- G01R31/28—Testing of electronic circuits, e.g. by signal tracer
- G01R31/317—Testing of digital circuits
- G01R31/3181—Functional testing
- G01R31/3183—Generation of test inputs, e.g. test vectors, patterns or sequences
- G01R31/318342—Generation of test inputs, e.g. test vectors, patterns or sequences by preliminary fault modelling, e.g. analysis, simulation
- G01R31/318357—Simulation
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01R—MEASURING ELECTRIC VARIABLES; MEASURING MAGNETIC VARIABLES
- G01R31/00—Arrangements for testing electric properties; Arrangements for locating electric faults; Arrangements for electrical testing characterised by what is being tested not provided for elsewhere
- G01R31/28—Testing of electronic circuits, e.g. by signal tracer
- G01R31/317—Testing of digital circuits
- G01R31/3181—Functional testing
- G01R31/3183—Generation of test inputs, e.g. test vectors, patterns or sequences
- G01R31/318364—Generation of test inputs, e.g. test vectors, patterns or sequences as a result of hardware simulation, e.g. in an HDL environment
Definitions
- Embodiments generally relate to hardware design verification methods and systems. Embodiments also relate to methods and systems for verifying integrated circuit designs. Embodiments additionally relate to Power On Self Test (POST) techniques and devices.
- POST Power On Self Test
- design verification In many instances it can be necessary to implement hardware design verification methods and systems.
- the objective of design verification is to ensure that errors are absent from a design.
- Modern integrated circuit (IC) manufacturing technology is enabling IC designers to place millions of transistors on a single IC.
- Design complexity is doubling every 12–18 months, which causes design verification complexity to increase at an exponential rate.
- competitive pressures are putting increased demands on reducing time to market.
- Today's design flow begins with a hardware specification document for the design.
- the engineer then implements the design in a language model, typically a Hardware Description Language (HDL).
- HDL Hardware Description Language
- Such a model can be utilized to discover incorrect input/output (I/O) behavior through a stimulus in expected “results out” paradigm at the top level of the design.
- simulation-based functional verification By far the most popular method of functional verification today is simulation-based functional verification, which is widely utilized within the digital design industry as a technique for detecting defects within hardware designs.
- a very wide variety of products are available in the market to support simulation-based verification methodologies.
- a fundamental problem with conventional simulation-based verification approaches is that they are vector and test bench limited.
- Simulation-based verification is driven by a test bench that explicitly generates the vectors to achieve stimulus coverage and also implements the checking mechanism.
- Test benches create a fundamental bottleneck in simulation-based functional verification. In order to verify a design hierarchy level, a test bench must be generated for it. This creates verification overhead for coding and debugging the test bench. Hence, a significant amount of expensive design and verification engineering resources are needed to produce results in a cumbersome and slow process.
- Formal verification is another class of tools that has entered the functional verification arena. These tools rely on mathematical analysis rather than simulation of the design. The strong selling point of formal verification is the fact that the results hold true for all possible input combinations to the design. However, in practice this high level of stimulus coverage has come at the cost of both error coverage and particularly usability. While some formal techniques are available, they are not widely used because they typically require the designer to know the details of how the tool works in order to operate it. Formal verification tools generally fall into two classes: (1) equivalence checking, and (2) model checking.
- Equivalence checking is a form of formal verification that provides designers with the ability to perform RTL-to-gate and gate-to-gate comparisons of a design to determine if they are functionally equivalent. Importantly, however, equivalence checking is not a method of functional verification. Rather, equivalence checking merely provides an alternate solution for comparing a design representation to an original golden reference. It does not verify the functionality of the original golden reference for the design. Consequently, the original golden reference must be functionally verified using other methods.
- Model checking is a functional verification technology that requires designers to formulate properties about the design's expected behavior. Each property is then checked against an exhaustive set of functional behaviors in the design. The limitation of this approach is that the designer is responsible for exactly specifying the set of properties to be verified. The property specification languages are new and obscure. Usually the technology runs into capacity problems and the designer has to engage with the tools to solve the problems.
- IC integrated circuit
- a plurality of predefined elements can be designed within a hardware specification document, wherein the hardware specification document provides a hardware design for a hardware device.
- the plurality of predefined elements can be stored within a database of hardware components, wherein each predefined element of the plurality of predefined elements is associated with a hardware component of the hardware device.
- Physical components of the hardware device can be compared with the predefined elements maintained within the database of hardware components upon an initial power-up of the hardware device in order to verify that the hardware device functions according to the hardware specification document.
- FIG. 1 illustrates a block diagram of a data processing system in which an embodiment of the present invention may be implemented
- FIG. 2 illustrates a high-level flowchart depicting logical operational steps, which may be followed to implement an embodiment of the present invention
- FIG. 3 illustrates a high-level flowchart depicting continuing logical operational steps of the flowchart depicted in FIG. 2 , in accordance with an embodiment of the present invention
- FIG. 4 illustrates a block diagram of a hardware interrupt system, which can be implemented in accordance with an embodiment of the present invention
- FIG. 1 a block diagram of a data processing system 100 in which the present invention may be implemented is illustrated.
- the depicted example is not meant to imply architectural limitations with respect to embodiments of the present invention, but is presented for general illustrative and edification purposes only.
- Data processing system 100 can employ a peripheral component interconnect (PCI) local bus architecture.
- PCI peripheral component interconnect
- a Processor 102 and a main memory 104 can be connected to PCI local bus 106 through PCI bridge 108 .
- PCI bridge 108 also may include an integrated memory controller and cache memory for processor 102 .
- a controller 103 can communicate with PCI local bus 106 to provide additional architectural support. Controller 103 may be utilized in place of to complement an integrated memory controller and cache memory for processor 102 .
- PCI local bus 106 may be made through direct component interconnection or through add-in boards.
- local area network (LAN) adapter 110 host bus adapter 112 , and expansion bus interface 114 are connected to PCI local bus 106 by direct component connection.
- audio adapter 116 graphics adapter 118 , and audio/video adapter (A/V) 119 are connected to PCI local bus 106 by add-in boards inserted into expansion slots.
- Expansion bus interface 114 provides a connection for a keyboard and mouse adapter 120 , modem 122 , and additional memory 124 .
- Host bus adapter 112 provides a connection for hard disk drive 126 , tape drive 128 , and CD-ROM 130 in the depicted example.
- Typical PCI local bus implementations will support three or four PCI expansion slots or add-in connectors.
- the depicted example includes four loads on the mother board and three expansion slots.
- FIG. 1 may vary.
- other peripheral devices such as optical disc drives and the like may be used in addition to or in place of the hardware depicted in FIG. 1 .
- FIG. 2 a high-level flowchart 200 depicting logical operational steps is illustrated, which may be followed to implement an embodiment of the present invention.
- FIG. 3 illustrates a high-level flowchart 300 depicting continuing logical operational steps of the flowchart 200 depicted in FIG. 2 , in accordance with an embodiment of the present invention.
- like parts or elements are indicated by identical reference numerals, such that flowcharts 200 and 300 represent a single continuous flowchart of logical operation steps.
- FIGS. 2 and 3 together generally illustrate a methodology that includes document parsing software utility, routines, and/or subroutines which search for predefined flags and formatting in a hardware specification document and extracts the hardware information from the hardware specification document.
- the document parsing software utility generates a database can be utilized by other utilities.
- the methodology of FIGS. 2 and 3 can also be utilized to implement an RTL code auto-generation utility that reads the database and creates valid RTL hardware description code that defines the storage elements in the hardware.
- a software code auto-generation utility can be utilized to read the database and create valid software code that defines accesses to the storage elements in the hardware, and which also can generate hardware specification tables, which can be utilized by a Power On Self Test (POST) function, which is described in further detail herein.
- POST Power On Self Test
- the process is initiated.
- a document writer can follow a specified procedure to created detailed descriptions of the hardware to be designed according to the hardware specification document.
- Such specified procedure includes the use of specified formats for register map tables, address map tables and register description sections of the hardware specification document.
- invisible flags are embedded in the document to be utilized by the document reader script, which will be described in more detail herein.
- the document can be saved and used by internal and external engineers as formatted.
- the document can be saved as a text-only document for use by the document reader script.
- a document parsing software utility reads the document(s), and creates, as depicted at block 214 , a database of all storage elements in the document that are visible to a microcontroller, such as, for example, controller 103 of data processing system 100 illustrated in FIG. 1 .
- a microcontroller such as, for example, controller 103 of data processing system 100 illustrated in FIG. 1 .
- an RTL code auto-generator can be utilized to create HDL code file(s).
- HDL generally refers to “Hardware Description Language”.
- the software code auto-generator can create software file(s) that contain definitions and declarations for every storage element and for every bit field within registers, strictly as defined in the hardware document specification.
- the software code auto-generator can create tables utilized by Power-On Self Test Code to check the hardware upon power-up. The use of the auto-generated software code ensures that the RTL hardware description complies with the hardware specification document.
- two code auto-generators can be implemented, including the hardware RTL code generator and the software code generator.
- Block 216 refers to hardware code.
- Blocks 220 – 222 refer to software code which is not RTL code.
- such code may be C or C++ code. It can of course be appreciated by those skilled in the art that C or C++ code is not considered a limiting feature of the present invention, because other types of programming code can also be utilized to implement embodiments.
- the use of the auto-generated software code for storage elements and the Power-On Self Test tables causes the software to fail if the hardware does not comply with the specification document.
- a test can be performed to determine if the hardware complies with the specification document. If so, then the hardware design is verified, as indicated at block 228 . If not, then the hardware design fails, as indicated at block 226 . The process then terminates, as depicted at block 230 .
- files can be organized according to a layered structured.
- a layered structure can be implemented as firmware and may include hardware drivers, which are based on code that actually manipulates hardware register bits or memory. These drivers can be contained in the context of one or more files that hold only code that affects the specific hardware in question.
- a hardware driver generally is composed of both initialization code, and the actual driver code.
- the layered structure can also include configuration code that loads data and then acts as a ROM (read only memory) for the remainder of the firmware operations.
- such a layer structure can include definitions that are specific to an external standard, such as, for example, the SAS or SCSI bus standards. These definitions can be contained in header files that hold definitions specific to that standard.
- the layered structure can also include operating system header and code files that exist to contain definitions and declarations utilized by a kernel to control the general flow of the software. These include all general code files that contain common definitions and declarations.
- the layer structure can include development code files are files that contain code utilized for debugging. Code that facilitates retargettable Output for tracing or any other functions that are not part of the actual firmware can be contained within such code files.
- the interface for each separately specified block of hardware can be contained within its own code file set.
- the intent of this action is to provide a hardware abstraction layer so that if any part of the hardware is upgraded or redesigned in a later generation of the chip, code changes are limited to only the files owning that hardware interface.
- the files can contain the following: ⁇ HW Block Name>.h.
- This file contains the interface between the hardware and the rest of the firmware.
- Such a file can include prototypes for any functions that are owned by the hardware interface and that are visible to other parts of the firmware (e.g., a driver API). This also includes ‘extern’ declarations for any constants that are owned by this hardware interface but that must be visible elsewhere.
- the files can also contain ⁇ HW Block Name>.c.
- This file contains the code that directly manipulates the hardware. This includes declarations for all private functions, variables, block-owned registers, and constants. This also includes definitions for all public functions and for constants declared ‘extern’ in the .h file.
- code architecture can be implemented to include an infinite loop, event handlers, and interrupt handlers.
- the kernel code which implements the architecture can be contained in the main.c and global.c/h files. This includes event handling code and various other general utilities that are used by other code but are not hardware-specific.
- a Power On Self Test can be implemented in accordance with embodiments of the present invention and may possess special capabilities due to a UNIX executable aspect of the compiled code that would not be available if this were truly loadable firmware.
- a number of data structures can be used in the POST, including a Register Block Space Table, which comprises an Array storing the size of the address space for each register block. Such a table can be utilized to test the reserved spaces for unspecified storage elements. Registered addresses can be also utilized in the POST as a list of number defined literals utilized in other tables.
- a “Go Mask Table” can also be utilized with the post, which comprises an array that contains an entry for every register that contains a GO bit.
- Each entry will contain the address of the register and a mask with zeroed bits where GO bits exist. Go bits are specified in the hardware specifications by the letters “Go” at the end of the bit name. Additional data structures include a Power-On Reset Value Table (POR VTable) and a “Write Bits table.”
- POR VTable can be implemented as an array organized by register within register block. Each entry contains the register's address, the POR specification for the register, and a mask value that contains zeroed bits wherever the hardware specification indicates that the POR value is unknown.
- a “Write Bits Table” can be configured as an array organized by register within register block. Each entry can contain the register's address and a mask value that contains zeroed bits wherever the hardware specification indicates that a non-writeable bit exists. A writeable bit can be defined as a bit that reads back what was written.
- An “On Chip RAM Information Table” can also be utilized with the POST in the form of an array for storing a word size (in 32-bit unsigned long values), number of words, and a mask for each entry in each on-chip RAM.
- the mask can include two unsigned long values with zeroed bits where no storage exists.
- Such a format can be utilized to determine the actual width of an entry in the RAM when the RAM has a non-DWORD word width.
- An internal buffer for example, can be 34 bits wide, and is therefore listed as possessing 2 32-bit entries per word.
- the MS mask can be set, however, to 0x00000003 to indicate that only two bits in the MS 32-bit entry are real.
- the top level POST program simply calls the CPU initialization program and then calls for a POST.
- the POST can verify the functionality of the hardware in the following order: 1. Test Power-On Reset (POR) values of registers; 2. Test Write/Read capabilities of registers; 3. Test Interrupts; 4. Test On Chip Memory; 5. Test Off-Chip Memory; and 6. Run any automated tests existing in the hardware design (i.e., referred to here as an RTEST).
- POR Test Power-On Reset
- the “GoBitTable” can be utilized.
- the POST will also test reserved register locations. Ideally these would read back zero and would not return what is written. For each address location in each register block, the following algorithm can be followed:
- An interrupt verification function can be implemented in accordance with an embodiment, which masks and clears all interrupts and sets the interrupt polarity to high.
- the interrupt verification function can then register an interrupt handler (IntISR( )) function with the compiler, call a function (PostTriggerlnt( )) to force each interrupt, and then reregister the “real” ISRs for actual firmware operation.
- the PostTriggerlnt( ) function may cause an interrupt by setting up a “watch dog” timer interrupt to trigger an interrupt signal.
- the IntISR( ) function sets a flag to show which interrupt occurred and then masks and clears the processor's interrupt logic.
- An On-Chip Memory Verification can be implemented as a function that can test the on-chip memories specified in the hardware specification.
- the On-Chip Memory Verification function can cycle through each on-chip memory and performs the following several tests, including writing incrementing or decrementing byte values to every location, then read back and verify. Other tests include, for example, writing 0xAAAAAAAA to every location, and then reading back and verifying. Another test can include writing 0x55555555 to every location, then read back and verify. In the first three tests the memory location directly below and above the indicated memory block space is also written and read to verify that it does NOT contain valid memory.
- An on-chip memory verification function can be utilized to write or read a single on-chip memory location. Such a function when reading compares the value with the expected value (i.e., a parameter). This returns a FAIL message or command if the address is valid. The read value does not compare, however, if the address is invalid. The case, the data is compared.
- the expected value i.e., a parameter
- the Off-Chip Memory Verification function can perform a particular number of operations. First Off-Chip Memory locations in the window can be written, as specified by auto-generated write test table entries. Second, the Off-Chip Memory values can be read and compared using the configurations designed according to step one above. Crosstalk in the off-chip data lines can be checked with an operation that performs a write of traveling 1's to the off-chip memory starting at location zero. Finally, the off-chip memory values can be read and compared to the off-chip memory values written via step 3 listed above.
- Hardware auto-test (RTEST) logic can be implemented as hardware designed specifically to test a hardware block automatically.
- the RTEST portion of the POST simply sets up the RTEST logic and then starts the hardware test.
- the POST code handles any interrupts generated by the RTEST logic. Any of the aforementioned tests may generate POST warnings or failures. Warnings will not stop the POST, but can cause the POST to return a nonzero value. Errors can halt the POST function and cause the firmware to trap.
- embodiments of the present invention are directed toward methods and systems for verifying a hardware specification of integrated circuit (IC) designs.
- Embodiments also include methods and systems for automatically verifying a hardware design based on a hardware specification document.
- a plurality of predefined elements can be designed within a hardware specification document, such that the hardware specification document provides a hardware design for a hardware device.
- the predefined elements can be stored within a database of hardware components, wherein each predefined element of the predefined elements is associated with a hardware component of the hardware device. Physical components of the hardware device can be compared with the predefined elements maintained within the database of hardware components upon an initial power-up of the hardware device in order to verify that the hardware device functions according to the hardware specification document.
- An RTL auto-generation utility or module generally auto-generates define statements utilized by the RTL code to decode and configure the hardware memories and registers.
- the software auto-generation utility or module auto-generates the same define statements utilized by the software code.
- the POST software auto-generation utility or module as indicated earlier, can then auto-generate table-based tests that can verify the accessibility and correctness of the on-chip memories, off-chip memories, and registers as specified in the IC specification document.
- modules can be typically implemented as a collection of routines and data structures that performs particular tasks or implements a particular abstract data type. Modules can be composed of two parts. First, a software module may list the constants, data types, variable, routines and the like that can be accessed by other modules or routines. Second, a software module can be configured as an implementation, which can be private (i.e., accessible perhaps only to the module), and that contains the source code that actually implements the routines or subroutines upon which the module is based. Thus, for example, the term module, as utilized herein can refer to a software module(s) or implementations thereof. Such modules can be utilized separately or together to form a program product that can be implemented through signal-bearing media, including transmission media and recordable media.
- Suitable modules which can be implemented in accordance with embodiments of the present invention include a comparing module, a testing module, an RTL auto-generation module, a software auto-generation module, and the like.
- the comparing module can automatically compare physical components of the hardware device with the predefined elements maintained within the database of hardware components upon an initial power-up of the hardware device, in order to verify that the hardware device functions according to the hardware specification document.
- the testing module can automatically force the hardware device to fail if the hardware device does not comply with the hardware specification document, in response to automatically comparing physical components of the hardware device with the predefined elements maintained within the database of the hardware components upon an initial power-up of the hardware device.
- the RTL auto-generation module can generate define statements utilized by an RTL code to decode and configure at least one hardware memory and at least one register thereof.
- the software auto-generation module can auto-generate the same set of define statements utilized by the software code thereof.
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Test And Diagnosis Of Digital Computers (AREA)
Abstract
Description
TABLE 1 |
Hardware Driver Files |
Hardware Block | Code File | Header File |
Ouray Register Definitions | <none> | OurayNN_reg.h |
Saspen Protocol Engine Register | <none> | Saspen_NN_reg.h |
Definitions | ||
Buffer Controller | bc.c | bc.h |
Microprocessor Interface | mpu.c | mpu.h |
RAM Test | rtest.c | rtest.h |
Saspen Sub-Blocks | ||
Saspen Command Buffer | cbuf.c | cbuf.h |
Saspen Data Buffer | dbuf.c | dbuf.h |
Saspen Frame Buffer | fbuf.c | fbuf.h |
Saspen Global | saspen.c | saspen.h |
Saspen Header Buffer | hbuf.c | hbuf.h |
Saspen Receive Data Path | dpt.c | dpt.h |
Saspen RX WCS | rxwcs.c | rxwcs.h |
Saspen Transmit Buffer | txb.c | txb.h |
Saspen Transmit Data Path | txdp.c | txdp.h |
Saspen Transmit Request | txreq.c | txreq.h |
Saspen TX WCS | txwcs.c | txwcs.h |
Host Sub-Blocks | ||
Command Automation Processor | cap.c | cap.h |
Command FIFO | cfifo.c | cfifo.h |
Context Cache | cc.c | cc.h |
Disk Thread Retrieval Channel | dtrc.c | dtrc.h |
Free Pointer Manager | fpm.c | fpm.h |
Host Global | host.c | host.h |
Host Thread Retrieval Channels | htrc.c | htrc.h |
Pending Write Table | pwt.c | pwt.h |
Prefetch Engine | peng.c | peng.h |
Read Context Manager | rcm.c | rcm.h |
Read DMA | rdma.c | rdma.h |
Receive Frame Router | rxfr.c | rxfr.h |
Status Context Manager | scm.c | scm.h |
Status Thread Retrieval Channel | strc.c | strc.h |
Tag Manager | tag.c | tag.h |
Transfer Control FIFO | tcfifo.c | tcfifo.h |
Write Context Manager | wcm.c | wcm.h |
Write DMA | wdma.c | wdma.h |
Disk Formatter Sub-Blocks | ||
Data Channel | dchan.c | dchan.h |
Data Path | dp.c | dp.h |
Disk Formatter Global | df.c | df.h |
Disk Formatter Writeable Control Store | wcs.c | wcs.h |
Error Correction Engine | ecc.c | ecc.h |
Release Control | rel.c | rel.h |
RG/WG Sequencer | rgwg.c | rgwg.h |
Sector Generation | sec.c | sec.h |
Servo Positioning Table | spt.c | spt.h |
Skip Mask Table | smt.c | smt.h |
Start Of Sector | sos.c | sos.h |
Transfer Control Table | tct.c | tct.h |
-
- 1. If the location exists in the Avoid table then skip it and continue to the next location.
- 2. Set the Go mask to 0xFFFFFFFF.
- 3. If the location contains a register then get the WriteBits mask from the Write Bits Table.
- 4. Else set the Write Bits mask to 0xFFFFFFFF.
- 5. If the location is in the Go Mask table then get the Go mask value.
- 6. If the Write Bits mask is zero then continue to the next location.
- 7. Read the register's current value.
- 8. XOR the read value with the Write Bits mask; AND the results with the Go mask.
- 9. Write to the register.
- 10. Read the register, AND this value with the Write Bits and Go mask.
- 11. Check the masked read value with the masked write value.
- 12. If the values do not match then FAIL to log file.
- 13. If the read value is non-zero and no register exists then FAIL to log file.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/624,347 US7096440B2 (en) | 2003-07-22 | 2003-07-22 | Methods and systems for automatic verification of specification document to hardware design |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/624,347 US7096440B2 (en) | 2003-07-22 | 2003-07-22 | Methods and systems for automatic verification of specification document to hardware design |
Publications (2)
Publication Number | Publication Date |
---|---|
US20050022058A1 US20050022058A1 (en) | 2005-01-27 |
US7096440B2 true US7096440B2 (en) | 2006-08-22 |
Family
ID=34079988
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/624,347 Expired - Lifetime US7096440B2 (en) | 2003-07-22 | 2003-07-22 | Methods and systems for automatic verification of specification document to hardware design |
Country Status (1)
Country | Link |
---|---|
US (1) | US7096440B2 (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080109772A1 (en) * | 2006-10-24 | 2008-05-08 | Pokorny William F | Method and system of introducing hierarchy into design rule checking test cases and rotation of test case data |
US8522176B2 (en) * | 2010-05-11 | 2013-08-27 | Synopsys, Inc. | Method of recording and replaying call frames for the testbench |
US8589841B2 (en) | 2012-04-05 | 2013-11-19 | International Business Machines Corporation | Automatic parity checking identification |
US20170017506A1 (en) * | 2008-09-04 | 2017-01-19 | Synopsys, Inc. | Software and Hardware Emulation System |
US9569582B2 (en) | 2014-01-03 | 2017-02-14 | International Business Machines Corporation | Template matching for resilience and security characteristics of sub-component chip designs |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP4251964B2 (en) * | 2003-11-10 | 2009-04-08 | 富士通マイクロエレクトロニクス株式会社 | Verification device, verification method, and program |
US8230263B2 (en) * | 2007-09-19 | 2012-07-24 | Lsi Corporation | Automated specification based functional test generation infrastructure |
JP5163308B2 (en) * | 2008-06-23 | 2013-03-13 | 富士通セミコンダクター株式会社 | IP model generation device, IP model generation method, and IP model generation program |
US9330419B2 (en) | 2012-05-01 | 2016-05-03 | Oracle International Corporation | Social network system with social objects |
CN116382992B (en) * | 2023-05-16 | 2023-09-19 | 上海孤波科技有限公司 | Hardware testing method and device, electronic equipment and storage medium |
CN117150998B (en) * | 2023-10-31 | 2024-01-19 | 上海合见工业软件集团有限公司 | Hardware module equivalence verification system |
Citations (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5452227A (en) * | 1991-11-13 | 1995-09-19 | Westinghouse Elec. Corp. | Method and apparatus for converting a programmable logic device designed into a selectable target gate array design |
US5600579A (en) | 1994-07-08 | 1997-02-04 | Apple Computer, Inc. | Hardware simulation and design verification system and method |
US5995736A (en) * | 1997-07-24 | 1999-11-30 | Ati Technologies, Inc. | Method and system for automatically modelling registers for integrated circuit design |
US6052524A (en) * | 1998-05-14 | 2000-04-18 | Software Development Systems, Inc. | System and method for simulation of integrated hardware and software components |
US6249899B1 (en) * | 1999-03-23 | 2001-06-19 | Hewlett Packard Company | System and method for detecting pass FETs |
US6321365B1 (en) * | 1999-01-26 | 2001-11-20 | Hewlett-Packard Company | System and method for detecting storage nodes that are susceptible to charge sharing |
US6360308B1 (en) | 1998-09-30 | 2002-03-19 | Lsi Logic Corporation | Buffer controller |
US6405347B1 (en) * | 1999-06-30 | 2002-06-11 | Hewlett-Packard Company | Method and apparatus for determining the maximum permitted and minimum required width of a feedback FET on a precharge node |
US6430652B1 (en) | 1997-12-30 | 2002-08-06 | Lsi Logic Corporation | Method and apparatus for streaming data in a data processing system |
US6539523B1 (en) * | 2000-05-08 | 2003-03-25 | Real Intent, Inc. | Automatic formulation of design verification checks based upon a language representation of a hardware design to verify the intended behavior of the hardware design |
US6571375B1 (en) | 2000-05-08 | 2003-05-27 | Real Intent, Inc. | Determining dependency relationships among design verification checks |
US20040030876A1 (en) * | 2002-08-07 | 2004-02-12 | Qureshi Shiraz A. | System and method for using a firmware interface table to dynamically load an ACPI SSDT |
US6718522B1 (en) * | 2000-08-15 | 2004-04-06 | Hewlett-Packard Development Company, L.P. | Electrical rules checker system and method using tri-state logic for electrical rule checks |
US20040216077A1 (en) * | 2003-04-28 | 2004-10-28 | International Business Machines Corp. | Method, system and program product for specifying and using a dial having a default value to configure a digital system described by a hardware description language (HDL) model |
US6990643B1 (en) * | 1999-05-13 | 2006-01-24 | Hewlett-Packard Development Company, L.P. | Method and apparatus for determining whether an element in an integrated circuit is a feedback element |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2565005B2 (en) * | 1991-03-08 | 1996-12-18 | 富士通株式会社 | Heterogeneous crystal synthesizer |
-
2003
- 2003-07-22 US US10/624,347 patent/US7096440B2/en not_active Expired - Lifetime
Patent Citations (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5452227A (en) * | 1991-11-13 | 1995-09-19 | Westinghouse Elec. Corp. | Method and apparatus for converting a programmable logic device designed into a selectable target gate array design |
US5600579A (en) | 1994-07-08 | 1997-02-04 | Apple Computer, Inc. | Hardware simulation and design verification system and method |
US5995736A (en) * | 1997-07-24 | 1999-11-30 | Ati Technologies, Inc. | Method and system for automatically modelling registers for integrated circuit design |
US6430652B1 (en) | 1997-12-30 | 2002-08-06 | Lsi Logic Corporation | Method and apparatus for streaming data in a data processing system |
US6052524A (en) * | 1998-05-14 | 2000-04-18 | Software Development Systems, Inc. | System and method for simulation of integrated hardware and software components |
US6360308B1 (en) | 1998-09-30 | 2002-03-19 | Lsi Logic Corporation | Buffer controller |
US6321365B1 (en) * | 1999-01-26 | 2001-11-20 | Hewlett-Packard Company | System and method for detecting storage nodes that are susceptible to charge sharing |
US6249899B1 (en) * | 1999-03-23 | 2001-06-19 | Hewlett Packard Company | System and method for detecting pass FETs |
US6990643B1 (en) * | 1999-05-13 | 2006-01-24 | Hewlett-Packard Development Company, L.P. | Method and apparatus for determining whether an element in an integrated circuit is a feedback element |
US6405347B1 (en) * | 1999-06-30 | 2002-06-11 | Hewlett-Packard Company | Method and apparatus for determining the maximum permitted and minimum required width of a feedback FET on a precharge node |
US6539523B1 (en) * | 2000-05-08 | 2003-03-25 | Real Intent, Inc. | Automatic formulation of design verification checks based upon a language representation of a hardware design to verify the intended behavior of the hardware design |
US6571375B1 (en) | 2000-05-08 | 2003-05-27 | Real Intent, Inc. | Determining dependency relationships among design verification checks |
US6718522B1 (en) * | 2000-08-15 | 2004-04-06 | Hewlett-Packard Development Company, L.P. | Electrical rules checker system and method using tri-state logic for electrical rule checks |
US20040030876A1 (en) * | 2002-08-07 | 2004-02-12 | Qureshi Shiraz A. | System and method for using a firmware interface table to dynamically load an ACPI SSDT |
US20040216077A1 (en) * | 2003-04-28 | 2004-10-28 | International Business Machines Corp. | Method, system and program product for specifying and using a dial having a default value to configure a digital system described by a hardware description language (HDL) model |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080109772A1 (en) * | 2006-10-24 | 2008-05-08 | Pokorny William F | Method and system of introducing hierarchy into design rule checking test cases and rotation of test case data |
US7823103B2 (en) * | 2006-10-24 | 2010-10-26 | International Business Machines Corporation | Method and system of introducing hierarchy into design rule checking test cases and rotation of test case data |
US20170017506A1 (en) * | 2008-09-04 | 2017-01-19 | Synopsys, Inc. | Software and Hardware Emulation System |
US10713069B2 (en) * | 2008-09-04 | 2020-07-14 | Synopsys, Inc. | Software and hardware emulation system |
US8522176B2 (en) * | 2010-05-11 | 2013-08-27 | Synopsys, Inc. | Method of recording and replaying call frames for the testbench |
US8924912B2 (en) | 2010-05-11 | 2014-12-30 | Synopsys, Inc. | Method of recording and replaying call frames for a test bench |
US8589841B2 (en) | 2012-04-05 | 2013-11-19 | International Business Machines Corporation | Automatic parity checking identification |
US9569582B2 (en) | 2014-01-03 | 2017-02-14 | International Business Machines Corporation | Template matching for resilience and security characteristics of sub-component chip designs |
Also Published As
Publication number | Publication date |
---|---|
US20050022058A1 (en) | 2005-01-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN110603528B (en) | Debugging system and method | |
US6678625B1 (en) | Method and apparatus for a multipurpose configurable bus independent simulation bus functional model | |
US7962869B2 (en) | Method and system for debug and test using replicated logic | |
KR100434240B1 (en) | Apparatus and method for in-circuit emulation using high-level programming language | |
US10255400B1 (en) | Debugging system and method | |
US20170115969A1 (en) | System and method for automatically generating device drivers for run time environments | |
US7096440B2 (en) | Methods and systems for automatic verification of specification document to hardware design | |
CN112417798B (en) | Time sequence testing method and device, electronic equipment and storage medium | |
US6917998B1 (en) | Reusable complex multi-bus system hardware prototype system | |
EP1913410B1 (en) | Method and system for debug and test using replicated logic | |
US7827517B1 (en) | Automated register definition, builder and integration framework | |
JP2002358340A (en) | Circuit for logical emulation, logical board with the circuit, logical emulator, and communication method in logical emulation | |
US20020108094A1 (en) | System and method for designing integrated circuits | |
CN100442293C (en) | Method for combination of original files of hardware design language and checking data files | |
CN117195783A (en) | Method for verifying chip design | |
US7584456B1 (en) | Method and apparatus for debugging embedded systems having read only memory | |
US6842883B2 (en) | Application of co-verification tools to the testing of IC designs | |
CN115017845A (en) | Bus driving type chip simulation excitation model for IP unit level verification | |
US20030237023A1 (en) | Associated apparatus and method for supporting development of semiconductor device | |
US12055588B2 (en) | Testbenches for electronic systems with automatic insertion of verification features | |
US7130784B2 (en) | Logic simulation | |
Bombieri et al. | Correct-by-construction generation of device drivers based on RTL testbenches | |
CN111338761A (en) | 51 single-chip microcomputer virtual interrupt controller and implementation method | |
CN110162438B (en) | Simulation debugging device and simulation debugging method | |
US11403449B1 (en) | Systems and methods for configurable switches for verification IP |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: LSI LOGIC CORPORATION, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FECHSER, DAVID A.;REEL/FRAME:014320/0312 Effective date: 20030715 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
AS | Assignment |
Owner name: DEUTSCHE BANK AG NEW YORK BRANCH, AS COLLATERAL AG Free format text: PATENT SECURITY AGREEMENT;ASSIGNORS:LSI CORPORATION;AGERE SYSTEMS LLC;REEL/FRAME:032856/0031 Effective date: 20140506 |
|
AS | Assignment |
Owner name: LSI CORPORATION, CALIFORNIA Free format text: CHANGE OF NAME;ASSIGNOR:LSI LOGIC CORPORATION;REEL/FRAME:033102/0270 Effective date: 20070406 |
|
AS | Assignment |
Owner name: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:LSI CORPORATION;REEL/FRAME:035390/0388 Effective date: 20140814 |
|
AS | Assignment |
Owner name: AGERE SYSTEMS LLC, PENNSYLVANIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS (RELEASES RF 032856-0031);ASSIGNOR:DEUTSCHE BANK AG NEW YORK BRANCH, AS COLLATERAL AGENT;REEL/FRAME:037684/0039 Effective date: 20160201 Owner name: LSI CORPORATION, CALIFORNIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS (RELEASES RF 032856-0031);ASSIGNOR:DEUTSCHE BANK AG NEW YORK BRANCH, AS COLLATERAL AGENT;REEL/FRAME:037684/0039 Effective date: 20160201 |
|
AS | Assignment |
Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH CAROLINA Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.;REEL/FRAME:037808/0001 Effective date: 20160201 Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.;REEL/FRAME:037808/0001 Effective date: 20160201 |
|
AS | Assignment |
Owner name: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD., SINGAPORE Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:041710/0001 Effective date: 20170119 Owner name: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:041710/0001 Effective date: 20170119 |
|
AS | Assignment |
Owner name: BELL SEMICONDUCTOR, LLC, ILLINOIS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.;BROADCOM CORPORATION;REEL/FRAME:044887/0109 Effective date: 20171208 |
|
AS | Assignment |
Owner name: CORTLAND CAPITAL MARKET SERVICES LLC, AS COLLATERA Free format text: SECURITY INTEREST;ASSIGNORS:HILCO PATENT ACQUISITION 56, LLC;BELL SEMICONDUCTOR, LLC;BELL NORTHERN RESEARCH, LLC;REEL/FRAME:045216/0020 Effective date: 20180124 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553) Year of fee payment: 12 |
|
AS | Assignment |
Owner name: BELL NORTHERN RESEARCH, LLC, ILLINOIS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CORTLAND CAPITAL MARKET SERVICES LLC;REEL/FRAME:059720/0223 Effective date: 20220401 Owner name: BELL SEMICONDUCTOR, LLC, ILLINOIS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CORTLAND CAPITAL MARKET SERVICES LLC;REEL/FRAME:059720/0223 Effective date: 20220401 Owner name: HILCO PATENT ACQUISITION 56, LLC, ILLINOIS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CORTLAND CAPITAL MARKET SERVICES LLC;REEL/FRAME:059720/0223 Effective date: 20220401 |