Fujitsu CM71-00329-7E User Manual

FUJITSU SEMICONDUCTOR CONTROLLER MANUAL

SOFTUNE

CM71-00329-7E

FR FAMILY

WORKBENCH

USER’S MANUAL

for V6

SOFTUNE

USER’S MANUAL

FR FAMILY

WORKBENCH

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. This manual is intended for engineers

developing various types of products using SOFTUNE Workbench. Be sure to read this manual

completely.

■ Trademarks

REALOS, SOFTUNE are trademark of Fujitsu Semiconductor Limited, Japan.

The company names and brand names herein are the trademarks or registered trademarks of their respective

owners.

■ Organization of Manual

This manual consists of two chapters.

CHAPTER1 Basic Functions

This chapter describes the basic functions on the SOFTUNE Workbench.

CHAPTER2 Dependence Functions

This chapter describes the functions dependent on each Debugger.

• 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. When you develop equipment incorporating the device based on such information, you must assume any responsibility arising out of such use of the information. FUJITSU SEMICONDUCTOR assumes no liability for any damages whatsoever arising out of the use of the information.

• Any information in this document, including descriptions of function and schematic diagrams, shall not be construed as license of the use or exercise of any intellectual property right, such as patent right or copyright, or any other right of FUJITSU SEMICONDUCTOR or any third party or does FUJITSU SEMICONDUCTOR warrant non-infringement of any third-party's intellectual property right or other right by using such information. FUJITSU SEMICONDUCTOR assumes no liability for any infringement of the intellectual property rights or other rights of third parties which would result from the use of information contained herein.

• The products described in this document are designed, developed and manufactured as contemplated for general use, including without limitation, ordinary industrial use, general office use, personal use, and household use, but are not designed, developed and manufactured as contemplated (1) for use accompanying fatal risks or dangers that, unless extremely high safety is secured, could have a serious effect to the public, and could lead directly to death, personal injury, severe physical damage or other loss (i.e., nuclear reaction control in nuclear facility, aircraft flight control, air traffic control, mass transport control, medical life support system, missile launch control in weapon system), or (2) for use requiring extremely high reliability (i.e., submersible repeater and artificial satellite). Please note that FUJITSU SEMICONDUCTOR will not be liable against you and/or any third party for any claims or damages arising in connection with above-mentioned uses of the products.

• Any semiconductor devices have an inherent chance of failure. You must protect against injury, damage or loss from such failures by incorporating safety design measures into your facility and equipment such as redundancy, fire protection, and prevention of over-current levels and other abnormal operating conditions.

• Exportation/release of any products described in this document may require necessary procedures in accordance with the regulations of the Foreign Exchange and Foreign Trade Control Law of Japan and/or US export control laws.

• The company names and brand names herein are the trademarks or registered trademarks of their respective owners.

CONTENTS

CHAPTER1 Basic Functions .......................................................................................... 1

1.1 Workspace Management Function ..................................................................................................... 2

1.2 Project Management Function ............................................................................................................ 3

1.3 Project Dependence ........................................................................................................................... 5

1.4 Make/Build Function ........................................................................................................................... 6

1.4.1 Customize Build Function .............................................................................................................. 7

1.5 Include Dependencies Analysis Function ........................................................................................... 9

1.6 Functions of Setting Tool Options ..................................................................................................... 10

1.7 Error Jump Function ......................................................................................................................... 11

1.8 Editor Functions ................................................................................................................................ 13

1.9 Storing External Editors .................................................................................................................... 15

1.10 Storing External Tools ...................................................................................................................... 17

1.11 Macro Descriptions Usable in Manager ............................................................................................ 18

1.12 Setting Operating Environment ......................................................................................................... 22

1.13 Debugger Types ............................................................................................................................... 23

1.14 Memory Operation Functions ........................................................................................................... 24

1.15 Register Operations .......................................................................................................................... 25

1.16 Line Assembly and Disassembly ...................................................................................................... 26

1.17 Symbolic Debugging ......................................................................................................................... 27

1.17.1 Referring to Local Symbols ......................................................................................................... 29

1.17.2 Referring to C/C++ Variables ...................................................................................................... 30

CHAPTER2 Dependence Functions ............................................................................ 33

2.1 Simulator Debugger .......................................................................................................................... 34

2.1.1 Instruction Simulation .................................................................................................................. 36

2.1.2 Memory Simulation ...................................................................................................................... 37

2.1.3 I/O Port Simulation ...................................................................................................................... 38

2.1.4 Interrupt Simulation ..................................................................................................................... 39

2.1.5 Reset Simulation ......................................................................................................................... 40

2.1.6 Low Power Consumption Mode Simulation ................................................................................. 41

2.1.7 STUB Function ............................................................................................................................ 42

2.1.8 Break ........................................................................................................................................... 43

2.1.8.1 Code Break ............................................................................................................................... 44

2.1.8.2 Data Break ................................................................................................................................ 45

2.1.8.3 Trace Buffer-full Break .............................................................................................................. 46

2.1.8.4 Guarded Access Break ............................................................................................................. 47

2.1.8.5 Forced Break ............................................................................................................................ 48

2.1.9 Measuring Execution Cycle Count .............................................................................................. 49

2.1.10 Trace ........................................................................................................................................... 50

2.1.10.1 Trace Sampling ........................................................................................................................ 51

2.1.10.2 Setting Trace ............................................................................................................................ 52

2.1.10.3 Displaying Trace Data .............................................................................................................. 53

2.1.10.4 Display Format of Trace Data ................................................................................................... 54

iii

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 ................................................................................................................... 58

2.1.11.1 Coverage Measurement Procedures ........................................................................................ 59

2.1.12 Checking Debugger Status .......................................................................................................... 62

2.2 Emulator Debugger (MB2197) .......................................................................................................... 65

2.2.1 Setting Operating Environment ................................................................................................... 66

2.2.1.1 MCU Operation Mode ............................................................................................................... 67

2.2.1.2 DRAM Refresh Control ............................................................................................................. 68

2.2.1.3 Cache Flush Control ................................................................................................................. 69

2.2.1.4 Operating Frequency ................................................................................................................ 70

2.2.2 Notes on Executing Program ....................................................................................................... 71

2.2.3 Commands Available during Execution of User Program ........................................................... 72

2.2.4 Break ........................................................................................................................................... 73

2.2.4.1 Code Break ............................................................................................................................... 74

2.2.4.2 Code Event Break .................................................................................................................... 76

2.2.4.3 Data Event Break ..................................................................................................................... 77

2.2.4.4 Trace Buffer-full Break .............................................................................................................. 78

2.2.4.5 Alignment Error Break .............................................................................................................. 79

2.2.4.6 External Trigger Break .............................................................................................................. 80

2.2.4.7 Forced Break ............................................................................................................................ 81

2.2.5 Measuring Execution Cycle Count .............................................................................................. 82

2.2.6 Trace ........................................................................................................................................... 83

2.2.6.1 Trace Data ................................................................................................................................ 84

2.2.6.2 Trace Sampling ........................................................................................................................ 85

2.2.6.3 Setting Trace ............................................................................................................................ 86

2.2.6.4 Displaying Trace Data .............................................................................................................. 87

2.2.6.5 Display Format of Trace Data ................................................................................................... 88

2.2.6.6 Searching Trace Data ............................................................................................................... 89

2.2.6.7 Saving Trace Data .................................................................................................................... 90

2.2.6.8 Clearing Trace Data ................................................................................................................. 91

2.2.6.9 Notes on Use of Tracing Function ............................................................................................ 92

2.2.7 Inaccessible Area ........................................................................................................................ 94

2.2.8 Checking Debugger Status .......................................................................................................... 95

2.3 Emulator Debugger (MB2198) .......................................................................................................... 98

2.3.1 Setting Operating Environment ................................................................................................. 100

2.3.1.1 Monitoring Program Automatic Loading ................................................................................. 101

2.3.1.2 MCU Operation Mode ............................................................................................................. 102

2.3.1.3 Cache Flush Control ............................................................................................................... 103

2.3.1.4 Operating Frequency .............................................................................................................. 104

2.3.1.5 External Memory Emulation ................................................................................................... 105

2.3.1.6 Debug mode ........................................................................................................................... 106

2.3.2 Notes on Executing Program ..................................................................................................... 107

2.3.3 Commands Available during Execution of User Program ......................................................... 108

2.3.4 Break ......................................................................................................................................... 110

2.3.4.1 Code Break ............................................................................................................................. 111

2.3.4.2 Data Break .............................................................................................................................. 113

2.3.4.3 Code Event Break .................................................................................................................. 114

2.3.4.4 Data Event Break ................................................................................................................... 116

2.3.4.5 Trace Buffer-full Break ............................................................................................................ 118

2.3.4.6 Alignment Error Break ............................................................................................................ 119

2.3.4.7 External Trigger Break ............................................................................................................ 120

2.3.4.8 Forced Break .......................................................................................................................... 121

2.3.4.9 Data Watch Break .................................................................................................................. 122

2.3.5 Control by Sequencer ................................................................................................................ 124

2.3.6 Measuring Execution Cycle Count ............................................................................................ 127

2.3.7 Trace ......................................................................................................................................... 128

2.3.7.1 Display Format of Trace Data ................................................................................................. 132

2.3.7.2 Saving Trace Data .................................................................................................................. 133

2.3.7.3 Notes on Use of Tracing Function .......................................................................................... 134

2.3.8 Measuring Performance ............................................................................................................ 136

2.3.8.1 Performance Measurement Procedures ................................................................................. 137

2.3.8.2 Displaying Performance Measurement Data .......................................................................... 139

2.3.9 Real-time Monitoring ................................................................................................................. 140

2.3.10 Power-on Debugging ................................................................................................................. 141

2.3.11 Inaccessible Area ...................................................................................................................... 142

2.3.12 RAM Checker ............................................................................................................................ 143

2.3.13 Checking Debugger Status ........................................................................................................ 147

2.4 Emulator Debugger (MB2100-01) ................................................................................................... 150

2.4.1 Starting debugging .................................................................................................................... 151

2.4.1.1 Power-on Reset ...................................................................................................................... 152

2.4.1.2 Operating Environments of the Target ................................................................................... 153

2.4.1.3 Security ................................................................................................................................... 155

2.4.2 Ending debugging ...................................................................................................................... 156

2.4.3 Efficiently Executing Debugging ................................................................................................ 157

2.4.3.1 Increasing Communication Speed during Debugging ............................................................ 158

2.4.3.2 Switching Debug Function ...................................................................................................... 159

2.4.4 Executing Program .................................................................................................................... 160

2.4.4.1 Setting/Release of Debug Functions ...................................................................................... 161

2.4.4.2 Monitoring ............................................................................................................................... 163

2.4.4.3 Power-on Debug ..................................................................................................................... 164

2.4.5 To Access the Flash Memory .................................................................................................... 166

2.4.6 To Interrupt the Program Execution [Break] .............................................................................. 170

2.4.6.1 Code Break (Hardware) .......................................................................................................... 171

2.4.6.2 Code Break (Software) ........................................................................................................... 173

2.4.6.3 Data Break .............................................................................................................................. 175

2.4.6.4 Trace Trigger Break ................................................................................................................ 176

2.4.6.5 Forced Break .......................................................................................................................... 177

2.4.6.6 Data Watch Break .................................................................................................................. 178

2.4.6.7 Sequencer .............................................................................................................................. 180

2.4.6.8 Guarded Access Break ........................................................................................................... 182

2.4.7 Measuring the Program Execution Time ................................................................................... 183

2.4.7.1 Measuring the Program Execution Cycle Count ..................................................................... 184

2.4.7.2 Measuring Event-to-Event Execution Cycle Count [Performance Measurement] .................. 186

2.4.8 Viewing Program Execution History [Trace] .............................................................................. 189

2.4.8.1 Displaying Trace Data ............................................................................................................ 191

2.4.8.2 Saving Trace Data .................................................................................................................. 198

2.4.8.3 Searching for Trace Data ....................................................................................................... 199

2.4.8.4 Obtaining Only Trace Data with Specified Attributes .............................................................. 200

2.4.8.5 Ending Trace Acquisition in Specified Conditions .................................................................. 201

2.4.9 Disabling Memory Access to Specified Area ............................................................................. 202

2.4.10 Displaying Messages Output from the User Program on Debugger ......................................... 203

2.4.11 Checking Debugger Status ........................................................................................................ 205

2.5 Monitor Debugger ........................................................................................................................... 208

2.5.1 Resources Used by Monitor Program ....................................................................................... 209

2.5.2 Break ......................................................................................................................................... 210

2.5.2.1 Software Break ....................................................................................................................... 211

2.5.2.2 Forced Break .......................................................................................................................... 212

2.5.3 Measuring Execution Time ........................................................................................................ 213

2.5.4 Inaccessible Area ...................................................................................................................... 214

INDEX................................................................................................................................... 215

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.14 Memory Operation Functions

1.15 Register Operations

1.16 Line Assembly and Disassembly

1.17 Symbolic Debugging

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.

■ Workspace Management Function

To manage two or more projects, workspace manages the following information:

• Project

• Active project

• Subproject

■ Project

The operation performed in SOFTUNE Workbench is based on the project. The project is a set of files and

procedures necessary for creation of a target file. The project file contains all data managed by the project.

■ Active Project

The active project is basic to workspace and undergoes [Make], [Build], [Compile/Assemble], [Start Debug],

and [Include Dependencies] in the menu. [Make], [Build], [Compile/Assemble], and [Include Dependencies]

affect the subprojects within the active project.

If workspace contains some project, it always has one active project.

■ Subproject

The subproject is a project on which other projects depend. The subproject target files are linked together

when creating parent project target files that have dependent relationships. When making/building a parent

project, the subproject which has a dependent relationships is make/build first before executing the make/

build for the parent project. If making and building of the subproject is unsuccessful, the parent project of

the subproject will not be made and built.

The target file in the subproject is however not linked with the parent project when:

• An absolute (ABS)-type project is specified as a subproject.

• A library (LIB)-type project is specified as a subproject.

■ Restrictions on Storage of Two or More Projects

Only one REALOS-type 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.

- Project configuration

- Active project configuration

- Information on source files, include files, other object files, library files

- Information on tools executed before and after executing language tools (customize build function)

■ Project format

The project file supports two formats: a 'workspace project format,' and an 'old project format.'

The differences between the two formats are as follows:

● Workspace project format

- Supports management of two or more project configurations

- Supports use of all macros usable in manager

- Does not support early Workbench versions *

● Old project format

- Supports management of just one project configuration

- Limited number of macros usable in manager

For details, refer to Section "1.11 Macro Descriptions Usable in Manager".

- Supports early Workbench versions *

When a new project is made, the workspace project format is used.

When using an existing project, the corresponding project format is used.

If a project made by an early Workbench version* is used, dialog asking whether to convert the file to the

workspace project format is opened. For details, refer to Section "2.13 Reading SOFTUNE Project Files of

Old Versions" in "SOFTUNE Workbench Operation Manual".

To open a project file in the workspace project format with an early Workbench version*, it is necessary to

convert the file to the old project format. For saving the file in other project formats, refer to Section "4.2.7

Save As" in "SOFTUNE Workbench Operation Manual".

*: FR V5: V50L03 or earlier

FR V3: V30L26 or earlier.

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.

In the new project configuration, the same files as those in the original project configuration are always

used.

By using the project configuration, the settings of programs of different versions, such as the optimization

level of a compiler and MCU setting, can be created within one project.

In the project configuration, the following information is managed:

• Name and directory of target file

• Information on options of language tools to create target file by compiling, assembling and linking source files

• Information on whether to build file or not

• Information on setting of debugger to debug target file

■ Active Project Configuration

The active project configuration at default undergoes [Make], [Build], [Compile/Assemble], [Start Debug],

and [Include Dependencies].

Note:

The setting of the active project configuration is used for the file state displayed in the SRC tab of project

window and includes files detected in the [Dependencies] folder.

If a macro function newly added is used in old project format, the macro description is expanded at the time of saving in old project format. For the macro description newly added, refer to Section "1.11 Macro Descriptions Usable in Manager".

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.

The use of project dependence enables simultaneous making and building of two or more projects

developed in one workspace.

A project configuration in making and building a subproject in the [Project] - [Configuration] - [Set Build

Configuration] command can be specified.

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.

For this function to work fully, the dependence between source files and include files should be accurately

grasped. To do this, SOFTUNE Workbench has a function for analyzing include dependence. To perform

this function, it is necessary to understand the dependence of a source file and include file. SOFTUNE

Workbench has the function of analyzing include dependence. For details, refer to Section "1.5 Include

Dependencies Analysis Function".

■ Build Function

Build function generates a target file by compiling/assembling all source files registered with a project,

regardless of whether they have been updated or not, and then by joining all required object files. Using

this function causes all files to be compiled/assembled, resulting in the time required for generating the

target file longer. Although the correct target file can be generated from the current source files.

The execution of Build function is recommended after completing debugging at the final stage of program

development.

Note:

When executing the Make function using a source file restored from backup, the integrity between an object file and a source file may be lost. If this happens, executing the Build function again.

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.

The following operations can be performed automatically during Make or Build using this function:

• Starting the syntax check before executing the Compiler.

• After executing the Converter, starting the S-format binary Converter (m2bs.exe) and converting Motorola S-format files to binary format files.

■ Setting Options

An option follows the tool name to start a tool from SOFTUNE Workbench. The options include any file

name and tool-specific options. SOFTUNE Workbench has the macros indicating that any file name and

tool-specific options are specified as options.

■ Macro List

If any character string other than parameters is specified, it is passed directly to the tool. For details about

the parameters, refer to Section "1.11 Macro Descriptions Usable in Manager".

The Setup Customize Build dialog provides a macro list for macro input. The build file, load module file,

project file submenus indicate their sub-parameters specified.

The environment variable brackets must have any item; otherwise, resulting in an error.

Table 1.4-1 Macro List

Macro List Macro Name

Build file %(FILE)

Load module file %(LOADMODULEFILE)

Project file %(PRJFILE)

Workspace file %(WSPFILE)

Project directory %(PRJPATH)

Target file directory %(ABSPATH)

Object file directory %(OBJPATH)

List file directory %(LSTPATH)

Project construction name %(PRJCONFIG)

Environment variable %(ENV[])

Temporary file %(TEMPFILE)

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.

For this reason, SOFTUNE Workbench has a built-in Include Dependencies Analysis function. This

function can be activated by selecting the [Project] -[Include Dependencies] command. By using this

function, uses can know the exact dependencies, even if an include file includes another include file.

SOFTUNE Workbench automatically updates the dependencies of the compiled/assembled files.

Note:

When executing the [Project] - [Include Dependencies] command, the Output window is redrawn and replaced by the dependencies analysis result.

If the contents of the current screen are important (error message, etc.), save the contents to a file and then execute the Include Dependencies command.

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.

Tool options include the options effective for all source files (common options) and the options effective

for specific source files (individual options). For details about the option setting, refer to Section "4.5.5

Setup Project" in "SOFTUNE Workbench Operation Manual".

● Common options

These options are effective for all source files (excluding those for which individual options are specified)

stored in the project.

● Individual options

These options are compile/assemble options effective for specific source files. The common options

specified for source files for which individual options are specified become invalid.

■ Tool Options

In SOFTUNE Workbench, the macros indicating that any file name and directory name are specified as

options.

If any character string other than parameters is specified, it is passed directly to the tool. For details about

the parameters, refer to Section "1.11 Macro Descriptions Usable in Manager". For details about the tool

options for each tool, refer to the manual of each tool.

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.

The SOFTUNE Workbench Error Jump function analyzes the source file names and line number

information embedded in the error message displayed in the Output window, opens the matching file, and

jumps automatically to the line.

The location where a source file name and line number information are embedded in an error message,

varies with the tool outputting the error.

An error message format can be added to an existing one or modified into a new one. However, the modify

error message formats for pre-installed Fujitsu language tools are defined as part of the system, these can

not be modified.

■ Syntax

A new error message format should be added when working the Error Jump function with user registered

tool. To set Error Jump, execute the [Setup] - [Error] command.

An error message format can be described in Syntax. SOFTUNE Workbench uses macro descriptions as

shown in the Table 1.7-1 to define such formats.

To analyze up to where %f, %h, and %* continue, SOFTUNE Workbench uses the character immediately

after the above characters as a delimiter. Therefore, in Syntax, the description until a character that is used

as a delimiter re-appears, is interpreted as a file name or a keyword for help, or is skipped over. To use %

as a delimiter, describe as %%. The %[char] macro skips over as long as the specified character continues

in parentheses. To specify "]" as a skipped character describes it as "\]". Blank characters in succession can

be specified with a single blank character.

Table 1.7-1 Special Characters for Analyzing Error Messages

Characters Semantics

%f Interpret as source file name and inform editor.

%1 Interpret as line number and inform editor.

%h Become keyword when searching help file.

%* Skip any desired character.

%[char] Skip as long as characters in [ ] continues.

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.

● Keyword marking function in C/C++/assembler source file

Displays reserved words, such as if and for, in different color.

● Error line marking function

The error line can be viewed in a different color, when executing Error Jump.

● Bookmark setup function

A bookmark can be set on any line, and instantaneously jumps to the line. Once a bookmark is set, the line

is displayed in a different color.

● Ruler, line number display function

The Ruler is a measure to find the position on a line; it is displayed at the top of the Edit window. A line

number is displayed at the left side of the Edit window.

● Automatic indent function

When a line is inserted using the Enter key, the same indent (indentation) as the preceding line is set

automatically at the inserted line. If the space or tab key is used on the preceding line, the same use is set at

the inserted line as well.

● Function to display Blank, Line Feed code, and Tab code

When a file includes a Blank, a Line Feed code, and Tab code, these codes are displayed with special

symbols.

● Undo function

This function cancels the preceding editing action to restore the previous state. When more than one

character or line is edited, the whole portion is restored.

● Tab size setup function

Tab stops can be specified by defining how many digits to skip when Tab codes are inserted. The default is

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. Use the

[Setup] - [Editor] command to set an external editor.

■ Precautions

● Error jump function

The Error Jump cannot move the cursor to an error line if the external editor does not have a function to

specify the cursor location when activated.

● File save at compiling/assembling

SOFTUNE Workbench cannot control an external editor. Always save the file you are editing before

compiling/assembling.

■ Setting Options

When activating an external editor from SOFTUNE Workbench, options must be added immediately after

the editor name. The names of file to be opened by the editor and the initial location of the cursor (the line

number) can be specified. SOFTUNE Workbench has a set of special parameters for specifying any file

name and line number, as shown in the Table 1.9-1 . If any other character string are described by these

parameters, such character string are passed as is to the editor.

%f (File name) is determined as follows:

1.If the focus is on the SRC tab of Project window, and if a valid file name is selected, the selected file name becomes the file name.

2.When a valid file name cannot be acquired by the above procedure, the file name with a focus in the built-in editor becomes the file name.

%x (project path) is determined as follows:

1.If a focus is on the SRC tab of project window and a valid file name is selected, the project path is a path to the project in which the file is stored.

2.If no path is obtained, the project path is a path to the active project.

The specification method of the file name containing a space is different by editors. For details, refer to the

Editor Manual.

Ex.)

MIFES "%f + %l"

WZ Editor "%f" /j%l

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

Note:

MIFES V1.0 %f + %l

UltraEdit32 %f/%l/1

TextPad32 %f(%l)

PowerEDITOR %f -g%l

Codewright32 %f -g%l

Hidemaru for Win3.1/95 /j%l:1 %f

ViVi /line=%l %f

• Regarding execution of error jump in Hidemaru:

To execute error jump in Hidemaru used as an external editor, use the [Others] - [Operating Environment] - [Exclusive Control] menu, and then set "When opening the same file in Hidemaru" and "Opening two identical files is inhibited".

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.

If a tool set as an external tool is designed to output the execution result to the standard output and the

standard error output through the console application, the result can be specified to the SOFTUNE

Workbench Output window. In addition, the allow description of additional parameters each time the tool

is activated.

To set an external tool, use the [Setup] - [Tool] command.

To select the title of a set tool, use the [Setup] - [Tool execution] command.

■ Setting Options

When activating an external tool from SOFTUNE Workbench, options must be added immediately after the

tool name. Specify the file names, and unique options, etc.

SOFTUNE Workbench has a set of special parameters for specifying any file name and unique tool

options.

If any characters described other than these parameters, such characters are passed as it is to the external

tool.

Note:

For details about the parameters, refer to Section "1.11 Macro Descriptions Usable in Manager".

When checking [Use the Output window], note the following:

1. Once a tool is activated, neither other tools nor the compiler/assembler can be activated until the tool is terminated.

2. 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.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.

The type of macro that can be specified and macro expansion slightly vary depending on where to describe

macros. The macros usable for each function are detailed below. For the macros that can be specified for

"Error Jump" and "External Editors", refer to Sections "1.7 Error Jump Function" and "1.9 Storing

External Editors".

■ Macro List

The following is a list of macros that can be specified in SOFTUNE Workbench.

The macros usable for each function are listed below.

• External tools : Table 1.11-1 and Table 1.11-2

• Customize build : Table 1.11-1 and Table 1.11-2

• Tool options : Table 1.11-2

The directory symbol \ is added to the option directories in Table 1.11-1 but not to the macro directories in

Table 1.11-2 .

The sub-parameters in Table 1.11-3 can be specified in %(FILE), %(LOADMODULEFILE), %(PRJFILE)

and %(WSPFILE).

The sub-parameter is specified in the form of %(PRJFILE[PATH]).

If the current directory is on the same drive, the relative path is used. The current directory is the

workspace directory for %(PRJFILE), and %(WSPFILE), and the project directory for other than them.

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. (*2)

%x Passed as directory of project file. (*2)

%X Passed as main file name of project file. (*2)

CHAPTER1 Basic Functions

%% Passed as %.

Table 1.11-2 List of macros that can be specified 2

Parameter Meaning

%(FILE) Passed as full-path name of file. (*1)

%(LOADMODULEFILE) Passed as full-path name of load module file. (*2)

%(PRJFILE) Passed as full-path name of project file. (*2)

%(WSPFILE) Passed as full-path name of workspace file.(*3)

%(PRJPATH) Passed as directory of project file. (*2)

%(ABSPATH) Passed as directory of target file. (*2)

%(OBJPATH) Passed as directory of object file. (*2)

%(LSTPATH) Passed as directory of list file. (*2)

%(PRJCONFIG) Passed as project configuration name. (*2)(*3)

%(ENV[Environment variable]) Environment variable specified in environment variable

brackets is passed.

%(TEMPFILE) Temporary file is created and its full-path name is

passed. (*4)

*1: The macros are determined as follows:

• Customize build

1. Source file before and after executing compiler and assembler

2. Target file before and after executing linker, librarian and converter

3. Configuration file before and after executing configuration

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. Information on configuration of active project in which file is stored as focus is on the SRC tab of project window and valid file name is selected

2. Information on configuration of active project if no valid file name can be obtained in 1

*3: Only project files in the workspace project format can be used for macros indicated.

*4: Data in the temporary file can be specified only for customize build.

Table 1.11-3 Lists of Sub parameters 1

Sub parameter Meaning

[PATH] Directory of file

[RELPATH] Directory of file

[NAME] Main file name of file

[EXT] Extension of file

[SHORTFULLNAME] Full path name of short file

[SHORTPATH] Directory of short file

[SHORTNAME] Main file name of short file

[FOLDER] Name of folder in which files are stored in the SRC tab of project

window (Can be specified only in %(FILE).) (*)

*: The macro can be used only in workspace-compatible Workbench. It is not expanded in workspace-

incompatible Workbench.

+ 204 hidden pages