Renesas PG-FP6 V1.06

PG-FP6 V1.06 Appendix A. Messages
R20UT4469EJ0800 Rev.8.00 Page 163 of 188
Oct.01.21
A.2 Error Messages Produced by the FP6 Main Unit
The following describes the error messages produced by the FP6 main unit. The first rows of the Message
column are messages displayed in the message display of the main unit. The second and subsequent rows
of the Message column are messages displayed in the FP6 Terminal.
No.
Message
Possible Workaround
001
Invalid PR5 data
The parameter file might not have been downloaded to the FP6, or the parameter file was
downloaded but is damaged. Download a correct parameter file to the FP6.
Invalid Parameter
File.
002
Not connected
The target device is manually connected. Enable automatic connection with the ‘autocon’
command or execute a ‘con’ command before the command that leads to this error.
No device
connected.
004
No response
The target device is not connected or is not responding. Check the connection to and
operating mode of the target device. Another possibility is disabling of connection by the
security functions of the target device. Refer to section 12.2, Problems during Operation.
The device is not
responding.
005
Not supported!
The command issued is not supported on the target device and thus cannot be used.
Check if the parameter file for the MCU to be connected has been downloaded to the FP6
main unit.
Not supported for
this device type.
006
Command
aborted!
The [Read] command has been canceled.
Cancel pressed,
command
aborted.
008
Parameter Error!
An illegal option was specified in the communications command. Refer to chapter 7, Usage
of Communications Commands, and specify a correct option.
Invalid argument.
009
HEX file Error!
The program file data downloaded to the FP6 may have been damaged. Download the
program file again.
HEX file contains
invalid data!!
012
Synchron. Failed
A failure in communications occurred while the FP6 was proceeding with connection to the
target device. Check the connection between the target device and the FP6. Slowing the
transfer rate may solve this problem.
Connection or
Synchronisation
failed.
013
Addr. Range err
The address given in the command exceeds the address range of the MCU.
014 RDY detect. fail The target device is not connected or is not responding. Check the connection to and
operating mode of the target device. Refer to section 12.2, Problems during Operation.
Connection or
Synchronisation
failed.
015 Freq. set failed Setting the frequency of the target device failed. Check if the oscillator frequency of the
target system matches the frequency specified in the FP6 Terminal, and if the frequency is
selectable for the MCU.
Connection or
Synchronisation
failed.
016 Baudrt. set fail Setting the baud rate of the target device failed. Check if the oscillator frequency of the
target system matches the frequency specified in the FP6 Terminal. The MCU may not
support the specified baud rate. Refer to the user’s manual of the MCU and specify a
supported baud rate.
Connection or
Synchronisation
failed.
017 ID code chk. err This error code and message are displayed when an ID code different from the security
code set in the target device is authenticated.
If you have forgotten the configured ID code, connection to the target device for serial
programming is basically disabled. However, erasure of the whole flash memory is enabled
as an exception in some target devices; for details, refer to the user’s manual of the target
device.
Security code
authentication
failed.