| ||||
| Home Products Download Events Support | ||||
Technical Support
On-Line Manuals
C166 User's Guide
C166 Introduction Compiling Programs Language Extensions Preprocessor Advanced Programming Error Messages Library Reference 
Appendix A. ANSI C Implementation 
Implementation-defined Behavior Compiler-Related Library-Related B. Version Differences Version 4.0 Differences Version 3.0 Differences Version 2.6 Differences Version 2.0 Differences Version 1.0 Differences C. Writing Optimum Code Memory Model Variable Location Variable Size Automatic Variables Avoid far/huge Pointer Cast Optimum C16x Code Other Sources D. Compiler Limits Compiler Limitations OMF Limitations E. Byte Ordering F. Hints, Tips, and Techniques Using Interrupts Program Execution Using the PEC Stack Problems Using Monitor-166 Using the bdata Type Using TRAPS.CUsing Monitor-166
If you want to test a C program using MON166, and if MON166 is installed at code address 0000h, consider the following rules:
- When you build the monitor, you must correctly specify the redirected reset and interrupt vector address to the monitor by editing the INT_ADR_SEG and INT_ADR_OFF definitions in the INSTALL.A66 or INST167.A66 monitor configuration files.
- You must use the linker's VECTAB directive to locate the interrupt and reset vectors for the target program to the correct starting address.
- When using MON166, you must protect the monitor's memory area from being used by your target program. You may use the linker's RESERVE directive to do that. For example:
L166 ... RESERVE (8h-0Bh, 88h-8Bh, 0B8h-0BBh, /* Monitor Traps */ 3E900h-3FFFFh) /* Monitor Code & Data */
| Contact Site Map Press Privacy | Copyright © 2012 ARM Ltd and ARM Germany GmbH. All rights reserved. |
