[avant, acorde] 10C1: DEVICE RECV TIMEOUT 0F – Customer Support

1. Meaning of the Error

"DEVICE RECV TIMEOUT" is an error indicating that there is no response from the target microcomputer after waiting for a certain period of time. This occurs when the command sent from the programmer is not normally received by the target microcomputer (the target microcomputer cannot respond because it has not received the command), or the programmer cannot receive the response from the target microcomputer.

The 2-digit code at the end represents the process when the error occurred, and "0F" indicates that an error occurred during the initial communication.

- Specific examples of factors causing "DEVICE RECV TIMEOUT":

If there is a disconnection in the data transmission line (TTXD) or clock signal (TCK), even if the programmer sends a command/data, the target microcomputer will not respond because it has not received the data.
If there is a disconnection in the data receive signal (TRXD), the programmer cannot receive the response data even if the target microcomputer sends it.
If the mode terminal or reset signal of the microcomputer is not connected correctly, the microcomputer does not operate in the flash rewriting operation mode, so even if the target microcomputer receives a command from the programmer, it cannot return a response.

If writing 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

When the "DEVICE RECV TIMEOUT 0F" error occurs alone (no other errors appear), it is highly likely due to the following hardware factors since it is an error during the initial communication.

<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.
In the case of 1-wire UART communication, a large pull-up resistor may cause the rising waveform to become dull.
-> (Remedy Example)
- If the pull-up resistor on the target board is 10kΩ, add a 4.7kΩ pull-up resistor on the fixture.
- Depending on the specifications of the microcomputer, an appropriate pull-up resistor is around 1k to 4.7kΩ. The smaller the resistance value, the less the dullness of the rising waveform.

For other items to check regarding wiring, please refer to the FAQ at the link below.
[Reviewing the wiring of fixture equipment]

Bit corruption occurred due to the influence of sudden noise, resulting in abnormal transmited data.
- If this occurs simultaneously during other processes (the 2-digit code at the end is ERASE:01, PROGRAM:03, etc.) or with other error codes, the possibility of a sudden noise factor is high.
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.
[Noise countermeasures in programming equipment]

To isolate the presence or absence of a hardware failure, please replace the probe hardware (PHX400, etc.) or the programmer main unit (AFX100, AFX210, etc.) with a spare unit and check if the situation improves.

While using an older version does not necessarily cause an error, it is recommended to verify operation with the latest version when a problem occurs for isolation purposes.

Please check the version of the definition program and Micom Pack (parameter file) you are using. If you are using an older version, please update to the latest version and check the operation.
Please check the version of the firmware and FPGA of the main unit. If you are using an older version, please update to the latest version and check the operation.

For how to check the current versions and how to update, please refer to the FAQs at the links below.
[How to check the various versions of NETIMPRESS]
[How to update the main unit firmware / FPGA]

Related to

Related articles