Datasheet

ARMulator Reference
ARM DUI0058D Copyright © 1999-2001 ARM Limited. All rights reserved. 4-59
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:
• the address range to which that region is mapped
• the data bus width in bytes
• the access time for the memory 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 on page 2-27.
NoteNote
A memory map file defines the characteristics of the memory areas defined in
peripherals.ami (see ARMulator configuration files on page 4-63). 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.
4.13.1 Format of a map file
The format of each line is:
start size name width access{*} read-times write-times
where:
start is the start address of the memory region in hexadecimal, for example
80000 .
size is the size of the memory region in hexadecimal, for example, 4000 .
name is a single word that you can use to identify the memory region when
memory access statistics are displayed. You can use any name. To ease
readability of the memory access statistics, give a descriptive name such
as SRAM, DRAM, or EPROM.