SuperH (SH) 64-bit RISC Series SH-5 System Architecture, Volume ...

PRELIMINARY DATA
WP channel type OA 151
Fields in WPC.WP_OAx_ACTION:
ACTION_EXCEPTION: Standard event handling sequence is followed. If SR.BL == ‘0’,
the RESVEC/DBRVEC offset is 0x100 (to denote a synchronous debug event of type
DEBUGOA). Otherwise, if SR.BL == ‘1’, the RESVEC/DBRVEC offset is 0x0 (to denote a
PANIC event).
EXPEVT is set to 0x960 to denote a DEBUGOA exception.
In addition, the effective operand address, is put into the TEA register.
ACTION_ECOUNT Supported.
ACTION_CHAIN_ALTER/CHAIN_ID Supported.
ACTION_PCOUNT/ACTION_RESET_ALL_PCOUNT/PCOUNT_ID: Supported
Fields in DM.WP_OAx_ACTION:
OA_MATCH: Supported
ACTION_INTERRUPT: Standard event handling sequence is followed. The RESVEC/
DBRVEC offset is 0x200 (to denote a DEBUGINT event).
EXPEVT is not set as this is a debug interrupt, not an exception.
DM.EXP_CAUSE.OA_MATCH_INTERRUPT is set to ‘1’.
ACTION_TRACE/TRACE_TYPE/ENABLE_TRACE_TIMESTAMP:
The data included in trace messages is the same as that used for comparison with
the DM.OA_MATCH_* registers. See Section 1.12.3: Data match registers on page 147
and Table 42: OA watchpoint trace message on page 125.
The contents of OA trace messages is controlled by the WPC.ADDR_IN_TRACE register
(see Section 1.5.1: on page 65).
D R A FT
OA trace messages include a field (DATA_FIELD_SIZE) which indicates the size of the
data written (see Table 42: OA watchpoint trace message on page 125).
This field specifies the amount of data written as being either 0, 1, 2, 4 or 8 bytes. It
also determines which bits of the data are included in the data comparison, valid
bits are compared and invalid bits are ignored.
Normally the value encoded corresponds directly to the amount of data written by
the triggering instruction.
05-SA-10003 v1.0
SuperH, Inc.
SH-5 System Architecture, Volume 3: Debug