![Xilinx Virtex-II Pro PPC405 Скачать руководство пользователя страница 242](http://html1.mh-extra.com/html/xilinx/virtex-ii-pro-ppc405/virtex-ii-pro-ppc405_user-manual_3410279242.webp)
550
March 2002 Release
1-800-255-7778
Virtex-II Pro™ Platform FPGA Documentation
R
string instructions can generate multiple effective addresses, all of which are
used to check for a DAC event. The DAC event is controlled by conditions
specified in the DBCR1 register.
A variety of DAC conditions can be specified:
•
Check for an exact data-address match.
•
Check for a data-address match using halfword, word, or cacheline
granularity.
•
Check for a data-address match within a range of addresses.
•
Check for a data-address match outside a range of addresses.
Each of the above DAC conditions can be further controlled to cause a debug
event only if the matching data access is a read or a write.
If debug interrupts are enabled, the SRR2 register is loaded with the effective
address of the instruction that caused the DAC event.
DAC Exact-Address Match
A DAC exact-address match causes a debug event when the effective address
contained in the specified DAC
n
register matches the effective address of the
operand. Read and write accesses can be checked independently. If a match
occurs, the corresponding status bit in DBSR is set to 1.
shows the control bits used to enable the DAC exact-address-match
debug events, the type of access that is checked by each event, the DACn
register used in the comparison, and the debug-status register bit set when the
event occurs. Any number of DAC exact-address-match conditions can be
enabled simultaneously. DAC address-range comparison must be disabled
(DBCR1[DA12]
=
0).
The processor does not clear the DBSR status bits when DAC events fail to
occur. After a DAC event is recorded by a debugger, the corresponding status
bits should be cleared to prevent ambiguity when recording future debug
events.
Specifying Exact-Match Granularity
Software can specify an operand-size granularity for use when performing the
address comparison with each DAC register. Normally, the comparison checks
for an exact address match or a byte-granular match. The comparison can be
modified to check for halfword, word, and cache-line granular matches. This
is useful when a debugger wants to cause a DAC event to occur when
any
byte
in a word is accessed.
Granularity is specified using the DBCR1[D1S] size field for comparisons
against the DAC1 register and the DBCR1[D2S] size field for comparisons
against the DAC2 register. This field specifies which low-order address bits
are
ignored
during the comparison. Because low-order address bits are
ignored, the comparison is aligned on an address boundary equivalent to the
Table 9-6:
DAC Exact-Address Match Resources
Event Enable Bit
(DBCR1)
Type of Access
Checked
DAC Register Used
Event Status Bit
(DBSR)
D1R
Load (Read)
DAC1
DR1
D1W
Store (Write)
DW1
D2R
Load (Read)
DAC2
DR2
D2W
Store (Write)
DW2
Содержание Virtex-II Pro PPC405
Страница 1: ...R Volume 2 a PPC405 User Manual Virtex II Pro Platform FPGA Developer s Kit March 2002 Release...
Страница 14: ...322 www xilinx com March 2002 Release 1 800 255 7778 Virtex II Pro Platform FPGA Documentation Preface R...
Страница 252: ...560 www xilinx com March 2002 Release 1 800 255 7778 Virtex II Pro Platform FPGA Documentation R...
Страница 260: ...568 www xilinx com March 2002 Release 1 800 255 7778 Virtex II Pro Platform FPGA Documentation R...
Страница 562: ...870 www xilinx com March 2002 Release 1 800 255 7778 Virtex II Pro Platform FPGA Documentation R...