mcs96仿真系统 这是一款mcs196仿真系统较完全的资料很好用 内带原理图说明

------------------------------------------------------------------------------- 80196 C Readme Copyright (C) 1996 Tasking Software BV Document date: 10/10/96 ------------------------------------------------------------------------------- INTRODUCTION ------------------------------------------------------------------------------- Thank you for purchasing a TASKING software product. This file describes the solved and the known problems of version 5.0 revision 3 of the 80196 toolchain. ------------------------------------------------------------------------------- ADDITIONAL RELEASE NOTES ------------------------------------------------------------------------------- The following section contains some last minute information about the 80C196 Compiler. This information could not make it into the manuals. --------------------------------------------------------------------------- NEW COMPILER CONTROLS --------------------------------------------------------------------------- The following compiler controls have been added: warning_true_false Primary control: enables the 'comparison always returns TRUE' and 'comparison always returns FALSE' warnings default: warning_true_false Syntax warning_true_false | nowarning_true_false Abbreviation wt | nowt Discussion Use this control to generate the 'comparison always returns TRUE' or the 'comparison always returns FALSE' warnings. These warnings will appear for instance when comparing two constants or when comparing a negative number with an unsigned integer. Use the nowarning_true_false control to suppress these warnings. ------------------------------------------------------------------------------- SOLVED PROBLEMS ------------------------------------------------------------------------------- SOLVED PR5100: ARGUMENT OUT OF RANGE FOR LOCATE CONTROL 0XE0000 PROBLEM DESCRIPTION: Using pragma locate with number above 0xFFFF results in error: Argument out of range for locate control WORKAROUND: No workaround. ------------------------------------------------------------------------------- SOLVED PR5101: LINKER ERROR 113: INSTRUCTION OPERAND OUT OF RANGE PROBLEM DESCRIPTION: Declaring interrupt function leads to RL196 ERROR 113 For model(ex) farcode only. WORKAROUND: no workaround. ------------------------------------------------------------------------------- SOLVED PR5138: COMPILER GENERATES LDB AND STB INSTEAD OF ELDB AND ESTB PROBLEM DESCRIPTION: Variable led is located to external memory 0xFB0055. If you program the C statement: if( led == 0 ) { etc. the compiler generates: cmpb R0,led bne If you program the C statement: led = 1; the compiler generates: ldb tmp0,#1 stb tmp0,led EXAMPLE: #pragma model(ex) int led; #pragma locate(led=0xFB0056) void main(void) { if( led == 0 ) { led = 1; } } WORKAROUND: Declare variable with keyword far, see below: #pragma model(ex) far int led; #pragma locate(led=0xFB0056) ------------------------------------------------------------------------------- SOLVED PR5142: COMPILER GENERATES "CMPL" INSTRUCTIONS FOR KB MODEL. PROBLEM DESCRIPTION: The compiler generates CMPL instructions for the KB model which is not supported by the chip according to the customer. The "CMPL" instruction is supported by the chip. The "CMPL" (compare two long words) instruction is unreliable when register 0 is used. Incorrect flags are set when register 0 is used with the compare long instruction. However, "CMPL" works completely correct with other long word registers. EXAMPLE: R0 equ 00H rseg at 1CH temp: dsw 2 ;space for long word cseg at 2080H ld temp,#0020H ;any number ld temp+2,#0000H cmpl R0,temp ;compares R0 to 0000 0020H jlt next_routine stop: br stop ... ... next_routine: ... WORKAROUND: Load value 0 in register before CMPL. rseg at 1CH temp: dsw 2 ;space for long word long_0: dsw 2 cseg at 2080H ld long_0,#0000H ;initialize long word register 0 ld long_0+2,#0000H ld temp,#0020H ;compare value ld temp+2,#0000H cmpl long_0,temp jlt next_routine stop: br stop ... ... next_routine: ... ... ------------------------------------------------------------------------------- SOLVED PR5143: INCORRECT CODE FOR POINTER TO LONG PROBLEM DESCRIPTION: When you specify a argument which is a pointer to a long, the compiler generates incorrect code. EXAMPLE: void foo( long *pb) { if(*pb > 1L) *pb = 1L; } void main(void) { long b; b = 2L; foo(&b); } See /usr/sec/support/80196/7165 WORKAROUND: None. ------------------------------------------------------------------------------- SOLVED PR5144: WRITING TEMP FILE IN ROOT DIR WHEN OPTION XR IS USED PROBLEM DESCRIPTION: When you specify option xref (xr) the compiler wants to create a temp file in the root directory. The name af the temp file is: $TA00023 EXAMPLE: c196 t.c xr WORKAROUND: Have read/write permission in the root directory. ------------------------------------------------------------------------------- SOLVED PR5152: #PRAGMA TMPREG(XX) DOES NOT WORK CORRECTELY PROBLEM DESCRIPTION: When using the #pragma tmpreg(xx), the compiler emits references to TMPREG0 instead of TMPREGxx, as described in the C manual pp 3-105 to 3-107. EXAMPLE: #pragma tmpreg(0C0H) void main(void) { int a,b,result; result = a + b; } ------------------------------------------------------------------------------- SOLVED PR5154: SWITCH CASE STATEMENT DOES NOT WORK WITH MD(EX) FARCODE PROBLEM DESCRIPTION: When the compiler generates a jump table for the case/switch statement and model(ex) and farcode are used, the generated code is not correct. EXAMPLE: generated code: @000C: cmp Tmp0,#8 bh @0016 shl Tmp0,#2 eld Tmp2,@TBL01+2[Tmp0] eld Tmp0,@TBL01[Tmp0] ebr [Tmp0] kseg far ------------------------------------------------------------------------------- SOLVED PR5165: &-OPERATOR GENERATES WRONG ADDRESS IN EXT.MODEL PROBLEM DESCRIPTION: The '&' operator generates wrong code in extended model. EXAMPLE: memcpy(&p1,&b,2); results in: ... C90400 R push R0 C902F0 push #p1:msw <- wrong addr C902F0 push #p1:lsw <- wrong addr F1000000 E ecall memcpy 650A0018 add SP,#0AH p=&p1; results in: A102F000 R ld p,#p1:lsw <- wrong addr A102F002 R ld p+2.#p1:msw <- wrong F0 ret WORKAROUND: Not known yet. ------------------------------------------------------------------------------- SOLVED PR5166: ABSOL.ADDR IN EXT.MODEL INTERPRETED AS 16-BIT ADDR ONLY. PROBLEM DESCRIPTION: absolute addresses in extended model (model(ex)) are interpreted only as 16-bit addresses. EXAMPLE: #define PERIPHERAL (*((unsigned char far *)0x01f002)) PERIPHERAL = 0x2a; results in: B12A1C ldb Tmp0,#2AH C70102F01C stb Tmp0,0F002H <- is a 16 bit addr! ------------------------------------------------------------------------------- SOLVED PR5170: E115 WHEN STRLEN() AND WINDOWING ARE USED PROBLEM DESCRIPTION: E115: is