25.02.2015 Views

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 ...

SHOW MORE
SHOW LESS

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 />

128 Debug protocols and interfaces<br />

IV watchpoint trace message (7-bytes minimum, 16-bytes maximum)<br />

Field<br />

Size<br />

Header <strong>bit</strong><br />

positions<br />

Description<br />

MESSAGE_TYPE 3-<strong>bit</strong>s [2:0] 0b010 or 0b011<br />

SOURCE_MODULE 3-<strong>bit</strong>s [5:3] 0 (WPC)<br />

EVENT_TYPE 5-<strong>bit</strong>s [10:6] 0x06 through 0x07 (see Table 89: <strong>SH</strong>-5 evaluation<br />

device trace message codes on page 247).<br />

OVER_STALL 1-<strong>bit</strong> [11]<br />

PC_ABSOLUTE 1-<strong>bit</strong> [12]<br />

DATA_FIELD_SIZE 3-<strong>bit</strong>s [15:13] Defines how much data was stored to memory by the<br />

triggering instruction.<br />

Value - Description<br />

0b000: The instruction which hit the watchpoint did<br />

not write to a memory location<br />

0b001: Undefined<br />

0b010: Undefined<br />

0b011: Undefined<br />

0b100: 1 byte. The instruction which hit the watchpoint<br />

did a 1 byte write to a memory location<br />

0b101: 2 byte write (as above)<br />

0b110: 4 byte write (as above)<br />

0b111: 8 byte write (as above)<br />

TIMESTAMP 0 or 1<br />

byte<br />

ASID 0 or 1<br />

byte<br />

PC 1, 2 or 4<br />

bytes<br />

N/A<br />

N/A<br />

N/A<br />

D R A FT<br />

Table 43: IV watchpoint trace message<br />

<strong>SuperH</strong>, Inc.<br />

<strong>SH</strong>-5 <strong>System</strong> <strong>Architecture</strong>, <strong>Volume</strong> 3: Debug 05-SA-10003 v1.0

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!