Filter
Top Products
6 Troubleshooting
6.5 Can FoUSB information be transmitted to KD?
A written program using FoUSB cannot be debugged with KD. It is necessary to
download a program on KD again when executing debug using KD. Therefore, written
program information in flash area is not transmitted to KD30 (KD3083).
6.6 A communication error occurs when the KD starts. What is
the cause of this problem?
If a communication error occurs when the KD starts, check the following.
1) Whether the cables are properly connected and whether the power is turned on?
2) Whether the serial port you set in the KD’s Init dialog box is correct?
3) Whether the Status indicator (D4: Status) of USB Monitor board is blink?
4) Has CNVss pin on the target board been pulled down?
5) Is the target MCU ID code “all 00h” or “all FFh”?
In 3), when the Status indicator is not blinking, the firmware of USB MCU is erased or
damaged. When firmware is erased or damaged, FoUSB (Flash-over-USB) and KD
(KD30, KD3083) cannot be used.
In such a case, it is necessary to download firmware compulsorily to USB MCU. Please
refer to [6.4 FoUSB cannot operate Why?], in order to download firmware compulsorily to
USB MCU.
6.7 A communication error occurred when debugging the
program. What is the cause of this problem?
1) If a communication error occurs when debugging your program, initialize the system
following the procedure described below. This should help you restart debugging.
(1) Click the <OK> button in the error dialog box to close the KD.
(2) Start up the KD again.
(3) Download your program.
2) Check whether the data “0FF900h” or “0FFF900h” is set when transmitting/receiving
via UARTi in your program.
74