PG-FP6 V1.06 Appendix A. Messages
R20UT4469EJ0800 Rev.8.00 Page 168 of 188
Oct.01.21
An error occurred during execution of the ‘slb’ command. A block for which the lock bit has
already been set might be disabled in the target device. To disable the lock bit, do not use
the ‘slb’ command but erase the target block. Alternatively, it 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.
588 GOT Comm err An error occurred during execution of the ‘got’ command. This might be due to a problem
with communications between the FP6 and target device. Refer to section 12.2, Problems
during Operation.
failure or timeout.
589 GLB Comm err An error occurred during execution of the ‘glb’ command. This might be due to a problem
with communications between the FP6 and target device. Refer to section 12.2, Problems
during Operation.
failure or timeout.
590 IDC Comn err An error occurred during execution of the ‘idc’ command. The OCD ID of a V850E2 cannot
be overwritten. This problem may be resolved by selecting [Erase Chip] as the erasure
option and erasing the flash options. Alternatively, it might be due to a problem with
communications between the FP6 and target device. Refer to section 12.2, Problems
during Operation.
failure or timeout.
An error occurred during execution of the ‘opb’ command. The option bytes of a V850E2
cannot be overwritten. This problem may be resolved by selecting [Erase Chip] as the
erasure option and erasing the flash options. Alternatively, it 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.
592 OTP Comm err An error occurred during execution of the ‘otp’ command. A block which has already been
set as OTP might be disabled in the target device. The block once an OTP has been set
cannot be released. Alternatively, it might be due to a problem with communications
between the FP6 and target device. Refer to section 12.2, Problems during Operation.
failure or timeout.
An error occurred during execution of the ‘sid’ 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.
An error occurred during execution of the ‘sed’ 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.
An error occurred during execution of the ‘ged’ 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.
An error occurred during execution of the ‘spd’ 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.
An error occurred during execution of the ‘stm’ 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.
An error occurred during execution of the ‘gtm’ 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.
This error occurs when the security setting to prohibit connection has been made. The
serial programming function then cannot be used.
In some target devices, this error does not occur even if connection has been prohibited
but the 004 error occurs instead.
SPD is active.
603 SWAS Recover
err
An error occurred during execution of the ‘swas_recover’ command. This might be due to a
problem with communications between the FP6 and target device. Refer to section 12.2,
Problems during Operation.
failure or timeout.
To Next Page
Loading...
