29.11.2014 Views

Fast Models Reference Manual - ARM Information Center

Fast Models Reference Manual - ARM Information Center

Fast Models Reference Manual - ARM Information Center

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

AEM <strong>ARM</strong>v7-A specifics<br />

AP==110 deprecated<br />

Pagetable entries using the encoding AP[2] = 1, AP[1:0] = 0b10 means read-only for both<br />

privileged mode and user mode accesses, but its use is deprecated in VMSAv7. Instead use AP[2]<br />

= 1, AP[1:0] = 0b11.<br />

A dirty cache line was invalidated but not cleaned<br />

When the invalidate cache maintenance operation is performed on a writeback cache, the data<br />

in any dirty lines might or might not have been flushed to the next cache level or backing RAM.<br />

Any subsequent data reads from that address are therefore ambiguous. It is legal to do this, but<br />

take care that it is not used improperly or else bugs can be introduced.<br />

Reserved encoding<br />

When extended addressing is in use, each 8-bit field of the MAIR0 and MAIR1 registers must be<br />

written with a valid memory type. Writing any field with values of the following form is<br />

unpredictable:<br />

• 0xyy xxxx for values of yy other than 0<br />

• xxxx 0xyy for values of yy other than 0<br />

• yyyy 0000 for values of yyyy other than 0<br />

• 0000 1xxx.<br />

Incoherency between S and NS memory<br />

Some system platforms (such as the VE) do not distinguish between SECURE and<br />

NON_SECURE memory accesses, and the storage destination depends only on the physical<br />

address regardless of the NS bit. In these cases, using S and NS versions of the same physical<br />

address can have unpredictable cache incoherency effects. For example, if the cache contains<br />

dirty lines for the same address in each state, the final memory contents depend on random<br />

eviction order.<br />

When the AEM, however, is used as a component in a system platform that distinguishes<br />

between S and NS accesses, this usage is perfectly legal and recommended, so this warning must<br />

be disabled by decreasing the value of the messages.severity_level_E_ReservedEncoding<br />

parameter.<br />

Exception level change<br />

Various unpredictable effects can occur if an MSR or CPS instruction is used to change privilege<br />

level, for example, leaving monitor mode with SCR.NS==0, leaving hyp mode, or entering user<br />

mode.<br />

In preference, target code must use one of the exception return operations such as RFE, ERET or<br />

SUBS PC, LR.<br />

<strong>ARM</strong> DUI 0423J Copyright © 2008-2011 <strong>ARM</strong>. All rights reserved. A-7<br />

ID051811<br />

Non-Confidential

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

Saved successfully!

Ooh no, something went wrong!