05.02.2013 Views

ARM Architecture Reference Manual ARMv7-A and ARMv7-R edition

ARM Architecture Reference Manual ARMv7-A and ARMv7-R edition

ARM Architecture Reference Manual ARMv7-A and ARMv7-R edition

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

A.1.2 Run-control <strong>and</strong> cross-triggering signals<br />

Recommended External Debug Interface<br />

<strong>ARM</strong> recommends implementation of the run-control <strong>and</strong> cross-triggering signals EDBGRQ,<br />

DBGTRIGGER, DBGRESTART, <strong>and</strong> DBGRESTARTED. These signals are particularly useful in a<br />

multiprocessor system, because using them:<br />

A debugger can signal a group of processors to enter Debug state.<br />

A debugger can signal a group of processors to leave Debug state.<br />

A system component can signal a group of processors to enter Debug state when any one of them<br />

enters Debug state because of a debug event on that processor. This is known as cross-triggering.<br />

If you implement the recommended signalling in your system hardware, this signalling means all of the<br />

processors in the group enter or leave Debug state nearly simultaneously.<br />

These signals can also be used in a uniprocessor implementation. For example, debug events not defined by<br />

the debug architecture might be generated externally to the processor. When one of these events occurs the<br />

external system can use these signals to cause the processor to enter Debug state. A trace macrocell might<br />

use these signals in this way.<br />

Contact <strong>ARM</strong> for details of a recommended Embedded Cross Trigger (ECT) peripheral that you can use in<br />

a multiprocessor system to implement this signalling.<br />

The following subsections describe each of the recommended signals:<br />

EDBGRQ<br />

DBGTRIGGER on page AppxA-6<br />

DBGRESTART <strong>and</strong> DBGRESTARTED on page AppxA-6.<br />

EDBGRQ<br />

EDBGRQ is the recommended implementation of the External Debug Request mechanism, see Halting<br />

debug events on page C3-38.<br />

EDBGRQ is active-HIGH.<br />

Once EDBGRQ is asserted it must be held HIGH until it is acknowledged:<br />

An implementation can use either DBGACK or DBGTRIGGER to acknowledge EDBGRQ, see:<br />

— DBGACK <strong>and</strong> DBGCPUDONE on page AppxA-7<br />

— DBGTRIGGER on page AppxA-6.<br />

Alternatively, debugger software might use an IMPLEMENTATION DEFINED method to acknowledge<br />

EDBGRQ. For example, once the processor has entered Debug state the debugger might reprogram<br />

the peripheral that is driving EDBGRQ.<br />

<strong>ARM</strong> DDI 0406B Copyright © 1996-1998, 2000, 2004-2008 <strong>ARM</strong> Limited. All rights reserved. AppxA-5

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

Saved successfully!

Ooh no, something went wrong!