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

Reset, panic and debug events 83<br />

State of DM.EXP_CAUSE <strong>bit</strong>s<br />

Value<br />

read<br />

Meaning<br />

Value<br />

written<br />

Effect<br />

1 Interrupt source was<br />

asserted<br />

0 The interrupt source will be de-asserted.<br />

Note that some interrupt sources require<br />

additional actions to fully de-assert them (see<br />

Table 29 on page 83).<br />

1 Writing 1 has no effect on the <strong>bit</strong>’s value.<br />

Table 28: State of reading/writing DM.EXP_CAUSE <strong>bit</strong>s<br />

The DEBUGINT handler should write ‘0’ to the appropriate <strong>bit</strong>(s) in DM.EXP_CAUSE as<br />

soon as it can. This will minimize the risk of losing new interrupts that arrive<br />

during the execution of the DEBUGINT handler.<br />

DM.EXP_CAUSE<br />

0x100010<br />

Field Bits Size Volatile? Synopsis Type<br />

DM_FIFO_INTERRUPT 0 1 ✓ DM FIFO interrupt RW<br />

Operation<br />

When read<br />

When written<br />

HARD reset 0<br />

This field is set whenever an interrupt is generated due to<br />

DM FIFO activity as selected by the FF_THRE<strong>SH</strong> field of<br />

DM.TRCTL (see Table 31 on page 97).<br />

Returns current value<br />

Updates value.<br />

Writing 0 Will partially clear the cause of the DM FIFO<br />

interrupt. In order to fully clear the interrupt, the DM FIFO<br />

must be setup to remove the cause (either reprogram<br />

DM.TRCTL.FF_THRE<strong>SH</strong> such that it will not generate debug<br />

Interrupts or empty the DM FIFO).<br />

Writing 1 has no effect - any pending DM FIFO interrupts will<br />

not be lost, and subsequent reads will return 1 (unless the<br />

source of the interrupt is unexpectedly removed).<br />

D R A FT<br />

Table 29: DM.EXP_CAUSE register definition<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

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

Saved successfully!

Ooh no, something went wrong!