DATA PROCESSOR WITH A DEBUG CIRCUIT

Abstract: A data processor has a debug circuit arranged to monitor whether operand data used for execution of a program meets a debug exception condition. The debug exception condition tests a two or more of multi-bit subfields of a vector operand independently. Debug action is taken if one or more of the multi-bit subfields meet the corresponding conditions.

Description: DATA PROCESSOR WITH A DEBUG CIRCUIT The invention relates to a data processing circuit with a debug feature and a method of using such a circuit. It is known to provide a data processor with a debug circuit that monitors data values that are output to memory. The debug circuit facilitates the analysis of the execution properties of programs at specific time points when specific conditions occur in the processor. A known debug circuit causes an interruption of normal program execution when a data value equal to a specified value is output to memory. It is also known to specify a bit-mask in addition to the value, the interruption occurring when the data value is equal to the specified value at the bit positions that are enabled by the bit-mask . It is also known to provide a data processor, such as a digital signal processor, with a vector processing capability. In this case, the data processor is able to process several arithmetic numbers in parallel in response to a vector instruction. For example, a vector ADD instruction specifies two input operands. These operands are for example 64 bits long, the data processor handling these operands as containing four fields of 16 bit, each representing a 16 bit number. In response to the vector ADD instruction the data processor adds pairs of number from corresponding fields in the operands of the vector ADD instruction, without carry between different fields. If applied to a vector processor the known debug circuit would make it possible to cause a debug interrupt when all fields of an operand have specified values, or when a mask-enabled field or combination of mask-enabled fields all have specified values. Amongst others, it is an object of the invention to provide for a data processor with an improved capability of taking debug action. It is a further object of the invention to provide a data processor that has vector instructions with an improved capability of taking debug action. The data processor according to the invention is set forth in Claim 1. In the data processor according to the invention, the debug circuit can be programmed to monitor data values in a more refined way than with a mask plus value. It is possible to take debug action whether one or more but less than all of a number of conditions is true. For example, one might program to take debug action as soon any one of a number of fields of a vector is zero, or if any one of the fields is bigger than a predetermined value or if one and no more than one of the number of fields meets such a condition etc. These and other advantageous aspects of the data processor and method according to the invention will be described in more detail using the following figures. Figure 1 shows a data processor Figure 2 shows part of a debug circuit. Figure 1 shows a data processor. The data processor contains an instruction processing circuit 10, a memory 12 and a debug circuit 14. The instruction processing circuit 10 has an address and control output and a data input/output coupled to the memory 12. The debug circuit 14 is coupled to the data input/output and the address and control output. The debug circuit 14 has an output coupled to an interrupt input of the instruction processing circuit 10 and a programming input coupled to the instruction processing circuit 10. In operation, the instruction processing circuit 14 processes a series of instructions from a program. These instructions may involve reading data from memory 12 and writing back data to memory 12. The debug circuit 14 monitors the data read and written between the instruction processing circuit 10 and memory 12. The debug circuit 14 tests a value of this data against a condition that has been programmed into the debug circuit. If the data satisfies the condition the debug circuit 14 takes debug action. Debug action may be the generation of an interrupt to the instruction execution circuit 10, for causing the instruction execution circuit 10 to stop normal processing of the program and to start executing a debug exception program. However, debug action as understood herein is not limited to the generation of interrupts: instead, for example, the debug circuit may capture additional data from the instruction processing circuit 10 and/or memory for later analysis (the additional data may include the program counter value, a timestamp, the content of registers etc.). Alternatively, the debug action may be to preserve data and/or address values passed between the memory 12 and the instruction processing circuit 10 during a window of instruction cycles in a time interval relative to the cycle in which the condition was met (such information may stored for all cycles, only to be overwritten by data for other cycles unless the condition is met). Alternatively debug action may involve incrementing a count value, and taking other debug action once the count value reaches a specified value. It will be clear that many different debug actions are conceivable, undertaken by exception only when the condition is met. A debug action is triggered as an exceptional result of instruction execution: triggering is not inherent to any instruction, but an exception generated when predefined circumstances occur during execution of an instruction. Thereupon the debug action facilitates inspection of the state of the data processor. Figure 1 shows the debug circuit 14 coupled to the connection between the instruction processing circuit 10 and the memory 12. This location is preferred because it provides a point where the most general access to processed data is available at the lowest cost. However, without deviating from the invention the debug circuit 14 may be located, elsewhere, for example between an ALU (Arithmetic Logic Unit, not shown) and a register file (not shown) in the processor or at an I/O port (not shown) etc. In case of a RISC processor, memory load and store operations are performed only by load and store instructions. In that case, the circuit of figure 1 can take the debug action only in case of load and/or store instructions. However, the invention is not limited to RISC: the invention applies as well to processors that access memory as part of other instructions, such as arithmetic instructions. Figure 2 shows a part of the debug circuit 14 that is responsible for monitoring whether the condition is met. The part of the debug circuit contains a data input register 20, with outputs for respective fields of the data coupled to field condition testing circuits 22a-d respectively. The field condition testing circuits 22a-d have outputs to a logical combination circuit 24. In addition, the debug circuit has an address/control data register 21, coupled to an address/control data comparator 23. The address/control data comparator 23 also has an output connected to the logical combination circuit 24. The debug circuit has a programming circuit 26 to control the condition tested by the debug circuit 26. The programming circuit 26 has a reference value register 262 with respective field outputs coupled to the field condition testing circuits 22a-d respectively. The programming circuit 26 has a mask register 264 with respective field outputs coupled to the field condition testing circuits 22a-d respectively. The programming circuit 26 has field condition programming registers 268a-d coupled to function control inputs of field condition testing circuits 22a-d respectively. The programming circuit 26 has a logical combination function programming register 269 coupled to the logic combination circuit 24. The programming circuit 26 has a reference address/control data register 266 coupled to address/control data comparator 23. A control circuit 260 is coupled to the reference value register 262, the mask register 264, the reference address/control data register, the field condition programming registers 22a-d, the combination function programming register 269. One or more circuits like the one shown in figure 2 may be incoφorated in the debug circuit 14 to test one or more conditions in parallel. In operation data values passed between the instruction processing circuit 10 and the memory 12 is stored into data register 20. Similarly address and control data passed to the memory 12 is stored in address/control register 21. The data register 20 divides the data values into different fields, for example four fields of 16 bits in case of 64 bit wide data. Of course this is an example: instead of four fields (as shown in figure 2) other numbers of fields may used. Similarly a different data size may be used. Preferably, the fields correspond to the fields used in vector instructions processed by the instruction processing circuit 14. Such vector processing instructions specify one or more operands and treat these operands as a set of fields, each field containing an independent number. In response to a vector processing instruction like ADD the instruction processing circuit 10 adds numbers from corresponding fields of two operands for a number of fields in parallel. The results are written into different fields of a result operand. By using the vector field size in the debug circuit 14 as well, the debug circuit 14 performs tests on different vector components. Preferably the fields have a predetermined size and positions in the operand, or a selectable one of a number of predetermined sizes and positions (in case of vector operations for different size fields, e.g. for 8 8-bit vector components are for 4 16-bit vector components). Each condition testing circuit 22a-d tests the data from a different one of the fields. In the test, the data from the relevant field is compared with corresponding data from the reference data register 262. Optionally the condition testing circuit 22a-d masks out the comparison for a number of bits in the field according to a mask value in the mask register 264. Without deviating from the invention masking may be omitted. The type of comparison for each particular field is controlled by the content of the field condition programming register 268a-d for that particular field. For example, the condition testing circuits 22a-d may provide for testing for any selectable condition from the following list: equality, not-equal, greater than, greater equal, less than, less equal. A smaller list of possible comparisons may also be used. Without deviating from the invention, a single field condition programming register may be used for all fields, or even a fixed type of comparison (e.g. test for equality) may be used. Preferably, the address/control value comparator 23 compares the address used to load or store the data with a reference address from the reference address register and/or the address/control comparator 23 compares control signals used to transfer the data between the processor 10 and memory 12 with reference control signals (such signals may include read/write selection, access privileges, task ID etc.). The logical combination circuit 24 logically combines the results of the comparisons in the different field condition testing circuits 22a-d. A result signal of the logical combination is output from the logical combination circuit 24 and used to trigger debug action. (By parts of the debug circuit not shown). Preferably, the type of logical combination is programmed with the combination function programming register 269. Thus, debug action may be triggered for example if a logical OR of condition signals that signal that a condition has been met for different ones of the fields of a data value. In this case any one of the fields may trigger debug action. However, other logical combinations may also be provided for, such as the logical OR of a selected subset of the fields, an exclusive OR of the condition signals (debug action if one and not more than one of the fields satisfies its condition), an exclusive or of the inverse of the condition signals (debug action if one and not more than one of the fields does not satisfy its condition) and so on. Preferably, the logical combination circuit 24 also uses a result of the comparison performed by the address control/value comparator 23. Thus, debug action may be triggered only if a programmed address is involved and/or only incase of read from memory or in case of write to memory. Preferably, this condition on addressing is also programmable. The programming information is loaded into the various registers 262, 264, 266, 268a-d, 269 by the control circuit. Preferably this is done under control of debug instructions executed by the instruction processing circuit. Debug instructions may be provided for enabling/disabling debug action, setting the reference data value, the mask value, condition control value and combination control value. In summary: a data processor has a debug circuit arranged to monitor whether operand data used for execution of a program meets a debug exception condition. The debug exception condition tests a two or more of multi-bit subfields of a vector operand independently. Debug action is taken if one or more of the multi-bit subfields meet the corresponding conditions.

Claims: CLAIMS: 1. A data processor comprising - an instruction processing circuit for executing a program; - a debug circuit arranged to - receive a programmed debug exception condition; - monitor whether operand data used by the instruction processing circuit for execution of the program meets the debug exception condition; - take debug action in response to detection that the operand data meets the debug exception condition, the debug circuit being arranged to use a debug exception condition that specifies taking debug action when one or more but less than all of a number of respective conditions on two or more multi-bit subfields of the operand data are true respectively. 2. A data processor according to Claim 1 , wherein the debug circuit is arranged to use a debug exception condition that specifies taking debug action when a logical OR of the respective conditions is true. 3. A data processor according to Claim 1 , wherein the instruction processing circuit is arranged to process a vector instruction that addresses the operand value, processing the multi-bit subfields as mutually independent arithmetic numbers. 4. A data processor according to Claim 1 , wherein the debug circuit is arranged to monitor whether operand data of a store to memory instruction and/or of a load from memory instruction meets the debug exception condition. 5. A data processor according to Claim 1, wherein the conditions on the respective multi-bit subfield are relational arithmetic conditions comparing the multi-bit subfields with respective numbers for those respective multi-bit subfields. 6. A data processor according to Claim 5, wherein the relational arithmetic condition is at least one of equality, non-equality, greater than, greater equal, less than or less equal. 7. A data processor according to Claim 1 , wherein the multi -bit subfields make up the entire operand data. 8. A data processor according to Claim 1, wherein the debug circuit is arranged to receive the debug exception condition with a field selection indication, indicating for which ones of one or more of the multi-bit subfields the conditions of the multi -bit subfield must be satisfied to trigger debug action. 9. A method of processing data with a data processor device, the method comprising - receiving a programmed debug exception condition; - processing instructions of a program; - monitor whether operand data used by the instruction processing circuit during execution of the program meets the debug exception condition; - taking debug action in response to detection that the operand data meets the debug exception condition, characterized in that the debug exception condition specifies taking debug action when one or more but less than all of a number of respective conditions on two or more multi -bit subfields of the operand data respectively are true.

Inventors: SIJSTERMANS FRANSISCUS W, VISSERS KORNELIS A, VRANKEN HENDRIKUS P E, SIJSTERMANS, FRANSISCUS, W., VISSERS, KORNELIS, A., VRANKEN, HENDRIKUS, P., E.
Applicants: KONINKL PHILIPS ELECTRONICS NV, KONINKLIJKE PHILIPS ELECTRONICS N.V.
Application year: 2000
Main classification: G06F11
IPC codes: G06F9, G06F11