CADFamily.com

AHBICM Model Reference Manual

2015-05-12T02:44:00.003-07:00

http://www.cadfamily.com/a/EDA_PCB/ARM/AHBICM-Model-Reference-Manual_3777.html

This section provides a summary of the functionality of the model. Note that the
AHBICM model does not model an existing ARM IP, and therefore no comparisons
(functional nor accuracy) against existing hardware are mentioned in this section.
2.1 Functionality
AHBICM is an add-on component to the AMBA AHB slave device. AHBICM connects up
to 8 AHB layers to a single shared slave in order to allow the slave to be used in a multilayer AHB system where multiple AHB layers require access to the same slave. Multilayer AHB designs offer higher bandwidth since multiple layers can access different
slave devices in parallel.

ARM Architecture Reference Manual

2015-05-12T02:44:00.001-07:00

http://www.cadfamily.com/a/EDA_PCB/ARM/ARM-Architecture-Reference-Manual_3772.html

SoC Designer Asynchronous AHB To AHB Bridge Cycle Approximat

2015-05-12T02:43:00.007-07:00

http://www.cadfamily.com/a/EDA_PCB/ARM/SoC-Designer-Asynchronous-AHB-To-AHB-Bridge-Cycle-Approximat_3774.html

Figure 3-1: Connection of 2 AHB subsystems through an AHB2AHBAync bridge
The two AHB subsystems can be running on different clock domains. The
AHB2AHBAsync bridge interface can be used to connect AHB buses, where the
originating bus 1 is running at a clock frequency which is a multiple of that of the target
bus 2 or vice-versa.
Please refer the AMBA design kit TRM for further information.
3.1.1 Fully Functional and Approximate Features
The following features of the AHB2AHBAsync bridge hardware are implemented in the
AHB2AHBAsync bridge model. However the exact behavior of the hardware
implementation is not accurately reproduced because some approximations and
optimizations that have been made for simulation performance:
• 32 or 64 bit data bus.

SoC Designer AHB2Mx Cycle Accurate Model

2015-05-12T02:43:00.005-07:00

http://www.cadfamily.com/a/EDA_PCB/ARM/SoC-Designer-AHB2Mx-Cycle-Accurate-Model_3775.html

2.2 Performance
The performance on the AHB2Mx CA model has been measured using the following
example system provided with the AHB2Mx in the AMBA2 package.
CPU : Intel(R) Xeon™ CPU 3.40GHz
RAM : 2GB
OS : RedHat Enterprise 3.0
Bogomips : 6789.52
The speed of the system was measured by running the AHB stub based system given in
the examples. The system uses an AHB2Mx bridge. The system used, is same as the
one shown in Figure-7-1. The performance on the example system is 45,100 cyclesc.

WRITING DEVICE HEADER FILES

2015-05-12T02:43:00.003-07:00

http://www.cadfamily.com/a/EDA_PCB/ARM/WRITING-DEVICE-HEADER-FILES_3773.html

Useful documents
There are some useful documents to help you write header files.
•IAR code standards (CppGuide.html)
•IAR header file template (EWARM_HeaderTemplate.doc)
Where to start
A few pointers:
1. Find the relevant and up-to-date device user guide (can usually be downloaded from the chip manufacturer’s web
site).
2. Check if IAR Systems already supports more devices from the same family. You can often re-use parts from other
header files belonging to the same chip family.
What is included in a header file?
A header file can be said to consist of 6 sections:
1. A header with the following information:
• Which IAR Compiler and Assembler that the header file designed for
• that the header file is used with ARM IAR C/C++ Compiler and Assembler
• IAR Systems copyright information and the header file creation year
• File revision: $ Revision $
2. Protection against multiple inclusions of the same header file

SoC Designer AHBCache Model

2015-05-12T02:43:00.001-07:00

http://www.cadfamily.com/a/EDA_PCB/ARM/SoC-Designer-AHBCache-Model_3776.html

AHBCache is an AHB compliant generic cache model. The model supports the following
features. This component does not model any specific IP.
The features of the model are :
• Direct mapped and set associative operation with 2, 4, or 8-way set associativity.
• Write back and write through modes.
• Allocate on read and write miss, and write around for write through mode only.
• User selectable critical word first read operation
• AHB compatible slave port for the CPU.
• AHB compatible master port for peripherals and system memory.
• Minimum cache size of 1 KB and a default memory size of 128 KB.
• Configurable access to the memory with width of 32/64 bits.
• Configurable cache line size width with default value of 32 bytes.
• Support for 4 non cacheable areas in the memory.
• Support for using HPROT control bit for cache access.
• Cache replacement using a random replacement policy.
• Model only supports little endianness at this point.

ARM ® Developer Suite Assembler Guide

2015-05-12T02:36:00.003-07:00

http://www.cadfamily.com/a/EDA_PCB/ARM/ARM--Developer-Suite-Assembler-Guide_3793.html

1.1 About the ARM Developer Suite assemblers
ARM Developer Suite (ADS) has:
• a freestanding assembler, armasm
• an optimizing inline assembler built into the C and C++ compilers.
The language that these assemblers take as input is basically the same. However, there
are limitations on what features of the language you can use in the inline assemblers.
Refer to the Mixing C, C++, and Assembly Language chapter in ADS Developer Guide
for further information on the inline assemblers.
The remainder of this book relates mainly to armasm
This chapter provides an introduction to the general principles of writing ARM and
Thumb assembly language. It contains the following sections:

AS950 ARM Applications Library Programmer’s Guide

2015-05-12T02:36:00.001-07:00

http://www.cadfamily.com/a/EDA_PCB/ARM/AS950-ARM-Applications-Library-Programmer-s-Guide_3792.html

This book is organized into the following chapters:
Chapter 1 Introduction
Read this chapter for an introduction to the ARM Applications Library.
Chapter 2 Adaptive Differential Pulse Code Modulation
Read this chapter for details on implementation, and for function
descriptions for adaptive differential pulse code modulation (ADPCM).
Chapter 3 G.711 A-law, µ-law, PCM Conversions
Read this chapter for details on implementation, and for function
descriptions for the G.711 standard for A-law and µ-law conversion of
pulse code modulation (PCM) signals.
Chapter 4 Fast Fourier Transform and Windowing
Read this chapter for details on implementation, and for function
descriptions for the fast Fourier transform (FFT), and implementations of
Hamming and Hanning windows that can be used with the FFT.
Chapter 5 Two-Dimensional Discrete Cosine Transform
Read this chapter for details on implementation, and for function and
macro descriptions for two-dimensional (2D) discrete cosine transform
(DCT).

ARM ® Developer Suite AXD and armsd Debuggers Guide

2015-05-12T02:35:00.005-07:00

http://www.cadfamily.com/a/EDA_PCB/ARM/ARM--Developer-Suite-AXD-and-armsd-Debuggers-Guide_3794.html

1.1 Debugger concepts
This section introduces some of the concepts involved in debugging program images.
1.1.1 Debugger
A debugger is software that enables you to make use of a debug agent in order to
examine and control the execution of software running on a debug target. This part of
the book covers AXD, the ARM eXtended Debugger. The second part of this book
covers armsd, the ARM Symbolic Debugger.
1.1.2 Debug target
At an early stage of product development there might be no hardware. The expected
behavior of the product is simulated by software. Even though you might run this
software on the same computer as the debugger, it is useful to think of the target as a
separate piece of hardware.

ARM ® Developer Suite CodeWarrior® IDE Guide

2015-05-12T02:35:00.003-07:00

http://www.cadfamily.com/a/EDA_PCB/ARM/ARM--Developer-Suite-CodeWarrior-IDE-Guide_3795.html

• See Chapter 9 Configuring a Build Target for information on configuring the
ARM toolchain from within the CodeWarrior IDE.
1.3.1 Online documentation and online help
Documentation for the CodeWarrior IDE for the ARM Developer Suite is available
online as part of the ARM Developer Suite documentation collection. If you have
installed ADS using the default name, select Programs → ARM Developer Suite
v1.2 → Online Books from the Windows Start menu to access the collection.
In addition, the CodeWarrior IDE for the ARM Developer Suite provides
context-sensitive online help. You can access this in either of the following ways:
• Click on the question mark icon at the top right corner of the window. A question
mark appears alongside the mouse pointer. Click with the mouse pointer on the
item that you want help with.

ARM ® Developer Suite Compilers and Libraries Guide

2015-05-12T02:35:00.001-07:00

http://www.cadfamily.com/a/EDA_PCB/ARM/ARM--Developer-Suite-Compilers-and-Libraries-Guide_3796.html

PowerPac -- Getting Started with IAR Embedded Workbench®

2015-05-12T02:32:00.001-07:00

http://www.cadfamily.com/a/EDA_PCB/ARM/PowerPac----Getting-Started-with-IAR-Embedded-Workbench_9975.html

Programming languages

There are two high-level programming languages you can use with the IAR

C/C++ Compiler:

● C, which follows the standard ISO 9899:1990 (commonly known as

ANSI C).

● C++ (depends on your product package). IAR Systems supports two

levels of the C++ language:

● Embedded C++ (EC++), a subset of the C++ programming standard. It

is defined by an industry consortium, the Embedded C++ Technical

committee.

● IAR Extended Embedded C++, with additional features such as full

template support, multiple inheritance (depending on your product

package), namespace support, the new cast operators, as well as the

Standard Template Library (STL).

PowerPac -- 8051 IAR C/C++ Compiler Reference Guide for the

2015-05-12T02:31:00.005-07:00

http://www.cadfamily.com/a/EDA_PCB/ARM/PowerPac----8051-IAR-C-C---Compiler-Reference-Guide-for-the_9973.html

RUNTIME ENVIRONMENT

To create the required runtime environment you should choose a runtime library and set

library options. You may also need to override certain library modules with your own

customized versions.

There are two different sets of runtime libraries provided:

● The IAR DLIB Library, which supports ISO/ANSI C and C++. This library also

supports floating-point numbers in IEEE 754 format and it can be configured to

include different levels of support for locale, file descriptors, multibyte characters,

et cetera. (This library is the default for the C++ language).

● The IAR CLIB Library is a light-weight library, which is not fully compliant with

ISO/ANSI C. Neither does it fully support floating-point numbers in IEEE 754

format nor does it support Embedded C++. (This library is used by default for the C

language).

PowerPac -- ARM® IAR Embedded Workbench マイグレーション

2015-05-12T02:31:00.003-07:00

http://www.cadfamily.com/a/EDA_PCB/ARM/PowerPac----ARM-IAR-Embedded-Workbench---------_9979.html

XLINKと ILINK

XLINKと ILINKは両方とも、 1つ以上の再配置可能オブジェクトファイルと 1

つ以上のオブジェクトライブラリの指定部分を結合し、実行可能イメージを

生成します。 XLINKでは、 IARシステムズのツールによって生成される

UBROFフォーマットのオブジェクトファイルしか入力に使用できません。出

力は、 UBROFまたは XLINKがサポートしているその他の出力フォーマットで

行われます。 ILINKでは、 ELFフォーマットのオブジェクトファイルを入力に

使用し、 ELFフォーマットの実行可能イメージを生成します。

バージョン 4.xでは、コンパイラはコードおよびデータを UBROFのセグメント

に配置します。このセグメントは、 XLINKにより、リンカコマンドファイル

で指定されているディレクティブに従って、メモリに配置されます。リンカ

コマンドファイルは、コマンドラインを拡張したもので、あらゆる XLINKの

コマンドラインオプションを指定することができます。バージョン 5.xでは、

コンパイラはコードおよびデータを ELFのセクションに配置します。

PowerPac -- IAR C/C++ Development Guide Compiling and linkin

2015-05-12T02:31:00.001-07:00

http://www.cadfamily.com/a/EDA_PCB/ARM/PowerPac----IAR-C-C---Development-Guide-Compiling-and-linkin_9977.html

The DLIB runtime

environment

This chapter describes the runtime environment in which an application

executes. In particular, the chapter covers the DLIB runtime library and how

you can modify it—setting options, overriding default library modules, or

building your own library—to optimize it for your application.

The chapter also covers system initialization and termination; how an

application can control what happens before the function main is called, and

how you can customize the initialization.

The chapter then describes how to configure functionality like locale and file

I/O, how to get C-SPY® runtime support, and how to prevent incompatible

modules from being linked together.

PowerPac -- IAR C/C++ 開発ガイドコンパイルおよびリ

2015-05-12T02:30:00.001-07:00

http://www.cadfamily.com/a/EDA_PCB/ARM/PowerPac----IAR-C-C------------------_9978.html

注 : 別のベンダのコンパイラで生成されたモジュールをリンクするには、そ

のベンダの追加サポートライブラリが必要になることがあります。

IAR ILINK リンカでは、オブジェクトファイルに含まれる属性に基づき、使

用する適切な標準 C/C++ ライブラリが自動的に選択されます。インポートさ

れるオブジェクトファイルには、これらのすべての属性が含まれないことが

あります。そのため、このような場合、以下の 1 つ以上の項目を検証して、

ILINK による標準ライブラリの選択をサポートする必要があります。

● 使用する CPU (--cpu リンカオプションを指定 )。

● フル I/O が必要な場合、フルライブラリ設定の標準ライブラリとリンクする

必要がある。

● --no_library_search リンカオプションとの組み合わせが可能な、ランタ

イムライブラリファイルを明示的に指定する。

PowerPac -- AVR® IAR embedded Workbench® IDE Migration

2015-05-12T02:28:00.005-07:00

http://www.cadfamily.com/a/EDA_PCB/ARM/PowerPac----AVR-IAR-em-x-bedded-Workbench-IDE-Migration-G_9983.html

Project file and project setup

The workspace and projects you have created with EWA90 are not compatibe with

EWAVR. If you are using the IAR Embedded Workbench IDE, follow these steps to

convert your project file manually:

1 Start your new version of the AVR IAR Embedded Workbench IDE and create a new

workspace by choosing File>New and then Workspace.

2 Choose Project>Create New Project to create a new project. To add your source code

files, choose Project>Add files. For detailed information about how to create

workspace and projects, see the tutorials available in the AVR IAR Embedded

Workbench User Guide.

PowerPac -- AVR® IAR C/C++ Compiler Reference Guide for Atme

2015-05-12T02:28:00.003-07:00

http://www.cadfamily.com/a/EDA_PCB/ARM/PowerPac----AVR-IAR-C-C---Compiler-Reference-Guide-for-Atme_9982.html

This section contains examples and descriptions of the segments used for storing code,

in other words, functions, and the interrupt vector table. Typically, these segments are

placed in the code memory space (flash).

The -Z command is used for defining all segments in the following examples. The

addresses used in the examples are based on the assumed target system described in the

Table 10, Memory layout of a target system (example), on page 35. Note that because

the described target system is limited in size of code memory space, several segments

supported by the compiler are not applicable for this target system.

For a complete list of all segments, see Summary of segments, page 149.

PowerPac -- IAR Embedded Workbench IDE Advanced RISC Machine

2015-05-12T02:28:00.001-07:00

http://www.cadfamily.com/a/EDA_PCB/ARM/PowerPac----IAR-Embedded-Workbench-IDE-Advanced-RISC-Machine_9981.html

PowerPac -- IAR Linker and Library Tools Reference Guide

2015-05-12T02:26:00.007-07:00

http://www.cadfamily.com/a/EDA_PCB/ARM/PowerPac----IAR-Linker-and-Library-Tools-Reference-Guide_9984.html

PowerPac -- QuickStart Card Upgrading an IAR Powerpac Produc

2015-05-12T02:26:00.005-07:00

http://www.cadfamily.com/a/EDA_PCB/ARM/PowerPac----QuickStart-Card-Upgrading-an-IAR-Powerpac-Produc_9985.html

Upgrading the license server

Product upgrades for network licenses might come with an

upgrade CD for the license server software. If that is the case,

perform the following steps on the same computer where you

have the current license server software installed.

Note: This will shut down the license server and make all

network licenses temporarily unavailable.

1 First uninstall the current version of the license server

software by selecting the appropriate Uninstall IAR

License Server item from the Start menu.

2 Insert the installation CD. The installation program

should start automatically. If it does not, run the

a u t o r u n . e x e program from the CD.

PowerPac -- QuickStart Card Installing IAR PowerPac™ using

2015-05-12T02:26:00.003-07:00

http://www.cadfamily.com/a/EDA_PCB/ARM/PowerPac----QuickStart-Card-Installing-IAR-PowerPac-using_9987.html

The installation procedure

The installation of IAR PowerPac™ is a three-stage

procedure:

A First you install the IAR Systems software using a

QuickStart key, which allows you to use the product

for 30 days.

B During this 30-day period, you must activate your

license by registering the product with IAR Systems.

Within 5 business days, you will receive a permanent

key for your license.

C Finally you install the permanent key. This opens up the

product for permanent usage.

Follow the detailed steps below for each stage.

A. Installing the software

1 Remove any dongles.

2 Insert the installation CD. The installation program

should start automatically. If it does not, run the

autorun.exe program from the CD.

PowerPac -- QuickStart Card Installing IAR embedded Workb

2015-05-12T02:26:00.001-07:00

http://www.cadfamily.com/a/EDA_PCB/ARM/PowerPac----QuickStart-Card-Installing-IAR-em-x-bedded-Workb_9988.html

The installation procedure

The IAR Embedded Workbench® installation is a three-stage

procedure:

A First you install the IAR Systems software using a

QuickStart key, which allows you to use the product

for 30 days.

B During this 30-day period, you must activate your

license by registering the product with IAR Systems.

Within 5 business days, you will receive a permanent

key for your license.

C Finally you install the permanent key. This opens up the

product for permanent usage.

Follow the detailed steps below for each stage.

A. Installing the software

1 Remove any dongles.

2 Insert the IAR Embedded Workbench installation CD.

The installation program should start automatically. If it

does not, run the autorun.exe program from the CD.

3 Select Install IAR Embedded Workbench®.

4 You must accept the license agreement when prompted.

By clicking the Accept button, you confirm that you

have read and understood the license agreement.

PowerPac -- QuickStart Card

2015-05-12T02:24:00.009-07:00

http://www.cadfamily.com/a/EDA_PCB/ARM/PowerPac----QuickStart-Card_9989.html

Installing IAR PowerPac™ for MSP430

The installation of IAR PowerPac for MSP430 requires that a compatible version of IAR

Embedded Workbench for MSP430 is installed on the PC. Check the file readme.htm

on the installation CD for information about compatible versions of IAR Embedded

Workbench for MSP430.

Step by step installation

1. Shut down IAR Embedded Workbench for MSP430.

2. Insert the IAR PowerPac for MSP430 installation CD. The installation program

should start automatically. If it does not, start autorun.exe from the CD.

3. Select Install IAR PowerPac™ for MSP430.

4. You must accept the license agreement when prompted. By selecting I accept the

terms of the license agreement, you confirm that you have read and understood

the license agreement.

PowerPac -- IAR PowerPac™ USB User Guide

2015-05-12T02:24:00.007-07:00

http://www.cadfamily.com/a/EDA_PCB/ARM/PowerPac----IAR-PowerPac-USB-User-Guide_9992.html

START WITHOUT USING AN EXAMPLE PROJECT

The best and easiest way to get started is to take a look at the IAR PowerPac USB example projects. IAR PowerPac

USB provides USB device drivers for some USB controllers. Using one of these drivers makes it easy to get the target

up and running. Refer to section Available USB drivers on page 93 for a list of all supported devices and their valid

identifiers.

If you are going to use IAR PowerPac USB with your own hardware, you might have to write your own device driver.

A driver template for the implementation is supplied. The template is located in

the<$TOOLCHAIN_DIR$>\PowerPac\USB\Example\Driver\ directory. If you do not want to start with one of the

supplied example projects, you have to perform the following steps to get the target system to behave like a mass storage

device or generic bulk device on the USB bus: