DOCSLIB.ORG

Reference Manual ARM DUI 0020D Contents

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

ARM Software Development Toolkit Version 2.0 Reference Manual Document Number: ARM DUI 0020D Issued: June 1995 Copyright Advanced RISC Machines Ltd (ARM) 1995 Beta Draft EUROPE JAPAN USA Advanced RISC Machines Limited Advanced RISC Machines K.K. ARM USA Fulbourn Road KSP West Bldg, 3F 300D, 3-2-1 Sakado, Suite 5, 985 University Avenue Cherry Hinton Takatsu-ku, Kawasaki-shi Los Gatos Cambridge CB1 4JN Kanagawa, 213 Japan California 95030 Telephone: +44 1223 400400 Telephone: +81 44 850 1301 Telephone: +1 408 399 5199 Facsimile: +44 1223 400410 Facsimile: +81 44 850 1308 Facsimile: +1 408 399 8854 Email: [email protected] Email: [email protected] Email: [email protected] Proprietary Notice ARM, the ARM Powered logo and EmbeddedICE are trademarks of Advanced RISC Machines Ltd. Neither the whole nor any part of the information contained in, or the product described in, this manual may be adapted or reproduced in any material form except with the prior written permission of the copyright holder. The product described in this manual is subject to continuous developments and improvements. All particulars of the product and its use contained in this manual are given by ARM in good faith. However, all warranties implied or expressed, including but not limited to implied warranties or merchantability, or fitness for purpose, are excluded. This manual is intended only to assist the reader in the use of the product. ARM Ltd shall not be liable for any loss or damage arising from the use of any information in this manual, or any error or omission in such information, or any incorrect use of the product. Change Log Issue Date By Change Prelim1 Nov 94 BJH/EH Created B01 Jan 95 AW Changes to reflect review comments; change of title B00 Feb 95 AW B01 comments incorporated C April 95 PB Updated, profiler chapter added D June 95 BJH/PO Edited Beta Draft ii Reference Manual ARM DUI 0020D Contents 1 Introduction 1-1 1.1 About This Manual 1-2 1.2 Release Components 1-3 1.3 Feedback 1-4 2 C Compiler 2-1 2.1 Introduction 2-2 2.2 About the ARM C Compiler 2-3 2.3 Invoking the Compiler 2-4 2.4 Using the ARM C Compiler 2-5 2.5 Keyword Options 2-8 2.6 Flag Options 2-10 2.7 Processor Selection Options 2-16 2.8 Implementation Details 2-17 2.9 Standard Implementation Definition 2-24 2.10 Portability 2-37 2.11 ANSI C vs K&R C 2-42 2.12 PCC Compatibility Mode 2-47 2.13 Machine-Specific Features 2-50 2.14 Floating Point Support 2-56 2.15 ARM/Thumb interworking 2-57 Reference Manual Contents-1 ARM DUI 0020D Contents 3 Assembler 3-1 3.1 Overview 3-2 3.2 Command Line Options 3-2 3.3 Assembly Language Overview 3-6 3.4 Directives 3-11 3.5 Symbolic Capabilities 3-18 3.6 Expressions and Operators 3-21 3.7 Conditional Assembly—[, | and ] 3-24 3.8 Repetitive Assembly—WHILE and WEND 3-24 3.9 Macros 3-25 4 ARM Instruction Set 4-1 4.1 The ARM Instruction Set—Overview 4-2 4.2 Branch Instructions—B and BL 4-7 4.3 Data Processing Instructions 4-8 4.4 PSR Transfer—MSR and MRS 4-11 4.5 Unsigned Word/Byte Data Transfer—LDR and STR 4-12 4.6 Halfword and Signed Data Transfer: LDRH, STRH, LDRSB, LDRSH4-13 4.7 Block Data Transfer—LDM and STM 4-14 4.8 Multiply Instructions—MUL, MLA 4-16 4.9 Long Multiply Instructions—MULL, MLAL 4-17 4.10 Single Data Swap—SWP 4-17 4.11 ARM to Thumb State Exchange—BX 4-18 4.12 Software Interrupt/Supervisor Call—SWI 4-19 4.13 Pseudo-Instructions—ADR and NOP 4-20 4.14 Generic Coprocessor Instructions 4-21 4.15 Floating Point Instructions 4-23 5 Thumb Instruction Set 5-1 5.1 Thumb Instruction Set—Overview 5-2 5.2 Branch Instructions—B and BL 5-5 5.3 Data-processing Instructions 5-7 5.4 Single Data Transfer Instructions—LDR and STR 5-11 5.5 Block Data Transfer Instructions—LDMIA and STMIA 5-14 5.6 Stack Operations—PUSH and POP 5-15 5.7 Thumb to ARM State Exchange—BX 5-16 5.8 Software Interrupt 5-16 5.9 Pseudo Instructions — MOV and NOP 5-17 Contents-2 Reference Manual ARM DUI 0020D Contents 6 Linker 6-1 6.1 Introduction 6-2 6.2 Using the Linker 6-3 6.3 Library Module Inclusion 6-10 6.4 Area Placement and Sorting Rules 6-11 6.5 Linker Pre-Defined Symbols 6-12 6.6 The Handling of Relocation Directives 6-13 6.7 ARM Object Format 6-15 6.8 Plain Binary Format 6-16 6.9 ARM Image Format 6-16 6.10 Extended Intellec Hex Format (IHF) 6-18 6.11 ARM Shared Library Format 6-18 6.12 Overlays 6-28 6.13 The Overlay Manager 6-32 6.14 Scatter Loading 6-41 7 Symbolic Debugger 7-1 7.1 About armsd 7-2 7.2 Line-Speed Negotiation 7-2 7.3 Command-line Options 7-3 7.4 Command Language 7-6 7.5 Specifying Source-level Objects 7-6 7.6 Accessing Variables 7-11 7.7 Symbols 7-14 7.8 Accessing and Executing Programs 7-15 7.9 Controlling Execution 7-17 7.10 Program Context 7-22 7.11 Low-level Debugging 7-23 7.12 Coprocessor Support 7-30 7.13 Miscellaneous Commands 7-32 7.14 Automatic Command Execution on Startup 7-35 7.15 Performance simulation using armsd 7-35 7.16 Semihosting under EmbeddedICE 7-41 8 ARM Profiler 8-1 8.1 About armprof 8-2 8.2 Command-line Options 8-2 8.3 Profiler output 8-3 9 ARM Librarian 9-1 9.1 About armlib 9-2 9.2 Command Line Options 9-2 Reference Manual Contents-3 ARM DUI 0020D Contents 10 ARM Object Format Decoder 10-1 10.1 About decaof 10-2 10.2 Command-line Options 10-2 11 ANSI to PCC C Translator 11-1 11.1 About topcc 11-2 11.2 Command Line Options 11-2 11.3 Translation Details 11-3 11.4 Issues with topcc 11-4 12 ARM Tool Reconfiguration Utility 12-1 12.1 About reconfig 12-2 12.2 Tool Reconfiguration 12-2 12.3 Using reconfig 12-8 12.4 Reconfiguration Errors 12-10 13 ARM make Utility 13-1 13.1 About armmake 13-2 13.2 Command-line Options 13-3 13.3 Makefile Format for armmake 13-4 13.4 Command Execution 13-6 13.5 Advanced Features 13-7 13.6 Miscellaneous Features 13-9 14 ARMulator 14-1 14.1 About the ARMulator 14-2 14.2 Modelling an ARM-Based System 14-2 14.3 ARMulator Release Components 14-3 14.4 Building an ARMulator Variant 14-4 14.5 Memory Interfacing 14-4 14.6 ANSI C Library 14-5 14.7 The ARMulator Environment 14-5 14.8 Memory Models 14-6 14.9 Co-processor Modelling 14-12 14.10 Modelling an Operating System or Low Level Monitor 14-16 14.11 Accessing ARMulator’s State 14-17 14.12 ARMulator Signals 14-18 14.13 Processor Selection 14-18 14.14 Event Handling 14-18 14.15 The ARM Debug Monitor 14-19 Contents-4 Reference Manual ARM DUI 0020D Contents 15 C Library 15-1 15.1 An Introduction to the Run-Time Libraries 15-2 15.2 Porting the ARM C Library 15-3 15.3 Source Organisation 15-4 15.4 Building a Target-Specific Library 15-6 15.5 Retargeting the Library 15-7 15.6 Details of Target-Dependent Code 15-10 16 Software Floating Point 16-1 16.1 Introduction 16-2 16.2 The ARM Floating Point Library 16-2 16.3 Usage 16-3 16.4 Interworking Between hardfp and softfp Systems 16-3 16.5 Calling the Floating Point Library from Assembler 16-3 16.6 Controlling Floating Point Exceptions from C 16-6 16.7 Formats 16-10 17 Demon 17-1 17.1 Introduction 17-2 17.2 Target Memory Map 17-3 17.3 Standard Monitor SWIs 17-4 17.4 The Implementation of Demon for the PIE Card 17-8 18 EmbeddedICE 18-1 18.1 The Effect of EmbeddedICE on the Debuggee 18-2 18.2 Vector Breakpoints 18-2 18.3 Configuration Data 18-2 18.4 Accessing the EmbeddedICE Macrocell Directly 18-3 18.5 Floating Point and Other Coprocessors 18-4 19 ARM Procedure Call Standard 19-1 19.1 Introduction 19-2 19.2 The ARM Procedure Call Standard 19-3 19.3 APCS Variants 19-11 19.4 C Language Calling Conventions 19-14 19.5 Function Entry 19-16 19.6 The APCS in Non-User ARM Modes 19-25 Reference Manual Contents-5 ARM DUI 0020D Contents 20 Thumb Procedure Call Standard 20-1 20.1 Introduction 20-2 20.2 Register Names 20-3 20.3 The Stack 20-4 20.4 Control Arrival and Return 20-6 20.5 C Language Calling Conventions 20-8 20.6 Function Entry 20-9 20.7 Function Exit 20-12 21 File Formats 21-1 21.1 ARM Image Format 21-2 21.2 ARM Object Format 21-10 21.3 ARM Object Library Format 21-26 21.4 ARM Symbolic Debug Table Format 21-32 22 Remote Debugging 22-1 22.1 ARM Remote Debug Interface 22-2 22.2 ARM Remote Debug Protocol 22-21 Contents-6 Reference Manual ARM DUI 0020D 1 Introduction This chapter introduces the ARM Software Development Toolkit and its documentation.
Recommended publications
  • ARM Software Development Toolkit Version 2.11 User Guide

    ARM Software Development Toolkit Version 2.11 User Guide

    211ug.book : SDT_UG_Front_cover.fm Page i Sunday, June 1, 1997 12:21 PM ARM Software Development Toolkit Version 2.11 User Guide Document number: ARM DUI 0040C Issued: May 1997 Copyright Advanced RISC Machines Ltd (ARM) 1996 Beta Draft Beta ENGLAND GERMANY Advanced RISC Machines Limited Advanced RISC Machines Limited Fulbourn Road Otto-Hahn Str. 13b Cherry Hinton 85521 Ottobrunn-Riemerling Cambridge CB1 4JN Munich UK Germany Telephone: +44 1223 400400 Telephone: +49 89 608 75545 Facsimile: +44 1223 400410 Facsimile: +49 89 608 75599 Email: [email protected] Email: [email protected] JAPAN USA Advanced RISC Machines K.K. ARM USA Incorporated KSP West Bldg, 3F 300D, 3-2-1 Sakado Suite 5 Takatsu-ku, Kawasaki-shi 985 University Avenue Kanagawa Los Gatos 213 Japan CA 95030 USA Telephone: +81 44 850 1301 Telephone: +1 408 399 5199 Facsimile: +81 44 850 1308 Facsimile: +1 408 399 8854 Email: [email protected] Email: [email protected] World Wide Web address: http://www.arm.com Partner Confidential - Final Draft 211ug.book : SDT_UG_Front_cover.fm Page ii Sunday, June 1, 1997 12:21 PM Proprietary Notice ARM, the ARM Powered logo and EmbeddedICE are trademarks of Advanced RISC Machines Ltd. Neither the whole nor any part of the information contained in, or the product described in, this manual may be adapted or reproduced in any material form except with the prior written permission of the copyright holder. The product described in this manual is subject to continuous developments and improvements. All particulars of the product and its use contained in this manual are given by ARM in good faith.
  • The Helios Operating System

    The Helios Operating System

    The Helios Operating System PERIHELION SOFTWARE LTD May 1991 COPYRIGHT This document Copyright c 1991, Perihelion Software Limited. All rights reserved. This document may not, in whole or in part be copied, photocopied, reproduced, translated, or reduced to any electronic medium or machine readable form without prior consent in writing from Perihelion Software Limited, The Maltings, Charlton Road, Shepton Mallet, Somerset BA4 5QE. UK. Printed in the UK. Acknowledgements The Helios Parallel Operating System was written by members of the He- lios group at Perihelion Software Limited (Paul Beskeen, Nick Clifton, Alan Cosslett, Craig Faasen, Nick Garnett, Tim King, Jon Powell, Alex Schuilen- burg, Martyn Tovey and Bart Veer), and was edited by Ian Davies. The Unix compatibility library described in chapter 5, Compatibility,im- plements functions which are largely compatible with the Posix standard in- terfaces. The library does not include the entire range of functions provided by the Posix standard, because some standard functions require memory man- agement or, for various reasons, cannot be implemented on a multi-processor system. The reader is therefore referred to IEEE Std 1003.1-1988, IEEE Stan- dard Portable Operating System Interface for Computer Environments, which is available from the IEEE Service Center, 445 Hoes Lane, P.O. Box 1331, Pis- cataway, NJ 08855-1331, USA. It can also be obtained by telephoning USA (201) 9811393. The Helios software is available for multi-processor systems hosted by a wide range of computer types. Information on how to obtain copies of the Helios software is available from Distributed Software Limited, The Maltings, Charlton Road, Shepton Mallet, Somerset BA4 5QE, UK (Telephone: 0749 344345).
  • ARM Command Line Workbook

    ARM Command Line Workbook

    ARM Command Line Workbook CS160 Computer Organization Version 1.1 October 27th, 2002 Revised Fall 2005 ARM University Program Version 1.0 January 14, 1997 ARM Command Line Workbook Introduction Aim This workbook provides the student with a basic understanding of the facilities provided by the ARM Toolkit for command line users. Note: For all of the command line tools provided with the toolkit it is possible to get on- line help on the command line parameters by specifying the toolname followed by -help. Prerequisites Before getting started, you will need to add the ARM tools to your command path. Make the following change to the ~/.zsh_files/.zshrc file: • export PATH="$PATH:/pkgs/arm202u/bin" Next, you will need to add an environment variable so that the ARM compiler knows where to find the appropriate libraries. Make the following change to the ~/.zshrc file: • export ARMLIB="/pkgs/arm202u/lib" Ask the GTAs for help if you don’t know how to do this. When done, issue the commands: source ~/.zshrc ~cs160/bin/armsetup.pl The latter will create a hierarchy of subdirectories and files in a directory called arm within your cs160 directory. The reference /cmdline/hello.c thus should be read as ~/arm/cmdline/hello.c Compiler The ‘Hello World’ example program is a simple C program which calls a subroutine. This program file can be found as /cmdline/hello.c #include <stdio.h> /* Declare subroutine before used by main */ void subroutine (void); int main() { printf("Hello World from main\n"); subroutine(); printf("And Goodbye from main\n"); return 0; } /* Define subroutine */ void subroutine() { printf("Hello from subroutine\n"); } 2 ARM Command Line Workbook Exercise 1.1 Compile this program with the ARM C compiler type armcc -g hello.c The C compiler automatically invokes the linker to produce an executable with the same name as the C module but with no file extension.
  • Updated Virtualrpc Components for RISC OS 6

    Updated Virtualrpc Components for RISC OS 6

    ne of the main things that keeps me using my Risc PC is the versatility of the operating system - mainly due to it’s universal draw file format. For Oinstance I construct the centre pages in Artworks as this now has excellent PDF export facilities. However for proofing the magazine before it gets sent to the printers I like to do a printout to see if everything works properly. Because Artworks now can deal with multiple pages it is very easy to save each page either as an Artworks file or Draw file directly into the magazine’s Ovation Pro file by dragging and dropping. A two second job! Other computer platforms don’t generally have this facility of moving files directly into open application windows. Generally to move a file to another application you have to use the dreaded ‘save as’ filer window - choose a suitable format - navigate to where you need to save the file - save it - go to the other application - open a filer window - navigate to the saved file - open it in the new application. If you need to transfer a different file type you generally have to go through all that palaver again. Two seconds on RISC OS, thirty seconds on OS X or Windows. Draw is a great program with no real equivalent on a PC or Mac. For instance it can be put to good use in music for constructing objects the original program can’t do. I use the Sibelius music setting program on both RISC OS and Windows. The RISC OS still has one or two advantages over the PC version, one of which is it’s ability to export to Draw.
  • Occam User Group

    Occam User Group

    for all users of occam and the transputer N912 January 1990 Contents EDITORIAL 2 Contributions to the newsletter 3 Occam user group publications 3 North American transputer users group publications 4 FORTHCOMING 4 Twelfth occam user group technical meeting 4 North American transputer users group spring meeting 5 Third Japanese transputer/ occam international conference 5 Thirteenth occam user group technical meeting 6 North American transputer users group fall meeting 6 Transputing 1991 7 REPORTS 9 Inaugural meeting of the occam user group: Latin America 9 Eleventh occam user group technical meeting 10 Why did the transputer cross The Pond? 14 Second seminar of the Swedish transputer user group 15 continued on back cover Meiko In-Sun Computing Surface Hardware (see page 98) occam is a trade mark of the INMOS Group of Companies 2 occam user group newsletteT EDITORIAL ~ ~ New groups seem to be springing up all around the world; this issue of nan the newsletter carries contact addresses for the first time for groups in U:E ~ Sweden and Latin America. We have contributions from as far afield as Brazil, the Basque country, and Bristol. It is all here: from exotic hardware (see for example pages 19, 82, 98 and many of the product announcements) to expressions of concern that software should be as unexciting as possible (see pages 22, 27). I would particularly like to draw your attention to the initiative to promote the occam language (see page 84); and to the CODE system from C-DAC (see pages 86 and18), an impromptu presentation of which stole the show in the exhibition at the OUG technical meeting in Edinburgh.
  • Chapter 13 ARM Image Format

    Chapter 13 ARM Image Format

    Chapter 13 ARM Image Format This chapter describes the ARM Image Format (AIF). It contains the following sections: • Overview of the ARM Image Format on page 13-2 • AIF variants on page 13-3 • The layout of AIF on page 13-4. ARM DUI 0041C Copyright © 1997 and 1998 ARM Limited. All rights reserved. 13-1 ARM Image Format 13.1 Overview of the ARM Image Format ARM Image Format (AIF) is a simple format for ARM executable images, consisting of: • a 128-byte header • the image code • the image initialized static data. An AIF image is capable of self-relocation if it is created with the appropriate linker options. The image can be loaded anywhere and it will execute where it is loaded. After an AIF image has been relocated, it can create its own zero-initialized area. Finally, the image is entered at the unique entry point. 13-2 Copyright © 1997 and 1998 ARM Limited. All rights reserved. ARM DUI 0041C ARM Image Format 13.2 AIF variants There are three variants of AIF: Executable AIF Executable AIF can be loaded at its load address and entered at the same point (at the first word of the AIF header). It prepares itself for execution by relocating itself if required and setting to zero its own zero-initialized data. The header is part of the image itself. Code in the header ensures that the image is properly prepared for execution before being entered at its entry address. The fourth word of an executable AIF header is: BL entrypoint The most significant byte of this word (in the target byte order) is 0xeb.
  • ARM Developer Suite Version 1.0.1

    ARM Developer Suite Version 1.0.1

    ARM Developer Suite Version 1.0.1 Tools Guide Copyright © 1999,2000 ARM Limited. All rights reserved. ARM DUI 0067B Copyright © 1999 and 2000 ARM Limited. All rights reserved. Release Information The following changes have been made to this book. Change History Date Issue Change October 1999 A Release 1.0 March 2000 B Release 1.0.1 Proprietary Notice ARM, the ARM Powered logo, Thumb, and StrongARM are registered trademarks of ARM Limited. The ARM logo, AMBA, Angel, ARMulator, EmbeddedICE, ModelGen, Multi-ICE, PrimeCell, ARM7TDMI, ARM7TDMI-S, ARM9TDMI, ARM9E-S, ETM7, ETM9, TDMI, STRONG, are trademarks of ARM Limited. All other products or services mentioned herein may be trademarks of their respective owners. Neither the whole nor any part of the information contained in, or the product described in, this document may be adapted or reproduced in any material form except with the prior written permission of the copyright holder. The product described in this document is subject to continuous developments and improvements. All particulars of the product and its use contained in this document are given by ARM in good faith. However, all warranties implied or expressed, including but not limited to implied warranties of merchantability, or fitness for purpose, are excluded. This document is intended only to assist the reader in the use of the product. ARM Limited shall not be liable for any loss or damage arising from the use of any information in this document, or any error or omission in such information, or any incorrect use of the product. ii Copyright © 1999,2000 ARM Limited.
  • USENIX Winter Conference

    USENIX Winter Conference

    February ! 990 The Australian UNIX* systems User Group Newsletter Volume 11 Number 1 February 1990 CONTENTS AUUG General Information ..................... 4 Editorial ........................... 5 Secretary’s Letter ......................... 7 AUUG Inc 1990 Annual Elections -- Nomination Form ............. 8 Western Australian UNIX systems Group Information ............. 9 SESSPOOLE Information ...................... 10 AUUG Book Club Reviews ...................... 11 AUUG Book Club Order Form .................... 18 X Technical Bibliography ...................... 19 Commonly Asked X Questions ..................... 25 AUUG Institutional Members ..................... 42 From the EUUG Newsletter - Volume 9 Number 4 .............. 44 Editorial ......................... 45 How To Protect Your Software .................. 46 The EUUG Conference Mailing System ................ 54 UNIX in Czechoslovakia .................... 57 EUUG Munich Conference, Spring 1990 ................ 60 USING -- UNIX Systems Information Networking Group .......... 64 EUUG Executive Report .................... 67 Report From ICEUUG ..................... 69 News From The Netherlands ................... 71 UKUUG Report ....................... 74 USENIX Association News For EUUG Members ............. 76 USENIX Winter Conference ................... 78 EUnet Growing Up In Spain ................... 81 EUUG Software Distribution ................... 88 ISO/IEC JTC1/SC22AVG15 (POSIX) Meeting October, 1989 ......... 92 The OPEN LOOKTM Graphical User Interface .............. 98
  • AMX 4-ARM Tool Guide KADAK I Copyright © 1997-2007 by KADAK Products Ltd

    AMX 4-ARM Tool Guide KADAK I Copyright © 1997-2007 by KADAK Products Ltd

    ® AMX™ 4-ARM Tool Guide First Printing: August 1, 1997 Last Printing: November 1, 2007 Copyright © 1997 - 2007 KADAK Products Ltd. 206 - 1847 West Broadway Avenue Vancouver, BC, Canada, V6J 1Y5 Phone: (604) 734-2796 Fax: (604) 734-8114 TECHNICAL SUPPORT KADAK Products Ltd. is committed to technical support for its software products. Our programs are designed to be easily incorporated in your systems and every effort has been made to eliminate errors. Engineering Change Notices (ECNs) are provided periodically to repair faults or to improve performance. You will automatically receive these updates during the product's initial support period. For technical support beyond the initial period, you must purchase a Technical Support Subscription. Contact KADAK for details. Please keep us informed of the primary user in your company to whom update notices and other pertinent information should be directed. Should you require direct technical assistance in your use of this KADAK software product, engineering support is available by telephone, fax or e-mail. KADAK reserves the right to charge for technical support services which it deems to be beyond the normal scope of technical support. We would be pleased to receive your comments and suggestions concerning this product and its documentation. Your feedback helps in the continuing product evolution. KADAK Products Ltd. 206 - 1847 West Broadway Avenue Vancouver, BC, Canada, V6J 1Y5 Phone: (604) 734-2796 Fax: (604) 734-8114 e-mail: [email protected] AMX 4-ARM Tool Guide KADAK i Copyright © 1997-2007 by KADAK Products Ltd. All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual or otherwise, without the prior written permission of KADAK Products Ltd., Vancouver, B.C., CANADA.
  • Developers' Newsletter No 36 December 1994

    Developers' Newsletter No 36 December 1994

    Developers' Newsletter No 36 December 1994 Contents: General News Greetings Order form Voicemail 1995 Subscriptions Product Directory BETT From our Australian Office Licences for Replay decompression software Training for Developers Technical News Aquarius Beta Use of the Territory Manager OS_SpriteOp 52 Put Sprite Grey Scaled Wimp_TextOp SWI Cache_Flush Printer HileCore Task shutdown protocol Risc PC Make Modes Application Notes PRM Errors and Omissions Developers' Disc 36 contents News from other sources Hrom Iota Software Aspex Software Enclosures Developers' disc 36 customers and that reflects badly on the whole Acorn General News community. Greetings For those of you with access to Impression Style, on Developers' Disc 36 you will find a copy of the Product We send you greetings from all of us at Acorn Developer Directory Information sheet (both sides) so that you can Support at the end of 1994. We wish you a successful print one whenever you need to. Please use this version 1995. rather than any earlier ones. Order form A Drawfile of the Registered Developers' Order Form is on BETT Developers' Disc 36. Please print out the form and complete Don't forget the BETT Show, the major Educational one each time you make an order and do not include either technology show in the UK, which is to be held at Olympia Special Offers or items supplied directly Developer Support in London from 11-14th January 1995. on the same order form. Don't forget to send payment with your order which should be clearly marked on the outside of From our Australian Office the envelope 'FAO Developer Support'.
  • Arm System-On-Chip Architecture.Pdf

    Arm System-On-Chip Architecture.Pdf

    Preface Aims This book introduces the concepts and methodologies employed in designing a system-on-chip (SoC) based around a microprocessor core and in designing the microprocessor core itself. The principles of microprocessor design are made con- crete by extensive illustrations based upon the ARM. The aim of the book is to assist the reader in understanding how SoCs and micro- processors are designed and used, and why a modern processor is designed the way that it is. The reader who wishes to know only the general principles should find that the ARM illustrations add substance to issues which can otherwise appear somewhat ethereal; the reader who wishes to understand the design of the ARM should find that the general principles illuminate the rationale for the ARM being as it is. Other microprocessor architectures are not described in this book. The reader who wishes to make a comparative study of architectures will find the required informa- tion on the ARM here but must look elsewhere for information on other designs. Audience The book is intended to be of use to two distinct groups of readers: • Professional hardware and software engineers who are tasked with designing an SoC product which incorporates an ARM processor, or who are evaluating the ARM for a product, should find the book helpful in their duties. Although there is considerable overlap with ARM technical publications, this book provides a broader context with more background. It is not a substitute for the manufac turer's data, since much detail has had to be omitted, but it should be useful as an introductory overview and adjunct to that data.
  • ARM Developer Suite Getting Started

    ARM Developer Suite Getting Started

    ARM® Developer Suite Version 1.2 Getting Started Copyright © 1999-2001 ARM Limited. All rights reserved. ARM DUI 0064D ARM Developer Suite Getting Started Copyright © 1999-2001 ARM Limited. All rights reserved. Release Information The following changes have been made to this book. Change History Date Issue Change October 1999 A Release 1.0 March 2000 B Release 1.0.1 October 2000 C Release 1.1 November 2001 D Release 1.2 Proprietary Notice Words and logos marked with ® or ™ are registered trademarks or trademarks owned by ARM Limited. Other brands and names mentioned herein may be the trademarks of their respective owners. Neither the whole nor any part of the information contained in, or the product described in, this document may be adapted or reproduced in any material form except with the prior written permission of the copyright holder. The product described in this document is subject to continuous developments and improvements. All particulars of the product and its use contained in this document are given by ARM in good faith. However, all warranties implied or expressed, including but not limited to implied warranties of merchantability, or fitness for purpose, are excluded. This document is intended only to assist the reader in the use of the product. ARM Limited shall not be liable for any loss or damage arising from the use of any information in this document, or any error or omission in such information, or any incorrect use of the product. ii Copyright © 1999-2001 ARM Limited. All rights reserved. ARM DUI 0064D Contents ARM Developer Suite Getting Started Preface About this book .............................................................................................