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.

Parity error reporting<br />

Protected Memory System <strong>Architecture</strong> (PMSA)<br />

The <strong>ARM</strong> architecture supports the reporting of both synchronous <strong>and</strong> asynchronous parity errors from the<br />

cache systems. It is IMPLEMENTATION DEFINED what parity errors in the cache systems, if any, result in<br />

synchronous or asynchronous parity errors.<br />

A fault status code is defined for reporting parity errors, see Fault Status <strong>and</strong> Fault Address registers in a<br />

PMSA implementation on page B4-18. However when parity error reporting is implemented it is<br />

IMPLEMENTATION DEFINED whether the assigned fault status code or another appropriate encoding is used<br />

to report parity errors.<br />

For all purposes other than the fault status encoding, parity errors are treated as external aborts.<br />

B4.4.3 Prioritization of aborts<br />

For synchronous aborts, Debug event prioritization on page C3-43 describes the relationship between debug<br />

events, MPU faults <strong>and</strong> external aborts.<br />

In general, the <strong>ARM</strong> architecture does not define when asynchronous events are taken, <strong>and</strong> therefore the<br />

prioritization of asynchronous events is IMPLEMENTATION DEFINED.<br />

Note<br />

A special requirement applies to asynchronous watchpoints, see Debug event prioritization on page C3-43.<br />

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

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

Saved successfully!

Ooh no, something went wrong!