Programmatic use of software debugging to redirect hardware related operations to a hardware simulator

• US 6,188,975 B1
• Filed: 03/31/1998
• Issued: 02/13/2001
• Est. Priority Date: 03/31/1998
• Status: Expired due to Term

• Current Assignee: Synopsys Incorporated
• Original Assignee: Synopsys Incorporated
• Inventors: Gay, Donald L.
• Primary Examiner(s): Teska, Kevin J.
• Assistant Examiner(s): FREJD, RUSSELL WARREN
• Application Number:
  US09/053,327
• Time in Patent Office: 1,050 Days
• Field of Search: 716/5, 716/18, 703/13, 703/14, 703/17, 703/22, 703/23, 703/27, 703/28, 703/26
• US Class Current: 703/22
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software
• CPC Class Codes: G06F 30/33 Design verification, e.g. functional simulation or model checking

Abstract

The present invention is a method that uses breakpoints in a debugging program to signify to a hardware software co-verification tool when to redirect hardware calls to a hardware simulator. The method includes executing a line of software code within a software component, determining whether the line of software code requires interaction with a hardware device, associating the line of software code with an interface module if the line of software code requires interaction with a hardware device, simulating the hardware device with a hardware model running under simulation, using the interface module to request a hardware operation from the hardware model when the line of software code requires a hardware operation; and providing data generated by the hardware model running under simulation in response to the request.

Claims

1. A method of performing hardware software co-verification, comprising the steps of:

obtaining a software component having a plurality of lines of software code, and having at least one of said lines of software code capable of making a hardware device interaction when executed;

executing said line of software code within said software component;

flagging said line with a breakpoint, if said line requires a hardware device interaction, wherein said breakpoint for indicating said line requires said hardware device interaction when executed;

associating said line with an interface module by a plug-in, if said line requires said hardware device interaction;

simulating said hardware device with a hardware model running under simulation;

using said interface module to make a request for a hardware operation from said hardware model running under simulation when said line requires said hardware device interaction; and

providing data generated by said hardware model running under simulation in response to said request.

2. The method in claim 1, wherein said data generated by said hardware model in said step of providing is received by a debugging program for use by said line of software code in said step of executing.

3. The method in claim 1, further including a step of executing a line of software code subsequent to said line of software code executed in said step of executing according to an execution flow corresponding to said software component.

4. The method in claim 1, wherein said hardware operation includes a read operation.

5. The method in claim 1, wherein said hardware operation includes a write operation.

6. The method in claim 1, further including a step of providing a debugging program to perform said step of executing said line of software code within said software component.

7. The method in claim 1, wherein said software component includes an applications software program.

8. The method in claim 1, wherein said software component includes lines of software code that comprises a hardware driver.

9. The method in claim 1, further including a step of providing a plug-in module to perform said step of determining whether said line of software code requires interaction with a hardware device.

10. The method in claim 1, further including a step of providing a plug-in module for associating said line of software code with an interface module if said line of software code requires interaction with a hardware device.

11. The method in claim 1, further including a step of providing a hardware simulator for simulating said hardware device using said hardware model.

12. The method in claim 1, further including a step of providing a debugging program to perform said step of executing said next line of software code according to an execution flow corresponding to said software component.

13. The method in claim 1, further including a step of responding to an interrupt signal generated by said hardware model, said step of responding including a step of redirecting said interrupt signal to a simulated target operating system.

14. A method of performing hardware software co-verification, comprising the steps of:

obtaining a software component having a plurality of lines of software code, and having at least one of said lines of software code capable of making a hardware device interaction when executed;

executing said line of software code within said software component;

flagging said line with a breakpoint, if said line requires a hardware device interaction, wherein said breakpoint for indicating said line requires said hardware device interaction when executed;

associating said line with an interface module by a plug-in, if said line requires said hardware device interaction;

simulating said hardware device with a hardware model running under simulation;

using said interface module to make a request for a hardware operation from said hardware model running under simulation when said line requires said hardware device interaction; and

providing data generated by said hardware model running under simulation in response to said request; and

executing a next line of software code according to an execution flow corresponding to said software component.

15. The method in claim 14, wherein said hardware operation includes a read operation.

16. The method in claim 14, wherein said hardware operation includes a write operation.

17. The method in claim 14, wherein said software component includes an applications software program.

18. The method in claim 14, wherein said software component includes lines of software code that comprises a hardware driver.

19. The method in claim 14, further including a step of providing a plug-in module to perform said step of determining whether said line of software code requires interaction with a hardware device.

20. The method in claim 14, further including a step of providing a plug-in module for associating said line of software code with an interface module if said line of software code requires interaction with a hardware device.

21. The method in claim 14, further including a step of providing a hardware simulator for simulating said hardware device using said hardware model.

22. The method in claim 14, further including a step of responding to an interrupt signal generated by said hardware model, said step of responding including a step of redirecting said interrupt signal to a simulated target operating system.

23. A method for determining whether a software component and a hardware device are properly designed to interact with each other, comprising the steps of:

preparing a hardware software co-verification system for operation by obtaining a software component having a plurality of lines of software code, and flagging at least one line of software code within said software component, said line of software code capable of making a hardware call when executed;

executing said software component;

sensing by a debugging program during said step of executing whether said line of software code within said software component has been flagged;

associating by a plug-in an interface module and a hardware model that are suitable for servicing said hardware call and redirecting said hardware call to said interface module for servicing, if said step of sensing results in identifying said line of software code previously flagged, wherein said line of software code requiring said hardware call;

using said interface module to receive and modify said hardware call into a compatible device specific format with said hardware model, and to provide necessary signals to communicate said hardware call to said hardware model according to said device specific format, said hardware model responding to said hardware call by simulating signals responsive to said hardware call; and

returning execution to the next line of software code awaiting execution within said hardware model running under simulation.

24. The method in claim 23, wherein said step of executing includes using a debugging program to execute said software component one line of software code at a time according to an execution flow dictated said software component.

25. The method in claim 23, wherein said step of flagging a line of software code is performed manually.

26. The method in claim 23, wherein said step of flagging a line of software code is performed through program control.

27. The method in claim 23, further including a step of responding to an interrupt signal generated by said hardware model, said step of responding including a step of redirecting said interrupt signal to a simulated target operating system.