Renesas Flash Programmer Package V20401 Free
Renesas Flash Programmer Package V20401 Free
Renesas Flash Programmer Package V20401 Free
01
Release Note
R20UT3049EJ0100
Rev.1.00
Jul 01, 2014
Thank you for purchasing the Renesas Flash Programmer (hereafter referred to as RFP) software for programming flash
memory.
This document describes specifications that have been added or changed, restrictions, and cautions on using the RFP.
Also see the users manual of the RFP for cautions on using the RFP.
See the following documents for restrictions related to the target device.
Users manual of target device
Restriction notification document for target device
R20UT3049EJ0100 Rev.1.00
Jul 01, 2014
Page 1 of 18
Release Note
Item No.
RFP Version
<1>
V1.01.00
<2>
V1.01.01
<3>
V1.02.00
<4>
V1.03.00
Remark
V1.03.01
<5>
V2.00.00
V2.00.01
<6>
V2.01.00
<7>
V2.01.01
<8>
V2.03.00
<9>
V2.04.00
V2.04.01
On the menu bar, click Help, and then select Version Information.
R20UT3049EJ0100 Rev.1.00
Jul 01, 2014
Page 2 of 18
Release Note
2.1
No.
RL78
78K
<2>
<3>
<4>
<5>
<6>
<7>
<8>
<9>
V850
2
RL78
78K
V850
RL78
78K
V850
RX
Support of RX family
All
All
All
RX
RL78
78K
V850
10
All
11
RX
12
RX200
13
RX100
14
RX
15
RX
16
RX
17
RX100
RX200
18
All
19
RH850
RX64x
R20UT3049EJ0100 Rev.1.00
Jul 01, 2014
Page 3 of 18
No.
Microcontroller
20
RX
21
RX
22
All
23
All
24
All
25
RX
Release Note
Specifications
<1>
<2>
<3>
<4>
<5>
<6>
<7>
<8>
<9>
R20UT3049EJ0100 Rev.1.00
Jul 01, 2014
Page 4 of 18
2.2
Release Note
The COMx has been added to the Select Communication Interface dialog box. The
COMxVoltage: box has been added to the Setting Power Supply dialog box. It is a function
to program it as a flash programmer by using the serial port of PC (COM port).
Implementation: This item has been implemented in products with RFP V1.02.00 and later versions.
The HCUHEX files created using the HEX Consolidation Utility (HCU), which is used for
generating ROM code for ordering Renesas Electronics preprogrammed flash memory
devices, can now be read.
Implementation: This item has been implemented in products with RFP V1.02.00 and later versions.
The Program file size monitor function has been added to the Information Settings dialog
box. If this check box is selected, execution of the Program command is suspended if the
program file is larger than the area to be written to.
Implementation: This item has been implemented in products with RFP V1.02.00 and later versions.
The RX family is now supported. In addition, a correspondence version may change with
microcontrollers. Please refer to the available microcontroller list.
Implementation: This item has been implemented in products with RFP V1.03.00 and later versions.
No. 5 Addition of two types of writing operation windows (basic mode and full mode)
Microcontroller: All
Description:
Two types of writing operation windows (Basic and Full modes) have been added.
Implementation: This item has been implemented in products with RFP V2.00.00 and later versions.
Implementation: This item has been implemented in products with RFP V2.00.00 and later versions.
R20UT3049EJ0100 Rev.1.00
Jul 01, 2014
Page 5 of 18
Release Note
Implementation: This item has been implemented in products with RFP V2.00.00 and later versions.
[User Boot Area Option] has been added in the [Project Settings] dialog box. It is used to
specify whether or not to include the user boot area in the scope of erase.
Implementation: This item has been implemented in products with RFP V2.00.00 and later versions.
[Reset Pin as Low] has been added in the [Project Settings] dialog box.
Implementation: This item has been implemented in products with RFP V2.00.00 and later versions.
Implementation: This item has been implemented in products with RFP V2.01.00 and later versions.
Even after a saved workspace file is moved to a different folder, the file can be opened.
Implementation: This item has been implemented in products with RFP V2.01.00 and later versions.
Support for programming by the E1 or E20 emulator through the MCUs FINE pin has been
added.
Implementation: This item has been implemented in products with RFP V2.01.00 and later versions.
Support for programming by the E1 or E20 emulator through the MCUs FINE pin has been
added.
Implementation: This item has been implemented in products with RFP V2.01.01 and later versions.
R20UT3049EJ0100 Rev.1.00
Jul 01, 2014
Page 6 of 18
Release Note
In full mode, a function that merges data from all program files in a project for output as a
single program file has been added.
Implementation: This item has been implemented in products with RFP V2.03.00 and later versions.
Saving the ID code data in an ID code file instead of a project file is now possible.
Implementation: This item has been implemented in products with RFP V2.03.00 and later versions.
[Connect Option] has been deleted from the [Lock Bit] category in the [Project Settings] dialog
box.
Implementation: This item has been implemented in products with RFP V2.03.00 and later versions.
When FINE is selected as the connection method, the [Mode Pin At Disconnection] category
in the [Project Settings] dialog box is now enabled.
Implementation: This item has been implemented in products with RFP V2.03.00 and later versions.
The 32-bit and 64-bit editions of Windows 8.1 are now supported. Windows XP is no longer
supported.
Implementation: This item has been implemented in products with RFP V2.04.00 and later versions.
The RH850 family and RX64x group are now supported. In addition, a correspondence
version may change with microcontrollers. Please refer to the available microcontroller list.
Implementation: This item has been implemented in products with RFP V2.04.00 and later versions.
No. 20 Change in specifications regarding result codes for the script command to perform blank checking
Microcontroller: RX
Description:
Specifications were changed so that the result code 1 is returned instead of 0 when
data/userboot is specified for an MCU which has neither a data area nor a user boot area in
response to the script command to perform blank checking.
Implementation: This item has been implemented in products with RFP V2.04.00 and later versions.
R20UT3049EJ0100 Rev.1.00
Jul 01, 2014
Page 7 of 18
Release Note
Functions to specify Lock each block, Lock the area, and Unlock the area have been
added as ways to specify the lock bits. Double clicking on an area name in the [Block Locking]
dialog box changes the way to specify the lock bits.
Implementation: This item has been implemented in products with RFP V2.04.00 and later versions.
Note
When unique code embedding does not proceed for the specified index
, the specifications
were changed so that the next index is not specified. This is in contrast to the former
specifications, in which it was specified.
Note: For example, unique code embedding does not proceed when the area for embedding a
unique code is different from the area for writing a program file.
Implementation: This item has been implemented in products with RFP V2.04.00 and later versions.
A confirmation dialog box was displayed on connection of an E1 or E20 when updating of the
firmware was required. The specifications have been changed so that the firmware is
automatically updated without displaying a confirmation dialog box.
Implementation: This item has been implemented in products with RFP V2.04.00 and later versions.
No. 24 Change in the specifications regarding the log file format of the script execution function
Microcontroller: All
Description:
The RFP version and the folder information for the script and work space files have been
added to the log file format for the script execution function.
Implementation: This item has been implemented in products with RFP V2.04.00 and later versions.
An [Address] tabbed page has been added to the [Erase] dialog box.
Implementation: This item has been implemented in products with RFP V2.04.00 and later versions.
R20UT3049EJ0100 Rev.1.00
Jul 01, 2014
Page 8 of 18
Release Note
Chapter 3 Restrictions
3.1
Restriction List
No.
Microcontroller
RL78/G13
V850ES/Jx3
V850ES/Sx3
RL78
78K
Restrictions
<2>
<3>
<4>
<5>
<6>
<7>
<8>
<9>
V850
4
RX
RL78
78K
V850
6
RL78
All
RX
RX
10
RX
11
RX
Restriction on connection of an
emulator other than E1 or E20
12
RX
13
RX
14
RL78/G10
RL78/G12
15
RX100
16
All
17
RX200
RX600
18
RX100
R20UT3049EJ0100 Rev.1.00
Jul 01, 2014
Page 9 of 18
No.
Microcontroller
19
RL78
78K
V850
Release Note
Restrictions
Restriction caused by "Unknown
error occurred" while a command is
being executed
<1>
<2>
<3>
<4>
<5>
<6>
<7>
<8>
<9>
R20UT3049EJ0100 Rev.1.00
Jul 01, 2014
Page 10 of 18
3.2
Release Note
Restriction Details
No. 1 Restriction that cannot release security setting
Microcontroller: The RL78/G13 group with no data flash memory (product type R5F101*****)
Description: Even if the flash memories of the MCUs for which security settings have been made are erased in
the Chip mode, the settings cannot be canceled. So if write protection has been enabled by
security settings, it cannot be disabled.
Workaround: To avoid this problem, do not enable write protection by using security settings. If write protection
is enabled in your MCU, disable it by the PG-FP5 flash memory programmer; then reprogram
flash memory.
Action:
This issue has been corrected in products with RFP V1.02.00 and later versions.
This issue has been corrected in products with RFP V1.03.00 and later versions.
No. 3 Restriction about choosing a HCUHEX file and changing a HEX file
Microcontroller: RL78, 78K, V850
Description: If choosing a HCUHEX file and changing a HEX file, the setting item which can be changed in a
[List of Settings] Dialog cannot be changed.
Workaround: [List of Settings] Dialog is closed with a Cancel button, and is opened again.
Action:
This issue has been corrected in products with RFP V2.00.00 and later versions.
Create a workspace file, A.rws in Basic mode and a workspace file, B.rws in Full mode.
(2)
(3)
Point to [File], [Create New Workspace], and then open [Create New Workspace] dialog and
click Cancel button to close.
(4)
This issue has been corrected in products with RFP V2.01.00 and later versions.
R20UT3049EJ0100 Rev.1.00
Jul 01, 2014
Page 11 of 18
Release Note
No. 5 Restriction that invalidates items in which HCUHEX file is specified on the first priority
Microcontroller: RL78, 78K, V850
Description: HCUHEX file is not specified on the first priority in items and items operate in inappropriate way
when conducting following operations.
<Invalid operation 1>
(1)
(2)
(3)
The project setting in Basic mode is able to use in Full mode by shifting the mode from the
Basic to the Full. However, settings which are applied by reading HCUHEX file are not
applied.
(2)
(3)
(4)
After opening [Project Settings] dialog box in Basic mode and then click Cancel button to
close, re-open [Project Settings] dialog box.
(5)
[Project Setting] edited at (2) is shown, This setting is applied clicking Complete button.
(2)
(3)
(4)
Workaround:Do not change the Basic or Full mode in using HCUHEX. Have HCUHEX file read again when
using HCUHEX file together with HEX file, before commands execution.
Action:
In planning.
This issue has been corrected in products with RFP V2.03.00 and later versions.
R20UT3049EJ0100 Rev.1.00
Jul 01, 2014
Page 12 of 18
Release Note
In planning.
This issue has been corrected in products with RFP V2.01.00 and later versions.
R20UT3049EJ0100 Rev.1.00
Jul 01, 2014
Page 13 of 18
Release Note
R20UT3049EJ0100 Rev.1.00
Jul 01, 2014
Page 14 of 18
Release Note
This issue has been corrected in products with RFP V2.01.00 and later versions.
This issue has been corrected in products with RFP V2.03.00 and later versions.
R20UT3049EJ0100 Rev.1.00
Jul 01, 2014
Page 15 of 18
Release Note
This issue has been corrected in products with RFP V2.01.00 and later versions.
This issue has been corrected in products with RFP V2.03.00 and later versions.
No. 13 Restriction with Display of Mode Pins at Disconnection Category while Programming
Microcontroller: RX
Description: In a project created under the conditions described in a), if the Tool list box for the project is
switched to E1 or E20, the Mode Pins at Disconnection category on the Other Settings tab in
Project Settings window is not shown.
a) This problem arises if the following conditions are all satisfied:
(1) RX is selected in the Using Target Microcontroller list box.
(2) COMx or USB Direct is selected in the Tool list box.
Workaround: On the File menu in the menu bar, select Open a workspace command so that the workspace file
can be reopened.
Action:
This issue has been corrected in products with RFP V2.03.00 and later versions.
R20UT3049EJ0100 Rev.1.00
Jul 01, 2014
Page 16 of 18
Release Note
No. 14 Restriction with Connecting Target System to Host PC via COMx Port
Microcontroller: RL78/G10, RL78/G12 (The reset pin can be used for other functions than reset.)
Description: Suppose that the program file where the PORTSELB value of the option byte 000C1H is 0 is
written to an MCU, and the COMx port of the host PC is used to connect the target system with the
PC. If any command is executed in the above MCU, the following errors arise and the MCU
cannot enter to the Flash Memory Programming mode:
- Error (E1000001): COMx communication time out.
- Error (E1002004): Communication failure or timeout.
Workaround: If you connect the target system to the COMx port of the host PC, do not write to the MCU any
program file where the PORTSELB value of the option byte 000C1H is 0. Otherwise, do not use
the COMx port but connect the E1 or E20 emulator via a USB cable.
Action:
This issue has been corrected in products with RFP V2.03.00 and later versions.
This issue has been corrected in products with RFP V2.03.00 and later versions.
No. 16 Restriction about starting programmer after double clicking a workspace file
Microcontroller: All
Description: If a work space file double-click with host PC which installed the RFP version V2.01.00 after
installing V2.00.00 or V2.00.01, originally, the main window of the version installed recently opens.
However, the main window of V2.00.00 or V2.00.01 opens.
Workaround: Open a work space file by the following method.
- Dragging and dropping a workspace file onto RFP.exe.
- Typing RFP.exe followed by the name of a workspace file at the command prompt and so on;
then executing it.
Action:
This issue has been corrected in products with RFP V2.01.01 and later versions.
R20UT3049EJ0100 Rev.1.00
Jul 01, 2014
Page 17 of 18
Release Note
This issue has been corrected in products with RFP V2.03.00 and later versions.
This issue has been corrected in products with RFP V2.03.00 and later versions.
No. 19 Restriction caused by "Unknown error occurred" while a command is being executed
Microcontroller: RL78, 78K, V850
Description: In some cases the output panel will indicate that an error has occurred while a program or verify
command is being executed. As a result, the status bar displays ERROR.
Workaround: Restart the RFP and execute the command again.
Action:
This issue has been corrected in products with RFP V2.03.00 and later versions.
All trademarks and registered trademarks are the property of their respective owners.
R20UT3049EJ0100 Rev.1.00
Jul 01, 2014
Page 18 of 18
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 of these circuits, software, and information in the design of your equipment. Renesas Electronics assumes no responsibility for any losses incurred by you or third parties arising from the
use of these circuits, software, or information.
2.
Renesas Electronics has used reasonable care in preparing the information included in this document, but Renesas Electronics does not warrant that such information is error free. Renesas Electronics
assumes no liability whatsoever for any damages incurred by you resulting from errors in or omissions from the information included herein.
3.
Renesas Electronics does not assume any liability for infringement of 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. 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 should not alter, modify, copy, or otherwise misappropriate any Renesas Electronics product, whether in whole or in part. Renesas Electronics assumes no responsibility for any losses incurred by you or
third parties arising from such alteration, modification, copy or otherwise misappropriation of Renesas Electronics product.
5.
Renesas Electronics products are classified according to the following two quality grades: "Standard" and "High Quality". The recommended 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 electronic appliances; machine tools; personal electronic
equipment; and industrial robots etc.
"High Quality": Transportation equipment (automobiles, trains, ships, etc.); traffic control systems; anti-disaster systems; anti-crime systems; and safety equipment etc.
Renesas Electronics products are neither intended nor 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 damages (nuclear reactor control systems, military equipment etc.). You must check the quality grade of each Renesas Electronics product before using it
in a particular application. You may not use any Renesas Electronics product for any application for which it is not intended. Renesas Electronics shall not be in any way liable for any damages or losses
incurred by you or third parties arising from the use of any Renesas Electronics product for which the product is not intended by Renesas Electronics.
6.
You should use the Renesas Electronics products described in this document within the range specified by Renesas Electronics, especially with respect to the maximum rating, operating supply voltage
range, movement power voltage range, heat radiation characteristics, installation and other product characteristics. Renesas Electronics shall have no liability for malfunctions or damages arising out of the
use of Renesas Electronics products beyond such specified ranges.
7.
Although Renesas Electronics endeavors to improve the quality and reliability of its products, semiconductor products have specific characteristics such as the occurrence of failure at a certain rate and
malfunctions under certain use conditions. Further, Renesas Electronics products are not subject to radiation resistance design. Please be sure to implement safety measures to guard them against the
possibility of physical injury, and injury or damage caused by fire in the event of the failure of a Renesas Electronics product, 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,
please evaluate the safety of the final products or systems manufactured by you.
8.
Please contact a Renesas Electronics sales office for details as to environmental matters such as the environmental compatibility of each Renesas Electronics product. Please use Renesas Electronics
products in compliance with all applicable laws and regulations that regulate the inclusion or use of controlled substances, including without limitation, the EU RoHS Directive. Renesas Electronics assumes
no liability for damages or losses occurring as a result of your noncompliance with applicable laws and regulations.
9.
Renesas Electronics products and technology may 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 should not use Renesas Electronics products or technology described in this document for any purpose relating to military applications or use by the military, including but not limited to the
development of weapons of mass destruction. When exporting the Renesas Electronics products or technology described in this document, you should comply with the applicable export control laws and
regulations and follow the procedures required by such laws and regulations.
10. It is the responsibility of the buyer or distributor of Renesas Electronics products, who distributes, disposes of, or otherwise places the product with a third party, to notify such third party in advance of the
contents and conditions set forth in this document, Renesas Electronics assumes no responsibility for any losses incurred by you or third parties as a result of unauthorized use of Renesas Electronics
products.
11. This document may not be reproduced or duplicated in any form, in whole or in part, without prior written consent of Renesas Electronics.
12. Please contact a Renesas Electronics sales office if you have any questions regarding the information contained in this document or Renesas Electronics products, or if you have any other inquiries.
(Note 1)
"Renesas Electronics" as used in this document means Renesas Electronics Corporation and also includes its majority-owned subsidiaries.
(Note 2)
"Renesas Electronics product(s)" means any product developed or manufactured by or for Renesas Electronics.
SALES OFFICES
http://www.renesas.com
2014 Renesas
Electronics
Corporation.
All rights
reserved.
2014 Renesas
Electronics
Corporation
and Renesas
Solutions
Corp.
Colophon
Colophon4.0
4.0