MMP Tutorial

The paging options are:

• code paging
• data paging
• both code and data paging

Making executables (either exe or dll) paged is the finest level of control of paging at runtime. In the order of precedence for paging keywords, the values in this file will be overridden by those in the oby file.

The following keywords are used to indicate whether the executable is unpaged or paged. If the executable is paged then the keywords indicate if code paging, data paging or both are to be used.

When using the above keywords, the following points must be considered.

• The keywords pageddata and unpageddata do not make sense for files that are not executable binaries, and will be ignored.
• The use of the paged, unpaged, pagedcode and unpagedcode keywords only states the default paging behaviour of the data that is to paged by the executable. The behaviour can be overridden by using the TChunkCreateInfo, RChunk and TChunkHeapCreateInfo API.
• The keywords in the table above, should appear on a separate line on their own and with no arguments
• If the build tools are configured to compress executables while building them (this is the default behaviour), then executables marked with paged or the pagedcode keyword will be implicitly byte-pair compressed.
• If a ROM/ROFS partition defines a pagingoverride, codepagingoverride or datapagingoverride as defaultpaged or defaultunpaged, then the pagability specified in the mmp file will be implemented.
• If a ROM/ROFS partition has defines pagingoverride, codepagingoverride or datapagingoverride as nopaging or alwayspage, then the pagability specified in the mmp file will be ignored.

Building the executable with the new keyword does not produce any errors or warnings.