Skip to main content

FAQs No. 1000462


FAQ 1000462

Latest Updated:2011年6月 17日

Functions: E1 ; E20 ; Debugging Function ; Emulator ; Warnings & Errors ; Pin ;

When I start up the E1/E20 emulator (during the connection process), I get the following message and the connection fails. (Target MCU: R8C Family)

“A timeout error has occurred during the communication with the target MCU(FFWERR_AENTRY_TMOUT).The target MCU and the selected device do not match. Or,There may be a problem in the pin processing of the MCU etc. Or,The emulator may have gone wrong.”

The following are possible causes of this problem.

  1. The wire connection between the E1/E20 emulator and the target MCU is either incorrect or is not set up according to the recommended circuit specification.
    Please refer to the E1/E20 Additional Document for Users Manual issued for the target MCU.
    Communication problems between the emulator and MCU may occur if the recommended circuit wiring is not followed.
    Examples of non-recommended circuit wiring: 1. A serial resistor introduced in the transmission signal (waveform may lose its shape); 2. No pull-up resistance in wiring; 3. A capacitor is connected to the wiring.
  2. The target MCU is not operating normally.
    The E1/E20 emulator may malfunction if the target MCU itself is not operating normally.
    Possible causes are listed below. Note that not all MCUs have all the pins described here.
    1. MCU operating voltage is not within specified parameters.
      This indicates a connection failure at the IC socket on the user system to which the MCU is inserted. This could be due to use of a socket that is not recommended for the target MCU or the socket is not screwed on tight enough.
    2. Some of the of the 14-pin connector Vss (GND) pins on the E1/E20 emulator are not connected.
      Some of the connector Vss (GND) pins are not connected to the E1/E20’s ground. Even if a few Vss (GND) pins are not connected to ground, the ground level will be unstable, preventing the MCU from operating normally. Make sure all of the E1/E20 emulator’s Vss (GND) pins on the 14-pin connector are connected to the user system’s ground.
  3. The MCU connected to the user system and the MCU selected at the time the debugger was booted are different.
    Confirm the product name of the MCU selected at the time the debugger was booted.
  4. E1/E20 emulator is broken.
    Run a self-check to make sure the E1/E20 is not broken.

Was this information useful to you? Yes NO

Suitable Products
E1 [R0E000010KCE00]
E20 [R0E000200KCT00]

End of content

Back To Top