FUJITSU SEMICONDUCTOR CONTROLLER MANUAL CM71-00329-7E FR FAMILY SOFTUNETM WORKBENCH USER’S MANUAL for V6
FR FAMILY SOFTUNETM WORKBENCH USER’S MANUAL for V6 FUJITSU SEMICONDUCTOR LIMITED
Preface ■ What is the SOFTUNE Workbench? SOFTUNE Workbench is support software for developing programs for the FR families of microprocessors / microcontrollers. It is a combination of a development manager, simulator debugger, emulator debugger, monitor debugger, and an integrated development environment for efficient development. ■ Purpose of this manual and target readers This manual explains the functions of SOFTUNE Workbench.
• • • • • • • The contents of this document are subject to change without notice. Customers are advised to consult with sales representatives before ordering. The information, such as descriptions of function and application circuit examples, in this document are presented solely for the purpose of reference to show examples of operations and uses of FUJITSU SEMICONDUCTOR device; FUJITSU SEMICONDUCTOR does not warrant proper operation of the device with respect to use based on such information.
CONTENTS CHAPTER1 Basic Functions .......................................................................................... 1 1.1 Workspace Management Function ..................................................................................................... 2 1.2 Project Management Function ............................................................................................................ 3 1.3 Project Dependence ..............................................................................
2.1.10.5 Searching Trace Data ............................................................................................................... 55 2.1.10.6 Saving Trace Data .................................................................................................................... 56 2.1.10.7 Clearing Trace Data ................................................................................................................. 57 2.1.11 Measuring Coverage ................................................
2.3.4.2 Data Break .............................................................................................................................. 2.3.4.3 Code Event Break .................................................................................................................. 2.3.4.4 Data Event Break ................................................................................................................... 2.3.4.5 Trace Buffer-full Break .....................................................
2.4.7.2 Measuring Event-to-Event Execution Cycle Count [Performance Measurement] .................. 2.4.8 Viewing Program Execution History [Trace] .............................................................................. 2.4.8.1 Displaying Trace Data ............................................................................................................ 2.4.8.2 Saving Trace Data .................................................................................................................. 2.4.
CHAPTER1 Basic Functions This chapter describes the basic functions on the SOFTUNE Workbench. 1.1 Workspace Management Function 1.2 Project Management Function 1.3 Project Dependence 1.4 Make/Build Function 1.5 Include Dependencies Analysis Function 1.6 Functions of Setting Tool Options 1.7 Error Jump Function 1.8 Editor Functions 1.9 Storing External Editors 1.10 Storing External Tools 1.11 Macro Descriptions Usable in Manager 1.12 Setting Operating Environment 1.13 Debugger Types 1.
CHAPTER1 Basic Functions 1.1 Workspace Management Function This section explains the workspace management function of SOFTUNE Workbench. ■ Workspace SOFTUNE Workbench uses workspace as a container to manage two or more projects including subprojects. For example, a project that creates a library and a project that creates a target file using the project can be stored in one workspace.
CHAPTER1 Basic Functions 1.2 Project Management Function This section explains the project management function of SOFTUNE Workbench. ■ Project Management Function The project manages all information necessary for development of a microcontroller system.
CHAPTER1 Basic Functions ■ Project Configuration The project configuration is a series of settings for specifying the characteristics of a target file, and making, building, compiling and assembling is performed in project configurations. Two or more project configurations can be created in a project. The default project configuration name is Debug. A new project configuration is created on the setting of the selected existing project configuration.
CHAPTER1 Basic Functions 1.3 Project Dependence This section explains the project dependence of SOFTUNE Workbench. ■ Project Dependence If target files output by other projects must be linked, a subproject is defined in the project required in the [Project] - [Project Dependence] command. The subproject is a project on which other projects depend. By defining project dependence, a subproject can be made and built to link its target file before making and building the parent project.
CHAPTER1 Basic Functions 1.4 Make/Build Function This section explains the make/build function of SOFTUNE Workbench. ■ Make Function Make function generates a target file by compiling/assembling only updated source files from all source files registered in a project, and then joining all required object files. This function allows compiling/assembling only the minimum of required files. The time required for generating a target file can be sharply reduced, especially, when debugging.
CHAPTER1 Basic Functions 1.4.1 Customize Build Function This section describes the SOFTUNE Workbench function to set the Customize Build function. ■ Customize Build Function In SOFTUNE Workbench, different tools can be operated automatically before and after executing the Assembler, Compiler, Linker, Librarian, Converter, or Configurator started at Compile, Assemble, Make, or Build.
CHAPTER1 Basic Functions Note: When checking [Use the Output window], note the following: • Once a tool is activated, Make/Build activated until the tool is terminated. • The Output window must not be used with a tool using a wait state for user input while the tool is executing. The user can not perform input while the Output window is in use, so the tool cannot be terminated. To forcibly terminate the tool, select the tool on the Task bar and input Control - C, or Control - Z.
CHAPTER1 Basic Functions 1.5 Include Dependencies Analysis Function This section describes the function of the Include Dependencies Analysis of SOFTUNE Workbench. ■ Analyzing Include Dependencies A source file usually includes some include files. When only an include file has been modified leaving a source file unchanged, SOFTUNE Workbench cannot execute the Make function unless it has accurate and updated information about which source file includes which include files.
CHAPTER1 Basic Functions 1.6 Functions of Setting Tool Options This section describes the functions to set options for the language tools activated from SOFTUNE Workbench. ■ Function of Setting Tool Options To create a desired target file, it is necessary to specify options for the language tools such as a compiler, assembler, and linker. SOFTUNE Workbench stores and manages the options specified for each tool in project configurations.
CHAPTER1 Basic Functions 1.7 Error Jump Function This section describes the error jump function in SOFTUNE Workbench. ■ Error Jump Function When an error, such as a compile error occurs, double-clicking the error message displayed in the Output window, opens the source file where the error occurred, and automatically moves the cursor to the error line. This function permits efficient removal of compile errors, etc.
CHAPTER1 Basic Functions [Example] *** %f(%l) %h: or, %[*] %f(%l) %h: The first four characters are "*** ", followed by the file name and parenthesized line number, and then the keyword for help continues after one blank character. This represents the following message: *** C:\Sample\sample.c(100) E4062C: Syntax Error: near /int.
CHAPTER1 Basic Functions 1.8 Editor Functions This section describes the functions of the SOFTUNE Workbench built-in standard editor. ■ Standard Editor SOFTUNE Workbench has a built-in editor called the standard editor. The standard editor is activated as the Edit window in SOFTUNE Workbench. As many Edit windows as are required can be opened at one time. The standard editor has the following functions in addition to regular editing functions.
CHAPTER1 Basic Functions ● Font changing function The font size for character string displayed in the Edit window can be selected.
CHAPTER1 Basic Functions 1.9 Storing External Editors This section describes the function to set an external editor to SOFTUNE Workbench. ■ External Editor SOFTUNE Workbench has a built-in standard editor, and use of this standard editor is recommended. However, another accustomed editor can be used, with setting it, instead of an edit window. There is no particular limit on which editor can be set, but some precautions (below) may be necessary.
CHAPTER1 Basic Functions Table 1.9-1 List of Special Characters for Analyzing Error Message Parameter Semantics %% Means specifying % itself %f Means specifying file name %l Means specifying line number %x Means specifying project path ■ Example of Optional Settings Table 1.9-2 Example of Optional Settings (For External Editors) Editor name Argument WZ Editor V4.0 %f /j%l MIFES V1.
CHAPTER1 Basic Functions 1.10 Storing External Tools This section describes the SOFTUNE Workbench function to set an external tool. ■ External Tools A non-standard tool not attached to SOFTUNE Workbench can be used by setting it as an external tool and by calling it from SOFTUNE Workbench. Use this function to coordinate with a source file version management tool.
CHAPTER1 Basic Functions 1.11 Macro Descriptions Usable in Manager This section explains the macro descriptions that can be used in the manager of SOFTUNE Workbench. ■ Macros SOFTUNE Workbench has special parameters indicating that any file name and tool-specific options are specified as options. The use of these parameters as tool options eliminates the need for options specified each time each tool is started.
CHAPTER1 Basic Functions Table 1.11-1 List of macros that can be specified 1 Parameter Meaning %f Passed as full-path name of file. (*1) %F Passed as main file name of file. (*1) %d Passed as directory of file. (*1) %e Passed as extension of file. (*1) %a Passed as full-path name of load module file. %A Passed as main file name of load module file. (*2) %D Passed as directory of load module file. (*2) %E Passed as extension of load module file.
CHAPTER1 Basic Functions • Tool options 1. Null character • Others 1. File as focus is on the SRC tab of project window and valid file name is selected 2. File on which focus is in internal editor as no valid file name can be obtained in 1 3. Null character if no valid file name can be obtained *2: The macros are determined as follows: • Customize build and tool options 1. Information on configuration of project under building, making, compiling and assembling • Others 1.
CHAPTER1 Basic Functions ■ Examples of Macro Expansion If the following workspace is opened, macro expansion is performed as follows: Workspace : Active project : Active project configuration Object directory : C:\Wsp\Wsp.wsp C:\Wsp\Sample\Sample.prj - Debug C:\Wsp\Sample\Debug\Obj\ Subproject : C:\Subprj\Subprj.prj Active project configuration - Release Object directory : C:\Subprj\Release\Obj\ Target file : C:\Subprj\Release\Abs\Subprj.
CHAPTER1 Basic Functions 1.12 Setting Operating Environment This section describes the functions for setting the SOFTUNE Workbench operating environment. ■ Operating Environment Set the environment variables for SOFTUNE Workbench and some basic items for the workspace. To set the operating environment, use the [Setup]-[Development] command. ● Environment Variables Environment variables are variables that are referred to mainly using the language tools activated from SOFTUNE Workbench.
CHAPTER1 Basic Functions 1.13 Debugger Types This section describes the types of SOFTUNE Workbench debuggers. ■ Type of debugger SOFTUNE Workbench integrates three types of debugger: a simulator debugger, emulator debugger, and monitor debugger. Any one can be selected depending on the requirement. ■ Simulator Debugger The simulator debugger simulates the MCU operations (executing instructions, memory space, I/O ports, interrupts, reset, etc.) with software to evaluate a program.
CHAPTER1 Basic Functions 1.14 Memory Operation Functions This section describes the memory operation functions. ■ Functions for Memory Operations • Display/Modify memory data Memory data can be display in the Memory window and modified. • Fill The specified memory area can be filled with the specified data. • Copy The data in the specified memory area can be copied to another area. • Compare The data in the specified source area can be compared with data in the destination area.
CHAPTER1 Basic Functions 1.15 Register Operations This section describes the register operations. ■ Register Operations The Register window is opened when the [View] - [Register] menu is selected. The register and flag values can be displayed in the Register window. For further details about modifying the register value and the flag value, refer to "4.4.4 Register" in "SOFTUNE Workbench Operation Manual".
CHAPTER1 Basic Functions 1.16 Line Assembly and Disassembly This section describes line assembly and disassembly. ■ Line Assembly To perform line-by-line assembly (line assembly), right-click anywhere in the Disassembly window to display the short-cut menu, and select [Inline Assembly]. For further details about assembly operation, refer to "4.4.3 Assembly" in "SOFTUNE Workbench Operation Manual". ■ Disassembly To display disassembly, use the [View] - [Assembly] command.
CHAPTER1 Basic Functions 1.17 Symbolic Debugging The symbols defined in a source program can be used for command parameters (address). There are three types of symbols as follows: • Global Symbol • Static Symbol within Module (Local Symbol within Module) • Local Symbol within Function ■ Types of Symbols A symbol means the symbol defined while a program is created, and it usually has a type. Symbols become usable by loading the debug information file.
CHAPTER1 Basic Functions ■ Line Number Information Line number information is set with the line number information table in SOFTUNE Workbench when a debug information file is loaded. Once registered, such information can be used at anytime thereafter.
CHAPTER1 Basic Functions 1.17.1 Referring to Local Symbols This section describes referring to local symbols and Scope. ■ Scope When a local symbol is referred to, Scope is used to indicate the module and function to which the local symbol to be referred belongs. SOFTUNE Workbench automatically scopes the current module and function to refer to local symbols in the current module with preference.
CHAPTER1 Basic Functions 1.17.2 Referring to C/C++ Variables C/C++ variables can be specified using the same descriptions as in the source program written in C/C++. ■ Specifying C/C++ Variables C/C++ variables can be specified using the same descriptions as in the source program. The address of C/ C++ variables should be preceded by the ampersand symbol "&". Some examples are shown in the Table 1.17-1 . Table 1.
CHAPTER1 Basic Functions ■ Notes on C/C++ Symbols The C/C++ compiler outputs symbol information with "_" prefixed to global symbols. For example, the symbol main outputs symbol information _main. However, SOFTUNE Workbench permits access using the symbol name described in the source to make program debugging described in C/C++ easier. Consequently, a symbol name described in C/C++ and a symbol name described in assembler, which should both be unique, may be identical.
CHAPTER1 Basic Functions 32
CHAPTER2 Dependence Functions This chapter describes the functions dependent on each Debugger. 2.1 Simulator Debugger 2.2 Emulator Debugger (MB2197) 2.3 Emulator Debugger (MB2198) 2.4 Emulator Debugger (MB2100-01) 2.
CHAPTER2 Dependence Functions 2.1 Simulator Debugger This section describes the functions of the simulator debugger. ■ Simulator Debugger The simulator debugger simulates the MCU operations (executing instructions, memory space, I/O ports, interrupts, reset, etc.) with software to evaluate a program. It is used to evaluate an uncompleted system, the operation of single units, etc. There are 2 types of simulator debuggers.
CHAPTER2 Dependence Functions Target program size CODE XX(KB) DATA YY(KB) Required RAM space (MB) = 20 + (XX / 64) 6 + (YY / 64) 1.5 However, RAM space larger than the above may be needed depending on program allocation. Allocate memory space consecutive areas should be reserved as much as possible.
CHAPTER2 Dependence Functions 2.1.1 Instruction Simulation This section describes the instruction simulation executed. ■ Instruction Simulation This simulates the operations of all instructions supported by the FR Family. It also simulates the changes in memory and register values due to such instructions.
CHAPTER2 Dependence Functions 2.1.2 Memory Simulation This section describes the memory simulation executed. ■ Memory Simulation The simulator debugger must first secure memory space to simulate instructions because it simulates the memory space secured in the host PC memory. • To secure the memory area, either use the [Setup] - [Memory Map] menu, or the SET MAP command in the Command window.
CHAPTER2 Dependence Functions 2.1.3 I/O Port Simulation This section describes I/O port simulation executed. ■ I/O Port Simulation (Input Port) There are two types of simulations in I/O port simulation: simulation. Input port simulation has the following types: input port simulation, and output port • Whenever a program reads the specified port, data is input from the pre-defined data input source.
CHAPTER2 Dependence Functions 2.1.4 Interrupt Simulation This section describes interrupt simulation executed. ■ Interrupt Simulation This simulates the MCU operation for an interrupt request. The following types can be used to allow an interrupt to occur. • When the instruction is executed as many cycles as the specified cycle count while executing a program (executing execution commands), generate an interrupt corresponding to the specified interrupt number to reset the interrupt generating condition.
CHAPTER2 Dependence Functions 2.1.5 Reset Simulation This section describes the reset simulation executed. ■ Reset Simulation The simulator simulates the operation when a reset signal is input to the MCU using the [Debug]-[Reset MCU] menu or RESET command, and initializes the registers. The function for performing reset processing by operation of MCU instructions (writing to RST bit in standby control register) is also supported.
CHAPTER2 Dependence Functions 2.1.6 Low Power Consumption Mode Simulation This section describes the low power consumption mode simulation executed. ■ Low Power Consumption Mode Simulation The MCU enters the low power consumption mode in accordance with the MCU instruction operation (Write to SLEEP bit or STOP bit of standby control register). Once in the sleep mode or stop mode, a message ("sleep" for sleep mode, "stop" for stop mode) is displayed on the Status Bar.
CHAPTER2 Dependence Functions 2.1.7 STUB Function This section describes the STUB function which executes commands automatically when the breakpoint hit occurs. ■ Outline of STUB Function The STUB function is supported so that a series of commands in the command list can automatically be executed when a specified breakpoint is hit. The use of this function enables spot processing, such as simple I/O simulation, external interrupt generation, and memory reprogramming, without changing the main program.
CHAPTER2 Dependence Functions 2.1.8 Break This Simulator Debugger provides five types of break functions. When by each break function aborts program execution, the address where a break occurred and the break factor are displayed.
CHAPTER2 Dependence Functions 2.1.8.1 Code Break This function causes a break by monitoring a specified address by software. A break occurs before executing an instruction at the specified address. ■ Code Break When the program reaches a break point (immediately before executing the instruction at the memory location), the simulator debugger executes the following processes: 1. Suspend program execution (before executing instruction). 2. Checks count of arrival time.
CHAPTER2 Dependence Functions 2.1.8.2 Data Break This function aborts the program execution when a data access (read/write) is made to a specified address. ■ Data Break When data is written or read to a data break point, the simulator debugger executes the following processes: 1. Suspend program execution after completing instruction execution 2. Checks access count. If the access count has not yet been reached the count for the specified data break point, the simulator resumes the program execution.
CHAPTER2 Dependence Functions 2.1.8.3 Trace Buffer-full Break This function aborts the program execution when the trace buffer becomes full. ■ Trace Buffer-full Break This function aborts the program execution when the trace buffer becomes full. When the trace buffer-full break occurs, the following message appears at the status bar. Break at address by trace buffer full ■ How to set Set the trace buffer-full break as follows. • Command - SET TRACE/BREAK For details, refer to "4.
CHAPTER2 Dependence Functions 2.1.8.4 Guarded Access Break A guarded access break suspends a executing program when accessing in violation of the access attribute set by using the [Setup]-[Memory Map] command, and accessing a guarded area (access-disabled area in undefined area).
CHAPTER2 Dependence Functions 2.1.8.5 Forced Break This function forcibly aborts the program execution to generate a break. ■ Forced Break This function forcibly aborts the program execution to generate a break. When the forced break occurred, the following message appears at the status bar. Break at address by command abort request ■ How to Generate A forced break is generated in the following methods: • Menu [Debug] - [Abort] menu For details, refer to "4.6.
CHAPTER2 Dependence Functions 2.1.9 Measuring Execution Cycle Count This function measures the program execution cycle count and step count. ■ The measuring item Measures program execution cycle count and step counts. ● Execution Cycle Count This is calculated based on the basic cycle count of each instruction described in the Programming Manual.
CHAPTER2 Dependence Functions 2.1.10 Trace The address and status information can be sampled during program execution to record it in a trace buffer. This function is called a trace. ■ Trace Data recorded with the trace function can be used to make a detailed analysis of a program execution history. The trace buffer is in the form of a ring. When it becomes full, it records the next data by automatically overwriting the buffered data at the beginning.
CHAPTER2 Dependence Functions 2.1.10.1 Trace Sampling Trace measurements are made of a program execution status during the interval between the start and stop of program execution. ■ Trace Sampling While the trace function is enabled, data is always sampled and recorded in the trace buffer during execution of an execution command. The program execution aborts due to a break factor such as a breakpoint, terminating the trace. Furthermore, when the trace buffer becomes full, a program break can be invoked.
CHAPTER2 Dependence Functions 2.1.10.2 Setting Trace You must set the following two items to perform a trace. After that, trace data will be sampled with the execution of the program. You can set this from the command window. ■ Setting Trace 1. Enable the trace function - This is done by [Setup] - [Trace] in the trace window shortcut menu. This program will startup and will be enabled. 2. Set the trace buffer full break - When the trace buffer is full, you can make a break.
CHAPTER2 Dependence Functions 2.1.10.3 Displaying Trace Data Data recorded in the trace buffer can be displayed. ■ Displaying Trace Data The trace window displays how much trace data is stored in the trace buffer. Also, you can use the SHOW TRACE command from the command window.
CHAPTER2 Dependence Functions 2.1.10.4 Display Format of Trace Data There are two display formats for displaying the data stored in the trace buffer. ■ Display Format of Trace Data • Display Only Instruction Operation: Specify Instruction • Display by Unit of Source Lines: Specify Source ■ Display Only Instruction Operation In this mode, the instruction operation is displayed in disassembly units. ■ Display by Unit of Source Lines This mode only displays source lines.
CHAPTER2 Dependence Functions 2.1.10.5 Searching Trace Data The trace buffer can be searched to locate target data. ■ Searching Trace Data Specify the address information for the search purpose. This search function can be run by clicking the Search button in the trace window.
CHAPTER2 Dependence Functions 2.1.10.6 Saving Trace Data The debugger has function of saving trace data. ■ Saving Trace Data Save the trace data to the specified file. For details on operations, refer to Sections "3.14 Trace Window", and "4.4.8 Trace" in "SOFTUNE Workbench Operation Manual"; and Section "4.9 Show Trace" in "SOFTUNE Workbench Command Reference Manual".
CHAPTER2 Dependence Functions 2.1.10.7 Clearing Trace Data To clear trace data, use the following command. ■ Clearing Trace Data When clearing trace data, the [Clear] command is executed from the short-cut menu in the trace window.
CHAPTER2 Dependence Functions 2.1.11 Measuring Coverage In the high-speed version simulator debugger, the C0 coverage measurement function is provided. Use this function to find what percentage of an entire program has been executed. ■ Coverage Measurement Function When testing a program, the program is executed with various test data input and the results are checked for correctness. When the test is finished, every part of the entire program should have been executed.
CHAPTER2 Dependence Functions 2.1.11.1 Coverage Measurement Procedures The procedure for coverage measurement is as follows: - Set range for coverage measurement : SET COVERAGE - Measure coverage : GO, STEP, CALL - Display measurement result : SHOW COVERAGE ■ Setting Range for Coverage Measurement Use the SET COVERAGE command to set the measurement range. The measurement range can be set only within the area defined as the debug area. Up to 32 ranges can be specified.
CHAPTER2 Dependence Functions - Displaying coverage rate of load module (Specify /MODULE for the command qualifier) >SHOW COVERAGE/MODULE sample.abs ........................ (84.03%) +- startup.asm .................... (90.43%) +- sample.c ...................... (95.17%) +- samp.c ....................... (100.00%) Displays the load modules and the coverage rate of each module. - Summary (Specify /GENERAL for command qualifier.
CHAPTER2 Dependence Functions - Displays per source line (Specify /SOURCE for the command qualifier) >SHOW COVERAGE/SOURCE sample.c * 66: void * 67: { 68: 69: 70: * 71: . 72: 73: . 74: . 75: } main main() int i; struct table *value[16]; for (i=0; i<16; i++) value[i] = &target[i]; sort_val(value, 16L); The execution situation of each source line is displayed. .
CHAPTER2 Dependence Functions 2.1.12 Checking Debugger Status This section explains how to check information about the simulator debugger. ■ Debugger Information This simulator debugger enables you to check the following information at startup. • SOFTUNE Workbench file information • Hardware information If any errors have been discovered during SOFTUNE Workbench operations, check this information and contact our sales department or support department.
CHAPTER2 Dependence Functions Version: SiiEd3.ocx version ------------------------------------------------------SiM911 Product name: SOFTUNE Workbench File Path: SiM911.dll path Version: SiM911.dll version ---------------------------Language Tools - FR Family SOFTUNE C/C++ Compiler version File Path: fcc911s.exe path - FR Family SOFTUNE Assembler version File Path: fasm911s.exe path - FR Family SOFTUNE Linker version File Path: flnk911s.exe path - FR Family SOFTUNE Librarian version File Path: flib911s.
CHAPTER2 Dependence Functions REALOS version: REALOS version ------------------------------------------------------SiIODef Product name: Softune Workbench File Path: SiIODef.dll path Version: SiIODef.
CHAPTER2 Dependence Functions 2.2 Emulator Debugger (MB2197) This section describes the emulator debugger functions that are available when the emulator debugger (MB2197) is specified. ■ Emulator Debugger When choosing the emulator debugger from the setup wizard, select one of the following emulators. • MB2197 • MB2198 The following description explains the case when MB2197 has been selected.
CHAPTER2 Dependence Functions 2.2.1 Setting Operating Environment This section explains the operating environment setup. ■ Setting Operating Environment For emulator debugger (MB2197), the following items must be set according to the operating environment. Each setting item has a default value at startup. Therefore, if the default value is used as it is, there is no need to change this setting. Adjusted settings can be used as new default settings from the next time.
CHAPTER2 Dependence Functions 2.2.1.1 MCU Operation Mode The following four modes are in the MCU Operation Mode. The Internal Trace Mode and External Trace Mode are enabled only with products using the DSU3 chips. The Full Trace Mode and Real-time Mode are not enabled with products using the DSU3 chips. • Full Trace Mode • Real Time Mode • Internal Trace Mode • External Trace Mode ■ Setting MCU Operation Mode Set the MCU operation mode. There are two modes: full trace, and real-time.
CHAPTER2 Dependence Functions 2.2.1.2 DRAM Refresh Control This section explains DRAM refresh setup. ■ DRAM Refresh Control The operating frequency of some DSU chips is automatically divided at a break (in emulation mode). When this happens, the register (RFCR) must be reset if the built-in DRAM refresh function is used on the user target. The RFCR register values for On Execution (in user mode) and On Break (in emulation mode) can be set by [RFCR] tab in debug environment setting dialog.
CHAPTER2 Dependence Functions 2.2.1.3 Cache Flush Control This section explains cache flush setup. ■ Cache Flush Control When using a chip with cache memory, rewriting the memory and software break point setup using commands is not reflected in the cache. Therefore, cache flushing must be performed when such commands are executed. The emulator debugger (MB2197) has a function to flush the cache automatically, monitor memory rewriting, and set software break points, etc.
CHAPTER2 Dependence Functions 2.2.1.4 Operating Frequency This section explains the setting of operating frequencies. ■ Operating frequencies Set the operating frequencies of the MCU. Enable only DSU3. DSU3 ranges from 1 to 200 MHz. This setting provides the optimum communication speed between the MCU and emulator. This function can be controlled by the [Frequency] tab in debug environment setting dialog. Notes: • This setting is used to set maximum operating frequencies.
CHAPTER2 Dependence Functions 2.2.2 Notes on Executing Program There are some precautions to observe when using program execution commands. ■ Real-time Functionality in Running Program When the MCU is in the full trace mode, there are some cases when a program cannot execute in real-time. The MCU operation mode can be set up by using either the [Emulation] tab in debug environment setting dialog, or the SET RUNMODE command in the Command window.
CHAPTER2 Dependence Functions 2.2.3 Commands Available during Execution of User Program This section explains the commands available during the execution of a user program. ■ Commands Available during Execution of User Program The emulator debugger (MB2197) allows you to use certain commands during the execution of a user program. For more details, refer to "■ Supported Debuggers" in "SOFTUNE Workbench Command Reference Manual".
CHAPTER2 Dependence Functions 2.2.4 Break The emulator debugger (MB2197) provides seven types of break functions. When by each break function aborts program execution, the address where a break occurred and the break factor are displayed.
CHAPTER2 Dependence Functions 2.2.4.1 Code Break This function aborts the program execution by monitoring a specified address by hardware or software. A break occurs before executing an instruction at the specified address. ■ Code Break This function aborts the program execution by monitoring a specified address by hardware or software. A break occurs before executing an instruction at the specified address.
CHAPTER2 Dependence Functions Notes: Hardware The hardware break requires the following cautions: - Do not set any hardware break in instruction placed in a delay slot. When the hardware break is set in the instruction, a branch does not occur even if the program is reexecuted after break. - Be sure to set a breakpoint at the starting address of the instruction. A break may not occur if an address other than the starting address is specified.
CHAPTER2 Dependence Functions 2.2.4.2 Code Event Break This function used breakpoints contained in the evaluation chip. The address mask, pass count, and sequential mode can be set. ■ Code Event Break This function uses breakpoints contained in an evaluation chip. The address mask and pass count can be set. Up to two breakpoints can be set and used in two modes. 1. OR mode (if a hit is found in either code event 1 or 2, a break occurs) 2.
CHAPTER2 Dependence Functions 2.2.4.3 Data Event Break This function uses breakpoints contained in the evaluation chip. The address mask, data size, access type, and sequential mode can be set. ■ Data Event Break This function uses breakpoints contained in the evaluation chip. The address mask, data size (byte/half word/word), and access attributes (read/write) can be set. Up to two breakpoints can be set and used in two modes. 1. OR mode (if a hit is found in either data event 1 or 2, break occurs) 2.
CHAPTER2 Dependence Functions 2.2.4.4 Trace Buffer-full Break This function aborts the program execution when the trace buffer becomes full. ■ Trace Buffer-full Break This function aborts the program execution when the trace buffer becomes full. When the trace buffer-full break occurs, the following message appears at the status bar. Break at address by trace buffer full ■ How to set Set the trace buffer-full break as follows. • Command - SET TRACE/BREAK For details, refer to "4.
CHAPTER2 Dependence Functions 2.2.4.5 Alignment Error Break This function aborts the program execution when an instruction access or a word/half word access beyond the boundary is made to the odd address. ■ Alignment Error Break This function aborts the program execution when an instruction access or a word/half word access beyond the boundary is made to the odd address. Whether to enable or disable the alignment error break can be set for both instruction access and data access.
CHAPTER2 Dependence Functions 2.2.4.6 External Trigger Break This function aborts the program execution when an external signal is input from the TRIG of the Emulator. ■ External Trigger Break This function aborts the program execution when an external signal is input from the TRIG of the Emulator. When the external trigger break occurs, the following message appears at the status bar. Break at address by external trigger break ■ How to set Set the external trigger break as follows.
CHAPTER2 Dependence Functions 2.2.4.7 Forced Break This function forcibly aborts the program execution to generate a break. ■ Forced Break This function forcibly aborts the program execution to generate a break. When the forced break occurred, the following message appears at the status bar. Break at address by command abort request ■ How to Generate A forced break is generated in the following methods: • Menu [Debug] - [Abort] menu For details, refer to "4.6.
CHAPTER2 Dependence Functions 2.2.5 Measuring Execution Cycle Count This function measures the program execution cycle count. ■ The measuring item Measures program execution cycle counts. The maximum measurable count is "2 to the power of 48 - 1", in other words, up to 281,474,976,710,655 cycles.
CHAPTER2 Dependence Functions 2.2.6 Trace The address and status information can be sampled during program execution to record it in a trace buffer. This function is called a trace. ■ Trace Data recorded with the trace function can be used to make a detailed analysis of a program execution history. The trace buffer is in the form of a ring. When it becomes full, it records the next data by automatically overwriting the buffered data at the beginning.
CHAPTER2 Dependence Functions 2.2.6.1 Trace Data Data sampled and recorded by tracing is called trace data. ■ Trace Data You can sample the following sizes using the emulation debugger. • Full Trace Mode: 65536 bytes • Real Time Trace Mode: 65536 bytes • Internal Trace Mode: 128 frames or 64 frames (The number of frame is different by an evaluation chip.) • External Trace Mode: 65536 frames The following data is sampled.
CHAPTER2 Dependence Functions 2.2.6.2 Trace Sampling Trace measurements of the program execution status are made during the interval between the program start and stop. The DSU3 chip emulator debugger (MB2197) performs trace measurements until the program execution stops, using the first or second code event or first data event as a trigger for starting trace measurement.
CHAPTER2 Dependence Functions 2.2.6.3 Setting Trace To perform a trace, complete steps 1 through 3 below. When a program is executed after completion of the following steps, trace data is sampled. Trace setup can also be performed from the command window. The DSU3 chip allows the trace measurement region for data access to be specified. ■ Setting Trace 1. Enable the trace function - This is done by [Setup] - [Trace] in the trace window shortcut menu. This program will startup and will be enabled. 2.
CHAPTER2 Dependence Functions 2.2.6.4 Displaying Trace Data Data recorded in the trace buffer can be Displayed. ■ Displaying Trace Data The trace window displays how much trace data is stored in the trace buffer. Also, you can use the SHOW TRACE command from the command window. When the emulator debugger uses the DSU3 chip, it displays branch information and data access information as trace data.
CHAPTER2 Dependence Functions 2.2.6.5 Display Format of Trace Data There is a format for displaying trace buffer data. ■ Display Format of Trace Data • Display Only Instruction Operation: (Specify Instruction) ■ Display Only Instruction Operation In this mode, the instruction operation is displayed in disassembly units.
CHAPTER2 Dependence Functions 2.2.6.6 Searching Trace Data The trace buffer can be searched to locate target data. ■ Searching Trace Data Specify the address, data, and access information for searching. The address and data can be masked. This search function can be run by clicking the Search button in the trace window.
CHAPTER2 Dependence Functions 2.2.6.7 Saving Trace Data The debugger has function of saving trace data. ■ Saving Trace Data Save the trace data to the specified file. For details on operations, refer to Sections "3.14 Trace Window", and "4.4.8 Trace" in "SOFTUNE Workbench Operation Manual" and Section "4.9 Show Trace" in "SOFTUNE Workbench Command Reference Manual".
CHAPTER2 Dependence Functions 2.2.6.8 Clearing Trace Data To clear trace data, use the following command. ■ Clearing Trace Data When clearing trace data, the [Clear] command is executed from short-cut menu in the trace window.
CHAPTER2 Dependence Functions 2.2.6.9 Notes on Use of Tracing Function This section describes the precautions to observe when displaying or searching for trace data.
CHAPTER2 Dependence Functions • When displaying valid pass cycles or instruction, the omitted trace data frame is displayed as follows: *** Address Lost Error *** Frame where address at code fetching could not be sampled. • At step execution by a single instruction, trace data may not be sampled correctly for each single instruction execution. If this happens, *** Address Lost Error *** is displayed.
CHAPTER2 Dependence Functions 2.2.7 Inaccessible Area This section explains inaccessible area. ■ Inaccessible area The inaccessible area is a function that suppresses access to memory when the debugger accesses a specified memory area (using commands, windows, etc. (*)). However, access to memory is not suppressed using program. The following commands are used to set an inaccessible area. SET MAP/INACCESSIBLE: Sets an inaccessible region. SHOW MAP/INACCESSIBLE: Displays an inaccessible region.
CHAPTER2 Dependence Functions 2.2.8 Checking Debugger Status This section explains how to check information about the emulator debugger (MB2197). ■ Debugger Information The emulator debugger (MB2197) enables you to check the following information at startup. • SOFTUNE Workbench file information • Hardware information If any errors have been discovered during SOFTUNE Workbench operations, check this information and contact our sales department or support department.
CHAPTER2 Dependence Functions Version: SiiEd3.ocx version ------------------------------------------------------SiM911 Product name: SOFTUNE Workbench File Path: SiM911.dll path Version: SiM911.dll version ---------------------------Language Tools - FR Family SOFTUNE C/C++ Compiler version File Path: fcc911s.exe path - FR Family SOFTUNE Assembler version File Path: fasm911s.exe path - FR Family SOFTUNE Linker version File Path: flnk911s.exe path - FR Family SOFTUNE Librarian version File Path: flib911s.
CHAPTER2 Dependence Functions DSU type : Currently used DSU type Monitor version : Version of monitor (dependent) Communication device : Device type Baud rate : Baud rate Host name : LAN host name REALOS version : REALOS version ------------------------------------------------------SiIODef Product name: Softune Workbench File Path: SiIODef.dll path Version: SiIODef.
CHAPTER2 Dependence Functions 2.3 Emulator Debugger (MB2198) This section describes the emulator debugger functions that are available when the emulator debugger (MB2198) is specified. ■ Emulator Debugger When choosing the emulator debugger from the setup wizard, select one of the following emulators. • MB2197 • MB2198 The following description explains the case when MB2198 has been selected.
CHAPTER2 Dependence Functions Notes: When FR80S is used, there are some restrictions on the debug functions as follows: • The debug functions shown in Table 2.3-1 are valid only when set in the internal RAM space. However, the code break and the data break are excluded. • The trace buffer stores only the trace data on which a write access is performed to the internal RAM when the MCU operation mode is set to "external trace mode".
CHAPTER2 Dependence Functions 2.3.1 Setting Operating Environment This section explains the operating environment setup. ■ Setting Operating Environment For emulator debugger (MB2198), the following items must be set according to the operating environment. Each setting item has a default value at startup. Therefore, if the default value is used as it is, there is no need to change this setting. Adjusted settings can be used as the new default settings from the next time.
CHAPTER2 Dependence Functions 2.3.1.1 Monitoring Program Automatic Loading The emulators debugger (MB2198) can update the monitoring program automatically at emulator startup. ■ Monitoring Program Automatic Loading When emulator debugger (MB2198) is specified, data in the emulator can be checked at the beginning of debugging to automatically load the appropriate monitoring program and configuration binary data into the emulator.
CHAPTER2 Dependence Functions 2.3.1.2 MCU Operation Mode The following four modes are in the MCU Operation Mode. The Full Trace Mode and Real-time Mode are not enabled with products using the DSU3 chips. • Full Trace Mode • Real Time Mode • Internal Trace Mode • External Trace Mode ■ Setting MCU Operation Mode Set the MCU operation mode. There are two modes: full trace, and real-time.
CHAPTER2 Dependence Functions 2.3.1.3 Cache Flush Control This section explains cache flush setup. ■ Cache Flush Control When using a chip with cache memory, rewriting the memory and software break point setup using commands is not reflected in the cache. Therefore, cache flushing must be performed when such commands are executed. The debugger has a function to flush the cache automatically, monitor memory rewriting, and set software break points, etc.
CHAPTER2 Dependence Functions 2.3.1.4 Operating Frequency This section explains the setting of operating frequencies. ■ Operating frequencies Set the operating frequencies of the MCU. The most suitable operating frequencies vary depending on the type of DSU. DSU3 ranges from 1 to 200 MHz and DSU4 from 1 to 266 MHz. This setting provides the optimum communication speed between the MCU and emulator. This function can be controlled by the [Frequency] tab in debug environment setting dialog.
CHAPTER2 Dependence Functions 2.3.1.5 External Memory Emulation This section explains the external memory emulation function. ■ External memory emulation Some DSU4 chips can use the RAM in the adapter unit in place of the user system memory. This function is called external memory emulation. For the FR Family, the ‘chip select’ terminal must be specified to access memory outside the chip. Therefore, when using the external memory emulation function, specify the chip select number.
CHAPTER2 Dependence Functions 2.3.1.6 Debug mode Debug mode includes the following modes. Selectable debug mode varies with the emulator or its connection configuration. • RealTimeMemory mode • RAM Checker mode ■ Setting of debug mode This mode sets debug mode. Debug mode includes RealTimeMemory mode and RAM Checker mode, and selectable debug mode varies with the emulator or its connection configuration.
CHAPTER2 Dependence Functions 2.3.2 Notes on Executing Program There are some precautions to observe when using program execution commands. ■ Real-time Functionality in Running Program When the MCU is in the full trace mode, there are some cases when a program cannot execute in real-time. The MCU operation mode can be set up by using either the [Emulation] tab in debug environment setting dialog, or the SET RUNMODE command in the Command window.
CHAPTER2 Dependence Functions 2.3.3 Commands Available during Execution of User Program This section explains the commands available during the execution of a user program. ■ Commands Available during Execution of User Program The emulator debugger (MB2198) allows you to use certain commands during the execution of a user program. For more details, refer to "■ Supported Debuggers" in "SOFTUNE Workbench Command Reference Manual".
CHAPTER2 Dependence Functions Notes: • The conditions which allow you to use the commands in Table 2.3-2 are limited to the following cases when a user program is executed. - [Debug] - [Run] - [Go] menu - [Go] button on the debug toolbar The commands in Table 2.3-2 cannot be used when the GO command is entered in the command window. • An error message appears if you enter a command that cannot be used during the execution of a user program. "E4404S Command error (MCU is busy).
CHAPTER2 Dependence Functions 2.3.4 Break The emulator debugger (MB2198) provides nine types of break functions. When by each break function aborts program execution, the address where a break occurred and the break factor are displayed.
CHAPTER2 Dependence Functions 2.3.4.1 Code Break This function aborts the program execution by monitoring a specified address by hardware or software. A break occurs before executing an instruction at the specified address. ■ Code Break This function aborts the program execution by monitoring a specified address by hardware or software. A break occurs before executing an instruction at the specified address. Hardware has the hardware/count for which a path count can be set.
CHAPTER2 Dependence Functions Notes: Hardware The hardware break requires the following cautions: • Do not set any hardware break in a instruction placed in a delay slot. When the hardware break is set in the instruction, a branch does not occur even if the program is reexecuted after break. • Be sure to set a breakpoint at the starting address of the instruction. A break may not occur if an address other than the starting address is specified.
CHAPTER2 Dependence Functions 2.3.4.2 Data Break This function aborts the program execution when a data access (read/write) is made to a specified address. ■ Data Break This function aborts program execution when a data access (read/write) is made to a specified address. Up to two breakpoints can be set. When the data break occurs, the following message appears at the status bar.
CHAPTER2 Dependence Functions 2.3.4.3 Code Event Break This function uses breakpoints contained in the evaluation chip. The address mask, pass count, and sequential mode can be set. ■ Code Event Break This function uses breakpoints contained in an evaluation chip. The address mask and pass count can be set. Up to two breakpoints can be set and used in two modes. 1. OR mode (if a hit is found in either code event 1 or 2, a break occurs) 2.
CHAPTER2 Dependence Functions Notes: • In the DSU3 chip, the code event can be used as a break factor and a trace measurement start factor. This mode is called a trace sampling mode. There are two trace sampling modes. - Full mode: The code event is used as a break factor. - Trigger mode: The code event is used as a trace measurement start factor. To use the code event as a break factor, set the full mode. Set as follows: Command - SET TRACE/FULL For details, refer to "4.
CHAPTER2 Dependence Functions 2.3.4.4 Data Event Break This function uses breakpoints contained in the evaluation chip. The address mask, data size, access type, and sequential mode can be set. ■ Data Event Break This function uses breakpoints contained in the evaluation chip. The address mask, data size (byte/half word/word), and access attributes (read/write) can be set. Up to two breakpoints can be set and used in two modes.
CHAPTER2 Dependence Functions Notes: • In the DSU3 chip, the data event can be used as a break factor and a trace measurement start factor. This mode is called a trace sampling mode. There are two trace sampling modes. - Full mode: The data event is used as a break factor. - Trigger mode: The data event is used as a trace measurement start factor. To use the data event as a break factor, set the full mode. Set as follows: Command - SET TRACE/FULL For details, refer to "4.
CHAPTER2 Dependence Functions 2.3.4.5 Trace Buffer-full Break This function aborts the program execution when the trace buffer becomes full. ■ Trace Buffer-full Break This function aborts the program execution when the trace buffer becomes full. When the trace buffer-full break occurs, the following message appears at the status bar. Break at address by trace buffer full ■ How to set Set the trace buffer-full break as follows. • Command - SET TRACE/BREAK For details, refer to "4.
CHAPTER2 Dependence Functions 2.3.4.6 Alignment Error Break This function aborts the program execution when an instruction access or a word/half word access beyond the boundary is made to the odd address. ■ Alignment Error Break This function aborts the program execution when an instruction access or a word/half word access beyond the boundary is made to the odd address. Whether to enable or disable the alignment error break can be set for both instruction access and data access.
CHAPTER2 Dependence Functions 2.3.4.7 External Trigger Break This function aborts the program execution when an external signal is input from the TRIG of the Emulator. ■ External Trigger Break This function aborts the program execution when an external signal is input from the TRIG of the Emulator. When the external trigger break occurs, the following message appears at the status bar. Break at address by external trigger break ■ How to set Set the external trigger break as follows.
CHAPTER2 Dependence Functions 2.3.4.8 Forced Break This function forcibly aborts the program execution to generate a break. ■ Forced Break This function forcibly aborts the program execution to generate a break. When the forced break occurred, the following message appears at the status bar. Break at address by command aborts request ■ How to Generate A forced break is generated in the following methods: • Menu [Debug] - [Abort] menu For details, refer to "4.6.
CHAPTER2 Dependence Functions 2.3.4.9 Data Watch Break This special break function suspends program execution when the program reaches a specified address where specified data matches. Use conditions vary depending on the connection state of the Emulator. ■ Data Watch Break This special break function suspends program execution when the program reaches a specified address where specified data matches. There are two patterns of software and hardware.
CHAPTER2 Dependence Functions ■ How to set Set the data watch break as follows. • Data watch break (hardware) • Command - SET BREAK/DATAWATCH • Dialog - "Code" tab in breakpoint setting dialog • Data watch break (software) • Command - SET BREAKCONDITION - SET BREAK/BREAKCONDITION • Dialog - "Data Watch Conditions" in breakpoint detail setting dialog Notes: Data watch break (hardware) • This function can be used only when the FR60Lite is used. For details, refer to "2.3.4 Break".
CHAPTER2 Dependence Functions 2.3.5 Control by Sequencer The emulator debugger (MB2198) have a sequencer that controls events. By using this sequencer it is possible to exercise break control while focusing on a certain program flow (sequence). The break generated by this function is called a sequential break. ■ Control by Sequencer The emulator debugger (MB2198) can have two types of sequencers depending on whether the external trace bus interface is provided for evaluation chips.
CHAPTER2 Dependence Functions The sequencer operates as shown below when it uses the real-time monitoring bus interface: [Setup Example] >SET SEQUENCE 1.3.2, r=4 Events 1, 3, and 2 are specified respectively for Levels 1, 2, and 3. Event 4 is specified as a restart condition. Start Level 1 Event 1 NO YES YES Event 4 NO Level 2 Event 3 NO YES YES Event 4 NO Level 3 Event 2 NO YES Break ■ Setting Sequencer The sequencer can be set by the dialog or the command.
CHAPTER2 Dependence Functions Note: Sequencer (Only Real-time Monitoring Bus Interface) 1. This function can be used only when the evaluation chip is the FR60Lite or FR80S. When FR80S is used, however, this function is valid only if the internal RAM space is allowed for write access. 2. There are cases when the actual code execution order and the data hit information order are switched, depending on the output timing of the external trace data.
CHAPTER2 Dependence Functions 2.3.6 Measuring Execution Cycle Count This function measures the program execution time. ■ The measuring item Measures program execution time and cycle count. The resolution of the execution time is 25ns, and up to "(2 to the power of 64 - 1) x 25ns" can be measured. Also, the maximum number of cycles that can be measured is "2 to the power of 64 - 1", in other words, up to 18,446,744,073,709,551,615 cycles.
CHAPTER2 Dependence Functions 2.3.7 Trace This section describes the trace function of the emulator debugger (MB2198). The program execution history can be analyzed in detail using the data recorded by trace. ■ Trace Buffer One data unit stored in the trace buffer is called a frame. Table 2.3-6 shows the trace buffer capacity for each operation mode. Table 2.
CHAPTER2 Dependence Functions Notes: 1. The execution time display function is available only when a DSU4 evaluation chip with the external trace bus interface is used. Furthermore, since the execution time is stored in the trace memory on the adapter unit, measurements cannot be made in the external trace mode in which the memory is used for trace data storage. 2. This function cannot be used when the performance mode in set as the event mode. For details, refer to "1.
CHAPTER2 Dependence Functions ■ Setting Trace Trigger When preselected conditions are met while monitoring the MCU bus operation, a trigger to start a trace can be generated. This function is called a trace trigger. To use the trace trigger function, specify the code (/CODE) and data access (/READ/WRITE). Up to 4 trace triggers can be preset each for code attribute and data access attribute.
CHAPTER2 Dependence Functions Note: Trace Trigger • This function can be used only when FR60Lite or FR80S is used. When FR80S is used, however, this function is valid only if the internal RAM space is allowed for write access. • If a trace trigger is set, the trace cannot be acquired until the trace starting trigger occurs. Disassembling and source are displayed in the trace from the jumps destination address of the branch instruction executed after the trace starting trigger has occurred.
CHAPTER2 Dependence Functions 2.3.7.1 Display Format of Trace Data There are three formats for displaying trace buffer data. ■ Display Format of Trace Data • Display Only Instruction Operation: Specify Instruction • Display Bus Cycles: Specify RAW data • Display by Unit of Source Lines: Specify Source ■ Display Only Instruction Operation In this mode, the instruction operation is displayed in disassembly units.
CHAPTER2 Dependence Functions 2.3.7.2 Saving Trace Data The debugger has function of saving trace data. ■ Saving Trace Data Save the trace data to the specified file. For details on operations, refer to Sections "3.14 Trace Window", and "4.4.8 Trace" in "SOFTUNE Workbench Operation Manual"; and Section "4.9 Show Trace" in "SOFTUNE Workbench Command Reference Manual".
CHAPTER2 Dependence Functions 2.3.7.3 Notes on Use of Tracing Function This section describes the precautions to observe when displaying or searching for trace data.
CHAPTER2 Dependence Functions • When displaying valid pass cycles or instruction, the omitted trace data frame is displayed as follows: *** Address Lost Error *** Frame where address at code fetching could not be sampled. • At step execution by a single instruction, trace data may not be sampled correctly for each single instruction execution. If this happens, *** Address Lost Error *** is displayed.
CHAPTER2 Dependence Functions 2.3.8 Measuring Performance It is possible to measure the time and pass count between two events. Repetitive measurement can be performed while executing a program in real-time, and when done, the data can be totaled and displayed. Using this function enables the performance of a program to be measured. To measure performance, set the event mode to the performance mode using the SET MODE command.
CHAPTER2 Dependence Functions 2.3.8.1 Performance Measurement Procedures Performance can be measured by the following procedure: • Set event mode. • Set minimum measurement unit for timer. • Specify performance-buffer-full break. • Set events. • Execute program. • Display measurement result. • Clear measurement result. ■ Setting Event Mode Select [Setup]-[Debug Environment]-[Debug Environment] - [Event] tab or use the SET MODE command to set the event mode to the performance mode.
CHAPTER2 Dependence Functions ■ Setting Events Set events using the SET EVENT command. The starting/ending point of time measurement and points to measure pass count are specified by events. Events at 4 points (1 to 4) can be set. However, in the performance measurement, the intervals, starting event number and ending event number are fixed in the following combination. - Measuring Time Two intervals have the following fixed event number combination.
CHAPTER2 Dependence Functions 2.3.8.2 Displaying Performance Measurement Data Display the measured time and measuring count by using the SHOW PERFORMANCE command. ■ Displaying Measured Time To display the time measured, specify the starting event number or the ending event number. Count of measuring within given time interval Event number >SHOW PERFORMANCE/TIME Minimum execution time Maximum execution time event min time max time avr time = = = = 1 -> 2 11637.0 17745.0 14538.
CHAPTER2 Dependence Functions 2.3.9 Real-time Monitoring This section explains the real-time monitoring function. ■ Command execution during program execution The real-time monitoring function updates the memory content in real time during program execution and displays it in a window. This emulator debugger (MB2198) is provided with a real-time memory window that can display two 256byte areas for real-time monitoring.
CHAPTER2 Dependence Functions 2.3.10 Power-on Debugging This section explains power-on debugging. ■ Power-on debugging The emulator debugger (MB2198) provides power-on debugging function. This emulator can debug the sequence performed immediately after target system power-on. The power-on debugging procedure is described below: 1. Set the DIP switch on the adapter board mounted in the upper section of the emulator. 2. Power on the target board and emulator main unit. 3.
CHAPTER2 Dependence Functions 2.3.11 Inaccessible Area This section explains inaccessible area by the emulator debugger for the MB2198. ■ Inaccessible area The inaccessible area is a function that suppresses access to memory when the debugger accesses a specified memory area (using commands, windows, etc. (*)). However, access to memory is not suppressed using program. The following commands are used to set an inaccessible area. SET MAP/INACCESSIBLE: Sets an inaccessible region.
CHAPTER2 Dependence Functions 2.3.12 RAM Checker This section describes the function of the RAM Checker. ■ Overview The RAM Checker obtains the access history of the monitoring address log in the SOFTUNE Workbench, and displays the log file graphically using the attached tool "RAM Checker Viewer".
CHAPTER2 Dependence Functions ■ Specification list Table 2.3-8 RAM Checker Specification List Numbers for monitoring points 8 points Size byte/halfword/word Event function Max 4 points Sampling rate 1ms (fixed) Updating interval 100ms (fixed) Type of log file SOFTUNE style or CSV style - SOFTUNE format When displaying using the RAM Checker Viewer (SOFTUNE format recommended) Default extension is ".SRL". - CSV format When other than the RAM Checker Viewer. The default extension is ".CSV".
CHAPTER2 Dependence Functions ■ Memory access during logging During program execution, the emulator debugger (MB2198) reads/writes memory after causing MCU break once to access, and then reexecuting the program. Therefore, when the emulator debugger accesses memory, it cannot get a log at the time of the memory access correctly. To prevent this, during logging, do not perform operation involving memory access (such as SET MEMORY/SHOW MEMORY command operation and memory window operation).
CHAPTER2 Dependence Functions ■ RAM Checker Viewer The RAM Checker Viewer is a tool to graphically display the data value that changes as time goes by. It displays data value in the following three formats: - Bit display (image of Logic Analyzer) - Data value display (line graph) - Bit/data value display (simultaneous display of bit and data value) Other display information includes CPU stop, trigger point, and data lost.
CHAPTER2 Dependence Functions 2.3.13 Checking Debugger Status This section explains how to check information about the emulator debugger (MB2198). ■ Debugger Information The emulator debugger (MB2198) enables you to check the following information at startup. • SOFTUNE Workbench file information • Hardware information If any errors have been discovered during SOFTUNE Workbench operations, check this information and contact our sales department or support department.
CHAPTER2 Dependence Functions Version: SiiEd3.ocx version ------------------------------------------------------SiM911 Product name: SOFTUNE Workbench File Path: SiM911.dll path Version: SiM911.dll version ---------------------------Language Tools - FR Family SOFTUNE C/C++ Compiler version File Path: fcc911s.exe path - FR Family SOFTUNE Assembler version File Path: fasm911s.exe path - FR Family SOFTUNE Linker version File Path: flnk911s.exe path - FR Family SOFTUNE Librarian version File Path: flib911s.
CHAPTER2 Dependence Functions DSU type : Currently used DSU type Common version : Version of monitor (common) Monitor version : Version of monitor (dependent) Configuration board ID : Configuration board ID Configuration board version : Configuration board version MCU frequency : Operating frequency Communication device : Device type Baud rate : Baud rate (at RS connection) Host name : LAN host name (at LAN connection) REALOS version : REALOS version --------------------------------------
CHAPTER2 Dependence Functions 2.4 Emulator Debugger (MB2100-01) This section describes the emulator debugger (MB2100-01) functions.
CHAPTER2 Dependence Functions 2.4.1 Starting debugging This section describes the method of starting debugging. ■ Starting Debugging When starting debugging, select the [Debug] - [Start debug] menu. When debugging is started by a new project, the setup wizard for performing initial setting is activated. For details, refer to "4.7.2.5 Setup Wizard" in "SOFTUNE Workbench Operation Manual". ■ Verification Items When Starting Debugging When starting debugging, perform checking for initial settings.
CHAPTER2 Dependence Functions 2.4.1.1 Power-on Reset This section describes how to issue the power-on reset. ■ Issuing the Power-on Reset To start the emulator debugger (MB2100-01), enable the DEBUG I/F. For details of DEBUG I/F, refer to the Hardware Manual for the product type you are using. For the emulator debugger (MB2100-01), the power-on reset is recommended. When the dialog of Figure 2.4-1 is displayed while debugging starts, DEBUG I/F is disabled. Issue the power-on reset.
CHAPTER2 Dependence Functions 2.4.1.2 Operating Environments of the Target This section describes the setting of the target operating environments. ■ Operating Environments of the Target In the emulator debugger (MB2100-01), it is necessary to set the following items according to the operating environments of the target. • Reference frequency of communication speed • Length of DEBUG I/F cable These settings influence the communication speed of the debugger.
CHAPTER2 Dependence Functions Notes: • When the actual value is different from the input value for the communication speed of the reference frequency, the debugger cannot be started. • For details on the DEBUG I/F (interface), refer to "EMBEDDED EMULATOR MB2100-01-E OPERATION MANUAL".
CHAPTER2 Dependence Functions 2.4.1.3 Security This section describes the security. ■ Security When beginning to debug it when the security function of target MCU is effective, it is necessary to enter the password in the emulator debugger (MB2100-01). For information of security function, refer to the Hardware Manual for the product type you are using. ■ How to enter When a dialog shown below is displayed, enter a preset password. The password is needs to be entered each time the debugger is activated.
CHAPTER2 Dependence Functions 2.4.2 Ending debugging This section describes the method of ending debugging. ■ Ending debugging When ending debugging, select the [Debug] - [End debug] menu. Turn off the power supply of the target after selecting the [End debug] menu. ■ When the debugger has aborted When the debugger has aborted for some reason, problems as described below can occur. When starting debugging again, take corresponding countermeasures.
CHAPTER2 Dependence Functions 2.4.3 Efficiently Executing Debugging This section describes setting for efficient debugging. ■ Setting Operating Environment Emulator debugger (MB2100-01) can perform efficient debugging by setting the following items in accordance with the operating environment and applications. • Standard high-speed communication For details, refer to "2.4.3.1 Increasing Communication Speed during Debugging". • Debug function For details, refer to "2.4.3.2 Switching Debug Function".
CHAPTER2 Dependence Functions 2.4.3.1 Increasing Communication Speed during Debugging This section describes setting for increasing the communication speed during debugging. ■ Standard High-speed Communication In the case of the emulator debugger (MB2100-01), when the standard high-speed communication is set to the optimal value, the phase modulation mode is enabled, and high-speed communication can be performed between the target and adapter.
CHAPTER2 Dependence Functions 2.4.3.2 Switching Debug Function This section describes the method of switching the debug function correspondingly to the usage. ■ Debug Functions Some of the debugging features are exclusive features which cannot be set simultaneously. Exclusive features require to switch modes depending on usage. The mode has two types described below. • Execution time mode This mode selects the method of measuring the user-program execution time.
CHAPTER2 Dependence Functions 2.4.4 Executing Program This section describes the method of executing a user program. ■ Executing a program A user program is executed in a procedure described below. 1. Open a project (workspace). Select the [File] - [Open workspace file] menu. 2. Start debugging. Refer to "2.4.1 Starting debugging". 3. Load an execution-desired target program. When loading a project target file, select the [Debug] - [Load target file] menu. 4. Execute program.
CHAPTER2 Dependence Functions 2.4.4.1 Setting/Release of Debug Functions The debug function is set or can be released while executing the user program. ■ Commands Available during Execution of User Program A specific debug feature can setting/be released while executing the user program in the emulator debugger (MB2100-01). Either the dialog or the command can setting/be released. Table 2.4-1 shows the commands available during execution of user program.
CHAPTER2 Dependence Functions Table 2.4-1 Commands Available during Execution of User Program (2 / 2) Function Trace operation Major Command name*1 4.15 SET TRACE (type2) 4.18 CLEAR TRACE 4.20 ENABLE TRACE (type2) 4.22 DISABLE TRACE (type2) 4.23 SEARCH TRACE 4.24 SET DATATRACEAREA 4.26 CANCEL DATATRACEAREA 4.33 SET DELAY *1 : Refer to "SOFTUNE Workbench Command Reference Manual". Note: An error message appears if you enter a command that cannot be used during the execution of auser program.
CHAPTER2 Dependence Functions 2.4.4.2 Monitoring This section describes the monitoring function. ■ Monitoring The monitoring function is capable of real-time referencing a variation in the value of a specific address during user program execution. The function is capable of a variation in the value of a specified watch variable, in addition to the value of a specific address. ■ How to use The use procedure of the monitoring function is described below.
CHAPTER2 Dependence Functions 2.4.4.3 Power-on Debug This section describes power-on debug function. ■ Power-on Debug Power-on debug is a function to debug the sequence immediately after turning on of the power supply of the target system. ■ How to use The use procedure of power-on debug is as follows: ● When power-on debug 1. Start debug. Select [Debug] - [beginning of debugging] menu. 2. Power-on debug mode is made effective. Select [Debug] - [Run] - [Power-on the debug] menu.
CHAPTER2 Dependence Functions Notes: • Other debug features cannot be used while debugging power-on at all. • When security is enabled, power on debug is not available. • Selecting the power-on debug menu, the following functions cleared. - Performance measurement - Execution cycle measurement • Issuing a chip reset during the execution of the user program, the following functions cleared.
CHAPTER2 Dependence Functions 2.4.5 To Access the Flash Memory This section describes the access method to the flash memory. ■ Access to Flash Memory In the emulator debugger (MB2100-01), the direct operation of the content of the flash memory can be done as well as RAM area. ■ What is flash memory synchronization? When data is written into the flash memory, the data is stored temporarily. The stored data and the contents of flash memory must be matched.
CHAPTER2 Dependence Functions - View the following dialogs. Line Assembly dialog (Disassembly window) Break setting dialog [Software] ● Flash memory synchronization [Debbuger -> Flash] • Manual flash memory synchronization Select the [Environment] - [Flash area control] menu. For details, refer to "4.7.4 Flash area control" in "SOFTUNE Workbench Operation Manual".
CHAPTER2 Dependence Functions ■ Examples of flash memory synchronization ● In the case of [Flash -> Debugger] An image in the case where the flash memory synchronization [Flash -> Debugger] has been performed is shown below. Figure 2.
CHAPTER2 Dependence Functions ● In the case of [Debugger -> Flash] An image in the case where the flash memory synchronization [Debugger -> Flash] has been performed is shown below. Figure 2.4-5 Variations in the values of the internal debugger and flash memory in the case of the flash memory synchronization [Debugger -> Flash] Debugger Flash memory FF FF FF FF FF FF FF FF Memory writing, loading, etc. by the user 12 34 56 78 FF FF FF FF Execution and reset, etc.
CHAPTER2 Dependence Functions 2.4.6 To Interrupt the Program Execution [Break] This section describes the method of interrupting the execution of the user program. ■ Break Functions The function to interrupt the execution of the user program is called a break function.
CHAPTER2 Dependence Functions 2.4.6.1 Code Break (Hardware) This function suspends program execution by monitoring a specified address by hardware. ■ Code Break (Hardware) This function suspends program execution by monitoring a specified address by hardware. A break occurs before an instruction at the specified address is executed. Code Break (Hardware) has the hardware/count for which a path count can be set.
CHAPTER2 Dependence Functions Notes: • Do not set the code break to an instruction placed in a delay slot. If a code break is set and the branch instruction is executed, the following phenomenon occurs. Hardware: A break set in the delay slot does not occur. • When setting a breakpoint, always specify the starting address of the instruction. A break may not occur if an address other than the starting address is specified. • A code break shares points with the following functions.
CHAPTER2 Dependence Functions 2.4.6.2 Code Break (Software) This function suspends program execution by monitoring a specified address by software. A break occurs before executing an instruction at the specified address. ■ Code Break (Software) This function suspends program execution by monitoring a specified address by software. The conditions are as follows.
CHAPTER2 Dependence Functions Notes: • Do not set the code break (software) to an instruction placed in a delay slot. When set, an incorrect instruction exception occurs. For details of the invalid instruction exception, refer to the Hardware Manual for the product type you are using. • When setting a code break (software) in a flash memory area, the contents of the flash memory at the specified address is temporarily rewritten. For details, refer to "2.4.5 To Access the Flash Memory".
CHAPTER2 Dependence Functions 2.4.6.3 Data Break This function suspends program execution when data access (read/write) is made to a specified address. ■ Data Break This function suspends program execution when data access (read/write) is made to a specified address. Up to 8 points can be set. When the data break occurs, the following message appears in the status bar.
CHAPTER2 Dependence Functions 2.4.6.4 Trace Trigger Break This function suspends program execution when a trace trigger terminates trace acquisition. ■ Trace Trigger Break This function suspends program execution when a trace trigger terminates trace acquisition. Only one point can be set. When the trace trigger break occurs, the following message appears in the status bar.
CHAPTER2 Dependence Functions 2.4.6.5 Forced Break This function forcibly suspends program execution. ■ Forced Break This function forcibly suspends program execution. When the forced break occurs, the following message appears in the status bar. Break at address by command abort request ■ How to Generate A forced break is generated in the following methods: • Menu [Debug] - [Abort] menu For details, refer to "4.6.2 Abort" in "SOFTUNE Workbench Operation Manual".
CHAPTER2 Dependence Functions 2.4.6.6 Data Watch Break This break function suspends program execution when the program reaches a specified instruction address while the value in the specified data address matches with specified data. ■ Data Watch Break This break function suspends program execution when the program reaches a specified instrution address while the value in the specified data address matches with specified data. Up to 2 points can be set.
CHAPTER2 Dependence Functions Notes: • A data watch break shares points with the following functions. The maximum number of data watch breaks varies depending on how those functions are used. - Code break - Data break - Trace trigger - Sequencer • The data watch break may stop if it hits a specified address after a few steps of instructions following the instruction with data detection access are executed. The program may not stop if it hits the specified address during the execution of an instruction.
CHAPTER2 Dependence Functions 2.4.6.7 Sequencer This is a function to abort the program execution when the program is executedalong with the event order specified by the user. ■ Control by Sequencer Set two events, and set the flow in order from level 1 to level 2 as the condition for terminating the sequencer. This sequencer is called a two-level sequencer. Also, all previous information of the flow can be reset, and events for restarting monitoring the flow through level 1 can be set again.
CHAPTER2 Dependence Functions ■ Specifications of Sequencer Table 2.4-2 shows the specifications of the sequencer for the emulator debugger (MB2100-01). Table 2.4-2 Specifications of Sequencer Function Specification No. of levels 2 levels Restart function Available (one) Conditions of each event (Code/data) Address Pass count : 1 to 1048575 Attribute : Read/write Data size : Byte, half-word, word (Attribute and data size can be specified only for data events.
CHAPTER2 Dependence Functions 2.4.6.8 Guarded Access Break This is a function to abort the program execution when an access violation to protected area of memory occurs. ■ Guarded Access Breaks This is a break caused when monitoring an access to a guarded area on memory. If a guarded access break occurs while executing a program, program execution is suspended with the following message on the status bar. Break at address by guarded access ■ How to set Set the guarded access break as follows.
CHAPTER2 Dependence Functions 2.4.7 Measuring the Program Execution Time This section explains the function to measure the program execution time. ■ Measured Items The emulator debugger (MB2100-01) can measure the following two items for the user program execution time. • Time measurement Measures the time from start of program execution to end. For details, refer to "2.4.7.1 Measuring the Program Execution Cycle Count".
CHAPTER2 Dependence Functions 2.4.7.1 Measuring the Program Execution Cycle Count This section explains the function of measuring the number of program execution cycles. ■ Measurement Items This function measures the number of program execution cycles or real-time.
CHAPTER2 Dependence Functions ■ Setting Measurement Unit Either of the following methods can be used to set the measurement unit. • Dialog - Time Measurement Dialog For details, refer to "4.6.8.1 Measurement Unit for Execution Time Measurement" of "SOFTUNE Workbench Operation Manual". • Command - SET TIMERSCALE For details, refer to "1.64 SET TIMERSCALE" of "SOFTUNE Workbench Command Reference Manual".
CHAPTER2 Dependence Functions 2.4.7.2 Measuring Event-to-Event Execution Cycle Count [Performance Measurement] This section explains how to measure the execution cycle count between two events. ■ Performance Measurement The emulator debugger (MB2100-01) measures the execution cycle count or real-time between two events, which the system has passed while a user program is running. This emulator debugger has the following features for performance measurement.
CHAPTER2 Dependence Functions ■ Measuring Procedure Use the following steps to measure the performance. 1. Specify the performance measuring interval. 2. Execute the measurement. 3. Display the measurement result. Each of these steps can be executed in two methods: using GUI (window or dialog) and using only the command. In both methods, the same measurement result is obtained. Using GUI for measuring 1. Display the performance window. - Select [View] - [Performance] menu. For details, refer to Section "3.
CHAPTER2 Dependence Functions ■ Remeasuring Remeasuring performance refers to a function that clears the measuring count during execution of a user program and remeasures from the beginning. To carry out remeasuring, select [Restart] in the shortcut menu of the performance window. If necessary, you can respecify the performance measuring interval (event) during execution. This restarts measuring at the times when events have been set.
CHAPTER2 Dependence Functions 2.4.8 Viewing Program Execution History [Trace] This section describes the trace function. ■ What is Trace The function that records the program execution history is called "trace". Trace data contains the following information, which is available for the analysis of the program execution history.
CHAPTER2 Dependence Functions Figure 2.4-9 shows how data is stored in the trace buffer. Figure 2.4-9 Acquiring Trace Data When a break occurred during execution of a program Start execution Stop execution Start execution Stop execution Program flow Trace Buffer | --------------- Max. 1,024 frames ---------------| When the trace trigger hits and a break occurs Start execution Trace trigger(break) Start execution Stop execution Program flow Trace Buffer | --------------- Max.
CHAPTER2 Dependence Functions 2.4.8.1 Displaying Trace Data This section explains how to display trace data. ■ Display Formats of Trace Data The following three formats can be used to display trace data. RAW data: Displays trace data without analyzing it. Instruction: Displays trace data in the order in which instructions are executed. Source: Displays trace data on a source line basis. ■ Trace Data Display Position Trace data is numbered by frame. This number is called a "frame number".
CHAPTER2 Dependence Functions 3. (If the trace window is already displayed), update trace data. - Right-click on the trace window, and select [Refresh] from the pop-up menu. Trace data is updated in the trance window. For details, refer to Section "3.14 Trace Window" in "SOFTUNE Workbench Operation Manual". Using command window 1. Display trace data for each display mode. RAW data: SHOW TRACE Instruction: SHOW DETAILTRACE Source: SHOW DETAILTRACE For details, refer to Section "4.
CHAPTER2 Dependence Functions 2.4.8.1.1 Trace Data Display Examples (RAW Data) This section describes trace data that is displayed in the RAW data mode. ■ RAW Data Display This format displays frames that are output from the emulator without analyzing them. Figure 2.4-11 shows a RAW data display example. Figure 2.4-11 RAW Data Display If a chip reset has occurred, "***Chip Reset***" appears next to "frame no" as shown in Figure 2.4-12 .
CHAPTER2 Dependence Functions frame no. Displays frame numbers in decimal notation. b-addr Displays a branch address or low-level reset occurrence address in hexadecimal notation, or displays the standby state.
CHAPTER2 Dependence Functions a-data Displays access data in hexadecimal notation. In some cases, however, it may display read IDs, depending on the a-stat and a-type status. a-stat a-type a-data read dma Read access data write - Write access data read cpu / lost Read ID r-id Displays an ID that associates the read ID of a-data with r-data. If read ID matches r-id, the r-data of that frame is set as read access data. r-data Displays the data value for CPU read access in hexadecimal notation.
CHAPTER2 Dependence Functions 2.4.8.1.2 Trace Data Display Example (Instruction) This section describes trace data that is displayed in the instruction mode. ■ Instruction Display This mode displays the branch addresses of the RAW data display in disassembly format. Figure 2.4-14 shows an instruction display example. Figure 2.4-14 Instruction Display The instruction display mode displays the following information in addition to the information displayed in the RAW data display mode.
CHAPTER2 Dependence Functions 2.4.8.1.3 Trace Data Display Example (Source) This section describes trace data that is displayed in the source line mode. ■ Source Display This mode displays only source lines. Figure 2.4-15 shows a source display example. Figure 2.4-15 Source Display frame no. Displays the frame number in decimal form. source Displays executed source lines.
CHAPTER2 Dependence Functions 2.4.8.2 Saving Trace Data This section explains how to save trace data. ■ Saving Trace Data Trace data can be saved in a specified file. The following two methods are available to save trace data: using GUI (window or dialog) and using only the command. The same result is obtained from both methods. Using Command for Saving Trace Data 1. Display the trace window. - Select [View] - [Trace] menu. 2. Specify the name of the file in which to save trace data.
CHAPTER2 Dependence Functions 2.4.8.3 Searching for Trace Data This section explains how to search for trace data. ■ Searching for Trace Data The specified address or frame number in trace data can be displayed. The following two methods are available to search for trace data: using GUI (window or dialog) and using only the command. The same result is obtained from both methods. Using GUI for Searching for Trace Data 1. Display the trace window. - Select [View] - [Trace] menu. 2.
CHAPTER2 Dependence Functions 2.4.8.4 Obtaining Only Trace Data with Specified Attributes This section explains the trace filter. ■ Trace Filter This function obtains only the data with a specified access attribute when fetching codes or obtaining data access information as trace data. The access attribute can be selected from read, write, or code.
CHAPTER2 Dependence Functions 2.4.8.5 Ending Trace Acquisition in Specified Conditions This section explains the trace trigger. ■ Trace Trigger A trigger can be generated to end trace acquisition in the specified conditions by monitoring the MCU bus running status. This function is called a "trace trigger". The trace trigger can be selected with either the code attribute or the data access attribute. If the trace trigger hits, the execution of the program can be stopped. For details, refer to Section "2.
CHAPTER2 Dependence Functions 2.4.9 Disabling Memory Access to Specified Area This section explains the access-prohibited area. ■ Access-prohibited Area The access-prohibited area has a function to inhibit memory access when the debugger tries to access the memory in the specified area (*1). However, it does not inhibit memory access from the program. (*1) The following shows the memory access by the commands or window operations.
CHAPTER2 Dependence Functions 2.4.10 Displaying Messages Output from the User Program on Debugger This section explains semihosting features. ■ What is Semihosting Feature This is a function to display the messages output from the user program on debugger window. This can be used only for products whose semihosting function is enabled. For details of availability of semihosting function, refer to "OCD" in the hardware manual of the product you are using. As shown in Figure 2.
CHAPTER2 Dependence Functions ■ Using Semihosting Feature Perform the following procedure to display the content of output request to MBR on the terminal window. 1. Controlling MBR with the user program MBR must be controlled in the user program, as shown in Figure 2.4-16 . Sample projects that include a method for controlling the MBR is attached to SOFTUNE Workbench V60L10 or later. Control MBR based on those.
CHAPTER2 Dependence Functions 2.4.11 Checking Debugger Status This section explains how to check information. ■ Debugger Information The emulator debugger (MB2100-01) enables you to check the following information at startup. • SOFTUNE Workbench file information • Hardware information If any errors have been discovered during SOFTUNE Workbench operations, check this information and contact our sales department or support department.
CHAPTER2 Dependence Functions SiM911 Product name: SOFTUNE Workbench File Path: SiM911.dll path Version: SiM911.dll version - - - - - - - - - - - - - - - - - - - - - - - - - - - Language Tools - FR Family SOFTUNE C/C++ Compiler version File Path: fcc911s.exe path - FR Family SOFTUNE Assembler version File Path: fasm911s.exe path - FR Family SOFTUNE Linker version File Path: flnk911s.exe path - FR Family SOFTUNE Librarian version File Path: flib911s.
CHAPTER2 Dependence Functions CPU family ID: ID that indicates the CPU family installed in the device DSU type ID: ID that indicates the OCD-DSU installation type.
CHAPTER2 Dependence Functions 2.5 Monitor Debugger This section describes the functions of the monitor debugger. ■ Monitor Debugger The monitor debugger performs debugging by putting the target monitor program for debugging into the target system and by communicating with the host. Before using this debugger, the target monitor program must be ported to the target hardware.
CHAPTER2 Dependence Functions 2.5.1 Resources Used by Monitor Program The monitor program of the monitor debugger uses the I/O resources listed below. The target hardware must have these resources available for the monitor program. ■ Required Resources The following resources are required to build the monitor program into the target hardware. Table 2.
CHAPTER2 Dependence Functions 2.5.2 Break The Monitor Debugger provides two types of break functions. When by each break function aborts program execution, the address where a break occurred and the break factor are displayed.
CHAPTER2 Dependence Functions 2.5.2.1 Software Break A software break is a function to make a break by executing an instruction embedded in memory. The break occurs before executing the instruction at the specified address. ■ Software Break A software break is a function to make a break by executing an instruction embedded in memory. The break occurs before executing the instruction at the specified address. Up to 16 break points can be set.
CHAPTER2 Dependence Functions 2.5.2.2 Forced Break This function forcibly aborts the program execution to generate a break. ■ Forced Break This function forcibly aborts the program execution to generate a break. When the forced break occurred, the following message appears at the status bar. Break at address by command abort request ■ How to Generate A forced break is generated in the following methods: • Menu [Debug] - [Abort] menu For details, refer to "4.6.
CHAPTER2 Dependence Functions 2.5.3 Measuring Execution Time This function measures the execution time of a program. ■ Measurement Item The execution time of a program is measured. The resolution of the execution time is 1s, and up to "(2 to the power of 32 - 1) x 1s" can be measured.
CHAPTER2 Dependence Functions 2.5.4 Inaccessible Area This section explains inaccessible area by the monitor debugger. ■ Inaccessible area The inaccessible area is a function that suppresses access to memory when the debugger accesses a specified memory area (using commands, windows, etc.*). However, access to memory is not suppressed using program. The following commands are used to set an inaccessible area. SET MAP/INACCESSIBLE: Sets an inaccessible region.
INDEX INDEX The index follows on the next page. This is listed in alphabetic order.
INDEX Index A Access Access to Flash Memory ............................... 166 Access-prohibited Area.................................. 202 Access Attributes Memory Area Access Attributes ...................... 37 Active Project Active Project..................................................... 2 Active Project Configuration .............................. 4 Alignment Error Break Alignment Error Break ............................. 79, 119 Assembly Line Assembly ...........................................
INDEX Debugging DEBUG I/F..................................................... 152 Ending debugging.......................................... 156 Power-on debugging ..................................... 141 Starting Debugging........................................ 151 Verification Items When Starting Debugging .......................................................... 151 Delay branch instruction Precaution on executing the delay branch instruction ...................................
INDEX STUB Function ................................................ 42 Trace Buffer-full Break....................... 46, 78, 118 Trace Trigger Break....................................... 176 How to use How to use............................................. 163, 164 I I/O Port I/O Port Simulation (Input Port)........................ 38 I/O Port Simulation (Output Port)..................... 38 Inaccessible area Access to memory area including inaccessible area.....................................
INDEX Operating Environment Operating Environment.................................... 22 Setting Operating Environment ....... 66, 100, 157 Operating Environments Operating Environments of the Target .......... 153 Operating frequencies Operating frequencies ............................. 70, 104 Operation Mode Setting MCU Operation Mode ................. 67, 102 Operation Requirements Operation Requirements ............................... 173 Operation requirements Operation requirements....................
INDEX Security Security.......................................................... 155 Semihosting Feature Using Semihosting Feature ........................... 204 What is Semihosting Feature......................... 203 Sequencer Control by Sequencer ............................ 124, 180 Operation of Sequencer................................. 180 Specifications of Sequencer .......................... 181 Simulation I/O Port Simulation (Input Port)........................
INDEX Trace Trigger Break Trace Trigger Break....................................... 176 U User Program Commands Available during Execution of User Program...................................... 72, 108 V Variables Specifying C/C++ Variables .............................30 W Workspace Workspace .........................................................2 Workspace Management Function ....................2 Workspace Management Workspace Management Function ....................
INDEX 222
Colophon CM71-00329-7E FUJITSU SEMICONDUCTOR CONTROLLER MANUAL FR FAMILY SOFTUNETM WORKBENCH USER’S MANUAL for V6 November 2011 the seventh edition Published FUJITSU SEMICONDUCTOR LIMITED Edited Sales Promotion Dept.
