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.

Non-invasive Debug Authentication<br />

C7.4 <strong>ARM</strong>v6 non-invasive debug authentication<br />

An <strong>ARM</strong>v6 processor might implement the v7 Debug non-invasive debug authentication signaling<br />

described in v7 Debug non-invasive debug authentication on page C7-4.<br />

In general, non-invasive debug authentication in <strong>ARM</strong>v6 Debug is IMPLEMENTATION DEFINED. For details<br />

of the implemented authentication scheme you must see the appropriate product documentation. In<br />

particular:<br />

it is IMPLEMENTATION DEFINED whether the NIDEN signal is implemented<br />

the exact roles of the following signals are IMPLEMENTATION DEFINED:<br />

— DBGEN, SPIDEN, <strong>and</strong> SPNIDEN<br />

— NIDEN, if it is implemented.<br />

However, an <strong>ARM</strong>v6 non-invasive debug authentication scheme must obey the following rules:<br />

If NIDEN is implemented then tying NIDEN <strong>and</strong> DBGEN both LOW guarantees that non-invasive<br />

debug is disabled.<br />

if NIDEN is not implemented then the mechanism for disabling non-invasive debug is<br />

IMPLEMENTATION DEFINED. An implementation might not support any mechanism for disabling<br />

non-invasive debug.<br />

When the Security Extensions are implemented, tying SPIDEN <strong>and</strong> SPNIDEN both LOW<br />

guarantees that non-invasive debug is not permitted in Secure privileged modes.<br />

In addition, if SPIDEN <strong>and</strong> SPNIDEN are both LOW then setting SDER.SUNIDEN to 0 guarantees<br />

that non-invasive debug is not permitted in Secure User mode.<br />

If non-invasive debug is enabled then if SDER.SUNIDEN is 1, non-invasive debug is permitted in<br />

Secure User mode.<br />

If NIDEN is implemented then tying NIDEN <strong>and</strong> SPNIDEN both HIGH is guaranteed to enable <strong>and</strong><br />

permit non-invasive debug in all modes in both security states.<br />

If NIDEN is not implemented then tying SPNIDEN HIGH is guaranteed to enable <strong>and</strong> permit<br />

non-invasive debug in all modes in both security states.<br />

Table C7-4 shows the architectural requirements for non-invasive debug behavior in an <strong>ARM</strong>v6 Debug<br />

implementation that does not include the Security Extensions.<br />

Table C7-4 <strong>ARM</strong>v6 non-invasive debug authentication requirements, Security Extensions<br />

not implemented<br />

NIDEN DBGEN Non-invasive debug behavior<br />

Implemented <strong>and</strong> LOW LOW Disabled.<br />

Implemented <strong>and</strong> HIGH x Enabled.<br />

C7-8 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!