Fujitsu F2MC-16FX MB2198 User manual

Fujitsu Microelectronics Europe
Application Note
MCU-AN-300217-E-V10
F²MC-16FX FAMILY
SUPPORT TOOL
EMULATOR SYSTEM MB2198
GETTING STARTED
APPLICATION NOTE

MB2198 – Getting Started
Revision History
MCU-AN-300217-E-V10 - 2 - © Fujitsu Microelectronics Europe GmbH
Revision History
Date Issue
2006-12-14 V1.0; MWi; release version
This document contains 32 pages.

MB2198 – Getting Started
Warranty and Disclaimer
©Fujitsu Microelectronics Europe GmbH - 3 - MCU-AN-300217-E-V10
Warranty and Disclaimer
To the maximum extent permitted by applicable law, Fujitsu Microelectronics Europe GmbH restricts
its warranties and its liability for all products delivered free of charge (eg. software include or
header files, application examples, target boards, evaluation boards, engineering samples of IC’s
etc.), its performance and any consequential damages, on the use of the Product in accordance with
(i) the terms of the License Agreement and the Sale and Purchase Agreement under which
agreements the Product has been delivered, (ii) the technical descriptions and (iii) all accompanying
written materials. In addition, to the maximum extent permitted by applicable law, Fujitsu
Microelectronics Europe GmbH disclaims all warranties and liabilities for the performance of the
Product and any consequential damages in cases of unauthorised decompiling and/or reverse
engineering and/or disassembling. Note, all these products are intended and must only be used
in an evaluation laboratory environment.
1. Fujitsu Microelectronics Europe GmbH warrants that the Product will perform substantially in
accordance with the accompanying written materials for a period of 90 days form the date of receipt
by the customer. Concerning the hardware components of the Product, Fujitsu Microelectronics
Europe GmbH warrants that the Product will be free from defects in material and workmanship under
use and service as specified in the accompanying written materials for a duration of 1 year from the
date of receipt by the customer.
2. Should a Product turn out to be defect, Fujitsu Microelectronics Europe GmbH´s entire liability
and the customer´s exclusive remedy shall be, at Fujitsu Microelectronics Europe GmbH´s sole
discretion, either return of the purchase price and the license fee, or replacement of the Product or
parts thereof, if the Product is returned to Fujitsu Microelectronics Europe GmbH in original packing
and without further defects resulting from the customer´s use or the transport. However, this warranty
is excluded if the defect has resulted from an accident not attributable to Fujitsu Microelectronics
Europe GmbH, or abuse or misapplication attributable to the customer or any other third party not
relating to Fujitsu Microelectronics Europe GmbH.
3. To the maximum extent permitted by applicable law Fujitsu Microelectronics Europe GmbH
disclaims all other warranties, whether expressed or implied, in particular, but not limited to,
warranties of merchantability and fitness for a particular purpose for which the Product is not
designated.
4. To the maximum extent permitted by applicable law, Fujitsu Microelectronics Europe GmbH´s
and its suppliers´ liability is restricted to intention and gross negligence.
NO LIABILITY FOR CONSEQUENTIAL DAMAGES
To the maximum extent permitted by applicable law, in no event shall Fujitsu
Microelectronics Europe GmbH and its suppliers be liable for any damages whatsoever
(including but without limitation, consequential and/or indirect damages for personal injury,
assets of substantial value, loss of profits, interruption of business operation, loss of
information, or any other monetary or pecuniary loss) arising from the use of the Product.
Should one of the above stipulations be or become invalid and/or unenforceable, the remaining
stipulations shall stay in full effect

MB2198 – Getting Started
Contents
MCU-AN-300217-E-V10 - 4 - © Fujitsu Microelectronics Europe GmbH
Contents
REVISION HISTORY.............................................................................................................. 2
WARRANTY AND DISCLAIMER........................................................................................... 3
CONTENTS ............................................................................................................................ 4
0 INTRODUCTION................................................................................................................ 6
1 GETTING STARTED ......................................................................................................... 7
1.1 Copying the “template” directory ............................................................................... 7
1.2 Adjusting the project files .......................................................................................... 7
1.3 Adjusting Linker Settings........................................................................................... 8
1.4 MCU change ............................................................................................................. 8
1.4.1 Choosing “Yes” ........................................................................................... 9
1.4.2 Choosing “No” ............................................................................................. 9
2 CREATING THE PROJECT ............................................................................................ 10
2.1 Opening the Softune Workbench............................................................................ 10
2.2 Entering the code .................................................................................................... 11
2.2.1 Main.c........................................................................................................ 11
2.2.2 Vectors.c ................................................................................................... 12
2.3 Compiling the Project.............................................................................................. 15
3 STARTING DEBUGGING................................................................................................ 17
3.1 Enter Debugging Mode ........................................................................................... 17
3.2 Executing the Program............................................................................................ 18
3.3 Ending the Debugging ............................................................................................ 18
4 CLOSING THE PROJECT............................................................................................... 19
4.1 Last steps................................................................................................................ 19
5 DEBUGGING ................................................................................................................... 20
5.1 Break Points............................................................................................................ 20
5.2 Mixed Display.......................................................................................................... 20
5.3 Monitoring Variables ............................................................................................... 20
5.4 Monitoring the CPU Registers................................................................................. 20
5.5 Monitoring Memory ................................................................................................. 21
6 MISCELLANEOUS .......................................................................................................... 22
6.1 View Mode of the Editor.......................................................................................... 22
6.2 Renaming the Abs-File............................................................................................ 22

MB2198 – Getting Started
Contents
©Fujitsu Microelectronics Europe GmbH - 5 - MCU-AN-300217-E-V10
6.3 Reference Settings for the LED-Project.................................................................. 23
7INSTALLING LAN ........................................................................................................... 26
7.1 Overview ................................................................................................................. 26
7.2 Configuring the LAN Adapter .................................................................................. 26
7.3 Configuring Operating System “WindowsTM”........................................................... 27
7.4 Checking the network-connection ........................................................................... 30
7.5 Troubleshooting ...................................................................................................... 30
7.6 Softune Workbench................................................................................................. 31

MB2198 – Getting Started
Introduction
MCU-AN-300217-E-V10 - 6 - © Fujitsu Microelectronics Europe GmbH
0Introduction
This document describes the first steps how to use the Emulator MB2198-01 together with
the Softune Workbench V30L33R08 or higher using an evaluation MCU with its Starter Kit.
For the hardware set up please refer to the Application Note mcu-an-300209-e-
16fx_mb2198_01_install, and the MB2198-01 and MB2198-500 Hardware Manuals.
To use this document, please install the corresponding MCU sample folders of your Fujitsu
Micros Documentation & Software DVD to your PC. Also, please read the notes on the DVD
inlet.
Note: This document describes exemplarily the proceeding with a MB96V300 MCU and a
FLASH-CAN-100P-340 Board.

MB2198 – Getting Started
Chapter 1 Getting Started
©Fujitsu Microelectronics Europe GmbH - 7 - MCU-AN-300217-E-V10
1Getting Started
PREPARING A NEW PROJECT
1.1 Copying the “template” directory
If you want to create a new project it is strongly recommended to use the “template project”
as a base of operations.
The “template project” includes all basic settings for a quick and safe start. It includes the
header and include files of the latest released version.
To start, copy the “template” directory with all its sub folders.
For example, we want to create a project, which toggles the LEDs on the FLASH-CAN-
100P-340 Starter Kit. For that, rename the copy of the “template” folder to “LED”.
1.2 Adjusting the project files
First click into the new “LED” folder and rename the following files:
Template.prj Led.prj
Template.wsp Led.wsp
Now open the file “Led.prj” with your favourite text editor.
You will find an entry like this:
[DirInfo]
PRJ=C:\Fujitsu\Sample\96340\template\
In the line “PRJ=” please edit the file path to your correct path. Of course, the “template” has
to be renamed to “led”.
Save and close the file. Attention: If you use MS Word, please be sure to save the file as a
normal text file, not as a word document!
Now open the file “Led.wsp” also with a text editor.
Do the following changes:
Rename to LED

MB2198 – Getting Started
Chapter 1 Getting Started
MCU-AN-300217-E-V10 - 8 - © Fujitsu Microelectronics Europe GmbH
[PrjFile]
Count=1
FILE-0=Template.prj FILE-0=Led.prj
ActivePrj=Template.prj ActivePrj=Led.prj
[SubPrj-Template.prj] [SubPrj-Led.prj]
Like in the Prj-File, you have to set your correct project folder path in the “WSP=” line:
[DirInfo]
WSP=C:\Fujitsu\Sample\96340\template\
Now save and close the file also as a normal text file.
The new project environment is now adjusted.
1.3 Adjusting Linker Settings
Note that especially the Linker settings in the category “Disposition/Connection” have to be
adjusted device specifically.
In the chapter 6.3 is a list of all settings for the MB96F348 device.
Please adjust RAM- and ROM-settings if you use a different device.
1.4 MCU change
In the project settings the MCU type can be adjusted:
Doing so, a dialog box will occur:

MB2198 – Getting Started
Chapter 1 Getting Started
©Fujitsu Microelectronics Europe GmbH - 9 - MCU-AN-300217-E-V10
1.4.1 Choosing “Yes”
By choosing “yes” the correct memory size and locations will be set to the linker settings. All
settings will be overwritten. Please note, that in this case the constant section is removed
and have to be entered again “by hand”.
1.4.2 Choosing “No”
By choosing “no”, the linker settings will not be affected. Please check in this case the
correct RAM and ROM size for the chosen MCU type.

MB2198 – Getting Started
Chapter 2 Creating the Project
MCU-AN-300217-E-V10 - 10 - © Fujitsu Microelectronics Europe GmbH
2Creating the Project
ENTERING THE SOURCE CODE
2.1 Opening the Softune Workbench
Now you can open the Softune Workbench. For installation of this tool please refer to the
Installation Guide Application Note MCU-AN-390209-E.
Choose the Menu File > Open. The following pop up window will occur:
Click “OK” for “Workspace/Project file”, and then browse to the file “Led.wsp”. Open it.
Then the following project structure will be displayed on
the left side of the Softune screen.
The top level is the Workspace itself: “Led”.
The next level contains the ABS-File of the Project,
which contains the compiled program.
The source files, their dependencies, and the debugger
settings follow.
For the moment the Source Files are in the point of
interest.
Open the Source File of the Main Program Main.c by
double clicking it in the window shown on the left.
Now a text editor window will open, which shows the
contents of Main.c. It will look like this:

MB2198 – Getting Started
Chapter 2 Creating the Project
©Fujitsu Microelectronics Europe GmbH - 11 - MCU-AN-300217-E-V10
The code only contains the chip specific header inclusion and in the main routine a frame for
the interrupt initialisation.
2.2 Entering the code
Assume that we want to have a “scrolling LED” on Port00 with a speed of 50 ms per LED.
Furthermore, we want to use an MCU Timer and an interrupt routine for the timing.
To do this, the files Main.c and vectors.c have to be edited.
2.2.1 Main.c
The following program example shows how to edit the main program source code for the
proposed purpose:
/* THIS SAMPLE CODE IS PROVIDED AS IS AND IS SUBJECT TO ALTERATIONS. FUJITSU */
/* MICROELECTRONICS ACCEPTS NO RESPONSIBILITY OR LIABILITY FOR ANY ERRORS OR */
/* ELIGIBILITY FOR ANY PURPOSES. */
/* (C) Fujitsu Microelectronics Europe GmbH */
/*------------------------------------------------------------------------
MAIN.C
- description
- See README.TXT for project description and disclaimer.
/*---------------------------------------------------------------------------*/
#include "mb96300.h"
unsigned char LED; /* Global byte for LED state */
/*-------------- Sub Routines -----------------------------------------------*/
void init_timer(void) /* initialisation function for 16-bit timer */

MB2198 – Getting Started
Chapter 2 Creating the Project
MCU-AN-300217-E-V10 - 12 - © Fujitsu Microelectronics Europe GmbH
{
TMRLR0 = 0x61A7; /* set reload value 25000 x 2us => 50ms */
TMCSR0 = 0x181b; /* prescaler 2,0us at 16 MHz */
}
void init_ports(void)
{
DDR00 = 0xFF; /* Set Port00 (LEDs) to Output */
PDR00 = 0x00; /* Turn off all LEDs */
}
/*-------------- Main Program -----------------------------------------------*/
void main(void)
{
init_timer();
init_ports();
LED = 0x01; /* Prepare LED byte for 1st LED */
InitIrqLevels();
__set_il(7); /* allow all levels */
__EI(); /* globally enable interrupts */
while(1); /* Let Interrupt handler do all things ... */
}
/*-------------- Interrupt Routine ------------------------------------------*/
__interrupt void Timer_IRQ_Handler(void)
{
TMCSR0_UF = 0; /* reset underflow interrupt request flag */
PDR00 = LED;
LED = LED * 2; /* "move" LED */
if (LED == 0) /* End reached? */
LED = 0x01; /* Start up again at position 0 */
}
The program first initialises the 16-Bit Reload Timer 0, then the LED-Port.
Then the program stops in an endless loop, but every 50 ms the Reload Timer sends an
interrupt request. The MCU then executes the Interrupt Service Routine, which clears the
Interrupt Request and sets a new “position” of the LED.
2.2.2 Vectors.c
Before executing the program, the interrupt definition has to be done. For that, open the file
“vectors.c” and edit the bold and italic entries of the following example:
/* THIS SAMPLE CODE IS PROVIDED AS IS AND IS SUBJECT TO ALTERATIONS. FUJITSU */
/* MICROELECTRONICS ACCEPTS NO RESPONSIBILITY OR LIABILITY FOR ANY ERRORS OR */
/* ELIGIBILITY FOR ANY PURPOSES. */
/* (C) Fujitsu Microelectronics Europe GmbH */
/*------------------------------------------------------------------------
VECTORS.C
- Interrupt level (priority) setting
- Interrupt vector definition
------------------------------------------------------------------------*/

MB2198 – Getting Started
Chapter 2 Creating the Project
©Fujitsu Microelectronics Europe GmbH - 13 - MCU-AN-300217-E-V10
#include "mb96300.h"
/*------------------------------------------------------------------------
InitIrqLevels()
This function pre-sets all interrupt control registers. It can be used
to set all interrupt priorities in static applications. If this file
contains assignments to dedicated resources, verify that the
appropriate controller is used.
NOTE: value 7 disables the interrupt and value 0 sets highest priority.
NOTE: Two resource interrupts always share one ICR register.
*/
#define MIN_ICR 12
#define MAX_ICR 88
#define DEFAULT_ILM_MASK 7
void InitIrqLevels(void)
{
int irq = MIN_ICR;
for(irq=MIN_ICR; irq<=MAX_ICR; irq++)
{
ICR = (irq << 8) | DEFAULT_ILM_MASK;
}
ICR = (51 << 8) | 2; /* IRQ51 = 16-Bit Reload Timer0
}
/*------------------------------------------------------------------------
Prototypes
Add your own prototypes here. Each vector definition needs is proto-
type. Either do it here or include a header file containing them.
*/
__interrupt void DefaultIRQHandler (void);
__interrupt void Timer_IRQ_Handler (void);
/*------------------------------------------------------------------------
Vector definiton
Use following statements to define vectors. All resource related
vectors are predefined. Remaining software interrupts can be added here
as well.
NOTE: If software interrupts 0 to 7 are defined here, this might
conflict with the reset vector in the start-up file.
*/
#pragma intvect DefaultIRQHandler 9 /* software interrupt 9 */
#pragma intvect DefaultIRQHandler 10 /* exception handler */
#pragma intvect DefaultIRQHandler 11 /* NMI */
#pragma intvect DefaultIRQHandler 12 /* Delayed Interrupt */
#pragma intvect DefaultIRQHandler 13 /* RC Timer */
#pragma intvect DefaultIRQHandler 14 /* MC Timer */
#pragma intvect DefaultIRQHandler 15 /* SC Timer */
#pragma intvect DefaultIRQHandler 16 /* reserved */
#pragma intvect DefaultIRQHandler 17 /* EXT0 */
#pragma intvect DefaultIRQHandler 18 /* EXT1 */
#pragma intvect DefaultIRQHandler 19 /* EXT2 */
#pragma intvect DefaultIRQHandler 20 /* EXT3 */
#pragma intvect DefaultIRQHandler 21 /* EXT4 */
#pragma intvect DefaultIRQHandler 22 /* EXT5 */
#pragma intvect DefaultIRQHandler 23 /* EXT6 */
#pragma intvect DefaultIRQHandler 24 /* EXT7 */
#pragma intvect DefaultIRQHandler 25 /* EXT8 */
#pragma intvect DefaultIRQHandler 26 /* EXT9 */

MB2198 – Getting Started
Chapter 2 Creating the Project
MCU-AN-300217-E-V10 - 14 - © Fujitsu Microelectronics Europe GmbH
#pragma intvect DefaultIRQHandler 27 /* EXT10 */
#pragma intvect DefaultIRQHandler 28 /* EXT11 */
#pragma intvect DefaultIRQHandler 29 /* EXT12 */
#pragma intvect DefaultIRQHandler 30 /* EXT13 */
#pragma intvect DefaultIRQHandler 31 /* EXT14 */
#pragma intvect DefaultIRQHandler 32 /* EXT15 */
#pragma intvect DefaultIRQHandler 33 /* CAN0 */
#pragma intvect DefaultIRQHandler 34 /* CAN1 */
#pragma intvect DefaultIRQHandler 35 /* PPG0 */
#pragma intvect DefaultIRQHandler 36 /* PPG1 */
#pragma intvect DefaultIRQHandler 37 /* PPG2 */
#pragma intvect DefaultIRQHandler 38 /* PPG3 */
#pragma intvect DefaultIRQHandler 39 /* PPG4 */
#pragma intvect DefaultIRQHandler 40 /* PPG5 */
#pragma intvect DefaultIRQHandler 41 /* PPG6 */
#pragma intvect DefaultIRQHandler 42 /* PPG7 */
#pragma intvect DefaultIRQHandler 43 /* PPG8 */
#pragma intvect DefaultIRQHandler 44 /* PPG9 */
#pragma intvect DefaultIRQHandler 45 /* PPG10 */
#pragma intvect DefaultIRQHandler 46 /* PPG11 */
#pragma intvect DefaultIRQHandler 47 /* PPG12 */
#pragma intvect DefaultIRQHandler 48 /* PPG13 */
#pragma intvect DefaultIRQHandler 49 /* PPG14 */
#pragma intvect DefaultIRQHandler 50 /* PPG15 */
#pragma intvect Timer_IRQ_Handler 51 /* RLT0 */
#pragma intvect DefaultIRQHandler 52 /* RLT1 */
#pragma intvect DefaultIRQHandler 53 /* RLT2 */
#pragma intvect DefaultIRQHandler 54 /* RLT3 */
#pragma intvect DefaultIRQHandler 55 /* PPGRLT */
#pragma intvect DefaultIRQHandler 56 /* ICU0 */
#pragma intvect DefaultIRQHandler 57 /* ICU1 */
#pragma intvect DefaultIRQHandler 58 /* ICU2 */
#pragma intvect DefaultIRQHandler 59 /* ICU3 */
#pragma intvect DefaultIRQHandler 60 /* ICU4 */
#pragma intvect DefaultIRQHandler 61 /* ICU5 */
#pragma intvect DefaultIRQHandler 62 /* ICU6 */
#pragma intvect DefaultIRQHandler 63 /* ICU7 */
#pragma intvect DefaultIRQHandler 64 /* OCU0 */
#pragma intvect DefaultIRQHandler 65 /* OCU1 */
#pragma intvect DefaultIRQHandler 66 /* OCU2 */
#pragma intvect DefaultIRQHandler 67 /* OCU3 */
#pragma intvect DefaultIRQHandler 68 /* OCU4 */
#pragma intvect DefaultIRQHandler 69 /* OCU5 */
#pragma intvect DefaultIRQHandler 70 /* OCU6 */
#pragma intvect DefaultIRQHandler 71 /* OCU7 */
#pragma intvect DefaultIRQHandler 72 /* FRT0 */
#pragma intvect DefaultIRQHandler 73 /* FRT1 */
#pragma intvect DefaultIRQHandler 74 /* IIC0 */
#pragma intvect DefaultIRQHandler 75 /* IIC1 */
#pragma intvect DefaultIRQHandler 76 /* ADC */
#pragma intvect DefaultIRQHandler 77 /* ALARM0 */
#pragma intvect DefaultIRQHandler 78 /* ALARM1 */
#pragma intvect DefaultIRQHandler 79 /* UART0 RX */
#pragma intvect DefaultIRQHandler 80 /* UART0 TX */
#pragma intvect DefaultIRQHandler 81 /* UART1 RX */
#pragma intvect DefaultIRQHandler 82 /* UART1 TX */
#pragma intvect DefaultIRQHandler 83 /* UART2 RX */
#pragma intvect DefaultIRQHandler 84 /* UART2 TX */
#pragma intvect DefaultIRQHandler 85 /* UART3 RX */
#pragma intvect DefaultIRQHandler 86 /* UART3 TX */
#pragma intvect DefaultIRQHandler 87 /* Main Flash memory interrupt */
#pragma intvect DefaultIRQHandler 88 /* Sat. Flash memory interrupt */
/*------------------------------------------------------------------------
DefaultIRQHandler()
This function is a placeholder for all vector definitions. Either use

MB2198 – Getting Started
Chapter 2 Creating the Project
©Fujitsu Microelectronics Europe GmbH - 15 - MCU-AN-300217-E-V10
your own placeholder or add necessary code here.
*/
__interrupt
void DefaultIRQHandler (void)
{
__DI(); /* disable interrupts */
while(1)
__wait_nop(); /* halt system */
}
The level for the interrupt in the example above is set to 2. Because the global level
threshold is set to 7 by the main program, you can choose any other number between 0 and
6.
Note that a prototype of your Interrupt Routine has to be defined as well as the vector of this
routine.
2.3 Compiling the Project
Because of the usage of the “Template Project”, you now can compile this example at this
moment. No other settings have to be done.
There are two ways to build to the whole project data. Either choose Project > Build or click
the button in the circle in the illustration below:
If no errors occur, the following message should be displayed in the lower window:
Now building...
------------------Configuration: Led.prj - Debug--------------------
Start.asm
Main.c
vectors.c
Mb96300.asm
Now linking...
<Your Path>\LED\ABS\Template.abs
Now starting load module converter...
<Your path>\LED\ABS\Template.mhx
------------------------------
No Error.
------------------------------
Assume you have forgotten to type the last ‘;’ in the “Main.c” file. Then the message will look
like the following:
Now building...
------------------Configuration: Led.prj - Debug--------------------
Start.asm
Main.c
*** <Your path>\led\src\main.c(48) E4062C:syntax error near `}'
vectors.c

MB2198 – Getting Started
Chapter 2 Creating the Project
MCU-AN-300217-E-V10 - 16 - © Fujitsu Microelectronics Europe GmbH
Mb96300.asm
------------------------------
Error detected.
------------------------------
To move quickly to the place where the error was found, simply double click the line with the
red error code. The error containing line will then be highlighted red in the code window.

MB2198 – Getting Started
Chapter 3 Starting Debugging
©Fujitsu Microelectronics Europe GmbH - 17 - MCU-AN-300217-E-V10
3 Starting Debugging
EXECUTING THE PROGRAM
3.1 Enter Debugging Mode
After a successful project built you can enter the debugger mode via three different
interfaces depending on your hardware set up:
•PC-COM-Port (RS232)
•LAN Interface
•USB Port
By double clicking on the correct connection type of the Debug dependency in the Project
window (*.sup-files), your PC will connect to the MB2198 Emulator and the Softune
Workbench will enter the Debugging Mode. Please refer to the Installation Guide Application
Note (MCU-AN-390209-E) for detailed information.
After a successful connection the Softune Workbench will look like this:
Note, that the interface has to be determined only once. Later you can choose the menu
Debug > Start debug to enter this mode.

MB2198 – Getting Started
Chapter 3 Starting Debugging
MCU-AN-300217-E-V10 - 18 - © Fujitsu Microelectronics Europe GmbH
3.2 Executing the Program
Now choose Debug > Run >Go,press F5 or click the button. Look at the Starter Kit. A
“scrolling” LED has to be flashing on the Board.
To halt the execution, choose Debug > Abort or click the button (Note that this button is
only active in execution mode). The emulator system now is being halted. The execution can
be continued by entering the “Go”-Mode again.
3.3 Ending the Debugging
To end the debugging just choose the menu Debug > End debug.

MB2198 – Getting Started
Chapter 4 Closing the Project
©Fujitsu Microelectronics Europe GmbH - 19 - MCU-AN-300217-E-V10
4Closing the Project
SAVING THE PROJECT DATA
4.1 Last steps
To save the project data choose File >Close Workspace.
Then the following pop up window will occur.
Click “Yes”. Afterwards you can close the Softune Workbench.
Note, that in the next start of the Workbench, your new LED-Project will occur in the menu
list File > Recent Workspace File.By simply clicking to “Led.wsp”, the whole project will
open again.

MB2198 – Getting Started
Chapter 5 Debugging
MCU-AN-300217-E-V10 - 20 - © Fujitsu Microelectronics Europe GmbH
5Debugging
A SHORT ASSORTMENT OF SOME DUBUGGER FUNCTIONS
5.1 Break Points
You can set break points in your compiled code to force the execution to stop at these
points.
Therefore enter the debugger mode. In general the code of the Start.asm file is displayed.
You can easy display the code of your Main.c file by double clicking it in the Workspace
window. Beside each command an arrow and a circle is displayed:
Clicking in the circle sets a break point. Depending on the selected break point type, a
differently coloured cross is shown in the circle. For the software break point (default), the
cross is blue, while there is a red cross in the circle for the hardware break point:
Clicking to this circle again releases the break point.
If you now start the execution, the CPU will halt on this break point. The actual line gets a
yellow background colour. Now you see the flag state of the status register just under the
project window.
The execution of course can be continued again by entering the run mode.
5.2 Mixed Display
Sometimes it is useful to see the compiled code together with the C source.
To display this enter the debugger mode, open the file to observe and click on the right
mouse button just over the code window. A pop up window with the entry “Mix display” has
to be selected. The code window now will look like this:
Note that now the break points can be set exactly to the regarding CPU Op Code.
5.3 Monitoring Variables
To watch the content of a variable during stopped execution, choose View > Watch. A small
new window will open. Go with the mouse pointer into it and press the right mouse button.
Then choose Set… . Enter now the name of the variable. It will then be displayed with its
name and its value in the Watch-Window.
To change the radix notation of the value, select the variable and click on the right mouse
button. The menu content Radix offers now display in Binary, Octal, Decimal, and
Hexadecimal formats.
5.4 Monitoring the CPU Registers
To monitor the CPU registers, choose View >Register. A small window with all CPU
registers and their contents will open then.