release.txt

kell软件

                 600 for V6.00)

      __KEIL__   defined to 1


    - C sfr and sbit declarations are now accepted.  The A51 Assembler
      now accepts the same register definition files as the C Compiler.
      For example:

      sfr  P0 = 0x80;
      sbit P0_1 = P0^1;

    - User-generated error output is now supported.  Standard error
      messages may be generated with the __ERROR__ directive.  For
      example:

      IF CVAR1LEN > 10
       __ERROR__ "CVAR1 LEN EXCEEDS 10 BYTES"
      ENDIF

      #ifdef TESTVERS && RELEASE
       #error TESTVERS GENERATED IN RELEASE MODE
      #endif

 
5.  Linker Enhancements

    BL51 Version 4.03 has the following improvements:

    - The DISABLEWARNING directive (Abbr. DW) allows you to selectively
      disable Linker warnings.  For example, to disable Warning 1 and
      Warning 5, use the following command line:

      BL51 myfile.obj DISABLEWARNING (1, 5)

    - The NOSORTSIZE directive (Abbr. NOSO) disables sorting program
      segments by size.  This is the method used in C51 Version 5 and
      earlier.  In C51 Version 6, the BL51 Linker sorts and locates
      segments by size.  This ensures fewer GAPS in the memory space and
      reduces memory consumption.

    - The SPEEDOVL directive (Abbr. SP) causes the linker to ignore
      constant segments (those that begin with ?CO?) from the overlay
      analysis.  You may need to use this directive if you have a large
      number of constant code segments in a program and the linker
      requires a very long time to run.  This directive might also be
      useful for applications that contain complex pointers to function
      tables (see the 8051 Utilities User's Guide, pages 34-41).  Note
      that if you use function pointers, you must manually adjust the
      call tree (using the OVERLAY directive) or the SPEEDOVL directive
      may result in unreported warnings.

    - The NOAJMP directive (Abbr. NOAJ) disables the use of the AJMP
      instruction in the interbank jump table in code banking programs.
      This option is required for 8051 derivatives that do not support
      the AJMP instruction.

    - The RECURSIONS directive (Abbr. RC) allows you to specify the
      number of recursions allowed before the linker generates the
      following fatal error and halts:

      FATAL ERROR 232: APPLICATION CONTAINS TOO MANY RECURSIONS.

      For example:
      BL51 test.obj  RECURSIONS(100)

      The linker may run for a long time in order to detect all 
      recursions and remove the references.  Therefore, the default
      setting is RECURSIONS(10).

    - The NOINDIRECTCALL directive (Abbr. NOIC) is used in code banking
      applications to signal the linker that calls through function
      pointers are made into the same code bank.  This generates faster
      indirect function calls in code banking programs.  If you use this
      directive, you must ensure that indirect function calls never
      cross a code bank.

    - The NOJMPTAB directive (Abbr. NOJT) is used in code banking
      programs to direct the BL51 linker to exclude the inter-bank call
      table normally used for bank-to-bank function calls.

      This directive is provided to enable you to create a user-defined
      bank switching mechanism.

      The NOJMPTAB directive modifies the behavior of BL51 as follows:

      a) The linker no longer needs the L51_BANK logic file.

      b) Call instructions are not modified to jump to the call table.

      c) Warnings are not generated if a jump or call is made to another
         bank.

      When you use NOJMPTAB, you must ensure that the proper bank is
      selected before you invoke a function in that bank.  BL51 does not
      select the bank automatically.

    - The XDATA and CODE directives now accept address ranges.  For
      example:

      BL51 myfile.obj CODE (0-0x2000, 0x4000-0x8000) XDATA (0-0x3FF)

      Specifies that BL51 may locate your program CODE anywhere in the
      ranges from 0000h to 2000h and from 4000h to 8000h.  BL51 may
      locate your program's XDATA variables anywhere from 0000h to 03FFh.
      BL51 warns you if your program CODE or XDATA exceeds the specified
      memory area size.

      The XDATA and CODE ranges are generated from the uVision2 Options
      dialog - Target page when you enter external memory devices.

    - In the segment control directives, wildcards are now accepted 
      when you locate segments.  

      Wildcards are now allowed in the segment location directives (CODE,
      XDATA, DATA, and so on).  For example:

      BL51 myfile.obj CODE (?pr?*?myfile (0x100))

      locates all program segments (functions) from myfile.obj starting
      at address 0100h.


6.  Manuals Provided

    This release of C51 includes the "Getting Started and Creating 
    Applications User's Guide".  This manual leads you step-by-step 
    through several example programs and also introduces you to our 
    broad product line.  It is a quick reference for all of our 8051 and
    251-based development tools and is available in PDF format in
    \KEIL\C51\HLP\GS51.PDF.


7.  Example Programs

    Several example programs are included in the EXAMPLES directory.
    These examples demonstrate how to use the uVision2 Project Manager
    and Debugger (see the uVision2 Quick Start Guide for details).


8.  New Devices & Register Header Files

    C51 Version 6.11 adds support for many 8051 derivatives currently
    available, including support for multiple DPTR's on Atmel, Dallas,
    Infineon, Philips and Temic devices.

    Header and other support files for most 8051 derivatives have been
    added.  Now, when you edit C or assembler source text, the correct
    register definition file is listed in the editor context menu (right
    mouse click to open).  Use the Insert "#include <regxxx.h>" item to
    include the register definition header file in your source code.


9.  uVision2 Debugger - On-Chip Peripherals in the Simulator

    With more than 400 derivatives on the market, it is impossible 
    for the uVision2 Debugger and Simulator to support all aspects 
    and on-chip peripherals of the various devices.  However, the 
    simulator currently supports all 8051 40-pin devices (similar to
    the 8051Fx, RD, RD+, 8052 and variants), the Analog Devices ADuC812,
    Philips LPC series, Philips 80C552/554, Dallas 320/520/530,
    Temic 89C51RD2 (including on-chip E2PROM), Temic 80C51CC2, and 
    Infineon C515, C517 and C517A.  We are constantly improving 
    simulation support for on-chip peripherals.  The next devices 
    implemented will be Infineon C504, C505C, C508, C515A, C515C.

    uVision2 now functions with the Monitor-51 Target Monitor.  In 
    the dialog Options, you may select Debug to enable the Monitor
    debugger with the Use Keil Monitor-51 Driver and adjust COM 
    port settings with the Settings button.

    As an alternative to the uVision2 Debugger, it is also possible to
    use dScope-51 (available in the C51 Version 5 package).  You may
    invoke dScope-51 via the uVision2 tools menu.
    
    - The following setup calls dScope-51 with an INI file that is
      dependent on the name of the current uVision2 project.

      a. Use uVision2 Tools - Customize Tool Menu dialog.

      b. Enter the following information:

         Menu Content:      Run dScope-51 with @P
         Command:           C:\C51\BIN\DSW51.EXE      
                            // depends on your installation
         Initial Folder:    <empty>
         Arguments:         -i @P.INI

    Now you may start dScope-51 directly from the uVision2 Tools 
    menu.  You may create a INI file that contains the following 
    content:

    Example: HELLO.INI (dScope INI file for HELLO project)
    LOAD 8051.DLL // device you want to simulate with dScope-51
    LOAD HELLO    // the application you want to load
    g, main       // run program til entry 'main'


10. Sales and Technical Support

    At Keil Software, we are dedicated to providing you with the 
    best development tools and technical support. More than 1200 
    technical support questions and related answers can be 
    accessed with the Keil Online Support Solutions Database at:

                      http://www.keil.com/support

    When a new question arises, the database is updated and published
    daily to the Web. This process enables you to get technical
    support at times when our support staff is unavailable. 

    If you experience any problems or have any questions about this
    product, contact one of our offices for assistance.

    In the USA...                  |   In Europe...
                                   |
    KEIL Software, Inc.            |   KEIL Elektronik GmbH
    1501 10th St., Suite 110       |   Bretonischer Ring 15
    Plano, Texas 75074             |   D-85630 Grasbrunn, Germany
                                   |
    Sales    [phone]        |   Sales    [phone]
    Support  [phone]        |   Support  [phone]
    Fax      [phone]        |   Fax      [phone]
    Email    [e-mail]     |   Email    [e-mail]
             [e-mail]   |            [e-mail]
                    

    We have more than 60 representatives around the world and the
    distributor's addresses can be found on our World Wide Web 
    page:
                     http://www.keil.com/
    
    Many of the features of the Keil Online Support Solutions 
    Database are the result of your suggestions. If you have any 
    ideas to improve our technical support or our web site,
    please give us your feedback!