CROSSWARE 8051DS Development Suite COMPONENTS

Transcription

1 CROSSWARE 8051DS Crossware Products was established in September 1984 to fill an important and expanding niche in embedded development software. It released a C compiler and assembler for the 8051 microcontroller in Following the success of this relatively simple compiler, it developed an advanced package supporting multiple memory models, common code merging, cross module type checking, code bank switching and time saving and uniue smart pointers Development Suite It was one of the first companies to release a fully 32-bit embedded development environment and tool chain for WIN32 platforms. It released the 8051 Virtual Workshop in 1998 allowing software developers to simulate their complete target system as well as the 8051 microcontroller. In 1999 it added a serial port debugging facilities to produce a complete 8051 Development Suite. Many more innovative features have since been added including a JTAG/C2 debugger for the Cygnal microcontrollers (February 2001), complex source level breakpoints (July 2001), debug monitors for the Atmel and Philips flash microcontrollers (December 2001), Code Creation Wizards for the Cygnal microcontrollers (February 2002), Code Creation Wizards for the Atmel flash microcontrollers (May 2002) and support for multiple application debugging (November 2002). COMPONENTS The 8051 Development Suite supports all bit variants and includes the following: Optimising ANSI C compiler, assembler, linker and library manager and libraries Source level Virtual Workshop simulator to debug complete target systems without hardware Source level serial port debugger and debug monitor to debug with target board Source level debugger to interface to the Cygnal EC1 and EC2 emulation cartridges Code Creation Wizards for the Cygnal chips and Atmel flash microcontrollers Embedded Development Studio integrated development environment eliminates the learning curve for using the tools Manuals in printed and electronic form Technical support and free updates for 12 months. Crossware Products Old Post House Silver Street Litlington Royston Herts SG8 0QE United Kingdom Telephone + 44 (0) Facsimilie + 44 (0) Web info@crossware.com 1 REF: 8051DS/0409

2 CROSSWARE The Crossware 8051 ANSI C compiler is a sophisticated application that generates code for the 8051 family of microcontrollers. It provides numerous extensions that allow access to 8051 specific features so that you can write your code completely in the C language without the need to resort to assembler code. It supports large, small and tiny memory models so you can create code for all 8051 variants whether or not they have external ram. It provides advanced features such as smart pointers and cross-module type checking to ease and speed the development process. It comes as part of the Crossware 8051 Development Suite which runs under Windows 9x, Windows NT 4.0, Windows 2000 and Windows XP. ANSI C COMPILER HIGHLIGHTS The ANSI C compiler protects your investment by ensuring future portability of your C source specific extensions enable you to access all of the resources of the 8051 and its variants from C. Smart pointers which can work out for themselves which memory area they are pointing to. This enables you to avoid inefficient 3 byte pointers yet still write ANSI C compatible code. Generates fast in-line code with a minimum of library calls for high speed performance on your target board. Optional code compression for when code size is an issue. Full type checking across modules traps programming errors and ensures that your C variables, function arguments, structure members, etc are consistent across your source files and with the appropriate libraries. Comprehensive source level debug output. Pre-written library routines, including high speed 32 bit and 64 bit floating point arithmetic. Register bank independent code. Easy to use C interrupt support with optional register bank switching. Memory bank switching to break the 64k barrier. Tiny, small and large memory models. Place variables in any memory area. Supports all 8-bit 8051 variants. Data output for Embedded Development Studio source code browser 1 REF: 8051C/0409 Crossware Products Old Post House Silver Street Litlington Royston Herts SG8 0QE United Kingdom Telephone + 44 (0) Facsimilie + 44 (0) Web info@crossware.com

3 Language Definition The compiler conforms to the 1989 ANSI C specification and in addition provides a number of general enhancements including: variables can be any length with all characters significant the_interrupt keyword declares a C function as an interrupt routine the _persist keyword declares that a variable will retain its contents (eg. in battery backed up ram) during power down and should therefore not be initialized. It also supports a number of features from the 1999 ANSI C Standard including: The // characters mark the start of a comment which extends to the end of the line. Variables with can be defined anywhere within a block, not just at the beginning. Variables can be defined within the initialising expression of a for loop. In addition, the compiler supports the C++ feature that allows variables to be defined within the conditional expressions of the for loop, while loop, if statement and switch statement The support libraries are a subset of the ANSI standard libraries. The supported functions are listed below specific language extensions are described below Language Extensions In addition to the general extensions described above, the compiler supports numerous 8051 specific extensions which enable you to maximise your use of the internal resources of the 8051 and its variants. These include: Direct access to the bits of variables located in the bdata memory area. Direct access to 8 bit sfr's, 16 bit sfr's and sfr bits to which you can allocate any C variable name. Additional interrupt ualifiers to allow you to specify the interrupt vector that a function will use (the compiler optionally generates all vectoring code) and an optional register bank for register bank switching. Qualifiers to enable you to place variables in bit, data, idata, bdata and xdata memory areas irrespective of the memory model being used (variables declared as const are automatically located in code space). 2

4 Data sizes The compiler uses the following sizes for the various C data types: char and unsigned char short int and unsigned short int int and unsigned int long and unsigned long float double long double enum bit fields bit pointers to variables pointers to functions : 1 byte : 2 byte : 2 bytes : 4 bytes : 4 bytes (32 bits) : 8 bytes (64 bits) : 8 bytes (64 bits) : up to 4 bytes (minimum size to accommodate members) : up to 32 bits : 1 bit : 1,2 or 3 bytes : 2,3 or 4 bytes Optimizations Optimizations include: constant folding dead code elimination strength reduction algebraic simplification jump/branch optimization suppression of integral promotion global register allocation removal of unreferenced local data cross-module optimization code compression Floating Point The Crossware 8051 ANSI C compiler supports both 32 bit and 64 bit floating point objects. 32 bit floating point objects contain only 23 bits of precision (the rest is used by the exponent and sign) and are therefore less precise than 32 bit long integers. They are however ideal for the application where low precision floating point arithmetic is all that is reuired. 64 bit floating point objects contain 53 bits of precision and are therefore ideal where arithmetic accuracy is an important issue. All floating point arithmetic and normalisation routines are hand-coded in 8051 assembler to provide fast and compact library code. 3

5 Memory Models Large Memory Model The large memory model is used for target systems that have external data memory (xdata). Local variables and function arguments are located in xdata memory and, by default, global and static variables are located here too unless they are const objects (which are located in program memory). If the target system has no xdata memory, the large memory cannot be used. Small Memory Model The small memory model is used for target systems that do not have external data memory or where the data reuirements of the program allow small memory model to be used. Local variables and function arguments are located in internal data memory (idata) and, by default, global and static variables are located here too unless they are const objects (which are located in program memory). Global and static variables can be located in external data memory (if available) by ualifying them with the _xdata keyword. Tiny Memory Model The tiny memory model is used for programs that are limited to 2K bytes in size and that do not use external data memory at all. The compiler generates ACALL and AJMP instructions as opposed to LCALL and LJMP. No references to external data memory are allowed and so the compiler will never generate the MOVX instruction. The tiny memory model is essential for 8051 variants that do not support the LCALL, LJMP and MOVX instructions such as the Philips 8XC750, 8XC748, 8XC751, 8XC749 and 8XC752. Code Compression When code compression is enabled, the compiler will replace matching blocks of assembler code with a call to single subroutine. The minimum number of assembler code bytes that the compiler will consider in this matching process is user definable allowing the amount of compression to be controlled by the user. The linker also participates in this code compression process automatically combining identical subroutines found in different modules into a single subroutine in the final program. 4

6 Reentrant/Non-reentrant Functions The compiler will produce both reentrant and non-reentrant functions. Reentrant functions are fully compatible with ANSI C and allow recursive calls within and between functions. Space for parameters and local variables is allocated dynamically on a stack located in either internal indirectly addressable data memory or external data memory depending on the memory model. However, the 8051 instruction set is not particularly well suited to conventional stack operations (it has no indexed addressing modes for accessing data memory) and a dramatic improvement in program size and speed can be achieved by implementing a statically allocated stack system. With this approach, each function has it's own fixed data memory for storage of its parameters and local variables. Because this memory is in a fixed location, if the function is called again while it is already running, the parameters and local variables of the second call will overwrite those of the first call. The function cannot be reentered and it is therefore a non-reentrant function. To minimise memory usage the linker carries out an analysis of the complete program and constructs a function call tree. It uses this call tree to determine which functions can safely share stack space. The stack space for functions that cannot possibly invoke each other are then overlaid. The linker is also able to exactly determine the total stack space reuired by functions that have a variable number of arguments (such as printf() and scanf()) and so no space is wasted allowing for additional arguments that are never present. (Some 8051 C compilers reuire the amount of reserved space to be specified by the programmer). A compiler command line option, on a dialog box option in the Embedded Development Studio, switches between the default between reentrant and non-reentrant functions. In addition the _reentrant and _nonreentrant keywords can be used to override the default for particular functions. 5

7 Smart Pointers The compiler supports pointers that point to any specific memory area and generic 3 byte pointers that can point to all memory areas. Some 8051 C compilers default to generic 3 byte pointers unless you declare a memory specific pointer using a ualifying keyword. It is then necessary to decorate your source code with non-ansi keywords in order to avoid program inefficiency. This decoration may be memory model specific and so if you switch memory models you have to change your source code too. The Crossware 8051 ANSI C compiler avoids this problem. Although it supports these pointer ualifiers, in most cases it is not necessary to use them. Instead any pointer that is not ualified is a smart pointer. It will then work out for itself from the way it is used what type of pointer it should be. This leaves you free to write ANSI compatible, memory model independent source code without any unnecessary loss of efficiency. Without Smart Pointers: int func (char _xdata * pch1) { char _xdata * pch2 ; pch2 = pch1 } int func ( char _idata * pch1) { char _idata * pch2 ; pch2 = pch1 ; } With Smart Pointers: int func ( char * pch1) { char * pch2 ; pch2 = pch1 ; } How to avoid 3 byte generic pointers Function Pointers Calling a non-reentrant function that has parameters via a function pointer reuires the arguments either be in registers or that the function pointer includes information about the location of the functions stack space. If the arguments are in registers then only very few parameters are allowed. In order to avoid this limitation the Crossware compiler uses the latter approach. The function pointer includes both the entry address of the function code and the data address of the functions stack space. Functions called via pointers can therefore have any number of parameters. 6

8 COMPILER I/O with or without streams Standard C uses streams for input to and output from the running program. Five streams will automatically be created at program startup and these are designated stdin, stdout, stderr, stdprn, and stdaux. Streams can be redirected, duplicated and can provide the basis of a filing system allowing new streams to be created, opened and closed. Functions such as fprintf(), sprintf(), fputs(), fgets() etc are stream based functions. Streams are essential if existing C code is being pointed to the The Crossware compiler supports streams. However, streams also consume memory (each stream reuires a structure) and, due to the need for common behaviour between different stream types, they can be relatively inefficient. Therefore the Crossware compiler also provides an alternative to streams. Streamless versions of for example puts(), gets(), printf(), scanf() etc are provided. A compiler option allows streams to be enabled or disabled. The streamed or streamless versions of the appropriate functions will automatically be included depending upon the option used. In-Line Assembler The compiler provides numerous features that allow you to access the 8051 features at the C source level. Nevertheless you can still embed assembler in your C code if you wish using the #asm/#endasm directives. The #asm/#endasm directives allow assembler code to be placed anywhere in a C source file, not just within functions. In addition the compiler supports the _asm keyword. This has a number of advantages over the #asm/#endasm approach. Firstly _asm statements can be generated using C macros and with full macro token replacement. Secondly, the C compiler can replace C variable names with the appropriate sub-string allowing easy access to global, static and local variables and parameters. #define ResetWatchdog() \ _asm ( mov 0c7h,#0aah ); \ _asm ( mov 0c7h,#055h ); \ _asm ( setb 0d8h ); main() { while (1) { ResetWatchdog(); HandleInput(); ResetWatchdog(); PerformAction(); } } 7

9 Code Bank Switching The compiler supports code bank switching. This allows programs greater than 64K bytes to be produced. Code bank switching is easy to use. You include a pragma in your source code ahead of the functions that you want to include in a switchable bank and you tell the linker where the code banks are located. The compiler and linker take care of every- Source Code Browsing The compiler optionally generates information on all of the definitions of and references to the identifiers used in your program. This includes functions, function parameters, local variables, global and static variables, enum identifiers, typedefs, goto labels and the tag names of structures, unions and enums. The Embedded Development Studio will then use this information to allow you to uickly navigate through your source code. Interrupt Functions Creating interrupt functions is simply a matter of ualifying it with the _interrupt keyword and specifying a vector number. The compiler takes care of everything else - creating the absolute code at the vector address to jump to the function when the interrupt occurs and saving and restoring the appropriate registers and other internal locations that are reuired during the interrupt. The compiler calculates the vector address from the vector number and so interrupt functions for all 8051 variants can be automatically created. You can also specify a register bank and the compiler will generate the reuired code to switch register banks on entry to the interrupt function. The compiler generates register bank independent code and so register banks can be switched without any adverse effects. 8

10 Cross-Module Optimization When the C compiler generates code for an interrupt function it has to ensure that all registers and other shared data that might be overwritten are saved on entry to the interrupt function and restored on exit. If the interrupt function calls any other functions then the compiler tries to determine the resources that are used by those functions and functions that they call so that it can minimise the registers and shared data that it saves. The compiler knows about all of the other functions in the same source file and so if no function is called that is not in the same source file then the data saved and restored will be minimised. If a function is called that is in another source file or in a library, then everything that can possibly be overwritten must be saved. Cross-module optimization extends the compilers knowledge of other functions to all of the source files in your project. So the data saved and restored will be minimised even if the interrupt function calls a function in another source file. Debug Records Comprehensive debug records are generated by the compiler and embedded in the object files for each module. These are used by the linker to perform cross-module type checking and for output to the final program file. 9

11 Variant Specific Features Siemens Arithmetic Unit The Siemens 80C517 family of chips provide an arithmetic unit which performs multiplication, division, shifting and normalisation routines. The compiler optionally takes advantage of this unit for unsigned 16 bit arith- SiLabs MAC Engine The C8051F120/1/2/3 and C8051F130/1/2/3 from Silicon Laboratories (formerly Cygnal) have a multiply and add (MAC) engine which can perform a signed 16-bit multiplication in 2 cycles. The compiler optionally takes advantage of this MAC engine for signed 16-bit multiplication. A set of alternative standard libraries are also provided which have been compiled with this option. C Library Support Routines abs() acos() acosl() asin() asinl() atan() atanl() atan2() atan2l() atof() atofl() atoi() atol() clearerr() ceil() ceill() cos() cosl() cosh() coshl() exit() exp() expl() fabs() fabsl() _fcvt() ferror() fgetc() fgets() fileno() floor() floorl() fprintf() fputc() fputs() free() frexp() frexpl() fscanf() getc() getchar() getche() gets() isalnum() isalpha() isacii() iscntrl() isdigit() isgraph() islower() isprintf() ispunct() isspace() isupper() isxdigit() itoa() labs() ldexp() ldexpl() log() logl() log10() log10l() longjmp() ltoa() malloc() memchr() memcmp() memcpy() memmove() memset() pow() powl() printf() putc() putchar() puts() rand() sbrk() scanf() setjmp() sin() sinl() sinh() sinhl() sprintf() srt() srtl() srand() sscanf() strcat() scanf() strchr() strcmp() strcpy() strcspn() strlen() strncat() strncmp() strncpy() strpbrk() strrchr() strspn() strstr() tan() tanl() tanh() tanhl() time() toascii() tolower() toupper() ultoa() ungetc() ungetch() 10

12 CROSSWARE The Crossware A8051NT is a sophisticated relocatable macro cross assembler that generates code for the 8051 family of microcontrollers. It comes as part of the Crossware 8051 Development Suite which runs under Windows 9x, Windows NT4.0, Windows 2000 and Windows XP Assembler for Windows HIGHLIGHTS Intel standard mnemonics for assembler code instructions. Two alternative source file formats (.a51 and.asm). Source level debug output in IEEE695 format. TECHNICAL DETAILS RELOCATABLE MACRO CROSS ASSEMBLER The cross assembler converts assembler code into an intermediate object module format which is subseuently linked with other intermediate object modules to create the final program. Features include: High speed assembly to create relocatable object module Intel standard segment directives Intel standard mnemonics Nestable macros with full argument passing Nestable conditional assembly Comprehensive range of assembler directives and pseudo ops Complex expression evaluation with Intel standard operators Upper and lower case labels with up to 255 significant characters Upper and lower case opcode mnemonics Upper and lower case macro names with up to 255 significant characters Comprehensive error checking with descriptive error messages Debug output of symbolic information User definable listing format C preprocessos style #define, #undef, #if, #else, #endif etc. Crossware Products Old Post House Silver Street Litlington Royston Herts SG8 0QE United Kingdom Telephone + 44 (0) Facsimilie + 44 (0) Web 1 REF: 8051A/0409 info@crossware.com

13 DEBUG OUTPUT The assembler can optionally generate full source level debug information. The linker updates these debug records to take account of the final location of the target program and outputs them to the target program file in IEEE695 format. Debuggers and in-circuit emulators that support this popular format can then use it to facilitate full source level debugging. The following assembler directives and pseudo-ops are available: bit bseg clist cseg data db dbit ds dseg dw end endc endm eu extrn fail fields ifc ifcc ific ifinc ifnc include iseg list listf macr mc md mex mod51 name noclist nolist nomc nomd nomex nomod51 noobj nopage nouna obj opt org page page pagewidth public rseg segment set spc sym ttl una using xseg 2

14 CROSSWARE The Crossware 8051 banked overlay linker, library manager and command like Make come as part of the Crossware 8051 Development Suite which runs under Windows 9x, Windows NT4.0, Windows 2000 and Windows XP. Banked Overlay Linker and Other Utilities LINKER HIGHLIGHTS Analyses C non-reentrant function calls and overlays local memory. Supports up to 256 banks of switchable program memory and 256 banks of switchable xdata memory. Supports multiple regions of ROM and RAM. Allows named segments to be located at user defined addresses and in a user defined order. Analyses the calls to non-reentrant C functions with variable numbers of arguments to determine the reuired stack space. Performs a complete type check across all modules in the program. Removes unncessary bank switching code. Contributes to the code compression process by combining common sub-routines across modules. RELOCATING LINKER The linker combines object modules created with the compiler and/or the assembler to create the final code that will run on your target system. It carries out the following functions: scans each module to collect segment and variable information arranges and positions segments at appropriate memory locations to suit the memory organisation of the target system and any specific location information supplied by the user finalises the values of all variables and calculates the results of any incomplete expressions extracts and relocates the code from each module to produce the final target program optionally updates the listing files produced by the compiler and/or assembler adding the final absolute address information. carries out a complete type check across all modules examining global variables, functions (return type, parameter types and numbers, reentrant attributes, interrupt attributes, and memory model 1 REF: 8051L/0409 Crossware Products Old Post House Silver Street Litlington Royston Herts SG8 0QE United Kingdom Telephone + 44 (0) Facsimilie + 44 (0) Web info@crossware.com

15 LINKER type) and structure and union member types to ensure total program integrity The linker will also construct a call tree of your C functions. It will use this to perform an overlay analysis of the local data areas of any non-reentrant functions, sharing memory wherever possible. It will report potential recursion of non-reentrant functions. At the same time, the parameter space for non-reentrant functions with variable numbers of arguments will be sized to the maximum reuired by any of the calls to that function. You can define multiple regions for both ROM and RAM to suit your target hardware and you can specifically locate named segments at any address you wish and define their order relative to each other. You can define up to 256 switchable banks of program memory and up to 256 switchable banks of xdata memory allowing you to address up to 16 MBytes of memory! The target program can be produced in a number of different formats including Intel hex, Intel OMF51, Motorola S' record, HP/Microtec IEEE695 format or as a binary rom image. No conversion utility has to be used - the linker directly outputs the program in the specified format. An optional link map will show the final location and sizes of all segments and the addresses of all global variables. LIBRARY MANAGER LIB Instead of being used to create a final target program, the object modules produced by the compiler and assembler can be integrated into a library. The library manager performs the tasks of: combining object modules into a library adding modules to an existing library removing or extracting modules from an existing library listing the contents of a library The Library manager can be automatically invoked from the Embedded Development Studio to build a complete object code library. An object code library can then be specified at link time when building your program. The linker will search the library and extract modules from it as necessary to complete your program. 2

16 MAKE MAKE UTILITY The MAKE utility simplifies the task of keeping object files, libraries and target programs up-to-date. It detects if any source or dependency files have changed since the last build and runs the appropriate tools (compiler, assembler, linker or library manager) to rebuild out-of-date files. It supports many advanced features including macros, inference rules, conditional inclusion and other preprocessing directives and in-line files with automatic temporary file creation. Although the Embedded Development Studio uses its own integrated routines to keep projects up-to-date, this stand-alone MAKE utility can be used to build projects from the command-line or from within another application. The Embedded Development Studio will automatically create a makefile which is fully compatible with this stand-alone MAKE utility. 3

17 CROSSWARE Code Creation Wizards speed the development process by generating configuration and application code and outline interrupt handlers in C. Code Creation Wizards HIGHLIGHTS Graphic point and click interface to create C source code. Cooperaton between Wizards to support dependencies between on-chip peripherals. Configuration code reloaded into Wizards to allow for easy modification. Configuration can be set allowing reconfiguration code to be generated. Outline interrupt handlers inserted into current source file. Full interrupt handlers generated for some peripherals. Complete interrupt driven buffered I/O handlers generated for UARTs. Crossware Products Old Post House Silver Street Litlington Royston Herts SG8 0QE United Kingdom The UART Wizard show above can generate a complete set of interrupt driven I/O handlers with a user defined input buffer size. Crossware Products is the business name of Crossware Limited. Registered address as above. Registered in England and Wales under company registration number CROSSWARE is a registered trademark of Crossware Associates. 1 Telephone + 44 (0) Facsimilie + 44 (0) Web info@crossware.com REF: 8051WIZ/0409

18 CROSSWARE HIGHLIGHTS Significantly reduces software development timescales Enables debug and verification without hardware Allows programmers to simulate complete target system Comes as part of the Crossware 8051 Development Suite for Windows Simulator/ Virtual Workshop source level simulation context coloured C source context coloured assembler source context coloured listing context coloured embedded assembler locals watch window four customisable watch windows freeze watch windows support for 8051 variants capture state seamless integration interrupt simulation extendible to simulation of complete target system on-line manuals printed manuals uart simulation timer simulation port views serial port views interrupt view multiple cycle counters multiple formats code coverage data coverage source code profiling call stack works with Crossware Windows tool chain works with your own tool chain disassembly window source level break points memory breakpoints step into step over step out step backwards trace trigger external interrupts map code to xdata memory memory mapped i/o trap delayed interrupts Crossware Products Old Post House Silver Street Litlington Royston Herts SG8 0QE United Kingdom Telephone + 44 (0) Facsimilie + 44 (0) Web info@crossware.com 1 REF: 8051VW/0409

19 The 8051 Virtual Workshop is a revolutionary new development tool which allows 8051 programmers to simulate their complete target system. It allows the software debugging and verification process to proceed in the absence of any target hardware. Used to its full potential, it can reduce software development timescales by at least an order of magnitude. The 8051 Virtual Workshop runs under Windows 9x, Windows NT4.0, Windows 2000 and Windows XP. At the heart of the system is an 8051 Instruction Set Simulator with full source level and graphical debugging facilities. What turns this simulator into a Workshop is the fact that it can rapidly be extended into a total simulation of the target system. The traditional debugging process reuires the presence of the hardware on which the software will run. Debugging may proceed using either a sophisticated in-circuit emulator or a simple serial port debug monitor. There are a number of drawbacks to this approach. Firstly the hardware has to be available and early in the design process it may not even exist; later the scarce development hardware boards will be in high demand and will be allocated on a priority basis to those with the most pressing need. Secondly problems with the hardware may hinder the software development process - it is very difficult in the early stages of a development to identify the source of a problem as either software or hardware. The Virtual Workshop puts control in the hands of the programmer. No longer dependent upon hardware, the programmer can develop, debug and verify the software and be confident that, when it is integrated with the hardware, it will function as designed. Developments in software design, in particular the introduction of real time UML (Unified Modelling Language), mean that the software engineer can get the design right first time. The Virtual Workshop allows the programmer to get the source code right first time too. Adding extensions to the Virtual Workshop is fast and effective due to the Wizards, tutorial and support provided with the package. The graphical simulation of a text display can take as little as two hours to develop, including the interpretation and analysis the display driver datasheet. A library of virtual components will build up over time and so later target systems can be simulated with hardly any effort at all. The system truly frees the programmer from the constraints of the rest of the development process. The 8051 Virtual Workshop integrates seamlessly with the Crossware Embedded Development Studio which provides project management, editing and other advanced facilities. It works extremely effectively with the 8051 ANSI C compilers and assemblers from Crossware but it works eually well stand-alone, with tool chains from other vendors. 2

20 Seamless Integration with the Embedded Development Studio The Embedded Development Studio forms an integrated environment that binds together the various Crossware tools. It automatically detects the presence of the Virtual Workshop and loads it to create a single unified application. The text windows that you see as you single step through your program are exactly the same as those you use to create and edit your source code. If you set a breakpoint as you edit your code, this is where execution will stop when you instruct the Simulator to Go. When the Virtual Workshop is used stand-alone', the Embedded Development Studio provides a customisable interface to your tool set. You can therefore edit and keep your project up-to-date using all of the sophisticated features of the Embedded Development Studio using your existing compiler, assembler and linker. Virtual Workshop extensions programmed in Microsoft Visual C++ using the Microsoft Foundation Classes will also integrate seamlessly with the Embedded Development Studio. The Embedded Development Studio is included with the Virtual Workshop. Please see separate datasheet for full details. Variants Supported The software fully simulates the 8051 and 8052 microcontrollers and many 8051 variants including those from Silicon Laboratories (formerly Cygnal), Atmel, Cypress, Philips and Dallas Semiconductor. Source Level Simulation The instruction set simulator at the heart of the Virtual Workshop will allow you to step through, trace and run your program at the source level. As execution proceeds you can watch its progression through your source code, stepping into, over and out of functions and halting at source level breakpoints. Alternatively, if your program does not contain any debugging information or if you want to view the detailed assembler code, a disassembly window is available. 3

21 Multiple Watch Windows for Local and Global Variables If you are programming in C, then you will want to view your C variables. You can open up to five watch windows to view these. One of these windows will automatically display local variables, automatically updating the variables listed as the move into and out of scope. The other four can display global and local variables of your choice. You can expand structures, unions and arrays and the address field will tell you where each variable or element is stored. You can freeze a complete watch window so that it doesn t get updated and so compare current and past values of the same variables. You can display values and addresses in decimal or hexadecimal. You can display the complete type information of your variables. Call Stack The call stack allows you to follow the progress of your program through the layers of function calls. The call stack window shows the name of each active function, and the values of the program counter, stack pointer and the source code line number reached in each function. You can navigate through the functions in the call stack - double clicking on the function name in the call stack window will take you to the location in your source code reached in that function. Views of Memory Areas You can open multiple views and watch all memory areas, setting breakpoints when memory locations are written, read or both. Coloured highlighting shows you which locations are changing and optionally you can enable data coverage so that you can clearly see which memory locations have been accessed and which have not. You can edit any memory location in hexadecimal or ASCII format. 4

22 View Named Registers You can open a view to display and edit named registers. Where an extension is active and providing support for an 8051 variant, the registers shown will be those of the variant. Interrupt Simulation and Views Interrupts are fully simulated and extendible to support enhancements provided by 8051 variants. External interrupts are level and edge sensitive and so will be triggered by an appropriate change to the port input line. An interrupt activity view shows you graphically which interrupts are enabled, how the interrupt priority masks are set and which interrupts are active at what priority level. UART Simulation and Views Cycle accurate simulation of the 8051 UART allows true simulation of serial I/O. A serial port activity view shows you the mode settings, driver source and clock doubling and interrupt flags. Bar indicators display the progress of the transmit and receive buffers as the data is clocked through. Legends will show you if your program has read the most recent input byte or if a byte has been overwritten by the next one before it was read. Input and output to the UART can be via a text window, a file or to and from Virtual Workshop extensions. If input is from an extension, the simulation will be sensitive to the RB8 bit allowing the 8051 multiprocessor communications protocol to be supported. Variants such as the Dallas DS87C320, which support two UARTS are supported with an additional I/O features and an additional activity view. 5

23 Timer Simulation and Views The 8051 and 8052 timers are fully simulated and the decrement feature present on many variants is supported too. The timer view shows the activity of the timers so that you can graphically see them in operation. Watchdog timers are simulated where the variant extension supports it The Port View The port views (one for each port) show the masked input, the unmasked input and the status of the latch. Input data for a port can be stored in a binary file and read as your program executes and of course input and output can be from and to Virtual Workshop extensions. State Capture The state capture facility allows you to store the complete internal state of the simulated microcontroller. You can capture the internal state any number of times and select and view them at a later stage. When you select and view a captured state, all of the memory views are updated to show the captured state. You can fully restore a captured state. Then, when you next run the simulator it will start with all conditions, memory, cycle counters, program counter, etc restored to the values current at the moment you captured the state. You can use this feature to repeatedly run a small segment of your code. Even the states of your Virtual Workshop extensions will be restored if you follow our programming guidelines. 6

24 Complex Drag and Drop Breakpoints Complex source level PC and data breakpoints can be set using an easy to use drag and drop interface to halt execution during both simulation and on-chip debugging. When on-chip debugging with the SiLabs chips, the hardware PC and internal memory breakpoint features of the chip are utilised. Multiple Application Debugging Multiple application debugging allows two or more applications running on the same target to be simultaneously developed. Typically this might be a boot loader and the application loaded by the boot loader. Multiple application debugging allows the application to be loaded and debugged even before the boot loader has been fully developed. 7

25 The Extension Interface The extension interface allows you to extend the Virtual Workshop so that it simulates additional features specific to your target system. You can add extensions to simulate as little or as much as you like. You can simulate all of your target system and develop your software to completion without any target hardware. The extension interface consists of a set of C function calls. You provide DLL s which support the calls of your choice. You can therefore write a very simple C program to interface to your simulating 8051 program supporting any algorithm or protocol you wish. It is easy though to write your extensions in C++ using the Microsoft Foundation Classes. We provide a wizard that works with the Microsoft environment to create an outline Virtual Workshop extension for you. You can then rapidly add your own target specific features providing algorithms, protocols, dialog boxes, menu items etc to create an extension that will integrate seamlessley with the Virtual Workshop. Multiple extensions are supported and so you can provide separate extensions for the different elements of your target system. And if you want your extensions to communicate with each other or with an entirely separate application that is possible too. Tutorial Writing powerful, graphical Virtual Workshop extensions using Microsoft Visual C++ is easy once you know how to do it. To get you up to speed as uickly as possible, a tutorial will take you step by step through the complete extension creation process. 8

26 Multiple Cycle Counters The status line contains three cycle counters. One of these displays the number of cycles executed since the start of the program, another displays the number cycles executed since the last command was issued (such as Step, Trace or Go). The third is a trip counter and displays the number of cycles executed since you last reset it to zero. Source Code Profiling As the simulator runs your program, it can optionally capture information about the execution history. It can use this information to produce an execution profile of your source code. This will tell you how much time your program spent executing in the different parts of your code. The profile results are listed in a text window, sorted in accordance with your selected criteria. A double click on a listed item will take you to the relevant line of your source code. Code and Data Coverage The information captured during execution can also be used to provide a coverage analysis. Code coverage will show you which parts of your code have been executed and which have not. Data coverage will show you which internal and external data memory locations have been accessed during execution. Memory The Virtual Workshop directly supports up to 64k of program memory, 64k of external ram, 256 bytes of internal ram and 128 bytes of SFR memory. You can easily add support for additional banked memory using your own extensions. Program File Formats The file formats supported for the 8051 program code are Intel hex, OMF51, IEEE695 and Binary. IEEE695 can contain comprehensive debugging information, Intel hex and OMF51 can be produced by the majority of 8051 tools, Intel hex is accepted by the majority of eprom programmers and binary format will be the same as an eprom image so if all you have is the eprom, you can transfer it to a file and load it into the simulator. Crossware Products is the business name of Crossware Limited. Registered address as above. Registered in England and Wales under company registration number CROSSWARE is a registered trademark of Crossware Associates. 9

27 CROSSWARE The Crossware 8051 Development Suite supports on-chip debugging with a serial port debug monitor and with the Silicon Laboratories (formerly Cygnal) EC1 and EC2 emulation cartridges. Serial Port Debug Monitor On-chip Debugging The Crossware 8051 Serial Port Debug Monitor is a small program that runs on your target system. It communicates with your PC via a serial port and enables you to use the 8051 Virtual Workshop as a remote source level debugger. It leaves all 8051 internal ram for your program by swapping its own stack and variables to and from external ram during context switches. It is written in C and the source code is provided in case you want to rebuild it for your specific target system. You can single step through your program at the source or assembler level as it runs on your target hardware. You can set program break points and run to these, you can step into and out of subroutines and functions. You can view memory, registers, variables, etc. just as you can during simulation. Debugging Silicon Laboratories Variants The SiLabs (Cygnal) microcontrollers include in-chip hardware debugging facilities. The EC1 and EC2 emulation cartridges provide an interface to these features. The Crossware 8051 Development Suite drives these emulation cartridges directly and so can access all of the features available including hardware execution and data breakpoints and hardware stack overflow and underflow traps. A single command switches the Virtual Workshop to remote debugger mode: Crossware Products Old Post House Silver Street Litlington Royston Herts SG8 0QE United Kingdom Telephone + 44 (0) Facsimilie + 44 (0) Web sales@crossware.com REF: 8051DBM/0401

28 DEBUG MONITOR TEMPLATES A number of Atmel flash memory microcontrollers are byte reprogrammable. This makes them ideal for supporting a debug monitor because any program address can be readily reprogrammed with a breakpoint instruction. For these chips, the serial port debug monitor is provided in the form of a template. When a template is selected, a complete debug monitor project is created with a chosen name and location. The UART Code Creation Wizard can be used to customise the baud rate and the debug monitor can then be immediately built and downloaded into the flash memory of the microcontroller. Crossware Products is the business name of Crossware Limited. Registered address as above. Registered in England and Wales under company registration number CROSSWARE is a registered trademark of Crossware Associates.

29 The Crossware Embedded Development Studio leverages the features of Windows to provide a development environment that allows the programmer to concentrate on the primary task of software development. It eliminates at a stroke, the learning curve normally associated with the use of a sophisticated tool chain and provides an extensive range of features to help the programmer. It encourages a project management approach with wizards and property pages to help with the setup process. It features a multi-threaded interface to multiple tool chains, an integrated feature rich text editor with full context colouring, multiple terminal emulators, a source code browser, complete on-line books with full text searching and a uniue configuration system to manage startup files and target specific options. 7 CROSSWARE EMBEDDED DEVELOPMENT STUDIO A user friendly Integrated Development Environment The Embedded Development Studio comes with the Crossware tools of your choice. Whatever Crossware tools you choose, they will be seamlessly integrated into the Embedded Development Studio allowing you to make your choice of target system from all of the options available. As you write your source code in the integrated editor, context colouring highlights the language keywords and the assembler opcodes supported by your target system. The Embedded Development Studio works out the dependencies in your source code and displays all of the files in your project in a project tree. Editing any of these files is only a double click away. When you click on the Build icon your code will be compiled, assembled and linked in the background allowing you to carry on with other important tasks. Crossware Products Old Post House Silver Street Litlington Royston Herts SG8 0QE United Kingdom Telephone + 44 (0) Facsimilie + 44 (0) Web info@crossware.com 1 REF: EDS/0409

30 HIGHLIGHTS User friendly interface to a sophisticated range of embedded development software. Dockable windows to help you organise your desktop. Project based approach with project files and dependencies displayed in a tree structure. Configure your project to build an executable program or object code library. Integrated build utility to keep your project up-to- date. Runs in the background allowing you to continue your work during the build process. Wizards to help you set up your options at the start of a new project. Property pages to allow you to adjust your project settings as your development proceeds. Integrated editor with context colouring of language keywords and the assembler opcodes supported by your chosen target system. Integrated terminal emulator operating at the maximum baud rates allowed by windows. Automatic generation of a build script which can be used to build your project from the command-line or from within another application. Integrated browser to easily locate C symbol definitions and references. File text search to locate and jump into text files. Uniue startup file system creates and maintains the startup code for your project. On-line books with full text search. Supports multiple Crossware tool chains and third party tool chains. Customisable commands allow you to run other executables. Allows multiple projects to be simultaneously loaded. TECHNICAL DETAILS DOCKABLE WINDOWS Multiple features reuire multiple views and organising the positions of these views on the screen can soon become a burden. When a new window is opened, the user is reuired to position it so that it does not obscure the other windows that need to be seen. Dockable windows overcome this problem. When a dockable window is opened it will automatically position itself near the edge of the screen. The other windows are moved to accommodate it and so nothing is obscured. It can be dragged so that it docks at a different location or so that it floats above the other windows. Alternatively it can be completely undocked so that it behaves like a conventional Windows window. 2

31 SEAMLESS INTEGRATION The Embedded Development Studio is a multiple target environment. It automatically detects which tools are present and configures itself accordingly. When you create a new project and select the target family, the tools for that target family are automatically made available. If a simulator or debugger for the target family is present then this is integrated into the Embedded Development Studio to form a single seamless environment. MULTI-THREADED INTERFACE Multi-threading is used extensively in the Embedded Development Studio. It is used by the find-in-files utility, by the terminal emulators and most importantly by the interface to tool chain components such as the compiler, assembler and linker. The various thread priorities have been carefully configured so that editing and other user tasks are not affected by tasks running in the background. CONFIGURATION MANAGEMENT One of the issues with embedded development is the initialisation of the target system. Different microcontrollers and target boards reuire different startup routines. There are too many variations to be covered by a standard set of routines and so the Embedded Development Studio provides a system to allow users to easily define and include their own routines. This configuration management system also allows other reuirements such as memory ranges, compiler and linker options, etc to be defined. This is ideal for managers of software teams who can pre-configure the Embedded Development Studio so that it allows their programmers to easily select the appropriate configuration. 3

32 PROJECT BASED APPROACH Your source files will be organised into a project and displayed in a tree structure. Your source files will be automatically scanned for dependencies and these dependency files will also be displayed in the project tree. The project tree is automatically updated as you add or remove files from your project. A number of actions can be performed from the project tree view. You can open, compile or assemble the selected file, create and open a listing of the compiled or assembled file, create and open a link map for the project and convert the project view to and from a dockable window. Object files can also be included in your project allowing you for instance to extract specific files from a non-default library for inclusion in your program. You can also add documentation files to your project. If they are text files (with a.txt extension) they will be opened in the Embedded Development Studio but otherwise they will be opened by the application associated with the particular file type. Therefore you can for instance include Word, WordPerfect, CorelDraw, Excel and Lotus documents in your project and can open then uickly from the project view. Version 4 of the Embedded Development Studio allows multiple projects to be simultaneously loaded into the environment. This is particularly useful if an application and a set of libraries are being combined, if a bootloader and the application it loads are being simultaneously developed, or if several co-operating applications are being developed. In addition source level browsing information can be combined across any or all of the projects loaded into the environment. Therefore, if an application and a set of libraries are being developed, the programmer can easily find all of the references and definitions for C identifiers across the complete set of projects. CREATING A NEW PROJECT When you want to create a new project you will be guided through the process by the New Project Wizard. You select the type of project you want (executable program, object code library or stand-alone Simulator/Virtual Workshop) and then answer a simple set of uestions that the Wizard will present to you. If you accept the defaults you will exit the project creation process with preliminary source code files that are complete enough to compile and run. 4

33 BUILD CONFIGURATION You can configure your project so that it creates an executable program that will run on your target system or so that it creates an object code library of reusable modules. All compiler, assembler, linker and library manager options can be configured from an easy to use set of tabbed dialog boxes. COMPILER OPTIONS The compiler options available will depend upon the selected target chip. For instance the 8051 C compiler supports different memory models, non-reentrant code etc and selections for these features automatically appear in the compiler settings tab if the 8051 chip is selected. Additional compiler options may be automatically used depending upon the particular chip variant selected from the family member list. ASSEMBLER OPTIONS Assembler options can be selected from the Assembler settings tab. Additional options will appear if the assembler for the selected chip supports them. Additional assembler options may be automatically used depending upon the particular chip variant selected from the family member list. 5

34 LINKER OPTIONS The Linker settings tab again adapts itself to the target chip with for instance the max idata field appearing for the 8051 chip. The basic ranges for ROM and RAM can be set up which is usually enough for the average program. ADVANCED LINKER OPTIONS In addition, Advanced linker settings allow named rom and ram segments to be located at precise addresses and located relative to each other in a defined order. Furthermore additional ranges for ROM and RAM can be set up and optionally declared with a bank number to support memory bank switching where reuired. LIBRARY MANAGER OPTIONS The Library settings tab allows the name of the file that will contain the library to be defined if you wish to change it from the default filename. 6

35 CUSTOM BUILD STEPS You can specify your own commands to be executed before and after the link step and before and after the library manager is run. Up to 10 commands can be run at each step and they can be either 16 bit or 32 bit programs. Each custom command can be saved with the project, with the family member, with the target family or with the application. Therefore you can choose which commands will automatically be present with complete flexibility. COMPLETELY CUSTOMISED BUILD If you want to use a simulator or Virtual Workshop with a third party tool chain, you can choose the Stand-Alone configuration as the project type. You can then specify your own commands for the compile, assembler and link stage and completely customise the build process using either 16 or 32 bit tools. You can also customise the environment to support tool chains that expect different environment variables to the normal INCLUDE and LIB variables. SOURCE CODE BROWSING The Crossware compilers optionally generate information on all of the definitions of and references to the identifiers used in your program. This includes functions, function parameters, local variables, global and static variables, enum identifiers, typedefs, goto labels and the tag names of structures, unions and enums. The Embedded Development Studio will then use this information to allow you to uickly navigate through your source code. You can open the browse dialog box to view the information and jump to the selected definition or reference or you can use hot key or mouse commands for rapid hyperjump navigation. 7

36 ADVANCED EDITING You can create and edit your source code using the advanced text editing features of the Embedded Development Studio. Features include: Context colouring of your C and assembler code. Assembler code is context coloured in pure assembler source files, when its embedded in C source and when its displayed in a listing. User specified colours for context coloured and normal text. User specified background colour. User specified fonts. Optional auto indent of C source. Optional auto indent of assembler source. User definable tab width. Convert tabs to spaces or keep as tab characters. Unlimited undo/redo. Cut, copy and paste blocks of text. Cut, copy and paste columns of text. Drag and drop blocks of text within and between documents. Drag and drop columns of text within and between documents. Text search and search and replace within documents with optional case sensitivity and regular expressions. Text search of files on disk with Go to Find, Go to Next and Go to Previous commands that will load the file and select the text found ready for immediate editing or replacement. Bookmarks. Auto save on project build. Optional auto reload of documents modified outside of the editor. Printing of document or selected text with user definable header and footer. Set and clear breakpoints to be used during debugging. Record and playback keystrokes and commands. 8

37 ON-LINE AND PRINTED MANUALS User manuals are provided printed and bound so that you can study the features and facilities available at your leisure and away from your computer. The identical manuals are available for instant access from within the Embedded Development Studio - you can press the hot help key over an indexed keyword to instantly bring up the appropriate topic or search the complete set of on-line manuals for a word, phase or complex expression. A full table of contents is displayed for each on-line manual. AVAILABILITY The Embedded Development Studio accompanies a range of development tools from Crossware. HOST SYSTEM REQUIREMENTS IBM compatible PC with an Intel Pentium or above running under Windows 9x, Windows NT4.0, Windows 2000 or Windows XP. Crossware Products is the business name of Crossware Limited. Registered address as above. Registered in England and Wales under company registration number CROSSWARE is a registered trademark of Crossware Associates. 9