4.13. Map files

The type and speed of memory in a simulated system can be detailed in a map file. A map file defines the number of regions of attached memory, and for each region:

armsd expects the map file to be called armsd.map, in the current working directory.

AXD accepts map files of any name. See AXD and armsd Debuggers Guide for details of how to use a particular map file in a debugging session.

To calculate the number of wait states for each possible type of memory access, the ARMulator uses the access times supplied in the map file, and the clock frequency from the debugger (see AXD and armsd Debuggers Guide).

See also Memory modelling with mapfiles.


A memory map file defines the characteristics of the memory areas defined in peripherals.ami (see ARMulator configuration files). A .map file must define rw areas that are at least as large as those specified for the heap and stack in peripherals.ami, and at the same locations. If this is not the case, Data Aborts are likely to occur during execution.

Copyright © 1999-2001 ARM Limited. All rights reserved.ARM DUI0058D