EUROScope lite 16FX

Reference Manual

Version: 01/2008

EUROS Embedded Systems GmbHCampestraße 12 | D-90419 Nuremberg | GermanyFon: +49-911-300328-0 | Fax: +49-911-300328-9Web: www.euros-embedded.comeMail: support@euros-embedded.com

Rev. Revision history Date

-001 Original issue 08.05.2007-002 Approved for in-house use and shipment to customers 15.06.2007-003 Description of the flashing tools 31.01.2008

EUROScope Reference Manual Contents

Table of contents

Chapter 1 Introduction1.1 What is EUROScope? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2 What is EUROScope lite 16FX?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.4 Explanation of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 2 Getting Started2.1 Establishing a Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.1.1 Fujitsu 16FX Boot ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.2 Paths to Program Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.3 Loading an Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.4 Running an Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Chapter 3 Reference3.1 Configuring the Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.1.1 The Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.1.2 Customizing the Shortcuts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.1.3 Customizing the Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103.2 Loading an Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103.3 The Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.3.1 Source Text View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.3.2 Breakpoint View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.3.3 Memory View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.3.4 Variable View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.3.5 Register View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.3.6 Terminal Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 4 Flashing tools4.1 Using the embedded flash tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154.2 Mode of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154.3 Configuring the flash agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164.4 Erasing Flash A/B memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174.5 Programming Flash A/B memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Chapter 5 Comparison between EUROScope full and EUROScope lite 16FX

i

Contents EUROScope Reference Manual

ii

EUROScope Introduction

Chapter 1 Introduction

1.1 What is EUROScope?EUROScope is a universal source level cross debugger which can be used with a variety of target systems yet providing the same poweful and easy to use interface. Since EUROScope is not rigidly linked to an operating system, it can also be used to debug standalone assembler and C programs. What is more, the tar-get platform is not restricted to one particular processor architecture. EUROScope has been developed and enhanced continuously by the staff at EUROS Embedded Systems GmbH as well as been adapted to suit new architectures. Liteweight and easy to use, the debugger can be installed on any system running Micro-soft Windows.Basic debug functions of EUROScope are:• Reading and writing to the target system• Loading program code into memory• Starting a program which has been loaded• Setting break points with various properties• Running a loaded program in steps• Program testing either on Assembler or C source text levels• Display and modification of the microcontroller registers• Display and modification of the microcontroller special function registers (SFR)• Symbolic display of user data according to their data types• Visualization of system objects of a RTOS EUROS application• Visualization of system objects of an OSEK application• Visualization of system and user events• Statical code analysis• Command Line Interpreter• Provision of terminal window• Memory emulation

Since EUROScope is a cross-debugger, the main component of the debugger runs on the host and is linked to the target system via an interface. There are a number of possibilities to establish connection between target and host system, though they all fall into one of three major categories:• JTAG/BDM personality module• small monitor application• debug agent task, part of the operating system

A small monitor or a debug agent task runs on the target system in order to execute commands from the debugger on the target system. The interface across which the connection between the host and target sys-tem is created is selectable and must be configured for each target system. This concept permits a powerful user interface which uses very little resources on the target system. Even when no real hardware target is present EUROScope provides memory emulation, that can be used to examine application executable and perform some basic analysis.

1

Introduction EUROScope

1.2 What is EUROScope lite 16FX?EUROScope lite 16FX is a version of the universal source level cross debugger EUROScope designed especially to be used with the microcontroller family 16FX of the company Fujitsu Microelectronics Europe. For the communication with the target system - in this case - the especially designed Fujitsu 16FX Boot ROM firmware is used. Since EUROScope lite 16FX - like EUROScope - is not rigidly linked to an operating system, it can also be used to debug standalone Fujitsu 16FX assembler and C programs. EURO-Scope lite 16FX has been developed and and will continuously be enhanced by the staff at EUROS Embedded Systems GmbH. EUROScope lite 16FX debugger can be installed on any system running Microsoft Windows.Basic debug functions of EUROScope lite 16FX are:• Reading and writing to the RAM memory of the target system• Reading and writing to the FLASH memory of the target system• Starting a program which has been loaded• Setting break points with various properties• Single stepping of the loaded application• Program debugging either on assembler or C source text levels• Display and modification of the 16FX microcontroller CPU register

Since EUROScope lite 16FX is a cross-debugger, the main component of the debugger runs on the host and is linked to the target system via an interface. In this case the• Fujitsu 16FX Boot ROM is used.

The Fujitsu 16FX Boot ROM runs on the target system, communicates with EUROScope lite 16FX and executes its commands. The communication between the host and target system is done via the asynchro-neous serial interface. This concept permits a powerful user interface with reduced use of internal RAM.

1.3 InstallationEUROScope lite 16FX comes with a handy installation script that provides for seamless setup and integra-tion with existing products. With its intuitive 4 step installation process, preparing a ready to use debug environment has never been that easy:

2

EUROScope Introduction

1.4 Explanation of TermsThe following is an explanation of a number of terms which are used in this document.Target System The hardware based on the Fujitsu 16FX microcontroller architecture on which the

application to be tested runs.Host The development computer on which EUROScope lite 16FX is running and which

is linked to the target system.Target File The file which is loaded onto the target system. This file must be an executable file.

(For example, *.ABS, *.MHX, *.BIN with the Softune Compiler from Fujitsu.)Source Text The application to be tested as a high level language file (normally C).16FX Boot ROM Build On-Chip firmware program running on the target system, that accepts and

executes debug commands.

3

Introduction EUROScope

4

EUROScope Getting Started

Chapter 2 Getting Started

2.1 Establishing a Connection

2.1.1 Fujitsu 16FX Boot ROMFujitsu 16FX Boot ROM target connection is a major EURO-Scope lite 16FX component providing means to access 16FX tar-get boards. The connection is maintained via the internal serial interface (RS232). To establish connection, please consider the steps described below.Select the correct port (COM1, COM2...) on the host system that is connected to the Boot ROM/Debug interface on the target sys-tem. Depending on your cable connection you may or may not need special drivers to access Boot ROM:- connecting through standard RS232 cable requires no extra drivers- connection through USB cable requires special FTDI drivers provided by Fujitsu. USB connection is only possible with some evaluation boards or custom design boards that have FTDI chipsThe parameters for the port must be configured in accordance with the 16FX Boot ROM specifications, in particular with regard to transfer speed. The Menu Preferences > Configure Tar-get Connection is available for this purpose.The Stop after serial interrupt option is always enabled by default.To establish the connection, use Connection > Open. If this menu

item is grayed out (unavailable), the connection may already be open. You can check the status of the con-nection from the status line at the bottom of the window:

2.2 Paths to Program SourcesTo ensure that EUROScope lite 16FX can display the source code for the application, you need to specify correct search paths. When creating a debug information file with the Softune IDE all sources are included by absolute file paths. To resolve source modules also in a different file envirnoment, EUROScope uses reltaive paths beginning from the ABS file location. Therefore a path or paths have to be set in the Search paths configuration. When using usual FME software templates and examples the relative path from the ABS file to the source files location is: ..\Src. In addition, the path for each directory containing program texts may be specified in a list. Please note that EUROScope lite 16FX does not limit the number of source paths entries, but the order of their importance is the same as the order of their apearance.

5

Getting Started EUROScope

In order to open the path table, go to menu item Preferences > Source Paths.... You can change each entry in the table as well as delete or insert entries. You can also change entries order, thus modify search order and relative importance of search paths. This is important when there are files with the same name, resid-ing in different directories. Only the first file path match which is found will be used.

Using the icons, you can insert new entries as well as delete or move selected entries. Double-click on an entry to change it or click again on the icon to redefine it in a pop-up window.

2.3 Loading an ApplicationIn order to start debugging application code as well as debug information should be available. From the menu File > Open Application... you can load complete binary file (program + debug information) into EUROScope lite 16FX (Symbol ). To copy (download) executable to the target system (Symbol ) without the debug information use menu item File > Start Download. These two actions can be combined by selecting File > Open Application and Download... (Symbol ).

2.4 Running an ApplicationOnce application has been downloaded you can begin debugging in real time, using real target hardware. In case your application is in C or another high level language, before starting user code, global variables and service structures need to be initialized. This can be done by using Target > Initialize. The program then stops automatically at the first line of main().You can now run the program step-by-step - that is, line by line in the high-level language or command by command in assembler. In the majority of cases, you will probably want to run the program as normal and only stop when a specific point in the application has been reached. To do this, you must first set a breakpoint at the appropriate location. This is achieved by double-clicking on the grey bar on the left of the source text window. EUROScope lite 16FX supports the following break types:Execution breakpoints Application is stopped upon executing specified instruction.Data breakpoints Application is stopped upon accessing specified address.Range breaks Application is stopped upon accessing specified code area.

6

EUROScope Getting Started

Depending on the way breakpoint are installed, Fujitsu 16FX Boot ROM supports:Software breakpoints Break is generated by replacing instruction with INT9 opcode in ram.Hardware breakpoints Break is generated by using 16FX memory and instruction patch.

There are 8 hardware breakpoints available in EUROScope lite 16FX for data and execution breaks. Depending on application requirements, this number can be reduced to make memory patching slots avail-able for the application.

7

Getting Started EUROScope

8

EUROScope Reference

Chapter 3 Reference

3.1 Configuring the Interface

3.1.1 The WindowsThe EUROScope lite 16FX debugger interface is freely configurable by the user. This allows the efficient use of the screen area. For this reason, docking windows have been used. The window for the application source text is a standard window with the exception that when it is maximized, it only takes up the avail-able space between the docked windows. New windows can be opened from the menu View > New... . New windows are initially always normal, undocked windows. If this window is moved, it automatically docks with the nearest window. The docking function can be suppressed by pressing the Ctrl Key, if for example you want to cascade a large number of windows. When you release the window you can see whether a win-dow is a normal or docked window by looking at the border which displays the position of the window when moving it. If the border is thin and black, the window is docked. If the border thick and grey, the win-dow is normal. Each window has a context menu which is accessed by clicking the right mouse button. These menus contain functions relevant to the window in question such as color..., which is used to change the background color of the window.

3.1.2 Customizing the Shortcuts

Many commands can be accessed using keyboard combinations which are known as shortcuts. These com-mands can be called up quickly without having to use the mouse each time. The shortcuts can be freely defined. When you click on Preferences > Shortcuts... the definition window appears. To do this, you must first select a macro and then use Create Shortcut to create a keyboard combination for this macro. Several keyboard combinations are possible for a macro. Individual keys can be removed from the combination by selecting the key from the Assigned Shortcuts field and clicking on Remove.

9

Reference EUROScope

3.1.3 Customizing the ToolbarYou can run individual commands using the icons on the toolbars.You can specify which icons appear where on the toolbar. Click on Preferences > Toolbars... to show or hide individual toolbars as well as to define new ones. The Menu bar cannot be deactivated otherwise it would no longer be possible to use EUROScope lite 16FX. The toolbars behave in the same way as docking windows in that they can be placed as small windows or docked between existing windows. The Large Buttons function is not available in this version.

When you click on the Commands tab you can drag and drop individual icons onto the toolbar. Deleting icons from the toolbar is achieved using the same principle in reverse - drag the unwanted icons from the toolbar to the Buttons field in the Customize window. The icons are grouped into categories to make it easier to find them. When you click on an icon in the Buttons field, a Description appears, which will also be used as a Tool Tip when the pointer is placed over the icon on the tool-bar. You can also place icons in the menu bar (File Edit ...).

3.2 Loading an ApplicationIn EUROScope lite 16FX loading the application always takes place in two stages, loading binary file to the target Flash memory via the Fujitsu Flash programmer and loading binary and debug information files to the EUROScope host memory (PC). These steps are necessary because EURSOScope 16FX lite needs the debug information from the target file but only the actual program is to be transferred to the target without debug information. Use File > Open Application... to carry out the first step and use File > Start Download to start downloading the file to the target system. Both stages can be combined using the com-mand File > Open Application and Download. The progress of the download is displayed on screen:

In case of connecting to a device with blank flash or a device with misconfigured BDM, initial download should be done either by using Fujitsu standalong pro-

10

EUROScope Reference

grammer or by connecting in serial communication mode (available in EUROScope full).

3.3 The Windows

3.3.1 Source Text ViewThe source text is not contained in the target file debug information. Conse-quently, the debugger must load this information from the host system. Some compilers save the paths relative from which the progran was compiled together with the debug information. In this case, it is sufficient to specify this directory. In the case of compilers which only save the filenames in the debug information, it is necessary to specify the paths of all source texts in the Source Paths window in EUROScope lite 16FX. Specifying the path is achieved using Preferences > Source Paths.... Keywords in the source text are displayed in different colors. The information on the keywords and the associated colors are specified in the file euros.ini. In the context menu for this window it is possible to automatically move the displayed section to the current executed line. This is achieved using Show PC. The current line is indicated by the following symbol: . It is also possible to move the section to a specific address using Show Address.... Since symbols are also permitted when entering the address, you can simply specify the name of a function and view this function in the source text window.

When entering an symbol in the Address window, you can call up a list of all icons by opening the input field drop-down menu. When you input the first few letters of an icons name, you can use the arrow keys to scroll up and down to automatically com-plete the name.

3.3.2 Breakpoint ViewBreakpoints can be placed in code windows, source text windows and the breakpoint window. All break-points are displayed as a list in the breakpoint window - in the other windows only those breakpoints are displayed which are located in the current section.To set a breakpoint in the code window (assembler view), double-click on the grey bar to the left of the

code. Active breakpoints are displayed as red dots . Simply click on a red dot to deactivate the break-

point - the breakpoint remains in the list in the breakpoint window. It is then displayed as a white dot . If you want to completely remove a breakpoint, simply double-click on a red dot.

11

Reference EUROScope

Displaying and setting breakpoints in the source text window is carried out in almost exactly the same way as in the code window. Nevertheless, it is possible here that more than one red dots are displayed for a breakpoint. This means that the compiler has entered the same address for two or more lines in the debug information.

All breakpoints are displayed in the Breakpoint window. Using the con-text menu (right-click on the mouse) you can remove, deactivate and activate all breakpoints or indi-vidual breakpoints and insert new ones. When inserting a new break-point, you must specify the address or a symbol. You can display a list of available symbols using the Pull-down

menu in the address input field. Depending on the compiler, the symbols can have an underscore before the actual name in the debug information. These underscores must be remembered when entering the symbol names. The Show menu item allows you to move the code and source text window to the section in which this breakpoint is located.

3.3.3 Memory ViewThe memory view always represents a section of the memory in the target system. Using the context menu, you can select the representation and the area. The start address for the area is set using Show Address.... It is also possible to enter an sym-bol name here too. Representation may take place using 8, 16 or 32 Bit. If ASCII has been activated, the content is also displayed as characters in the memory view. It is only necessary to change from Little- or Big Endian when changing processor types. In this case, the representation of the 16 and 32 Bit numbers is affected. In the case of Little Endian architectures, the lower value byte is located in memory first (at the smaller address). In the case of Big Endian architectures, the higher value byte is located in memory first. All memory contents which are represented in red have changed since the screen was last refreshed. The window is always refreshed when the target system is stopped, for example, after each line if the application is running on a line by line basis.

3.3.4 Variable ViewIn the variable view, all local variables in the current routine are displayed. The left part of the screen displays all variable names in a tree structure. Branches in this tree structure are structures or fields which open out when you click on the + symbol. The Value column con-tains the current values of the variables. The representation of the int-variables can be changed between hexadecimal and decimal using the context menu. By clicking on Show Strings in the context menu, you can activate the additional display of indicators on charac-

ters as strings. The Info column displays the type information for the variables. These contain the type of variable, its location (address in memory or name of register) and in the case of structures, the offset to the basic address. With a double click on the value of a variable it is poosible to change the value.

3.3.5 Register ViewThe processor’s registers for the target system are displayed in this window. Their representation corre-sponds for the Fujitsu 16FX family of microcontrollers. Register contents which have changed since the last time the screen was refreshed are displayed in red.

3.3.6 Terminal Window

12

EUROScope Reference

All characters which are output by the application through the „printf“ style output interface are displayed in the terminal window. The input of data for the application is also possible here. It should be noted here that the Stop after Serial Interrupt option in the menu Preferences > Configure Target Connection cannot then be activated. The terminal does not support any control characters, in other words it does not emulate a known terminal. The number of lines which are stored in the terminal window can be configured via the context menu. Furthermore, the output which takes place through the terminal window can be logged in a protocol file. To do this you must first specify the name of the protocol file using Protocol File... in the con-text menu. By selecting Send Protocol to File ’<filename>’ you can activate the saving of the logfile. If you previously activated the option Append to Protocol File, the data is attached to an existing file; if this point was not activated, the old data is deleted.

13

Reference EUROScope

14

EUROScope Flashing tools

Chapter 4 Flashing tools

4.1 Using the embedded flash toolsEUROScope lite 16FX can be used for flashing both Flash A and Flash B memory of supported Fujitsu MCUs. This is accomplished by providing a feature-rich integrated tool and set of Flash B algorithms that can be easily extended or customized. As long as EUROScope flash protocol is followed it is possible to use any custom made flashing algorithm.There are two options available in EUROScope to find appropriate flash algorithm - automatic detection and using custom initialization scripts. Fujitsu 16FX target connection implements automatic flash type recognition based on chip identifier of the connected device. Automatic detection and flash recognition is done upon opening your target connection, so no additional actions are required to flash your data.

4.2 Mode of operationThere are two options available for flashing data or application code:- using EUROScope flash dialog either by pressing corresponding toolbar button, or by selecting the Tools->Flash menu item.- downloading application directly using the File -> Open Application and Download menu item.

15

Flashing tools EUROScope

4.3 Configuring the flash agentAs erasing and changing flash contents may alter configuration settings of Boot ROM provided with your device, it’s necessary to let EUROScope know desired baud rate, auto start and security settings in effect after new data is flashed. Therefore a Boot ROM configuration dialog is shown first after selecting flash button or menu item:

Depending on the existing configuration EUROScope will enable or disable certain security buttons. Please refer to Fujitsu documentation regarding the flash security options. Kindly note, that improper use of locking may prevent you from reading flash contents.However, the default configuration provided by EUROScope will cover all typical debug sessions.After the configuration has been closed, EUROScope will read available flash configuration data, match the device ID and provide appropriate interface controlling the underlying flash agent. Depending on the connection speed a short delay may be observed after closing configuration window and showing flash control dialog. This time is required to transfer the flash agent to the target memory and perform intial sta-tus check of target hardware.

16

EUROScope Flashing tools

4.4 Erasing Flash A/B memoryOnce flash agent has taken control, EUROScope will show the following flash control dialog:

It is required that the existing flash contents must be erased prior writing new data. Flash agents are pro-grammed in a way to minize flash wearout. So if the flash memory is already empty, no erase will be per-formed. Standard erase procedure includes blank check, so once the message “Erase successful” has been prompted this also means blank check has returned OK:

17

Flashing tools EUROScope

4.5 Programming Flash A/B memoryEUROScope flash tool takes advantage of all available EUROScope object format analyzers. Therefore any supported file can be opened, processed and written into flash. For Fujitsu 16FX this means that com-mon formats ABS, MHX, BIN are parsed and analyzed.

EUROScope flash tool provides generic interface for flashing different memory devices. Therefore depending on the flash agent and debug interface some buttons may not be available. For example Fujitsu 16FX flash agents not only write data but also check for consistency. Therefore “Verify” button is disabled - there is no need for separate data verification.When using Fujitsu 16FX Boot ROM target connection, portions of the Boot ROM configuration block can be overwritten and will differ from the original contents of the binary file. However, no customer code and data sections will be affected.After flashing is complete, it is required to reset the target device, in order to take control away from the downloaded flash agent and reestablish the ongoing target connection:

18

EUROScope Flashing tools

19

Flashing tools EUROScope

20

EUROScope Comparison between EUROScope full and EUROScope lite 16FX

Chapter 5 Comparison between EUROScope full and EUROScope lite 16FX

The full version of EUROScope offers much more functionality in comparison with the EUROScope lite 16FX one. These additional functionality makes the development of the embedded applications for Fujitsu 16FX even easier. The following table contains a summary of most important functions of EUROScope and whether they are available in the lite or in the full version:

Table 1: Function comparison

Function Comment Package

1 Reset lite/full

2 Initialize lite/full

3 Set Start address lite/full

4 Go lite/full

5 Stop lite/full

6 Step Into lite/full

7 Step Over lite/full

8 Leave Function lite/full

9 Run Until Cursor lite/full

10 Fill Memory lite/full

11 Verify Program Image full

Communication

12 Open lite/full

13 Close lite/full

Tools (flash programming)

14 Adopt Algorithm Erasing lite/full

15 Adopt Algorithm Writing lite/full

16 Configure target RCB lite/full

17 Patch user program with RCB lite/full

21

Comparison between EUROScope full and EUROScope lite 16FX EUROScope

Preferences

18 Source path lite/full

19 Toolbars lite/full

20 Shortcuts lite/full

21 User Tools lite/full

22 Fonts lite/full

23 Load Configuration lite/full

24 Save Configuration lite/full

25 Save Configuration As lite/full

26 Recent Configuration lite/full

27 Configure Bootloader lite/full

28 Configure Target lite/full

29 Select Target Connection lite/full

Asynchronous communication lite/full

Asynchronous dial-up lite/full

Passive/Silent connect lite/full

Debugging in Mode 2 full

Handle security key in Mode 2 full

View

30 Toolbar lite/full

31 Status bar lite/full

32 New breakpoints lite/full

33 Set/Clear breakpoint lite/full

Set/Clear Range breakpoint lite/full

External break (stop) lite/full

Instruction break full address lite/full

Operand break full address lite/full

Instr/Operand break address mask lite/full

Instr/Operand break address mask lite/full

Operand break data value lite/full

Reserve channels for application full

Table 1: Function comparison

Function Comment Package

22

EUROScope Comparison between EUROScope full and EUROScope lite 16FX

34 Callstack full

35 EUROS objects if EUROS installed full

36 EUROStrace if EUROS installed full

37 Function browser full

38 Memory window lite/full

39 Watch window lite/full

40 Manual update of regiters lite/full

41 Extended LX register view lite/full

42 Ram and register shadowing lite/full

43 SFR window full

44 Source window lite/full

45 Terminal window lite/full

46 Variables (local) window lite

47 Variables (local/global) window full

48 Command Line interpreter full

49 ORTI objects if OSEK installed full

Special operation

50 Remotely release COM port lite/full

51 Enhanced file path handling lite/full

52 Enhanced hex address handling lite/full

Device awareness

53 Support device configuration lite/full

54 Select device based on hardware chip id lite/full

Table 1: Function comparison

Function Comment Package

23

Comparison between EUROScope full and EUROScope lite 16FX EUROScope

24