Skip to main content

FP6 Terminal Error Guide

PG-FP6

1. When an error produces the message ‘ERROR: 004 No response’

2. When an error produces the message ‘023 Inv. Sig. addr.’

3. When an error produces the message ‘Communication failure or timeout’


 

1. When an error produces the message ‘ERROR: 004 No response’

Cause 1
 
  • The connection with the target system might be wrong.
Action 1
 
  1. Confirm that the connection with the target system is correct by referring to the PG-FP6, Renesas Flash Programmer Additional Document for User's Manual (Recommended Circuits for Connecting the Flash Programmer) (PDF | English, 日本語).
  2.  
Cause 2
 
  • The operating mode of the target device might be wrong.
Action 2
 
  • The FP6 is connected to the target device in boot mode or serial programming mode.
    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.
  •  
Cause 3
 
  • The wrong MCU might be selected in the [Create New Setting] dialog box.
    The wrong target device might be selected for the settings file.
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 FP6, 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 PG-FP6.
Action 6
 
  • None. Change the target device if this is required.
  •  

2. When an error produces the message ‘023 Inv. Sig. addr.’

Cause 1
 
  • An attempt was made to connect a target device which differs from that when the settings file was created.
Action 1
 
  1. Create a new settings file or use the correct settings file 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 FP6 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 “023 Inv. Sig. addr.” will occur. In the FP6, create and change settings files for use before and after changes to the memory mapping.
  2.  

3. When an error produces the message ‘Communication failure or timeout’

Cause 1
 
  • The connection to the target system may be wrong.
Action 1
 
  1. Confirm that the connection to the target system is correct by referring to the PG-FP6, Renesas Flash Programmer Additional Document for User's Manual (Recommended Circuits for Connecting the Flash Programmer) (PDF | English, 日本語).
  2.  
Cause 2
 
  • Settings of the target system and FP6 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 FP6 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 FP6. 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 FP6. Check that the reset circuit is free of problems.
  3.  
Cause 4
 
  • Communications between the FP6 and target device might not be stable.
Action 4
 
  1. Check that there is no noise on the communications line.
  2. report_problem Good communications may not be possible if you are using a self-made cable, a self-made extension cable, or the like for connection with a tool.
  3.