EasyManua.ls Logo

Renesas PG-FP6 V1.06

Renesas PG-FP6 V1.06
188 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
PG-FP6 V1.06 Appendix A. Messages
R20UT4469EJ0800 Rev.8.00 Page 167 of 188
Oct.01.21
No.
Message
Possible Workaround
106
DLM Comm err.
An error occurred during execution of the ‘dlm’ command. This might be due to a problem
with communications between the FP6 and target device. If the same error occurs even if
you try the operation again, improve the connection environment between the FP6 and
MCU. Slowing the transfer rate may solve this problem.
DLM error.
(0xXX)
107 Require Authen A transition in the life cycle that requires authentication may have been made with the ‘pfo’
command. However, use the ‘dlm’ command in such cases ([DLM Transition] in the FP6
Terminal menu). Alternatively, execute the ‘ers_chip’ command ([Initialize device] in the
FP6 Terminal menu) to initialize the target device.
This operation
requires
authentication.
108 DLM Comm err. A transition in the life cycle by the target device failed. A state that does not allow
transitions from the current life cycle may have been specified. Acquire the flash options of
the target device and confirm that the state that can transit has been specified.
Cannot transition
to the specified
state from the
current state.
204 Not connected A ‘dcon’ command was issued when the target device was already disconnected from the
FP6.
No Device
connected.
210 Already conn. A ‘con’ command was issued when the target device was already connected to the FP6.
The FP6 target commands can be issued.
Device already
connected.
302 HEX range err The address range of the downloaded program file extends beyond the set address range.
Check the specified program file. When there is no problem even if data out of the range
have been included, deselect [Program File Size Monitor] in the [FP6 Options] dialog box.
HEX file exceeds
target device
flash range.
303 Invalid ID Tag The format of the ID Tag is not correct. Download the correct file.
For information on the ID Tag, refer to the Terminology table of this user’s manual.
Invalid ID Tag
400 Targ. power det. This error message is displayed when the FP6 should supply VCC power but VCC has
been detected as already being 0.2 V or higher in the target system before VCC is
supplied. Check VCC in the target system. If there is no problem with the target system,
the FP6 main unit might be damaged. Run a self-test. If this does not resolve the problem,
contact a Renesas Electronics sales representative or distributor.
Power failure.
402
FP6 int Vcc fail
The FP6 main unit might be damaged. Contact a Renesas Electronics sales representative
or distributor.
Power failure.
404
Targ. power fail
This error message is displayed when [VCC Monitor] is selected in the [FP6 Manager]
dialog box but the VCC voltage is outside the range of the VCC setting by ±5% just before
starting communication. Check VCC in the target system. If there is no problem with the
target system, the FP6 main unit might be damaged. Run a self-test. If this does not
resolve the problem, contact a Renesas Electronics sales representative or distributor.
Power failure.
405 Power failure An overcurrent was detected when VCC was output. Check the connection with the MCU
and VCC on the target system. If there is no problem with the target system, the FP6 main
unit might be damaged. Run a self-test. If this does not resolve the problem, contact a
Renesas Electronics sales representative or distributor.
Power failure.
407
Input Power fail.
The voltage of the USB and the power adapter is not correct. When the same error occurs
even after the connected PC or AC adapter is changed, the FP6 main unit might be
damaged. Contact a Renesas Electronics sales representative or distributor.
Power failure.
585 GOB Comm err An error occurred during execution of the ‘gob’ command. This might be due to a problem
with communications between the FP6 and target device. Refer to section 12.2, Problems
during Operation.
Communication
failure or timeout.
586 GID Comm err An error occurred during execution of the ‘gid’ command. This might be due to a problem
with communications between the FP6 and target device. Refer to section 12.2, Problems
during Operation.
Communication
failure or timeout.

Table of Contents

Related product manuals