156 partitions. The maximum number of memory partitions in a domain
180 Memory Partitions
184 and access attributes. It is intended that memory partitions are used to
185 control access to system memory. Defining memory partitions are subject
191   that partitions be sized to some power of two, and aligned to their own
195 - Partitions within the same memory domain may not overlap each other. There is
196   no notion of precedence among partitions within a memory domain.  Partitions
208 - Memory domain partitions are intended to control access to system RAM.
209   Configuration of memory partitions which do not correspond to RAM
212 There are two ways to define memory partitions: either manually or
215 Manual Memory Partitions  argument
231 Automatic Memory Partitions  argument
234 Automatic memory partitions are created by the build system. All globals
247 Automatic memory partitions are only configured as read-write
277 If multiple partitions are being created, a variadic preprocessor macro can be
284 Automatic Partitions for Static Library Globals  argument
287 The build-time logic for setting up automatic memory partitions is in
310 Pre-defined Memory Partitions  argument
313 There are a few memory partitions which are pre-defined by the system:
325 Library-specific partitions are listed in ``include/app_memory/partitions.h``.
347 Add Memory Partitions into a Memory Domain
350 There are two ways to add memory partitions into a memory domain.
352 This first code sample shows how to add memory partitions while creating
374 This second code sample shows how to add memory partitions into an initialized
393     The maximum number of memory partitions is limited by the maximum
431 to the partition. Since the access control of memory partitions relies on