EUROScope lite 16FX Reference Manual

Transcription

1 lite 16FX Reference Manual June 2007 EUROS Embedded Systems GmbH Campestraße 12 D Nuremberg Germany Fon: Fax: Web:

2 Rev. Revision history Date -001 Original issue Approved for in-house use and shipment to customers

3 Reference Manual Contents Table of contents Chapter 1 Introduction 1.1 What is? What is lite 16FX? Installation Explanation of Terms Chapter 2 Getting Started 2.1 Establishing a Connection Fujitsu 16FX Boot ROM Paths to Program Sources Loading the Application Running the Application Chapter 3 Reference 3.1 Configuring the Interface The Windows Customizing the Shortcuts Customizing the Toolbar Loading the Application The Windows Source Text View Breakpoint View Memory View Variable View Register View Chapter 4 Comparison between and lite 16FX i

4 Contents Reference Manual ii

5 Introduction Chapter 1 Introduction 1.1 What is? 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 is not rigidly linked to an operating system, it can also be used to debug standalone assembler and C programs. What is more, the target platform is not restricted to one particular processor architecture. 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 Microsoft Windows. Basic debug functions of 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 Comman Line Interpreter Memory emulation Since 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 system 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 provides memory emulation, that can be used to examine application executable and perform some basic analysis. 1

6 Introduction 1.2 What is lite 16FX? lite 16FX is a version of the universal source level cross debugger 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 is used. Since lite 16FX - like - is not rigidly linked to an operating system, it can also be used to debug standalone Fujitsu 16FX assembler and C programs. lite 16FX has been developed and and will continuously enhanced by the staff at EUROS Embedded Systems GmbH. lite 16FX debugger can be installed on any system running Microsoft Windows. Basic debug functions of lite 16FX are: Reading and writing to the target system 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 16FX microcontroller register Since 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 is a fixed firmware besides user ROM and runs on the target system, communicates lite 16FX and executes its commands. The communication between the host and target system is done via the asynchroneous serial interface. This concept permits a powerful user interface with reduced use of user RAM. 1.3 Installation lite 16FX comes with a handy installation script that provides for seamless setup and integration with existing products. With its intuitive 4 step installation process, preparing a ready to use debug environment has never been that easy: 2

7 Introduction 1.4 Explanation of Terms The following is an explanation of a number of terms which are used in this document. Target System Host Target File Source Text 16FX Boot ROM The hardware based on the Fujitsu 16FX microcontroller architecture on which the application to be tested runs. The development computer on which lite 16FX is running and which is linked to the target system. The file which is loaded onto the target system. This file must be an executable file. (For example, *.ABS with the Softune Compiler from Fujitsu.) The application to be tested as a high level language file (normally C). Build On-Chip firmware program running on the target system, that accepts and executes debug commands. 3

8 Introduction 4

9 Getting Started Chapter 2 Getting Started 2.1 Establishing a Connection Fujitsu 16FX Boot ROM Fujitsu 16FX Boot ROM target connection is a major EUROS cope lite 16FX component providing means to access 16FX target 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 system. 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 The 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 Target Connection is available for this purpose. You can activate the option Stop after serial interrupt in order to stop the application with the ESC key on the host. After this, however, it is no longer possible for the application to receive inputs from lite 16FX via the terminal window. 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 connection from the status line at the bottom of the window: 2.2 Paths to Program Sources To ensure that lite 16FX can display the source code for the application, you need to specify correct search paths. The Softune compiler includes absolute file names and path names in the debug information for the target files, which makes it necessary to specify one root directory and automatically reconstruct source tree. It is also possible to enter a relative path, witch will be resolved starting from ABS file location. In addition, the path for each directory containing program texts may be specified in a list. Please note that 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

10 Getting Started 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, residing 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. Doubleclick on an entry to change it or click again on the icon to redefine it in a pop-up window. 2.3 Loading the Application In 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 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 the Application Once 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. lite 16FX supports the following breakpoint types: Execution breakpoints Application is stopped upon executing specified instruction. Data breakpoints Range area breakpoints Application is stopped upon accessing specified address. Application is stopped upon accessing specified code area. 6

11 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 lite 16FX for data and execution breaks. 7

12 Getting Started 8

13 Reference Chapter 3 Reference 3.1 Configuring the Interface The Windows The 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 available 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 window 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 window 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 Customizing the Shortcuts Many commands can be accessed using keyboard combinations which are known as shortcuts. These commands 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

14 Reference Customizing the Toolbar You 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 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 toolbar. You can also place icons in the menu bar (File Edit...). 3.2 Loading the Application In lite 16FX loading the application always takes place in two stages, loading binary file to the targer Flash memory via the Fujitsu Flash programmer and loading binary and debug information files to the 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 command File > Open Application and Download. The progress of the download is displayed on screen. 10

15 Reference 3.3 The Windows Source Text View The source text is not contained in the target file debug information. Consequently, 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 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 complete the name Breakpoint View Breakpoints can be placed in code windows, source text windows and the breakpoint window. All breakpoints 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 breakpoint - 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 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 two red dots are displayed for a breakpoint. 11

16 Reference 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 context menu (right-click on the mouse) you can remove, deactivate and activate all breakpoints or individual breakpoints and insert new ones. When inserting a new breakpoint, 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 Memory View The 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 symbol 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 Variable View In 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 contains 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 characters 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 Register View The processors registers for the target system are displayed in this window. Their representation corresponds for the Fujitsu 16Fx family of microcontrollers. Register contents which have changed since the last time the screen was refreshed are displayed in red. 12

17 Comparison between and lite 16FX Chapter 4 Comparison between and lite 16FX In general, offers much more functionality in comparison with the lite 16FX version. 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 and whether they are available in the lite or in the professionalprofi version: Table 1: Function comparison Function Comment Package File lite/profi 1 Open Application lite/profi 2 Open Application and Download lite/profi 3 Load additional Symbols lite/profi 4 Start Download lite/profi 5 Abort Download lite/profi 6 Exit lite/profi Target lite/profi 7 Reset lite/profi 8 Initialize lite/profi 9 Set Start address lite/profi 10 Go lite/profi 11 Stop lite/profi 12 Step Into lite/profi 13 Step Over lite/profi 14 Leave Function lite/profi 15 Run Until Cursor lite/profi 16 Fill Memory lite/profi 17 Verify Program Image profi 13

18 Comparison between and lite 16FX Table 1: Function comparison Function Comment Package Communication 18 Open lite/profi 19 Close lite/profi Tools (flash programming) 20 Adopt Algorithm Erasing profi 21 Adopt Algorithm Writing profi 22 Configure target RCB profi 23 Patch user program with RCB profi Preferences 24 Source path lite/profi 25 Toolbars lite/profi 26 Shortcuts lite/profi 27 User Tools lite/profi 28 Fonts lite/profi 29 Load Configuration lite/profi 30 Save Configuration lite/profi 31 Save Configuration As lite/profi 32 Recent Configuration lite/profi 33 Configure Bootloader lite/profi 34 Configure Target lite/profi 35 Select Target Connection lite/profi 36 Asynchronous communication lite/profi 37 Asynchronous dial-up lite/profi 38 Passive/Silent connect lite/profi 39 K-Line communication profi 40 Synchronous communication profi 41 Debugging in Mode 2 profi 42 Handle security key in Mode 2 profi 14

19 Comparison between and lite 16FX Table 1: Function comparison Function Comment Package View 43 Toolbar lite/profi 44 Status bar lite/profi 45 New breakpoints lite/profi 46 Set/Clear breakpoint lite/profi 47 Set/Clear Range breakpoint lite/profi 48 External break (stop) lite/profi 49 Instruction break full address lite/profi 50 Operand break full address lite/profi 51 Instr./Operand break address mask lite/profi 52 Instr./Operand break address mask lite/profi 53 Operand break data value lite/profi 54 Reserve channels for application profi 55 Callstack profi 56 EUROSobjects if EUROS installed profi 57 EUROStrace if EUROS installed profi 58 Function browser profi 59 Memory window lite/profi 60 Watch window lite/profi 61 Manual update of regiters lite/profi 62 Extended LX register view lite/profi 63 RAM and register shadowing lite/profi 64 SFR window profi 65 Source window lite/profi 66 Terminal window profi 67 Variables (local) window lite 68 Variables (local/global) window profi 69 Command Line interpreter profi 70 ORTIobjects if OSEK installed profi 15

20 Comparison between and lite 16FX Table 1: Function comparison Function Comment Package Special operation 71 Remotely release COM port lite/profi 72 Enhanced file path handling lite/profi 73 Enhanced hex address handling lite/profi Device awareness 74 Support device configuration lite/profi 75 Select device based on hardware chip id lite/profi 16