ARM CoreLink MMU-500 System Memory Management Unit Technical Reference ManualRevision: r2p0
Home >  Preface > About this book > Conventions

Conventions

This book uses the conventions that are described in:

Typographical conventions

The following table describes the typographical conventions:

Table 1. Typographical conventions

StylePurpose
italicIntroduces special terminology, denotes cross-references, and citations.
boldHighlights interface elements, such as menu names. Denotes signal names. Also used for terms in descriptive lists, where appropriate.
monospaceDenotes text that you can enter at the keyboard, such as commands, file and program names, and source code.
monospaceDenotes a permitted abbreviation for a command or option. You can enter the underlined text instead of the full command or option name.
monospace italicDenotes arguments to monospace text where the argument is to be replaced by a specific value.
monospace boldDenotes language keywords when used outside example code.
<and>

Encloses replaceable terms for assembler syntax where they appear in code or code fragments. For example:

MRC p15, 0 <Rd>, <CRn>, <CRm>, <Opcode_2>
small capitalsUsed in body text for a few terms that have specific technical meanings, that are defined in the ARM® Glossary. For example, implementation defined, implementation specific, unknown, and unpredictable.

Signals

The signal conventions are:

Signal level

The level of an asserted signal depends on whether the signal is active-HIGH or active-LOW. Asserted means:

  • HIGH for active-HIGH signals.

  • LOW for active-LOW signals.

Lowercase n

At the start or end of a signal name denotes an active-LOW signal.

Copyright © 2013, 2014 ARM. All rights reserved.ARM DDI 0517C
Non-ConfidentialID031814
PDF file icon  PDF version
Home >  Preface > About this book > Conventions