Renesas Flash Programmer V3.08 User Manual
lash memory programming software
User’s Manual
All information contained in these materials, including products and product specifications,
website (http://www.renesas.com).
Rev. 2.00 Apr 2021
www.renesas.com
[
Renesas Flash Programmer V3.08
F
represents information on the product at the time of publication and is subject to change by
Renesas Electronics Corp. without notice. Please review the latest information published by
Renesas Electronics Corp. through various means, including the Renesas Electronics Corp.
© 2021 Renesas Electronics Corporation. All rights reserved.
Corporate Headquarters
Contact information
Trademarks
Notice
1. Descriptions of circuits, software and other related information in this document are provided only to illustrate the operation of semiconductor products
and application examples. You are fully responsible for the incorporation or any other use of the circuits, software, and information in the design of your
product or system. Renesas Electronics disclaims any and all liability for any losses and damages incurred by you or third parties arising from the use of
these circuits, software, or information.
2. Renesas Electronics hereby expressly disclaims any warranties against and liability for infringement or any other claims involving patents, copyrights, or
other intellectual property rights of third parties, by or arising from the use of Renesas Electronics products or technical information described in this
document, including but not limited to, the product data, drawings, charts, programs, algorithms, and application examples.
3. No license, express, implied or otherwise, is granted hereby under any patents, copyrights or other intellectual property rights of Renesas Electronics or
others.
4. You shall be responsible for determining what licenses are required from any third parties, and obtaining such licenses for the lawful import, export,
manufacture, sales, utilization, distribution or other disposal of any products incorporating Renesas Electronics products, if required.
5. You shall not alter, modify, copy, or reverse engineer any Renesas Electronics product, whether in whole or in part. Renesas Electronics disclaims any
and all liability for any losses or damages incurred by you or third parties arising from such alteration, modification, copying or reverse engineering.
6. Renesas Electronics products are classified according to the following two quality grades: “Standard” and “High Quality”. The intended applications for
each Renesas Electronics product depends on the product’s quality grade, as indicated below.
"Standard": Computers; office equipment; communications equipment; test and measurement equipment; audio and visual equipment; home
"High Quality": Transportation equipment (automobiles, trains, ships, etc.); traffic control (traffic lights); large-scale communication equipment; key
Unless expressly designated as a high reliability product or a product for harsh environments in a Renesas Electronics data sheet or other Renesas
Electronics document, Renesas Electronics products are not intended or authorized for use in products or systems that may pose a direct threat to
human life or bodily injury (artificial life support devices or systems; surgical implantations; etc.), or may cause serious property damage (space system;
undersea repeaters; nuclear power control systems; aircraft control systems; key plant systems; military equipment; etc.). Renesas Electronics disclaims
any and all liability for any damages or losses incurred by you or any third parties arising from the use of any Renesas Electronics product that is
inconsistent with any Renesas Electronics data sheet, user’s manual or other Renesas Electronics document.
7. No semiconductor product is absolutely secure. Notwithstanding any security measures or features that may be implemented in Renesas Electronics
hardware or software products, Renesas Electronics shall have absolutely no liability arising out of any vulnerability or security breach, including but not
limited to any unauthorized access to or use of a Renesas Electronics product or a system that uses a Renesas Electronics product. RENESAS
ELECTRONICS DOES NOT WARRANT OR GUARANTEE THAT RENESAS ELECTRONICS PRODUCTS, OR ANY SYSTEMS CREATED USING
RENESAS ELECTRONICS PRODUCTS WILL BE INVULNERABLE OR FREE FROM CORRUPTION, ATTACK, VIRUSES, INTERFERENCE,
HACKING, DATA LOSS OR THEFT, OR OTHER SECURITY INTRUSION (“Vulnerability Issues”). RENESAS ELECTRONICS DISCLAIMS ANY AND
ALL RESPONSIBILITY OR LIABILITY ARISING FROM OR RELATED TO ANY VULNERABILITY ISSUES. FURTHERMORE, TO THE EXTENT
PERMITTED BY APPLICABLE LAW, RENESAS ELECTRONICS DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR IMPLIED, WITH
RESPECT TO THIS DOCUMENT AND ANY RELATED OR ACCOMPANYING SOFTWARE OR HARDWARE, INCLUDING BUT NOT LIMITED TO THE
IMPLIED WARRANTIES OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
8. When using Renesas Electronics products, refer to the latest product information (data sheets, user’s manuals, application notes, “General Notes for
Handling and Using Semiconductor Devices” in the reliability handbook, etc.), and ensure that usage conditions are within the ranges specified by
Renesas Electronics with respect to maximum ratings, operating power supply voltage range, heat dissipation characteristics, installation, etc. Renesas
Electronics disclaims any and all liability for any malfunctions, failure or accident arising out of the use of Renesas Electronics products outside of such
specified ranges.
9. Although Renesas Electronics endeavors to improve the quality and reliability of Renesas Electronics products, semiconductor products have specific
characteristics, such as the occurrence of failure at a certain rate and malfunctions under certain use conditions. Unless designated as a high reliability
product or a product for harsh environments in a Renesas Electronics data sheet or other Renesas Electronics document, Renesas Electronics products
are not subject to radiation resistance design. You are responsible for implementing safety measures to guard against the possibility of bodily injury,
injury or damage caused by fire, and/or danger to the public in the event of a failure or malfunction of Renesas Electronics products, such as safety
design for hardware and software, including but not limited to redundancy, fire control and malfunction prevention, appropriate treatment for aging
degradation or any other appropriate measures. Because the evaluation of microcomputer software alone is very difficult and impractical, you are
responsible for evaluating the safety of the final products or systems manufactured by you.
10. Please contact a Renesas Electronics sales office for details as to environmental matters such as the environmental compatibility of each Renesas
Electronics product. You are responsible for carefully and sufficiently investigating applicable laws and regulations that regulate the inclusion or use of
controlled substances, including without limitation, the EU RoHS Directive, and using Renesas Electronics products in compliance with all these
applicable laws and regulations. Renesas Electronics disclaims any and all liability for damages or losses occurring as a result of your noncompliance
with applicable laws and regulations.
11. Renesas Electronics products and technologies shall not be used for or incorporated into any products or systems whose manufacture, use, or sale is
prohibited under any applicable domestic or foreign laws or regulations. You shall comply with any applicable export control laws and regulations
promulgated and administered by the governments of any countries asserting jurisdiction over the parties or transactions.
12. It is the responsibility of the buyer or distributor of Renesas Electronics products, or any other party who distributes, disposes of, or otherwise sells or
transfers the product to a third party, to notify such third party in advance of the contents and conditions set forth in this document.
13. This document shall not be reprinted, reproduced or duplicated in any form, in whole or in part, without prior written consent of Renesas Electronics.
14. Please contact a Renesas Electronics sales office if you have any questions regarding the information contained in this document or Renesas
Electronics products.
(Note1) “Renesas Electronics” as used in this document means Renesas Electronics Corporation and also includes its directly or indirectly controlled
(Note2) “Renesas Electronics product(s)” means any product developed or manufactured by or for Renesas Electronics.
subsidiaries.
electronic appliances; machine tools; personal electronic equipment; industrial robots; etc.
financial terminal systems; safety control equipment; etc.
(Rev.5.0-1 October 2020)
TOYOSU FORESIA, 3-2-24 Toyosu,
Koto-ku, Tokyo 135-0061, Japan
www.renesas.com
Renesas and the Renesas logo are trademarks of Renesas
Electronics Corporation. All trademarks and registered trademarks
are the property of their respective owners.
For further information on a product, technology, the most up-to-date
version of a document, or your nearest sales office, please visit:
www.renesas.com/contact/.
© 2021 Renesas Electronics Corporation. All rights reserved.
General Precautions in the Handling of Microprocessing Unit and Microcontroller
Unit Products
The following usage notes are applicable to all Microprocessing unit and Microcontroller unit products from Renesas. For detailed usage notes on the products
covered by this document, refer to the relevant sections of the document as well as any technical updates that have been issued for the products.
1. Precaution against Electrostatic Discharge (ESD)
A strong electrical field, when exposed to a CMOS device, can cause destruction of the gate oxide and ultimately degrade the device operation. Steps
must be taken to stop the generation of static electricity as much as possible, and quickly dissipate it when it occurs. Environmental control must be
adequate. When it is dry, a humidifier should be used. This is recommended to avoid using insulators that can easily build up static electricity.
Semiconductor devices must be stored and transported in an anti-static container, static shielding bag or conductive material. All test and measurement
tools including work benches and floors must be grounded. The operator must also be grounded using a wrist strap. Semiconductor devices must not be
touched with bare hands. Similar precautions must be taken for printed circuit boards with mounted semiconductor devices.
2. Processing at power-on
The state of the product is undefined at the time when power is supplied. The states of internal circuits in the LSI are indeterminate and the states of
register settings and pins are undefined at the time when power is supplied. In a finished product where the reset signal is applied to the external reset
pin, the states of pins are not guaranteed from the time when power is supplied until the reset process is completed. In a similar way, the states of pins in
a product that is reset by an on-chip power-on reset function are not guaranteed from the time when power is supplied until the power reaches the level
at which resetting is specified.
3. Input of signal during power-off state
Do not input signals or an I/O pull-up power supply while the device is powered off. The current injection that results from input of such a signal or I/O
pull-up power supply may cause malfunction and the abnormal current that passes in the device at this time may cause degradation of internal elements.
Follow the guideline for input signal during power-off state as described in your product documentation.
4. Handling of unused pins
Handle unused pins in accordance with the directions given under handling of unused pins in the manual. The input pins of CMOS products are
generally in the high-impedance state. In operation with an unused pin in the open-circuit state, extra electromagnetic noise is induced in the vicinity of
the LSI, an associated shoot-through current flows internally, and malfunctions occur due to the false recognition of the pin state as an input signal
become possible.
5. Clock signals
After applying a reset, only release the reset line after the operating clock signal becomes stable. When switching the clock signal during program
execution, wait until the target clock signal is stabilized. When the clock signal is generated with an external resonator or from an external oscillator
during a reset, ensure that the reset line is only released after full stabilization of the clock signal. Additionally, when switching to a clock signal produced
with an external resonator or by an external oscillator while program execution is in progress, wait until the target clock signal is stable.
6. Voltage application waveform at input pin
Waveform distortion due to input noise or a reflected wave may cause malfunction. If the input of the CMOS device stays in the area between V
and V
(Min.) due to noise, for example, the device may malfunction. Take care to prevent chattering noise from entering the device when the input level
IH
is fixed, and also in the transition period when the input level passes through the area between V
7. Prohibition of access to reserved addresses
Access to reserved addresses is prohibited. The reserved addresses are provided for possible future expansion of functions. Do not access these
addresses as the correct operation of the LSI is not guaranteed.
8. Differences between products
Before changing from one product to another, for example to a product with a different part number, confirm that the change will not lead to problems.
The characteristics of a microprocessing unit or microcontroller unit products in the same group but having a different part number might differ in terms of
internal memory capacity, layout pattern, and other factors, which can affect the ranges of electrical characteristics, such as characteristic values,
operating margins, immunity to noise, and amount of radiated noise. When changing to a product with a different part number, implement a system-
evaluation test for the given product.
(Max.) and VIH (Min.).
IL
(Max.)
IL
Use this software after sufficiently confirming the manual of the microcontroller in use.
How to Use This Manual
1. Purposes and Target Readers
The purpose of this manual is to give users an understanding of the basic specifications and correct use of the
Renesas Flash Programmer. This manual is intended for users who are using the flash programmer in
designing and developing a system that employs a Renesas Electronics microcontroller equipped with on-chip
flash memory.
It is assumed that the readers of this manual have a basic knowledge of microcontrollers, Windows, and
Linux, and some knowledge of electrical and logic circuits.
2. Conventions
• Note: Footnote for item marked with “Note” in the text.
• Caution: Information requiring particular attention
• Remark: Supplementary information
• Numeral representations: Binary ... xxxx or xxxxB
Decimal ... xxxx
Hexadecimal ... 0xXXXX or xxxxH
• “ ”: Any character or item on the screen that can be selected or input
• : Name of a button
• [ ]: Name of a command, dialog box, tabbed page, option, or area on the screen
Term
Meaning
E1/E20/E2/E2 Lite
Abbreviation of “the E1, E20, E2, or E2 emulator Lite”
J-Link
SEGGER-produced debug probe for MCUs
Tool used
General term for the tool used by the customer, whether an E1, E20, E2, E2 Lite, or
Target MCU
The Renesas Electronics MCU with on-chip flash memory which is in use by the user
Target system
User-designed board on which the target MCU is mounted
Input clock
A clock from an oscillator or a resonator which is externally input to the target MCU
Parameter file
Parameter files include information required to program the flash memory of the
ID code
Authentication code used in flash programming and in on-chip debugging. For
RPI file
RPI files are image files generated by the RFP that combine usable HEX files and
RPE file
An encrypted program file that has been generated by the encryption utility program
3. Terminology
The meanings of the terms used in the Renesas Flash Programmer manual are as follows.
RFP Abbreviation of “Renesas Flash Programmer”, software for programming flash
memory
J-Link.
MCU Abbreviation of “microcontroller unit”
Project file Project files hold the data required to write programs. In the RFP, a project file holds
the settings related to the programming environment, such as target MCU settings
and command option specifications. Project files have the filename extension *.rpj.
(1/2)
target MCU, and are created by acquiring information from the MCU. Parameter files
have the extension *.fcf.
details, refer to the user’s manual of the target MCU.
Lock bit One of the safety functions of the MCU. For details, refer to the user’s manual of the
target MCU.
HEX file Program file without flash option data
flash options data.
Program file “Program file” refers to a file that contains a program to be written to the MCU. The
RFP supports the following program file formats.
a. HEX files in Intel HEX format
b. HCUHEX files in Intel HEX format
c. HEX files in Motorola S format
d. HCUHEX files in Motorola S format
e. RPI files
Refer to section 1.5.1, RPI File.
The only supported character code is ASCII (one byte). Unicode (two bytes) is not
supported.
f. RPE files
Refer to section 1.5.2, RPE File.
COMx COMx is a serial interface port of the host PC.
When writing data to the target system by using a serial interface of the host PC,
select COMx as the tool to be used. Any value from 1 to 256 can be specified for x.
Term
Meaning
USB Direct
USB Direct is a method of writing to the MCU in the USB boot mode by using the
OTP
A security function of the MCU. For details, refer to the user’s manual of the target
Access window (AW)
This is also referred to as the “flash shield window”. The specified range is selected
DLM
Management to maintain security in the entire life cycle of the device (device life-
Authentication code
A collective term for authentication codes, including ID codes, passwords, and
USB interface port of the host PC.
FINE FINE is a single- or dual-line communications interface operating through the FINE
pin or pins of an MCU. Some of our MCUs support writing via single line FINE.
ID authentication mode One of the security functions of the MCU. Connection of the flash programmer is
protected by ID authentication.
MCU.
as the access window (and window area), and functionality in other ranges is
restricted to a degree which depends on the operating mode. For details, refer to
the user’s manual of the target MCU.
Flash options Flash options are settings which determine the state after the MCU is reset, and is
a general term for settings which must be specified separately from the HEX file.
TSIP Dedicated hardware secure IP (trusted secure IP) for managing the encryption key.
For details, contact a Renesas Electronics sales office.
(2/2)
cycle management).
For details, refer to the user’s manual of the target MCU.
DLM keys.
Term in This Application
To be Replaced with
Access window (AW)
Flash shield window
Term in This Application
To be Replaced with
4. Replacing Terms
Some terms used in this application should be replaced as shown in the table below, depending on the MCU
to be used.
USB Direct USB interface mode
• When an RL78 is to be used:
Term in This Application To be Replaced with
• When an RH850 with an extended user area is to be used:
User Boot Area Extended user area
All trademarks and registered trademarks are the property of their respective owners.
Table of Contents
1. Overview .......................................................................................................................... 10
1.1 Features ................................................................................................................................................... 10
1.2 Supported Microcontrollers ...................................................................................................................... 10
1.3 System Overview ..................................................................................................................................... 11
1.3.1 Connection with the Target System ............................................................................................... 11
1.4 Operating Environment ............................................................................................................................ 12
1.4.1 Hardware Environment .................................................................................................................. 12
1.4.2 Software Environment .................................................................................................................... 12
1.5 Formats of Program Files ........................................................................................................................ 13
1.5.1 RPI File ........................................................................................................................................... 13
1.5.2 RPE File ......................................................................................................................................... 13
1.6 Relative Paths for Files ............................................................................................................................ 13
2. Descriptions of Functions ................................................................................................ 14
2.1 Main Window ........................................................................................................................................... 14
2.2 Creating a New Project ............................................................................................................................ 15
2.2.1 [Create New Project] Dialog Box.................................................................................................... 15
2.2.2 [Tool Details] Dialog Box ................................................................................................................ 17
2.2.3 [Set Clock] Dialog Box ................................................................................................................... 20
2.2.4 [Authentication] Dialog Box ............................................................................................................ 21
2.3 Operating the Tabbed Pages ................................................................................................................... 22
2.3.1 [Operation] Tabbed Page ............................................................................................................... 23
2.3.2 [Operation Settings] Tabbed Page ................................................................................................. 25
2.3.3 [Block Settings] Tabbed Page ........................................................................................................ 29
2.3.4 [Flash Option] Tabbed Page .......................................................................................................... 31
2.3.5 [Connect Settings] Tabbed Page ................................................................................................... 36
2.3.6 [Unique Code] Tabbed Page .......................................................................................................... 37
2.3.7 [User Keys] Tabbed Page .............................................................................................................. 41
2.4 Menu Bar.................................................................................................................................................. 42
2.4.1 [File] Menu ...................................................................................................................................... 42
2.4.2 [Device Information] Menu ............................................................................................................. 45
2.4.3 [Help] Menu .................................................................................................................................... 50
2.5 Simple Use of Project Files from a Command Line ................................................................................. 51
2.5.1 Exit Code ........................................................................................................................................ 51
2.5.2 Restriction ...................................................................................................................................... 51
2.5.3 Command-line Syntax .................................................................................................................... 51
2.5.4 Start Options .................................................................................................................................. 52
2.5.5 Example of Command-line Statements ......................................................................................... 56
2.6 Command Line for Linux or Windows ...................................................................................................... 56
2.7 Encryption Utility Program ....................................................................................................................... 57
2.7.1 Exit Code ........................................................................................................................................ 57
2.7.2 Command-line Syntax .................................................................................................................... 57
2.7.3 Start Options .................................................................................................................................. 57
2.8 Renesas Flash Programmer Utility Program ........................................................................................... 58
2.8.1 Exit Code ........................................................................................................................................ 58
2.8.2 Command-line Syntax .................................................................................................................... 58
2.8.3 List of Commands .......................................................................................................................... 59
2.8.4 Start Options .................................................................................................................................. 59
3. Operating the RFP ........................................................................................................... 61
3.1 Flow of Operations ................................................................................................................................... 62
4. Troubleshooting ............................................................................................................... 71
4.1 Problems during Startup .......................................................................................................................... 71
4.2 Problems during Operation ...................................................................................................................... 72
4.3 Problems during Communications ........................................................................................................... 77
4.4 Error Messages ........................................................................................................................................ 78
5. Points for Caution ............................................................................................................ 84
5.1 Manipulating the User Boot Mat .............................................................................................................. 84
5.2 Host PC .................................................................................................................................................... 84
5.3 USB-to-Serial Converter .......................................................................................................................... 84
5.4 Check before Connection ........................................................................................................................ 84
5.5 Erase Chip of the RH850 Family ............................................................................................................. 84
5.6 Connecting through a COM Port or USB Direct ...................................................................................... 85
5.7 Auto-padding with 0xFF ........................................................................................................................... 85
5.8 Verification after Protecting the MCU ...................................................................................................... 85
5.9 MCUs Supporting a Dual-Bank Structure ................................................................................................ 85
Renesas Flash Programmer V3.08 1. Overview
1. Overview
The Renesas Flash Programmer (hereafter referred to as the RFP) is software that uses an E1 emulator
(hereafter referred to as the E1), E20 emulator (hereafter referred to as the E20), E2 emulator (hereafter
referred to as the E2), or E2 emulator Lite (hereafter referred to as the E2 Lite) via a serial or USB interface or
a J-Link debug probe (hereafter referred to as the J-Link) to erase, write, and verify programs on a target
system on which a Renesas Electronics MCU with on-chip flash memory is mounted.
1.1 Features
• Writing controlled by the host PC
• High-speed writing by using an emulator
• Simple operation for writing with a simple GUI specific to development
• Automatic writing from a command line
• Programming of a unique code to a designated area of flash memory
• Support of encrypted program files
1.2 Supported Microcontrollers
Microcontrollers supported by the RFP are listed on the Web page at the following link:
https://www.renesas.com/rfp
R20UT4813EJ0200 Rev.2.00 Page 10 of 87
Apr.01.21
Renesas Flash Programmer V3.08 1. Overview
+
Renesas
Flash Programmer
Serial cable (RS-232C)
USB cable
1.3 System Overview
An overview of the RFP system is illustrated in the following diagram.
E1
PC
USB cable
E20
E2
E2 Lite
J-Link
Target cable
Target system
Figure 1-1 RFP Connection Image
1.3.1 Connection with the Target System
For examples of programming circuits by using the E1, E20, E2, or E2 Lite, refer to the user’s manuals for the
individual products.
For examples of programming circuits by using the USB, refer to the hardware manual of the target MCU you
are using.
Examples of programming circuits by using the serial interface of the host PC are provided on the web page at
the following link.
https://www.renesas.com/rfp
R20UT4813EJ0200 Rev.2.00 Page 11 of 87
Apr.01.21
Renesas Flash Programmer V3.08 1. Overview
1.4 Operating Environment
1.4.1 Hardware Environment
(1) Host PC
• Processor: 1 GHz or faster
• Main memory: At least 1 Gbyte (2 Gbytes or more when using 64-bit Windows); 2 Gbytes or more
recommended
• Display: 1,024 x 768 or higher
• Interface: USB 2.0 (when using E1, E20, E2, E2 Lite, USB Direct, or J-Link)
Serial interface (RS-232C, when using COMx)
(2) Tools supported
• E1
• E20
• E2
• E2 Lite
• J-Link
Note: The following restrictions apply to the J-Link.
Target MCUs: RA series
Communications method: 2-wire UART
Communications rates: 115200 bps or 9600 bps
Remark: The supported target MCUs differ with the tool. For the target MCUs supported by the different
tools, refer to List of MCUs Supported by Renesas Flash Programmer V3.
1.4.2 Software Environment
(1) OSs supported
• Windows 7 (32-bit and 64-bit)
• Windows 8.1 (32-bit and 64-bit)
• Windows 10 (32-bit and 64-bit)
• Linux (Ubuntu 18.04 LTS, x64/ARM32/ARM64)
• Linux (Ubuntu 20.04 LTS, x64/ARM32/ARM64)
Remarks: 1. We recommend having the latest service pack or version of Windows installed.
2. The GUI (RFPV3.exe) does not run under Linux.
(2) Required software
• Windows: Microsoft .NET Framework 4.5.2 or a later version
• Linux: Refer to the guide “rfp_cli.md”, which is separately provided. Note that this is a markdown-format
English file.
R20UT4813EJ0200 Rev.2.00 Page 12 of 87
Apr.01.21
Renesas Flash Programmer V3.08 1. Overview
1.5 Formats of Program Files
For a HEX file to be readable by the RFP, it must have the correct format and satisfy the following conditions.
If a program file with a non-supported format is read, an error will occur.
(1) Intel HEX format
• The format file ends with the end record.
• All lines consist solely of record types 00 to 05.
(2) Motorola S format
• The format file ends with the end record (S7, S8, or S9).
• All lines consist solely of record types S0 to S9 (excluding S4).
1.5.1 RPI File
An RPI file is an image file that the RFP can generate. An RPI file combines program code and flash options
data. Refer to section 2.4.1 for the generation of these files.
1.5.2 RPE File
An RPE file is a file generated by using the encryption utility program to encrypt a program file. Refer to
section 2.7 for the generation of such files.
1.6 Relative Paths for Files
When the following files are registered in a project, the RFP automatically uses relative paths in saving the
files under the project directory.
• Program file
• Unique code file
R20UT4813EJ0200 Rev.2.00 Page 13 of 87
Apr.01.21
Renesas Flash Programmer V3.08 2. Descriptions of Functions
(1)
(2)
(3)
(4)
2. Descriptions of Functions
This chapter describes the window structure and functions of the RFP.
2.1 Main Window
After the RFP is started, the main window as shown below will appear.
Figure 2-1 Main Window
(1) Menu bar
For the menu bar, refer to section 2.4, Menu Bar.
(2) Tabbed pages
Operations on the tabbed pages enable controlling the RFP for writing, setting options, and so on. For details
on the individual tabbed pages, refer to section 2.3, Operation of the Tabbed Pages.
(3) Log output panel
The version information of RFP and the contents and results of command execution are displayed here.
Caution: Log entries older than the 1500th line are automatically removed.
(4) Clear status and message
Pressing this button clears the contents of the log output window and the status information on the [Operation]
tabbed page.
R20UT4813EJ0200 Rev.2.00 Page 14 of 87
Apr.01.21
Renesas Flash Programmer V3.08 2. Descriptions of Functions
(1)
(2)
(3)
(4)
(5)
2.2 Creating a New Project
2.2.1 [Create New Project] Dialog Box
Selecting [File] → [Create a new project] in the menu bar makes the [Create New Project] dialog box appear.
The configuration of the dialog box is shown below.
Figure 2-2 [Create New Project] Dialog Box
(1) Microcontroller
Select the type of target MCU to be used.
(2) Project Name and Project Folder
Specify the name of a project which is to be newly created and the project folder which will hold the created
project file.
Remark: Since the project name is used in the file name, characters that are not usable in file names cannot
be used.
(3) Communication
Set up communications with the target MCU.
• “Tool”
Select the tool to be used for connection with the target MCU.
Caution: For the USB connection of RX65x, RX66x, RX72x, RA, RE devices with Renesas SynergyTM, select
“COM”, since serial communications are performed through a virtual USB COM port.
Remark: The usable tools may differ with the selected target MCU.
• “Interface”
When this item is selectable, select the method for communicating with the target MCU.
R20UT4813EJ0200 Rev.2.00 Page 15 of 87
Apr.01.21
Renesas Flash Programmer V3.08 2. Descriptions of Functions
• Tool Details…
Make detailed settings for the tool to be used. The tool in use and the setting for the supply of power
supply are shown to the right of Tool Details…. For details on Tool Details…, refer to section 2.2.2, [Tool
Details] Dialog Box.
(4) Wide Voltage
When “Wide Voltage” is selected, each command can be executed with the target microcontroller set to wide
voltage mode. When writing to the target MCU proceeds with a voltage lower than 2.4 V, deselect this
checkbox. For details on the wide voltage mode, refer to the user’s manual of the target MCU.
Remark: “Wide Voltage” is not displayed for those target MCUs which do not support it.
(5) Connect
Clicking on Connect enables connection with the target MCU.
At this time, the following dialog boxes might be displayed according to the type of the target MCU; enter a
value in each dialog box to continue processing to make the connection.
• [Set Clock] dialog box
• [Authentication] dialog box
For details on these dialog boxes, refer to sections 2.2.3, [Set Clock] Dialog Box, and 2.2.4,
[Authentication] Dialog Box.
Caution: If the connection is made with incorrect settings, the tool or the target system might be damaged.
For details, refer to chapter 5, Points for Caution.
R20UT4813EJ0200 Rev.2.00 Page 16 of 87
Apr.01.21
Renesas Flash Programmer V3.08 2. Descriptions of Functions
(3)
(4)
(1)
(2)
(5)
(6)
2.2.2 [Tool Details] Dialog Box
The [Tool Details] dialog box consists of the following tabbed pages.
• [Select Tool] tabbed page
• [Reset Settings] tabbed page
• [Mode Pin Setting] tabbed page
The [Mode Pin Setting] tabbed page is only displayed when the E1, E20, E2, or E2 Lite is selected.
Figure 2-3 [Tool Details] Dialog Box
(1) [Select Tool]
Tools which are currently available are shown; select the tool to be used.
When the “Auto Select” checkbox is selected, the tool which is shown at the top of the list is automatically
selected. To directly select the tool to be used, deselect the “Auto Select” checkbox and select a tool from the
list.
Remark: For the E1, E20, E2, or E2 Lite, the serial number of the emulator is shown.
R20UT4813EJ0200 Rev.2.00 Page 17 of 87
Apr.01.21
Renesas Flash Programmer V3.08 2. Descriptions of Functions
(2) Power Supply
Select the power-supply function of the tool.
Select “None” if no power is to be supplied from the tool in use.
Specify the voltage when the tool in use is to supply power.
For the power-supply function, refer to the user’s manual of the tool you are using.
Caution: Do not use the power-supply function from the tool in processing for mass-production; instead,
supply power which matches the MCU’s specifications from the target system. Since the voltage
supplied from the tool depends on the performance of the USB power supply of the host PC, its
precision cannot be guaranteed.
Remark: [Custom] only appears in the [Tool Details] dialog box when the E2 emulator is selected. A voltage
within the range from 1.8 V to 5.5 V can be specified.
(3) Setting of RESET
Sets the operation of the reset signal when the RFP is disconnected from the target MCU.
• Reset Pin as Low
After the RFP is disconnected from the target MCU, the low level continues to be output from the RESET
pin.
• Reset Pin as Hi-Z
After the RFP is disconnected from the target MCU and the RESET pin has been at the low level, the
RESET pin enters the hi-Z state. This setting is used when the user wishes to operate the target MCU on
completion of processing with the RFP.
(4) Settings for reset signals
Make settings for pins to be used for the output of reset signals to the target MCU.
Remark: Reset signals are only displayed when the COM port is selected for the tool.
• Selection of the RTS or DTR signal
Selected: The signal is used as a reset signal.
Deselected: The signal is not used as a reset signal.
• Logic of the signal
Selected: The RTS or DTR signal outputs the high level when the device is reset.
Deselected: The RTS or DTR signal outputs the low level when the device is reset.
(5) Setting of entry to boot mode
Make settings for pins when the target MCU is connected.
• “Boot Mode Entry by RFP”
The settings of “Pin Output” and “Pin Setting” according to the recommended circuits of the tool in use are
made automatically.
Remark: For the recommended circuit, refer to the user’s manual and the additional document of the tool
you are using.
R20UT4813EJ0200 Rev.2.00 Page 18 of 87
Apr.01.21
Renesas Flash Programmer V3.08 2. Descriptions of Functions
14 Pins
38 Pins
Pin Name (RX Family)
1
15
io4 2 ―
GND
3
21
io5 4 3
io0 5 11
TxD 6 1
io1 7 8
io3 8 14
VCC
9
17 ― 10 2 io2
11
19
RxD
12 ― GND
13 9 RESET
14 5 GND
• “Boot Mode Entry by User”
Manually make the settings for “Pin Output” and “Pin Setting”.
Remark: “Boot Mode Entry by User” might not be selectable depending on the target MCU or tool in use and
the communications interface.
(6) Setting of outputs
Selecting “Boot Mode Entry by User” for boot mode entry enables the setting of outputs.
The boxes set the output of the io0 to io5 pins of the tool in use when the target MCU is connected.
• Pin Output
Selected: The target pin is used as an output pin.
Deselected: The target pin is used as hi-Z.
• Pin Setting (High)
Selected: The high level is output.
Deselected: The low level is output.
For pin assignments of io0 to io5 in the E1, E20, E2, and E2 Lite, refer to table 2-1 and table 2-2.
Table 2-1 Pin Assignments for the E1, E20, E2, and E2 Lite
Remark: TxD and RxD are signal names of the MUC side.
R20UT4813EJ0200 Rev.2.00 Page 19 of 87
Apr.01.21
Renesas Flash Programmer V3.08 2. Descriptions of Functions
20 Pins
Pin Name (RA Family)
Pin Name (RE Family)
Remark
1
VCC
VCC
2 ―
RxD
3 GND
GND
4 io4
io4 / TxD
E2 Lite cannot use
5
GND
GND
6 TxD ― 7 ― ― 8 RxD
― 9
GND
GND
10
RESET
RESET
11 ― ― 12
io3
io3
E2 Lite cannot use
13 ― ― 14
io1
io1
E2 Lite cannot use
15
GND
GND
16
io5
io5
E2 Lite cannot use
17
GND
GND
18
io0
io0
E2 Lite cannot use
19
GND
GND
20
io2
io2
E2 Lite cannot use
Table 2-2 Pin Assignments for the E2, and E2 Lite
Remark
- TxD and RxD are signal names of the MUC side.
- E2 Lite does not support the RE family.
2.2.3 [Set Clock] Dialog Box
The input clock must be set to suit the type of the target MCU.
If setting of the input clock is required, the [Set Clock] dialog box will appear.
Figure 2-4 [Set Clock] Dialog Box
Enter the frequency of the input clock and click on OK.
The value for frequency is entered in MHz. If you want to enter a value in smaller units than MHz, use a
decimal point.
R20UT4813EJ0200 Rev.2.00 Page 20 of 87
Apr.01.21
Renesas Flash Programmer V3.08 2. Descriptions of Functions
2.2.4 [Authentication] Dialog Box
If entering an authentication code is required, the [Authentication] dialog box will appear.
Remark: Whether or not there is an authentication code function depends on the target MCU.
Figure 2-5 [Authentication] Dialog Box
• Authentication Code
Enter the authentication code in hexadecimal notation (0 to 9 and A to F).
• Auto Authentication
When this checkbox is selected, the authentication code is saved in the project file and authentication
automatically proceeds from the next time the project is opened.
Caution
- If the value of the input field takes up fewer than the number of effective bytes, the RFP
automatically pads the input data with 0xFF after the input value.
- When an RX-family device is connected via the RFP, input the value in the order ID1, ID2, ..., ID16.
However, for a device with control code, enter the value of the code as the first of the effective
bytes.
Example:
When the number of effective bytes = 16, control code = 0x45, ID code = ID1=0x01, ID2=0x02,
ID3=0x03, ID4=0x04, ID5=0x05, ID6=0x06, ID7=0x07, ID8=0x08, ID9=0x09, ID10=0x0A,
ID11=0x0B, ID12=0x0C, ID13=0x0D, ID14=0x0E, and ID15=0x0F, the value will be
‘450102030405060708090A0B0C0D0E0F’.
- When RX72x, RX71x, RX66x, RX65x, or RX64x device is connected via a debug tool which has
been specified with the CS+ or e2 studio, the order for input of the authentication code changes to
that shown below.
ID4 ID3 ID2 ID1 ID8 ID7 ID6 ID5 ID12 ID11 ID10 ID9 ID16 ID15 ID14 ID13
- When an RA-family, Renesas Synergy-family, or RE-family device is connected to the RFP, input
values to be specified for registers of the target MCU in order of bits 127 to 0 in byte units. Since the
input specification may also differ with the tool, confirm the input specification of the tool you will be
using.
Remark: The default authentication code in some target MCUs at the time of shipment is all FFs. For details,
refer to the user’s manual of the target MCU.
R20UT4813EJ0200 Rev.2.00 Page 21 of 87
Apr.01.21
Renesas Flash Programmer V3.08 2. Descriptions of Functions
2.3 Operating the Tabbed Pages
When “Create New Project” is completed normally, the main window of the RFP is displayed.
Operating the tabbed pages in the main window allows you to make detailed settings of the RFP.
The tabbed pages consist of the seven listed below.
• [Operation] tabbed page
• [Operation Settings] tabbed page
• [Block Settings] tabbed page
• [Flash Option] tabbed page
• [Connect Settings] tabbed page
• [Unique Code] tabbed page
• [User Keys] tabbed page
The following describes the configuration and operation of each tabbed page.
Figure 2-6 Main Window
R20UT4813EJ0200 Rev.2.00 Page 22 of 87
Apr.01.21
Renesas Flash Programmer V3.08 2. Descriptions of Functions
2.3.1 [Operation] Tabbed Page
The [Operation] tabbed page shows information on the project and flash operation.
(1)
(2)
(3)
(4)
(5)
Figure 2-7 [Operation] Tabbed Page
(1) Project Information
Information on the selected project is shown.
(2) Endian
Select the endianness for the data of the program file.
This item does not appear for target MCUs which do not support changing the endianness in the RFP.
• “Little”
Set the handling of files for programming as little endian.
• “Big”
Set the handling of files for programming as big endian.
(3) Program File
Set the path to a file to be programmed in the flash memory of the target MCU.
Click on Browse… to select a file.
Multiple files for programming are also selectable simultaneously. Refer to 2.3.1.1, Selecting Multiple Program
Files, for details.
(4) File Check Sum
CRC-32 check sum of the selected program file is displayed.
Caution: This CRC-32 is a check sum for whole of file, not for HEX data. The file check sum is different from
the check sum of the one obtained from MCU.
R20UT4813EJ0200 Rev.2.00 Page 23 of 87
Apr.01.21
Renesas Flash Programmer V3.08 2. Descriptions of Functions
Immediately after the RFP has been started or after clicking on the Clear button under the
A command is being executed.
(1)
(2)
(5) Flash Operation
Clicking on Start leads to the execution of commands to handle the processing shown above Start.
Information on the state is indicated with color and characters in the status display to the right of Start. For the
status display, refer to table 2-3.
The type of flash operation can be changed on the [Operation Settings] tabbed page. For the [Operation
Settings] tabbed page, refer to section 2.3.2, [Operation Settings] Tabbed Page.
Table 2-3 State Information
output panel
A command has been executed and ended normally.
Processing has stopped during the execution of a command.
Processing failed after the execution of a command.
2.3.1.1 Selecting Multiple Program Files
When selecting multiple files, specify all desired files beforehand then press the [Start] button to run the actual
programming. Selecting Browse… opens the [Specify a program file] dialog box. The files can be recorded by
selecting them by mouse or by using the CTRL or SHIFT keys with the mouse or mouse and cursor keys, and
then selecting Open.
Figure 2-8 [Program File] Group Box after the Selection of Multiple Files for Programming
(1) Program Files
Only the file names are displayed when multiple files have been selected. That is, the path is separately
displayed.
(2) File Information
The path to the files for programming is displayed.
Caution
- An error occurs if an RPI, HCUHEX, or RPE file is specified in the selection of multiple files.
- An error occurs when writing to the flash area in cases of overlapping between the addresses of the
data files for programming.
- The selected multiple files must be in the same folder.
R20UT4813EJ0200 Rev.2.00 Page 24 of 87
Apr.01.21
Renesas Flash Programmer V3.08 2. Descriptions of Functions
2.3.2 [Operation Settings] Tabbed Page
Settings for the flash operation can be changed on the [Operation Settings] tabbed page.
Remark: Some items will not be shown according to the selected program file or the type of the target MCU.
(3)
(1)
(4)
(5)
(2)
(6)
Figure 2-9 [Operation Settings] Tabbed Page
(1) Command
Specify the type of processing that will proceed after clicking on Start in the main window.
When multiple operations are specified for “Command”, each operation is executed from the top item in order.
The following five types of processing can be specified for “Command”, and are described in more detail
following the summaries below.
• Erase
Erase the flash area.
The range of areas to be erased conforms to the setting made with “(3) Erase Option”.
• Program
Program the flash area.
The operation reflects the setting made under “(4) Program & Verify Option”.
• Verify
Perform verification.
The operation reflects the setting made under “(4) Program & Verify Option”.
• Program Flash Options
Set flash options such as “Lockbit”, “OTP”, “Access Window”, “Option Bytes”, and “Security”.
The programming setting conforms to the settings made on the [Block Settings] and [Flash Option] tabbed
pages.
Note, however, that this command is not displayed if an HCUHEX file, RPI file, or RPE file generated by
encrypting an HCUHEX file or RPI file is selected, in which case the flash options are always programmed.
R20UT4813EJ0200 Rev.2.00 Page 25 of 87
Apr.01.21
Renesas Flash Programmer V3.08 2. Descriptions of Functions
• Verify Flash Options
Select whether or not to verify values in the flash option area.
• Checksum
Acquire the checksum.
The checksum is calculated by the method selected under “(5) Checksum Type”.
Remark: The results are output in units of areas of flash memory. Use the verify command if you want to
check the consistency of data in units of blocks.
(2) Fill with 0xFF
Select the method for handling ranges for which files have no data in each area of flash memory.
• When this option is selected
Programming: The value 0xFF is programmed to bytes in ranges for which the program file has no data.
Verifying: Ranges containing no data from a program file are regarded as having the value 0xFF for
comparison.
• When this option is not selected
Programming: Ranges for which the program file has no data are not programmed.
Verifying: Ranges for which the program file has no data are not verified.
Caution: Even if “Fill with 0xFF” is not selected, this action always applies for the minimum unit of
programming by the MCU.
(3) Erase Option
Set options when “Erase” is selected for “Command”.
• Erase Selected Blocks
Erase only those blocks selected on the [Block Settings] tabbed page.
For the [Block Settings] tabbed page, refer to section 2.3.3, [Block Settings] Tabbed Page.
• Erase All Blocks
Erase all blocks.
Caution: Erasure processing may be skipped for certain blocks reserved by the MCU due to security
functions and so on.
• Erase Chip
Erase all blocks and clear the flash options.
Caution: This processing does not restore the MCU to its state at shipment. If correct settings are not
programmed for the flash options after erasing the chip, the MCU will not operate.
When this processing is used on an RH850 family product, be sure to refer to chapter 5, Points for
Caution.
R20UT4813EJ0200 Rev.2.00 Page 26 of 87
Apr.01.21
Renesas Flash Programmer V3.08 2. Descriptions of Functions
(4) Program & Verify Option
Set options here when you have selected “Program” or “Verify” for “Command”.
• Erase Before Program
The range where data are to be programmed is erased beforehand if this option is selected.
Caution: The range to be erased depends on the minimum unit of erasing by the MCU.
• Verification type
Select the type of verification as one of the following items. Depending on the target MCU, only one type
may be available.
Verify by reading the device
Data are acquired with a read command from the MCU and the RFP handles comparison.
Comparison cannot proceed if the MCU is in a state such that reading is prohibited.
Verify in the device
Data are re-sent to the MCU in response to the verify command and the MCU side handles
comparison.
Depending on the specifications of the verify command, the range for comparison may extend beyond
the programmed data, and this may lead to an error in verification if “Fill with 0xFF” was not selected.
• Skip ID Code Verify
In general, do not select the checkbox when this feature is displayed as an option. However, use this
feature in cases of the following type.
The security settings of the MCU may make reading of the ID code impossible since the ID code in the
MCU is protected. This may lead to an error may occur in verification processing. To avoid errors of this
type, select this checkbox to use the feature.
For details, refer to section 5.8, Verification after Protecting the MCU.
(5) Checksum Type
Select the type of calculation when “Checksum” is selected for “Command”.
The available types of calculation differ according to the target MCU.
• Calculate block selection range
Applies to: RL78
When this option is selected
The range of calculation is limited to blocks that are selected in the [P.V] column on the [Block Settings]
tabbed page.
When this option is not selected
The result for the whole area of the flash memory is output.
R20UT4813EJ0200 Rev.2.00 Page 27 of 87
Apr.01.21
Loading...