ARM VERSION 1.2 Datasheet download pdf (Page 12)

Introduction

1.1 Debug target overview

You can debug your prototype software using either of the debuggers described in AXD

and armsd Debuggers Guide, or a third party debugger. The debugger runs on your host

computer. It is connected to a target system that your prototype software runs on.

Your target system can be any one of:

• a software simulator, ARMulator, simulating ARM hardware

• an ARM evaluation or development board

• a third-party ARM-based development board

• ARM-based hardware of your own design.

1.1.1 ARMulator

A software simulator, ARMulator, is supplied with ADS. ARMulator runs on the same

host computer as the debugger. It includes facilities for communication with the

debugger.

ARMulator is an instruction set simulator. It simulates the instruction sets and

architecture of ARM processors, together with a memory system and peripherals. You

can extend it to simulate other peripherals and custom memory systems (see Chapter 3

Writing ARMulator models).

You can use ARMulator for software development and for benchmarking

ARM-targeted software. It models the instruction set and counts cycles. There are limits

to the accuracy of benchmarking, see Accuracy on page 2-2.

This book is mainly concerned with the ARMulator.

1.1.2 Hardware targets

You can use one of three different arrangements for a debugger to communicate with a

hardware target system:

• You can run a debug monitor, such as Angel or RealMonitor, on the target system,

in addition to your application code. The debug monitor handles communication

with the debugger.

• If your target processor has EmbeddedICE

logic, you can set:

— breakpoints in your code

— watchpoints in memory.

1 2 ... 7 8 9 10 11 12 13 14 15 16 17 ... 175 176

No comments

ARM VERSION 1.2 Datasheet Page 12