• After the Monitor Program is written to the MCU and the Monitor Program communicates with the Debugger, the user program can be debugged. Use RS-232C for communication between the Debugger and the Monitor Program.
  • The Monitor Program is automatically written to the MCU when the Debugger is started up. Therefore, there is no need to write the Monitor Program to the MCU using a flash programmer.
  • You can debug by the same pin handling as Standard Serial I/O Mode 2 for the flash programmer.
  • Initialize (erase) the user program area using a flash programmer before using the Monitor Program.

System Configuration


  • PC with Serial Port
  • Communication Cable
  • Target Board, Power Supply
  • Debugger

* You can download the Debugger from "Downloads" button.


Process flow



Operating Environment

The operating environment depends on your debugger.

M16C R8C FoUSB/UART debugger (High-performance Embedded Workshop Version)

PC IBM PC/AT or compatible PC with Intel Pentium III 600MHz or higher
OS Windows XP, Windows 2000, Windows ME, Windows 98 SE (98)
Memory 128MB or higher
Interface 9-pin D-SUB Serial Interface


M16C R8C FoUSB/UART debugger (KD30 Version)

PC IBM PC/AT or compatible PC with Intel DX4 100MHz/Pentium II 75MHz or higher
OS Windows XP, Windows 2000, Windows ME, Windows 98 SE (98), Windows 95
Memory 16MB or higher
Interface 9-pin D-SUB Serial Interface



ID Check Function

The ID check function, which provides protection against accidentally erasing the user program, is supported except in R8C/10 and R8C/11 Groups with Boot Program Version 0.90. This function checks the addresses in which the ID code is stored when the Debugger is started up, and executes the debugging program (erase internal ROM and download Monitor Program) only when the ID code is "all FFh".
When the ID code is not "all FFh", the Debugger displays a time-out error and KD30 will not operate (internal ROM will not be erased and Monitor Program will not be downloaded).


ID Code at Debug Completion

[R8C/10 and R8C/11 Groups Boot Program Ver.0.90]
The Monitor Program sets ID3, ID4, and ID6 to "00h". All other codes are set according to the ID code of the user program. For example, if the user program ID code is set to "all FFh", the codes will be as follows.
Therefore, we recommend setting the user program ID code to "all 00h" .


ID1: FFh (address 0FFDFh)
ID2: FFh (address 0FFE3h)
ID3: 00h (address 0FFEBh)
ID4: 00h (address 0FFEFh)
ID5: FFh (address 0FFF3h)
ID6: 00h (address 0FFF7h)
ID7: FFh (address 0FFFBh)


[R8C/10 and R8C/11 Groups Boot Program Ver.1.00 or later and Other Groups of  R8C Family]
The Monitor Program sets ID1 through ID7 to "all FFh". Therefore, regardless of what the ID code is set to in the user program, this will not be reflected in the final outcome. Accordingly, after debug is completed, the ID code will always be "all FFh".


Upgrade Information

Debugger (High-performance Embedded Workshop version / KD version)

<<KD debugger does not have a plan to revise any more.>>

* Target product : M32C M16C UART Monitor Program | R8C UART Monitor Program


High-performance Embedded Workshop version

[Latest Version]

  • Released Date : 1. July, 2007
  • Software name :
    • M16C R8C FoUSB/UART Debugger
    • M32C FoUSB/UART Debugger
  • Version : V.1.03 Release 00
  • New feature(s)
    • Comes with High-performance Embedded Workshop V.4.03.00
    • [Disconnect] function
    • Representational function of instruction format specifier in disassembly language
    • Assignment function to bit-field members
    • Some more improvements
    For details, see ToolNews.


[How to upgrade to the latest version]
Download free updates from the "Download site". Upgradable from any previous versions.


[How to install]
Each emulator and monitor debugger is not bundled with High-performance Embedded Workshop. Please download from the "Download site" in the left navigation on this page. Installing this emulator debugger add High-performance Embedded Workshop environment a debugging function.


KD version

[Latest Version]

Released Date

9. June, 2004

25. August, 2004

28. May, 1999

Software name KD30
(M16C R8C FoUSB/UART Debugger)
(M32C FoUSB/UART Debugger)
(M32C UART Debugger)
Version Ver.4.10 Release 1 Ver.3.30 Release 1 Ver.1.00 Release 1

* : KD308 is a M16C/80 Group debugger for "M32C M16C UART Monitor Program". This product has no plan to support High-performance Embedded Workshop in the future.


[How to upgrade to the latest version]
Download free updates from the each "Download site".


M16C R8C FoUSB/UART debugger (KD30 Version)

Family Series Group Part No.
R8C R8C/1x R8C/10 R5F21102
R8C/11 R5F21112
R8C/12 R5F21122
R8C/13 R5F21132
R8C/14 R5F21142
R8C/15 R5F21152
R8C/16 R5F21162
R8C/17 R5F21172

Below you will find information to support the development of your application.


Information supporting development tools

Title Description
My Renesas Create a My Renesas account to use our tool download services,
receive e-newsletter/update notifications, and take advantage of our other services.
e-learning Information for studying and learning about microcontrollers and microprocessors.
FAQ Frequently asked questions and useful hints for development.
Forum A forum and community site to share technical information,
questions and opinions with others who use Renesas MCU's.
Tool News Tool release information and other important information.
Operating Environment Information on system requirements and operating environment for the latest
version of tools.
Tool Environmental Information Information on RoHS compliance of tools.
Info on Discontinued Products A list of Renesas software and tools that have been discontinued and
are no longer being offered for new projects.