Renesas Flash Programmer

1. When an error produces the message ‘E3000105 There is no response from the device.’

2. When an error produces the message ‘E3000107 This device does not match the connection parameters.’

3. When an error produces the message ‘E4000003 A timeout error occurred.’

4. When the following errors occur while the tool is connected

5. When the following errors occur during communications

 

1. When an error produces the message ‘E3000105 There is no response from the device.’

Cause 1
 
  • The connection with the target system might be wrong.
Action 1
 
  1. Check that the connection with the target system is in accord with the recommended circuits shown in the user’s manual of the tool in use. Also check that all required pins of the tool have been connected.
  2. For the RL78 family, check that the EMVDD pins of the E1, E20, E2, or E2 Lite have been correctly connected.
  3.  
Cause 2
 
  • The operating mode of the target device might be wrong.
Action 2
 
  1. Refer to the user’s manual for the target device and check that all required mode pins are being handled correctly.
  2. For the RX family, check that the settings for I/O signals in the [Tool Details] dialog box match the wiring of the target system.
  3.  
Cause 3
 
  • The wrong MCU might be selected in the [Create New Project] dialog box.
Action 3
 
  • Select the same MCU as the target device.
  •  
Cause 4
 
  • The target device might not be receiving a clock signal.
Action 4
 
  • Check the clock supply on the target system.
  •  
Cause 5
 
  • Power might not be being supplied normally to the target device.
Action 5
 
  1. Check the power supply setting.
  2. If the power is being supplied from the tool in use, the power might not be sufficient. In such cases, supply power from the target system. Confirm that the supply of power on the target system is possible.
  3.  
Cause 6
 
  • The security functions of the target device may restrict the connection to the RFP.
Action 6
 
  • None. Change the target device if this is required.
  •  
Cause 7
 
  • The RFP may not be connected to the target device due to the compatibility with the host PC or the USB-to-serial converter.
Action 7
 
  1. We do not recommend the use of a USB-to-serial converter because it may cause delays in timing and data being lost due to the specifications of the converter. Check the operation of the USB-to-serial converter you are using. If timing is delayed or data are being lost, you may consider using a different USB-to-serial converter.
  2. report_problem Recommended product for use as a USB-to-serial converter: FT232R from FTDI
  3.  
Cause 8
 
  • The MCU may not have been reset.
Action 8
 
  • When the connection is through a COM port or USB Direct, the RFP does not control the reset pin of the MCU. Reset the MCU in advance when connecting with a target device. If the MCU has been started in boot mode by a power-on reset and connected or disconnected by the RFP, it must also be reset in advance when re-connecting with the target device.
  •  

2. When an error produces the message ‘E3000107 This device does not match the connection parameters.’

Cause 1
 
  • An attempt was made to connect a target device which differs from that when the project was created.
Action 1
 
  1. Create a new project or use the correct project with the target device.
  2.  
Cause 2
 
  • The memory structure might have been changed by the option settings of the target device.
Action 2
 
  1. When the MCU has a function that for changing the mapping of the flash memory, such as a dual-bank structure, the RFP recognizes the MCU as a different one before and after changes to the memory mapping. Accordingly, after a change to the memory mapping in the MCU, the error “E3000107 This device does not match the connection parameters.” will occur. In the RFP, create and change projects for use before and after changes to the memory mapping.
  2.  

3. When an error produces the message ‘E4000003 A timeout error occurred.’

Cause 1
 
  • The connection to the target system may be wrong.
Action 1
 
  1. Confirm that the connection to the target system is correct according to the recommended circuits shown in the user’s manual of the tool you are using.
  2. report_problem Good communications may not be possible if you are using a USB-to-serial converter or a self-made target cable for connection with a tool.
  3.  
Cause 2
 
  • Settings of the target system and RFP may not match.
Action 2
 
  1. Baud rate: Check the operating frequency of the target device to see if the baud rate exceeds the allowable communications rate and if the baud rate is appropriate.
  2. Clock settings: Check if the clock settings for the target device in the RFP match the actual clock of the target system.
  3.  
Cause 3
 
  • The target device might have been reset during communications.
Action 3
 
  1. Power supply of the target device: An internal reset might occur in the target device due to voltage fluctuations during communications with the RFP. Check that the power supply is free of problems.
  2. External reset: A reset might have been applied to the target device by an external reset circuit during communications with the RFP. Check that the reset circuit is free of problems.
  3.  
Cause 4
 
  • The settings of switches of the 20-pin to 14-pin conversion adapter (RTE0T00020KCA00000R) for the E2 emulator may be wrong.
Action 4
 
  1. Refer to the E2 emulator user’s manual and confirm that the settings of switches of the 20-pin to 14-pin conversion adapter for the E2 emulator are correct.
  2.  

4. When the following errors occur while the tool is connected

  • E3000203: An error occurred while connecting to the tool.
  • E3000204: An error occurred while communicating with the tool.
  • E3000205: An error occurred while updating the tool firmware.
  • E3000206: An error occurred while initializing the tool.
Action 1
 
  1. The tool you are using might have locked up. Try disconnecting and then reconnecting the USB cable.
Action 2
 
  1. The host PC might be unstable or the USB port might be broken. Restart the host PC or connect the tool to a USB port other than that you are trying to use.
Action 3
 
  1. On the E1, E20, or E2, the tool might be damaged. Refer to the user’s manual of the tool you are using and run the self-diagnostic test.
Action 4
 
  1. If the power is being supplied from the tool, the power might not be sufficient. In such cases, supply power from the target system.
  2.  

5. When the following errors occur during communications

  • E300010C: Received data from the device is corrupted.
  • E4000004: A framing error occurred while receiving data.
  • E4000005: A parity error occurred while receiving data.
  • E4000006: An overrun error occurred while receiving data.
  • E1000004: A transmission data error occurred in the device.
Action 1
 
  1. The setting of the target device might be wrong or communications might not be stable. Check the following items.
    • Check that there is no noise on the communications line.
    • Check that the tool in use is properly connected with the target system.
    • Check that unused pins are being handled correctly.
    • Confirm that the correct input clock and transfer rate are selected. Stable programming might be achieved by setting a lower value for the transfer rate.
  2. report_problem Good communications may not be possible if you are using a USB-to-serial converter, a self-made cable, a self-made extension cable, or the like for connection with a tool.
  3.  
Action 2
 
  1. When the RFP is connected to RL78/G10, G1M, G1N, G15, or G16 via the USB-to-serial converter, a parity error may occur due to the hardware. In such a situation, consider the use of another USB-to-serial converter.