Datasheet

Differences
2-30 Copyright © 1999-2001 ARM Limited. All rights reserved. ARM DUI 0064D
• New configuration mechanism
• ARMulator byte order set from the debuggers on page 2-31
• Changes to default behavior on page 2-31.
License management
The ARMulator is now license-managed at the model level, through FLEXlm.
Integrated ARMulator and new processor models
The ARMulator has been restructured to provide a single interface to all processor
models that is easier to use and modify. All ARMulator models are accessible through
a single target DLL (
armulate.dll ). The BATS DLL is not supplied with ADS 1.1. The
ARMulator is now supplied as a shared object under UNIX.
The ARMulator has been upgraded to support the latest processors. It provides new
models of:
• the ARM9 (ARM946E and ARM966E)
• ARM10, including VFP10
• XScale.
New API for memory models
The ARMulator provides a new memory model interface that enables you to add
memory and peripheral models without rebuilding the complete ARMulator. The
ARMulator rebuild kit has been replaced with the ARMulator Extension Kit.
New configuration mechanism
The
armul.cnf configuration mechanism has been split to separate features that can be
edited and those that cannot. The ARMulator recognizes two file extensions:
• Files ending
.dsc , such as armulate.dsc , are supplied with ARMulator DLLs.
They describe the cores and peripherals the DLL can emulate. They are not
intended to be edited.
• Files ending
.ami are intended to be edited. A .ami file can define one or more
named systems, for selection by the
-cpu option in armsd or a dialog box in a GUI
debugger.
The
armulate.dll model looks at environment variables ARMDLL and ARMCONF for paths to
search for its configuration files. It loads all the files with those extensions it can find
(on the paths specified by the
ARMDLL and ARMCONF environment variables). If it cannot
find any, it issues an error message and fails to initialize.