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.

Debug Register Interfaces<br />

To have full debug support for power-down <strong>and</strong> re-powering of the processor, the following registers <strong>and</strong><br />

individual bits need to be in the debug power domain:<br />

DBGECR This enables the debugger to set the OS Unlock Catch bit to 1 any time <strong>and</strong> still break on<br />

completion of the power-up sequence. If this register was in the core power domain, the<br />

power-down event would clear this catch bit to 0. For more information, see Event Catch<br />

Register (DBGECR) on page C10-78.<br />

DBGDRCR[0] Halt request bit<br />

This enables the debugger to request a Debug state entry even if the processor is powered<br />

down. Also, if the debugger makes this request before powering-down but the request<br />

cannot be satisfied, for example because the processor is in Secure state but<br />

(DBGEN AND SPIDEN) = 0, the request remains pending through power-down.<br />

Note<br />

The processor has to be powered up to respond to a pending DBGDRCR[0] Halt request or<br />

External Debug request.<br />

OS Lock Access Register<br />

This enables the lock that the OS sets before saving the debug registers to remain set through<br />

power-down. For details see OS Lock Access Register (DBGOSLAR) on page C10-75.<br />

Device Power-down <strong>and</strong> Reset registers<br />

These registers must be in the debug power domain because some of their functions are used<br />

for debugging power-down events. See Device Power-down <strong>and</strong> Reset Control Register<br />

(DBGPRCR), v7 Debug only on page C10-31, Device Power-down <strong>and</strong> Reset Status<br />

Register (DBGPRSR), v7 Debug only on page C10-34.<br />

Lock Access Register, if implemented<br />

If implemented, this register must be in the debug power domain because it is used to enable<br />

certain accesses by external debug interface, <strong>and</strong> this functionality is required when<br />

debugging power-down events.<br />

Identification registers <strong>and</strong> the DBGDIDR<br />

The identification registers are at addresses 0xD00-0xDFC, <strong>and</strong> 0xFD0-0xFEC. For details of<br />

these registers see Management registers, <strong>ARM</strong>v7 only on page C10-88.<br />

Debugger operation only requires the above registers <strong>and</strong> bits to be in the debug power domain. However,<br />

to rationalize the split between the debug <strong>and</strong> core power domains in the register map, <strong>ARM</strong>v7 requires an<br />

implementation that supports debug over power-down to have all bits of the following registers in the debug<br />

power domain:<br />

DBGDIDR, DBGECR, <strong>and</strong> DBGDRCR<br />

No error response is returned on read or write accesses when the core power domain is<br />

powered down.<br />

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

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

Saved successfully!

Ooh no, something went wrong!