SuperH (SH) 64-bit RISC Series SH-5 System Architecture, Volume ...
SuperH (SH) 64-bit RISC Series SH-5 System Architecture, Volume ...
SuperH (SH) 64-bit RISC Series SH-5 System Architecture, Volume ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
PRELIMINARY DATA<br />
<strong>SuperH</strong>yway watchpoint comparators 181<br />
Transaction type<br />
The <strong>SuperH</strong>yway bus may be implemented with multiple segments and separate<br />
request and response segments. At a functional level, the <strong>SuperH</strong>yway bus analyzer<br />
has no knowledge of multiple bus segments or separate request and response<br />
segments. The debug user sets a single opcode value and an associated opcode mask<br />
in DM.WP_PLX_CTRL and this can be a request opcode or a response opcode depending<br />
on the type of transaction the debug user wants to monitor. This single opcode is<br />
used by the comparators which exist on each request segment and response<br />
segment.<br />
Transaction source<br />
Each <strong>SuperH</strong>yway request and response carries an 8-<strong>bit</strong> field that identifies the<br />
originator of the bus request. Each watchpoint has two fields associated with the<br />
source device, one field for the source device value and a second field for a mask. The<br />
mask field allows requests and responses from different devices to be matched.<br />
Destination device<br />
The destination device field in the <strong>SuperH</strong>yway request and response consists of the<br />
top <strong>bit</strong>s of the address. In the case of <strong>SH</strong>-5, the destination field is the top 8-<strong>bit</strong>s of<br />
the 32-<strong>bit</strong> address. Each watchpoint has two fields associated with the destination<br />
device, one field for the destination device value and a second field for a mask. The<br />
mask field allows requests and responses to different devices to be matched.<br />
It is an implementation specific property as to whether the destination comparator<br />
is implemented.<br />
Address<br />
The address field in the request header defines an address in the specified<br />
destination device. In the case of <strong>SH</strong>-5, this address field is 24-<strong>bit</strong>s wide with the<br />
least-significant 3-<strong>bit</strong>s forced to zero, that is, addresses are always 8-byte aligned.<br />
Watchpoint registers define an address range by means of start address and end<br />
address parameters. The address comparison range can be as small as one bus word<br />
(8-bytes).<br />
D R A FT<br />
<strong>SuperH</strong>yway responses do not have an address field, so that the watchpoint address<br />
range comparison is ignored for responses.<br />
05-SA-10003 v1.0<br />
<strong>SuperH</strong>, Inc.<br />
<strong>SH</strong>-5 <strong>System</strong> <strong>Architecture</strong>, <strong>Volume</strong> 3: Debug