09.12.2012 Views

Cortex-A8 Technical Reference Manual - ARM Information Center

Cortex-A8 Technical Reference Manual - ARM Information Center

Cortex-A8 Technical Reference Manual - ARM Information Center

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.

Debug<br />

Locks The debugger or software running on the system might lock out different parts of<br />

the register map so they cannot be accessed while the debug session is in certain<br />

states.<br />

Power down<br />

The APB interface does not permit accesses to registers inside the core power<br />

domain when the core powers down.<br />

Privilege of memory access permission<br />

When nonprivileged software tries to access the APB interface, the system ignores or generates<br />

an abort response on the access. You must implement this restriction at the system level because<br />

the APB protocol does not have a control signal for privileged or user access. You can choose<br />

to have the system either ignore or abort the access. Although you can place additional<br />

restrictions on the memory transactions that are permitted to access the APB interface, <strong>ARM</strong><br />

does not recommend this.<br />

Locks permission<br />

You can lock the APB interface so access to some debug registers is restricted. There are two<br />

locks:<br />

Software lock<br />

The debug monitor can set this lock to prevent erratic software from modifying<br />

debug registers settings. See the <strong>ARM</strong> Architecture <strong>Reference</strong> <strong>Manual</strong> for more<br />

information. A debug monitor can also set this lock prior to returning control to<br />

the application, to reduce the chance of erratic code changing the debug settings.<br />

When this lock is set, writes to all debug registers are ignored, except those writes<br />

generated by the external debugger. See Lock Access Register on page 12-44 for<br />

more information.<br />

OS Lock An OS can set this lock on the debug register map so access to some debug<br />

registers is not permitted while the OS is performing a save or restore sequence.<br />

When this lock is set, the APB interface aborts accesses to registers in the core<br />

power domain. See Operating System Lock Access Register on page 12-33 for<br />

more information.<br />

Note<br />

• The state of these locks is held on debug power domain and, therefore, is not lost when<br />

the core powers down.<br />

• These locks are set to their reset values only on reset of the debug power domain<br />

(PRESETn reset).<br />

• Be sure to set the PADDR31 input signal to 1 for accesses originated from the external<br />

debugger for the Software Lock override feature to work. See Table 12-5 on page 12-10<br />

for more details.<br />

• If you access a reserved or unused register while any lock is set to 1, it is Unpredictable<br />

whether or not the APB interface generates an error response.<br />

<strong>ARM</strong> DDI 0344K Copyright © 2006-2010 <strong>ARM</strong> Limited. All rights reserved. 12-9<br />

ID060510 Non-Confidential

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

Saved successfully!

Ooh no, something went wrong!