Hardware and software debug using data dependency tracing
AssigneeNXP USA, Inc.
InventorsSandeep Jain, Ashish Mathur
Life of this patent
Estimating the term…
Loading patent…
AssigneeNXP USA, Inc.
InventorsSandeep Jain, Ashish Mathur
Estimating the term…
A system and method to record and trace data exchanges between cooperating hardware unit operations and software unit operations, providing an efficient mechanism to trace back to a root cause point from an observed failure point in a series of executed instructions performed within a data processing system. A data debug memory records information pertaining to each system memory access performed by instructions executed by the hardware and software units into separate memory information blocks. Linked relationships are created between certain ones of the memory information blocks to represent data dependencies that occurred between the instructions. These linked relationships may then be utilized to generate lists that map the various data dependencies between the executed instructions.
A method for operating debug circuitry to facilitate debugging of operations performed by a hardware unit and a software unit in a data processing system that includes a system memory, the method comprising:
A data processing system comprising:
A method for facilitating debugging of operations performed by a hardware unit and a software unit that are included in a data processing system that includes a system memory, wherein a first operation performed by the hardware unit comprises a first plurality of instructions that read data from the system memory, perform a first computation, and write a result of the first computation to the system memory, wherein a second operation performed by the software unit comprises a second plurality of instructions that read data from the system memory, perform a second computation, and write a result of the second computation to the system memory, the method comprising:
The method as recited in 17, further comprising generating a producer list for a specific instruction, wherein the producer list includes an identification of each system memory access that had an effect on data pertaining to the specific instruction, wherein the generating of the producer list further comprises utilizing the block sequential, memory read list, and producer linked list fields to identify each system memory access that had the effect on the data pertaining to the specific instruction.
The method as recited in 17, further comprising generating a consumer list for a specific instruction, wherein the consumer list includes an identification of each system memory access that had an effect on data pertaining to the specific instruction, wherein the generating of the consumer list further comprises utilizing the block sequential, memory write list, and consumer linked list fields to identify each system memory access that had the effect on the data pertaining to the specific instruction.
Dependencies are inferred from the claim text.