Legal claims defining the scope of protection, as filed with the USPTO.
1. A debugging device comprising: a first communication interface that couples the debugging device to a host computer; a second communication interface that couples the debugging device to a target device; and a script interpreter executing on the debugging device, the script interpreter receiving a script from the host computer via the first communication interface, the script comprising a non-compiled string of text characters, the script defining a loop that involves performing a plurality of reads from the target device, the script interpreter interpreting the script and causing the debugging device to communicate with the target device over the second communication interface such that the plurality of reads is carried out.
2. The debugging device of claim 1 , wherein the script includes a loop statement, and wherein the loop statement includes an expression and at least one statement.
3. The debugging device of claim 2 , wherein said at least one statement is a read statement.
4. The debugging device of claim 3 , wherein the expression indicates a number, the number specifying a number of times that a read defined by said read statement is to be performed.
5. The debugging device of claim 2 , wherein the script includes a second statement in addition to said at least one statement.
6. The debugging device of claim 1 , wherein the performing of the plurality of reads results in an amount of data being retrieved from the target device, and wherein the script includes a statement that causes the amount of data to be sent from the debugging device to the host computer.
7. The debugging device of claim 1 , wherein the script is not compiled on the host computer, and wherein the script is not compiled on the debugging device.
8. The debugging device of claim 1 , wherein there is no operating system stored on the debugging device.
9. The debugging device of claim 1 , wherein the target device comprises an on-chip debugging circuit, and wherein the second communication interface couples the debugging device to the on-chip debugging circuit of the target device.
10. The debugging device of claim 1 , wherein the script is communicated from the host computer to the debugging device as a payload of a network packet.
11. The debugging device of claim 1 , wherein the script comprises ASCII text characters.
12. A method, comprising: receiving a script from a host computer onto a hardware debugging device, the script comprising a non-compiled string of text characters, the script defining a debugging action, the debugging action requiring a plurality of sub-actions be performed; interpreting the script; generating a plurality of microcommands from the script; and sending the plurality of microcommands to a target device, the microcommands causing the target device to perform the plurality of sub-actions.
13. The method of claim 12 , wherein the debugging action includes a read of a block of memory locations on the target device, and wherein one of the plurality of sub-actions is a read of one of the memory locations.
14. The method of claim 13 , wherein the target device includes a processor, the processor having on-chip debugging hardware, and wherein the microcommands are executed by the on-chip hardware.
15. The method of claim 14 , wherein one of the microcommands causes an operation selected from a group consisting of: stop the processor, single-step the processor, read and write to various internal registers within the processor, read and write to a data memory, set breakpoints in code executed by the processor, stuff instructions into the processor, read and write watchpoints, read status registers, and exercise and monitor the processor.
16. The method of claim 13 , wherein the target device includes a JTAG interface, and wherein the microcommands are received by the JTAG interface.
17. The method of claim 12 , wherein said interpreting of the script occurs on the hardware debugging device, and wherein the script includes a statement that causes data to be sent from the hardware debugging device to the host computer.
18. The method of claim 12 , wherein the script includes a loop statement, an arithmetic operator, and a variable.
19. The method of claim 12 , wherein the script includes a sleep statement.
20. The method of claim 12 , wherein the script includes a break statement.
21. The method of claim 12 , wherein the script includes a boolean operator.
22. The method of claim 12 , wherein the script comprises ASCII text characters.
23. A debugging device comprising: a first communication interface that couples the debugging device to a host computer; a second communication interface that couples the debugging device to a target device; and means for receiving a script from the host computer, the script defining a debugging action to be taken with respect to the target device, the script comprising a non-compiled string of text characters, the debugging action requiring a plurality of sub-actions to occur, the means also being for interpreting the script and generating therefrom a plurality of microcommands that are sent to the target device.
24. The debugging device of claim 23 , wherein the microcommands are performed by the target device such that the sub-actions occur.
25. The debugging device of claim 23 , wherein one of the sub-actions involves setting a breakpoint.
26. The debugging device of claim 23 , wherein the script includes a loop statement, an arithmetic operator, and a designation of a register internal to a processor of the target device.
27. The debugging device of claim 23 , wherein the script comprises ASCII text characters.
28. A debugging device comprising: a first communication interface that couples the debugging device to a host computer; a second communication interface that couples the debugging device to a target device; and a script interpreter executing on the debugging device, the script interpreter receiving a script from the host computer via the first communication interface, the script comprising a non-compiled string of text characters, the script interpreter interpreting the script and causing the debugging device to communicate with the target device over the second communication interface such that a debugging action is performed.
29. The debugging device of claim 28 , wherein there is no operating system stored on the debugging device.
30. The debugging device of claim 28 , wherein the script includes a sleep statement.
31. The debugging device of claim 28 , wherein the script includes a loop statement, and wherein the loop statement includes an expression and at least one statement.
32. The debugging device of claim 31 , wherein said at least one statement is a read statement.
33. The debugging device of claim 32 , wherein the expression indicates a number, the number specifying a number of times that a read defined by said read statement is to be performed.
34. The debugging device of claim 28 , wherein the script comprises ASCII text characters.
35. The debugging device of claim 28 , wherein the script comprises NULL terminated ASCII text.
Unknown
November 13, 2007
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.