Holtek HT-IDE, User Manual

Page: 53 / 258

•
Breakpoints of address or data, in binary form with don’t-care bits, are
permitted.
•
When an instruction is set to be an effective breakpoint, the HT-ICE will
stop at this instruction, but will not execute it, i.e. this instruction will
become the next one to be executed. Although an instruction is an
effective breakpoint, the HT-ICE may not stop at this instruction due to
execution flow or conditional skips. If an effective breakpoint is in the
Data Space (RAM), the instruction that matches this conditional break-
point data will always be executed. The HT-ICE will stop at the next
instruction.
Description of breakpoint items
A breakpoint consists of the following descriptive items. It is not necessary
to set all items, Fig 5-3:
•
Space
The location of the breakpoint, either Program Code space or Data space.
•
Location
The actual location of the breakpoint. The next paragraph will give the
location format.
•
Content
The data content of breakpoint. This item is effective only when the Space
is assigned to the Data space. The Read and Write check box are used for
executing conditions of the breakpoint.
•
Externals
External signal breakpoint. There are 4 external signals, ET0, ET1, ET2
and ET3 at location JP3 on the I/O interface card.
→
Format of description items - Location
The allowed formats of Location items are:
•
Absolute address (in code space or data space) with 4 format types,
namely decimal, hexadecimal (suffix with ’H’ or ’h’), binary and don’t-care
bits. For example
20, 14h, 00010100b, 10xx0011
represents decimal 20, hexadecimal 14h, binary 00010100b and don’t care
bits 4 and 5 respectively.
Note
Don’t-care bits must be in binary format.
Chapter 5 HT-IDE Menu – Debug
43