1. Meaning of the Error
At the start of communication, the programmer reads the device ID,
confirms that it is a predetermined value, and then proceeds with
the process. The "UNEXPECTED MCU" error occurs when the read ID
turns out to be an unexpected value.
*Depending on the definition program, it may be output as
"1120 IDCODE MISMATCH" with the same error code, but the error
factors and countermeasures are the same.
confirms that it is a predetermined value, and then proceeds with
the process. The "UNEXPECTED MCU" error occurs when the read ID
turns out to be an unexpected value.
*Depending on the definition program, it may be output as
"1120 IDCODE MISMATCH" with the same error code, but the error
factors and countermeasures are the same.
If programming has not been successful even once (100% error rate),
please first check the following points, including whether the programmer
is set up correctly:
-
Make sure that the correct definition program and Micom Pack
are used for the target microcomputer. -
Check the manuals for the definition program and Micom Pack
to ensure that the parameter settings are correct according
to the conditions of your target board. -
Check the "Typical connection example" described in the manual
of the Micom Pack to ensure that it is correctly connected to the target.
2. Main Error Factors and Remedies
-
The correct Micom Pack suitable for the target microcomputer
is not used.
Example: If the read ID differs depending on the microcomputer type,
an error will be recognized as an unexpected ID has been read. -
Communication abnormality due to wiring problems, etc.
Since reading the ID is the very first communication performed,
there is a possibility that data transmission/reception itself cannot be
performed normally. Therefore, please check the following points.
<Contact Failure / Wiring Failure>
-
There is a problem with the wiring, such as poor contact of the probe pins
or connectors, or disconnection. -
When the wiring length of the fixture is long, or when a large series
resistor is inserted into the communication line on the target board,
the rising or falling waveform of the signal may become dull.
-> (Remedy Example)- Keep the wiring length of the fixture as short as possible.
- Try lowering the communication baud rate from 5Mbps to 2.5Mbps.
For other items to check regarding wiring, please refer to the FAQ at the link below. [FAQ: Reviewing the wiring of fixture equipment]
<Noise factors>
<Noise factors>
-
Overshoot or undershoot occurs at the rising or falling edge of the signal.
The waveform of the rising or falling edge of the signal may collapse and
affect communication due to the influence of the device's drive capability,
transmission line impedance matching, or signal reflection at connectors, etc.
-> (Remedy Example)- Add a damping resistor of several tens to 100Ω in series with the signal line.
- Add a pull-down resistor of around 1kΩ to the signal line.
-
When implementing these remedies, please select appropriate circuit
constants while checking the signal waveform.
For other noise countermeasures, please refer to the FAQ at the link below.
[FAQ: Noise countermeasures in programming equipment]
[FAQ: Noise countermeasures in programming equipment]