Renesas RL78 Series Installation and operating instructions

Application Note
R20AN0632EJ0100 Rev.1.00 Page
1
of 23
Jul.20.21
RL78 Debugging Functions Using the Serial Port
Introduction
This application note describes how to use the RL78 debugging functions using the serial port.
Target Device
RL78
Contents
1. Overview .................................................................................................................................4
1.1 Overview of COM Port debugging...........................................................................................................4
1.2 Applicable devices...................................................................................................................................4
2. User system design.................................................................................................................5
2.1 Example of recommended connection between USB-to-serial conversion adapter and MCU...............5
2.1.1 General RL78 family connectivity..........................................................................................................5
2.2 Things to keep in mind when connecting................................................................................................6
2.2.1 RESET# pin...........................................................................................................................................6
2.2.2 TOOL0/TOOLTxD/TOOLRxD pins........................................................................................................8
2.2.3 GND.......................................................................................................................................................9
2.2.4 Power supply voltage ............................................................................................................................9
3. Usage notes..........................................................................................................................10
3.1 Power on/off ..........................................................................................................................................10
3.1.1 Power supply sequence ......................................................................................................................10
3.2 MCU resources that are used ...............................................................................................................11
3.2.1 Securing the debug monitor area........................................................................................................12
3.2.2 Securing the stack area for debugging ...............................................................................................13
3.2.3 Setting the on-chip debug option byte area ........................................................................................14
3.2.4 Setting the security ID .........................................................................................................................15
3.3 Reset .....................................................................................................................................................16
3.3.1 Behavior after reset.............................................................................................................................16
3.3.2 Registers after reset............................................................................................................................16
3.3.3 Pin reset during break .........................................................................................................................16
3.4 Flash memory........................................................................................................................................16
3.4.1 Debugging notes for self-programming...............................................................................................16
3.4.2 Voltage at which flash memory cannot be written and operation in flash operation mode.................17
3.5 GDIDIS function.....................................................................................................................................18
3.6 MCUs that are used in debugging.........................................................................................................18
3.6.1 Use in mass-production products........................................................................................................18

RL78 RL78 Debugging Functions Using the Serial Port
R20AN0632EJ0100 Rev.1.00 Page
2
of 23
Jul.20.21
3.6.2 Standalone operation check................................................................................................................18
3.7 Final evaluation of user program...........................................................................................................18
3.8 Debugging functions..............................................................................................................................19
3.8.1 “Go to Here” function ...........................................................................................................................19
3.8.2 Debugging in standby mode................................................................................................................19
3.8.3 Pseudo RRM/DMM functions..............................................................................................................20
3.8.4 Start/Stop functions.............................................................................................................................20
3.8.5 Emulation of flash memory CRC accumulator function ......................................................................20
3.8.6 Notes on the break function ................................................................................................................21
3.8.7 Setting and deleting events during user program execution...............................................................21
3.8.8 Trace function......................................................................................................................................21
3.8.9 Precautions when using flash read protection ....................................................................................21
3.9 How to improve debug performance.....................................................................................................22
Revision History............................................................................................................................23

RL78 RL78 Debugging Functions Using the Serial Port
R20AN0632EJ0100 Rev.1.00 Page
3
of 23
Jul.20.21
Definitions of Terms
The terms used in this document are defined and used as follows.
Host machine
A personal computer for controlling the emulator.
User system
The customer's application system using the MCU to be debugged.
User program
The application program to be debugged.
Flash writing software
In this document, this term refers to the Renesas Flash Programmer.
Meaning of “#” at the end of the pin name (signal name)
The # at the end of a pin name (signal name) indicates that it is a “Low” active pin (signal)
(example: RESET#).

RL78 RL78 Debugging Functions Using the Serial Port
R20AN0632EJ0100 Rev.1.00 Page
4
of 23
Jul.20.21
1. Overview
This guide presents the information you should be aware of when debugging RL78 devices with COM
Port debugging using a commercial USB-to-serial conversion adapter.
1.1 Overview of COM Port debugging
With the COM Port debugging system, you perform debugging by connecting to the target board from a
USB port of the host machine via a USB-to-serial conversion adapter instead of an emulator such as E2.
The adapter is recognized as the COM Port of the host machine when communicating with the target
device using the serial port.
It enables debugging of target devices using a commercially available USB-to-serial conversion adapter.
1.2 Applicable devices
Devices in the RL78 family that support COM Port debugging. Check the device's manual to see if it is
supported.
Table 1-1 List of debugging functions
Item
Support
Content
COM Port
E2 Lite
Reference/change memory during program execution
Pseudo real-time RAM monitor
(RRM)
Y*1
Y
CPU occupied during memory reference
Dynamic Memory Modification (DMM)
Y*1
Y
CPU occupied during memory changes
Event function
Up to
2points
Up to
2points
Can be used for hardware breaks
(or trace function*2)
Break
functions
Software breaks
Y
Y
Up to 2000 points
Hardware breaks
Y
Y
Execution address or data access
Forced breaks
Y
Y
-
Trace
functions
Acquired information
Y
Y
Branch source PC information
Start event
Y
Y
User program execution start, event start
End event
Y
Y
User program stop, event end, trace full
Execution time measurement function
N
Y
-
Hot plugin
N
Y
-
Coverage function
N
N
-
Y: supported, N: not supported
*1 RRM/DMM is possible on a per-variable basis, but it is recommended that the memory panel display
should be 1 or 2 lines and the update interval should be 5000 msec or more. If too much is displayed,
the debugger may become unresponsive.
*2 Only for devices with a trace function

RL78 RL78 Debugging Functions Using the Serial Port
R20AN0632EJ0100 Rev.1.00 Page
5
of 23
Jul.20.21
2. User system design
2.1 Example of recommended connection between USB-to-serial conversion
adapter and MCU
The recommended connection between the USB-to-serial conversion adapter and the MCU when using
COM Port debugging is shown below. For details on the processing of each signal line, refer to 2.2
Things to keep in mind when connecting.
2.1.1 General RL78 family connectivity
An example of connecting the USB-to-serial conversion adapter to the RL78 family is shown in Figure
2.1.
*CTS# is unused. Perform pin processing according to the specifications of the
serial conversion adapter you are using.
Figure 2.1 Example of connecting the USB-to-serial conversion adapter to the RL78 family

RL78 RL78 Debugging Functions Using the Serial Port
R20AN0632EJ0100 Rev.1.00 Page
6
of 23
Jul.20.21
2.2 Things to keep in mind when connecting
The pattern length between the USB-to-serial conversion adapter and the MCU should be as short as
possible (50 mm or less is recommended). Also, do not route signal lines on the board other than
between the USB-to-serial conversion adapter and the MCU.
For details on pin processing when COM Port debugging is not used, refer to the user's manual
(hardware edition) of the relevant MCU.
2.2.1 RESET# pin
The RESET# pin is used for resetting to the device.
An example of a connection to the RESET# pin area is shown in Figure 2.2.
When performing flash writing from the flash writing software, ensure that the reset signal on the user
system does not collide with the reset signal from the COM Port debugging.
Note that COM Port debugging does not support the RESET# pin masking function.
In addition, configure the debugger properties to match the pin (DTR/RTS) that controls the RESET# pin.
By default, the debugger/flash writing software uses DTR, so if you want to use RTS, be sure to change
the property settings.
The recommended connection is the DTR connection shown in Figure 2.2. If you are using a USB-to-
serial conversion adapter without DTR, use the RTS connection in Figure 2.3.
When using Printf debugging in the Arduino development environment, refer to Figure 2.4 when
connecting. Since RTS is fixed at LOW and the buffer output is disabled, RESET is pulled up externally.
Figure 2.2 RESET# pin connection example
(DTR connection)
Figure 2.3 RESET# pin connection example
(RTS connection)

RL78 RL78 Debugging Functions Using the Serial Port
R20AN0632EJ0100 Rev.1.00 Page
7
of 23
Jul.20.21
* The reference type name of the buffer connected to
DTR# is “74LVC1G126”.
OE control is as follows.
H: Enable output
L: Disable
Figure 2.4 RESET# pin connection example (with
buffer)
The following notes pertain to Figure 2.2, Figure 2.3, and Figure 2.4.
•Do not insert capacitors, additional series resistors, filters, etc. into the signal line as it may prevent normal
communication.
•The circuit and resistance values listed are recommended values and are not guaranteed.
Determine the circuit design and resistance values by taking into account the specifications and noise of the
target device.
•The reset circuit should be Nch.O.D output, and the pull-up in the reset circuit should be at least 10 kΩ or no pull-
up.

RL78 RL78 Debugging Functions Using the Serial Port
R20AN0632EJ0100 Rev.1.00 Page
8
of 23
Jul.20.21
2.2.2 TOOL0/TOOLTxD/TOOLRxD pins
The TOOL0/TOOLTxD/TOOLRxD pins are occupied and used when COM Port debugging is used.
Pin functions that are multiplexed to these pins cannot be used.
In addition, COM Port debugging uses the TOOLTxD/TOOLRxD pins to send and receive data to and
from the target device. Since mode entry is done using TOOL0, TOOL0 must be connected via the
TOOLRxD pin and resistor. No pull-up resistor is necessary.
When using COM Port debugging, do not set the port mode register dualed to TOOLRxD (PM1.1 when
TOOLRxD is a dual-use pin for P11) to 0 (output). If you do, the TOOLRxD pin, which is used in COM
Port debugging, will be in output mode and you will not be able to debug.
Figure 2.5 TOOL0/TOOLTxD/TOOLRxD pin connection example
Do not insert capacitors, additional series resistors, filters, etc. into the signal line as it may prevent normal
communication.

RL78 RL78 Debugging Functions Using the Serial Port
R20AN0632EJ0100 Rev.1.00 Page
9
of 23
Jul.20.21
2.2.3 GND
The GND of the USB-to-serial conversion adapter must be the same GND as the VSS pin of the MCU.
2.2.4 Power supply voltage
Use COM Port debugging at 1.8 V or higher, and stay within the operating voltage range of the USB-to-
serial conversion adapter. For debugging below 1.8 V, use E2.

RL78 RL78 Debugging Functions Using the Serial Port
R20AN0632EJ0100 Rev.1.00 Page
10
of 23
Jul.20.21
3. Usage notes
3.1 Power on/off
Follow the steps below to power the user system on and off.
3.1.1 Power supply sequence
[At the start of use]
(1) Confirm power is off
Make sure the user system is powered off.
(2) Connect user system
Connect the user system to the host machine.
(3) Start debugger or flash writing software
Start the debugger or flash writing software.
*If you are using VBUS supply as the system power supply, go to step (5).
(4) Power up user system
Turn on the power to the user system.
(5) Connect to user system from debugger or flash writing software through COM Port
The connection method varies depending on the software.
[At the end of use]
(1) Disconnect user system from debugger or flash writing software through COM Port
The disconnection method varies depending on the software.
*If you are using VBUS supply as the system power supply, go to step (3).
(2) Power off user system
Turn off the power to the user system.
(3) Exit debugger or flash writing software
Exit the debugger or flash writing software.
(4) Detach user system
Detach the user system from the host machine.

RL78 RL78 Debugging Functions Using the Serial Port
R20AN0632EJ0100 Rev.1.00 Page
11
of 23
Jul.20.21
3.2 MCU resources that are used
Figure 3.1 shows the areas occupied during COM Port debugging.
These areas (shaded sections) show the space used for debugging. Do not make changes to these
areas, for example by placing user programs or data there. If you make changes there, COM Port
debugging will lose control over execution.
However, when “Disable flash rewriting” is selected in the debugger properties, the internal ROM area
shown in Figure 3.1 is not used (only the internal RAM area is used).
For details about selecting “Disable flash rewriting” in the debugger properties, refer to 3.2.3
Setting the on-chip debug option byte area and 3.4.2
Voltage at which flash memory cannot be written and operation in flash operation mode.
Figure 3.1 MCU resources that are used
*1 The reset vector area is used by the COM Port debugging program during COM Port debugging.
If you make changes there, COM Port debugging will lose control over execution.

RL78 RL78 Debugging Functions Using the Serial Port
R20AN0632EJ0100 Rev.1.00 Page
12
of 23
Jul.20.21
3.2.1 Securing the debug monitor area
The debug monitor area contains the debug monitor program.
The monitor program performs initialization of the debugging communication interface, run/break
processing of the CPU, etc. This area must not be overwritten by the user program.
You must ensure that no user programs or data are placed in the 23-byte area near the on-chip debug
option byte area and the area up to 768 bytes before the internal ROM end address. *1
The reset vector is changed to the address where the monitor program is placed.
[How to secure areas]
If you are not using this area in the user program, you do not necessarily need to secure it. However, in
order to avoid trouble when starting the debugger, it is recommended to secure this area in advance, for
example by using the build tool.
*1 The area will vary depending on whether you are using the pseudo RRM/DMM function and/or the Start/Stop
function.
Example (internal ROM 256KB device)
Using neither the pseudo RRM/DMM function nor the Start/Stop function
Monitor program placed at 0x3FF00 to 0x3FFFF (256 bytes)
Using either the pseudo RRM/DMM function or the Start/Stop function
Monitor program placed at 0x3FE00 to 0x3FFFF (512 bytes)
Using both the pseudo RRM/DMM function and the Start/Stop function
Monitor program placed at 0x3FD00 to 0x3FFFF (768 bytes)

RL78 RL78 Debugging Functions Using the Serial Port
R20AN0632EJ0100 Rev.1.00 Page
13
of 23
Jul.20.21
3.2.2 Securing the stack area for debugging
Use 4 bytes as the stack area for debugging. Since this area is located directly under the stack area, the
address of the debug stack area varies as the stack increases or decreases. In other words, it consumes
4 bytes extra for the stack area consumed by the user program. Be careful not to let the debug stack area
extend beyond the internal RAM. *1
When using the Start/Stop function, the debug stack area is 8 bytes.
Figure 3.2 shows an example of the stack area increasing when the internal RAM start address is
0xFCF00.
Figure 3.2 Overview of address variation in the debugging stack area
*1 For self-programming, use 12 bytes as the stack area for debugging.
Refer to the self-programming manual for how to secure the stack for self-programming.
The Start/Stop function cannot be used during self-programming.

RL78 RL78 Debugging Functions Using the Serial Port
R20AN0632EJ0100 Rev.1.00 Page
14
of 23
Jul.20.21
3.2.3 Setting the on-chip debug option byte area
This is a security setting that prevents a third party from reading the contents of the flash memory.
Refer to the user's manual for your specific device to see the values that can be set.
If connecting the on-chip debugging emulator, it is necessary to set the security ID.
[Setting procedures] *1
There are two ways to set the on-chip debug option byte area.
Make sure that you perform the setting in one of these ways.
(a) Embed the on-chip debug option byte at address 0xC3 of the user program
(b) Set it with the build tool
For details on this setting method, refer to the build tool's user's manual.
*1 When the value of the on-chip debug option byte is set to disable on-chip debugging (OCDENSET = 0) on
the device, if you select “Disable flash rewriting” in the debugger properties, you will not be able to start the
debugger. If you select “Allow flash rewriting”, you will be able to start the debugger, but the flash memory
will be erased when the debugger starts.
Also, note that it may not be possible to start the debugger depending on the LVD setting of option byte 0xC1.

RL78 RL78 Debugging Functions Using the Serial Port
R20AN0632EJ0100 Rev.1.00 Page
15
of 23
Jul.20.21
3.2.4 Setting the security ID
This setting prevents the contents of memory from being read by a third party through the debug
interface. The security ID is embedded in the internal flash memory at address 0xC4 to 0xCD.
The debugger starts only when the security ID set by the debugger matches the memory contents at
address 0xC4 to 0xCD. If there is not a match, instead of starting, the behavior of the debugger depends
on the settings of the on-chip debugging option byte area (see the user's manual hardware for the
specific device).
If you forget the security ID, erase the flash memory and set the security ID again.
There are two ways to set the security ID for the internal flash memory.
If (a) and (b) are set at the same time, the setting of (b) takes precedence.
(a) Embed the security ID at address 0xC4 to 0xCD in the user program
You can embed the security ID at address 0xC4 to 0xCD in the user program.
If you embed the security ID shown in Table 3-1, the security ID set in the debugger would be
“0123456789ABCDEF1234” (the letters can be either uppercase or lowercase). *1 *2
(b) Set it with the build tool
For details on this setting method, refer to the build tool's user's manual.
Table 3-1 Security ID setting example
Address
Setting
0x000C4
0x01
0x000C5
0x23
0x000C6
0x45
0x000C7
0x67
0x000C8
0x89
0x000C9
0xAB
0x000CA
0xCD
0x000CB
0xEF
0x000CC
0x12
0x000CD
0x34
*1 If you want to connect the debugger to a device that has a security ID, you must enter the security ID in
the debugger. For more information about authentication, check the user's manual for the debugger that
you are using.
*2 The setting value “0xFFFFFFFFFFFFFFFFFFFF” (all bytes “0xFF”) is prohibited.

RL78 RL78 Debugging Functions Using the Serial Port
R20AN0632EJ0100 Rev.1.00 Page
16
of 23
Jul.20.21
3.3 Reset
3.3.1 Behavior after reset
After an external pin reset or an internal reset, the monitor program performs debugging initialization
processing. Therefore, the time from the reset occurrence to the execution of the user program differs
from the actual device operation. It takes longer to execute the user program when flash rewriting is
allowed in the debugging tool than when flash rewriting is disabled (max 100 ms).
3.3.2 Registers after reset
During COM Port debugging, the SP value after reset is as follows.
•If the device has at least 768 bytes of internal RAM: FC00h
•The device has less than 768 bytes of internal RAM: Internal RAM start address+0x20
Example: RAM start address 0xFEF00: 0xEF20
3.3.3 Pin reset during break
During COM Port debugging, if you perform a pin reset during a break, the debugger becomes
unresponsive. Do not perform a pin reset during a break.
3.4 Flash memory
3.4.1 Debugging notes for self-programming
(1) Non-rewritable areas in self-programming
If you rewrite the area that contains the debug monitor by flash self-programming, COM Port
debugging will lose control over execution. This also applies when boot swap is performed.
(2) Break during self-programming
If you want to set a break other than forced break during self-programming, enable the debugger
property “Self-programming”.
Forced breaks during self-programming can cause COM Port debugging to lose control over
execution.
(3) Pseudo RRM/DMM function during self-programming
The pseudo RRM/DMM function is not available while the user program is running the flash self-
programming library or data flash library.
(4) Watch panel display during self-programming
While the user program is running the flash self-programming library or data flash library, memory
cannot be accessed by the RAM monitor function. Therefore, the value of a variable registered in
the watch panel is displayed as “?”.

RL78 RL78 Debugging Functions Using the Serial Port
R20AN0632EJ0100 Rev.1.00 Page
17
of 23
Jul.20.21
3.4.2 Voltage at which flash memory cannot be written and operation in flash operation
mode
If the following debugger operations, which involve rewriting the flash memory, are executed at a
voltage at which flash memory cannot be written or erased, or when flash rewriting is disabled in the
debugger properties, the debugger raises an error and the operation is ignored.
•Write to internal flash memory
•Set/cancel software breakpoint
•Start execution from the location where the software breakpoint is set
•Step execution at the location where the software breakpoint is set
•Step-over execution, return-out execution
•Execute to cursor position
•Set/change/cancel hardware break
•Switch internal reset masking
•Switch peripheral break
In addition, the operating frequency range and operating voltage range are set in the flash operation
mode. If the operating frequency range or operating voltage range is outside the range, normal operation
may fail.

RL78 RL78 Debugging Functions Using the Serial Port
R20AN0632EJ0100 Rev.1.00 Page
18
of 23
Jul.20.21
3.5 GDIDIS function
The Global Digital Input Disable Register (GDIDIS) prevents through current in the input buffer when
EVDD = 0 V. During COM Port debugging, do not set GDIDIS=1 (input buffer input prohibited) because
communication (TOOLTxD/TOOLRxD pins) will not be possible.
3.6 MCUs that are used in debugging
3.6.1 Use in mass-production products
The MCUs that are used in COM Port debugging are placed under stress by repeated programming of
flash memory during emulation. MCUs that are used in debugging should not be used in mass-production
for end users.
Furthermore, since a program for COM Port debugging is written to the MCU during debugging, do not
save the contents of the flash memory of the MCU used in debugging for use as product ROM data.
3.6.2 Standalone operation check
After downloading the load module file to the device for on-chip debugging by COM Port debugging,
do not disconnect the USB interface cable to check the operation of the device alone. After debugging,
the device contains a processing program for on-chip debugging, which is different from the program
used in actual operation.
3.7 Final evaluation of user program
Before entering the mass production phase, be sure to perform a final evaluation of the program
written to a flash ROM by the Renesas Flash Programmer flash writing software or other flash
programmer on a standalone basis without using COM Port debugging.

RL78 RL78 Debugging Functions Using the Serial Port
R20AN0632EJ0100 Rev.1.00 Page
19
of 23
Jul.20.21
3.8 Debugging functions
Stepped execution function
(1) SFR values during stepped execution
The value of some SFRs (special function registers) might remain unchanged when stepping into
code. If the value of the SFRs does not change while stepping in, operate the microcontroller by
executing the instructions continuously instead of executing them in steps.
Step into (stepped execution): Instructions in the user-created program are executed one by one.
Continuous execution: The user-created program is executed from the current PC.
(2) Division operation step into (for a device equipped with a multiplier and divider/multiply-
accumulator)
When the instruction which sets bit 0 (DIVST) of the multiplication/division control register (MDUC)
to 1 is stepped, the division operation does not finish. However, there is no problem with the
stepped execution through the division operation at the C source level.
(3) Illegal memory access detection function
When the function to detect illegal memory accesses is enabled (IAWCTL.7 = 1), no internal reset
will occur if you have done the following:
•Performed stepped execution for an instruction that will generate an illegal memory access.
•Set a software breakpoint at an instruction that will generate an illegal memory access and then
executed a program from that point.
(4) RAM guard function
When the RAM guard function is enabled (except when IAWCTL.5,4 = 0,0), the guarded RAM can
be overwritten when stepped execution to overwrite the guarded RAM area is performed.
The RAM is also rewritten if the guarded RAM area is rewritten from the memory panel during a
break.
3.8.1 “Go to Here” function
If “Go to Here” is selected, the software breakpoints and event breakpoints that have been set so far will
be temporarily invalidated.
3.8.2 Debugging in standby mode
A break is a CPU interrupt. Therefore, if a break is generated by the following debugging functions,
standby mode is canceled.
•Forced break
•Stepped execution of the standby instruction (stops the user program after execution of the
instruction)
•Short break generated by the pseudo RRM function
•Short break generated by the pseudo DMM function
•Short break generated by setting a breakpoint while executing the user program

RL78 RL78 Debugging Functions Using the Serial Port
R20AN0632EJ0100 Rev.1.00 Page
20
of 23
Jul.20.21
3.8.3 Pseudo RRM/DMM functions
Note the following points when using the pseudo RRM function or the pseudo DMM function.
•Standby mode (HALT or STOP) may be canceled during monitoring.
•The pseudo RRM/DMM function does not work while the CPU operating clock is stopped.
•When there is large number of monitoring points, the responsiveness of the debugger slows.
•Monitoring by using a watch panel instead of a memory panel reduces the impact on debugger
responsiveness.
•The pseudo RRM/DMM function does not work while running on the sub-clock.
•Even when the RAM guard function is enabled, memory contents can be rewritten by the pseudo
DMM function.
3.8.4 Start/Stop functions
Note the following points if you intend to use this functionality.
•Even if the start/stop function writes new values to the CPU registers, the states of the registers are
restored when the function ends.
•Stepped execution of the start/stop functions is not possible. However, the functions work when
RUN is performed internally, such as when the CALL instruction is stepped over.
•Breaks cannot be used in Start/Stop functions.
•When execution of a user program starts from an address where a software breakpoint has been
set, the instruction at the breakpoint is executed before the start function is run.
The order of execution is (a), (b), and (c) below.
(a) Stepped execution (due to the break) of the instruction where the breakpoint is set
(b) Running the start function
(c) Executing instructions of the user program following the address where the breakpoint is set
(continuous execution)
•When thestart function is enabled and the user program is executed froman addressat which an event
break condition is set, the condition can only be satisfied after the start function has been executed.
Step-execute the instruction to start the user program from the next address after that at which an
event break condition is set, or disable the start function if you do not require it.
•If you intend to use a stop function specified by a Start/Stop function, specify a subroutine which
returns normally. If the specified subroutine does not return normally, the emulator debugger will
lose control over execution. To restore control, issue a reset of processing from the debugger.
3.8.5 Emulation of flash memory CRC accumulator function
(1) High-speed CRC (code flash: all areas)
In on-chip debugging, the CRC calculation result may differ from the actual result because the
monitor program is in place and the reset vector is rewritten. Confirm the operation of the high-
speed CRC on the device alone without the debugger.
(2) General-purpose CRC (code flash: specified area)
In on-chip debugging, the CRC calculation result may differ from the actual result when one of the
following areas is specified as the CRC calculation target area because the monitor program is in
place and the reset vector is rewritten.
•Reset vector area
•Debug monitor area
•On-chip debug option byte area
•Areas where software breaks are specified