Summary of the content on the page No. 1
®
™
AMX 68000 Target Guide
First Printing: April 15, 1994
Last Printing: March 1, 2005
Copyright © 1994 - 2005
KADAK Products Ltd.
206 - 1847 West Broadway Avenue
Vancouver, BC, Canada, V6J 1Y5
Phone: (604) 734-2796
Fax: (604) 734-8114
Summary of the content on the page No. 2
Summary of the content on the page No. 3
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 Suppo
Summary of the content on the page No. 4
Copyright © 1994-2005 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. DISCLAIMER KADAK Products Ltd. makes no representations or warranties with respect to th
Summary of the content on the page No. 5
AMX 68000 TARGET GUIDE Table of Contents Page 1. Getting Started with AMX 68000 1 1.1 Introduction ........................................................................................ 1 1.2 AMX Files .......................................................................................... 2 1.3 AMX Nomenclature ........................................................................... 4 1.4 AMX 68000 Target Specifications ..................................................... 5 1.
Summary of the content on the page No. 6
AMX 68000 TARGET GUIDE Table of Contents (Cont'd) Appendices Page Appendix A. Target Parameter File Specification A-1 A.1 Target Parameter File Structure ......................................................... A-1 A.2 Target Parameter File Directives ....................................................... A-3 A.3 Porting the Target Parameter File ...................................................... A-11 Appendix B. AMX 68000 Service Procedures B-1 Appendix C. AMX 68000 ROM Option
Summary of the content on the page No. 7
1. Getting Started with AMX 68000 1.1 Introduction ™ The AMX Multitasking Executive is described in the AMX User's Guide. This target guide describes AMX 68000 which operates on the Motorola MC680xx, MC683xx and all architecturally compatible processors. Throughout this manual, the term M68000 refers specifically to the Motorola MC680xx and MC683xx families of processors and all processors which are exact replicas. When distinctions are not important, the term M68000 is used to reference any
Summary of the content on the page No. 8
1.2 AMX Files AMX is provided in C source format to ensure that regardless of your development environment, your ability to use and support AMX is uninhibited. AMX also includes a small portion programmed in M68000 assembly language. Figures 1.2-1, 2 and 3 summarize the AMX modules provided with AMX 68000. The AMX product manifest (file MANIFEST.TXT) is a text file which indicates the current AMX revision level and lists the AMX modules which are provided with the product. File Name Module CJ
Summary of the content on the page No. 9
File Name Module CJ532KA .C Kernel task services CJ532KB .C General task services CJ532KBR.C CJ532KC .C Timer Manager CJ532KCR.C CJ532KD .C Task management services CJ532KDR.C CJ532KE .C Task termination services CJ532KF .C Suspend/resume task CJ532KG .C Time slice services CJ532KH .C Task status CJ532KI .C Enter and Exit AMX CJ532KJ .C General object access CJ532KK .C AMX Vector Table access CJ532KL .C Private AMX list manipulation CJ532KM .C AMX task scheduler hook services CJ532KX .C AMX Kern
Summary of the content on the page No. 10
1.3 AMX Nomenclature The following nomenclature standards have been adopted throughout the AMX Target Guide. Numbers used in this manual are decimal unless otherwise indicated. Hexadecimal numbers are indicated in the format 0xABCD or $ABCD. The terminology A(Table XYZ) is used to define addresses. It is read as "the address of Table XYZ". Read/write memory is referred to as RAM. Read only memory (non-volatile storage) is referred to as ROM. AMX symbol names and reserved words are identified
Summary of the content on the page No. 11
1.4 AMX 68000 Target Specifications AMX 68000 was initially developed and tested using the Motorola MC68020, MC68040 and MC68332 processors on a variety of Motorola evaluation boards. However, the AMX 68000 design criteria fully encompass the Motorola M68000 processor family requirements. AMX uses a set of design constants which vary according to the constraints imposed by each target processor. When operating on the M68000 processor, these design constants assume the values listed in Figure
Summary of the content on the page No. 12
1.5 Launch Requirements The M68000 must be properly configured for use before AMX is launched. The manner in which this is accomplished will depend on your target hardware implementation and on the startup code provided with your C compiler. AMX does not include bootstrap code to initialize the M68000 processor. It is assumed that you will have a boot ROM present which configures the M68000 for your specific hardware configuration and begins program execution at the entry to your C startup co
Summary of the content on the page No. 13
Trace Controls AMX alters the state of the status register (SR) whenever it enables or disables interrupts. When AMX disables interrupts, it also clears the trace control bits (T or T0 and T1) to 0. When AMX enables interrupts, the trace control bits remain unaltered. Consequently, you may not be able to use your debugger to single step trace through private AMX code sequences. M68000 Stack Use The M68000 begins execution in supervisor mode (and interrupt mode for the MC68020, MC68030, MC68040,
Summary of the content on the page No. 14
Memory Management Unit (MMU) The MC68030, MC68040, MC68LC040 and MC68060 include a Memory Management Unit (MMU) to support a demand-paged virtual memory environment. AMX does not support the M68000 memory management unit. If you are using AMX on the Motorola MC68000, MC68008, MC68010 or MC683xx processors, this restriction does not apply. These processors do not implement the M68000 memory management unit and allow direct access to the full 20, 24 or 32-bit address space supported by the parti
Summary of the content on the page No. 15
2. Program Coding Specifications 2.1 Task Trap Handler AMX 68000 supports task traps for the M68000 zero divide, bounds check and overflow faults. A zero divide fault occurs if any M68000 instruction attempts an integer division by zero. A bounds check fault occurs if the M68000 CHK instruction detects an array bound violation. An overflow fault occurs if the overflow flag (V) is set in the status register (SR) at the time an M68000 TRAPV instruction is executed. The Task Trap Handler can b
Summary of the content on the page No. 16
2.2 Task Scheduling Hooks There are four critical points within the AMX Task Scheduler. These critical points occur when: a task is started a task ends a task is suspended a task is allowed to resume. AMX allows a unique application procedure to be provided for each of these critical points. Pointers to your procedures are installed with a call to procedure cjkshook. You must provide a separate procedure for each of the four critical points. Since these procedures execute as part of the AMX
Summary of the content on the page No. 17
3. The Processor Interrupt System 3.1 Operation The M68000 classifies all internal and external sources of interruption as exceptions. The processor automatically determines the cause of the exception and then branches indirectly through entries in the processor Exception Vector Table to an appropriate exception specific procedure. The particular procedures which service internal or external device interrupt requests are called Interrupt Service Procedures. All other procedures are referred t
Summary of the content on the page No. 18
Default Exception Service Procedures AMX provides default service procedures for most exceptions. The zero divide, bounds check and overflow exceptions are serviced by AMX using its Task Trap Handler mechanism. All other exceptions handled by AMX are treated as fatal. AMX calls a Fatal Exception Procedure cjksfatalexh in module CJ532UF.C identifying the exception and the machine state at the time of the exception. If the Fatal Exception Procedure returns, AMX calls the Fatal Exit Procedure c
Summary of the content on the page No. 19
3.2 AMX Vector Table The M68000 processor provides an Exception Vector Table, often referred to as the AMX Vector Table, through which device interrupts are vectored and processor faults are trapped. The position of entries in the table and the vector numbers used to reference them are dictated by Motorola. AMX provides a set of cjksixxxx service procedures to allow you to dynamically access or modify entries in the AMX Vector Table. The Motorola vector numbers must be used in all calls to th
Summary of the content on the page No. 20
Vector Vector Enable Name Number Mask Exception CJ_PRVNRES 0, 1 Reset CJ_PRVNBE 2 $00000004 Bus error (access fault) CJ_PRVNAE 3 $00000008 Address error CJ_PRVNII 4 $00000010 Illegal instruction CJ_PRVNZD 5 $00000020 Zero divide CJ_PRVNCH 6 $00000040 CHK instruction trap CJ_PRVNTV 7 $00000080 TRAPV instruction trap CJ_PRVNPV 8 $00000100 Privilege violation CJ_PRVNTR 9 $00000200 Trace CJ_PRVNLA 10 $00000400 Line 1010 (A) emulator CJ_PRVNLF 11 $00000800 Line 1111 (F) emulator 12 reserved CJ_PRVNCP
