Tuning Wiki
Applies to

Check the hardware and software limits stated in this article.

Which version and operation?

NefMoto is an open-source tool for communicating with supported VW/Audi ME7 ECUs. These notes use the project's source revision a9b8350, published as v1.9.9.0-rc0, a pre-release. Earlier stable releases and other tools can differ in buttons, capabilities and recovery behaviour. Check the documentation for the version actually used. No connection or programming test by this wiki is implied.

Record the ECU identification and tool version, interface and driver, in-car or bench connection, protocol, and whether the operation concerns flash, an EEPROM mirror or a physical EEPROM. Confirm the actual connector and tool support with the relevant service and project documentation. Keep a verified original ECU read and a recovery plan appropriate to that unit.

Connection or programming failure?

SymptomWhat the project recommends checking
Adapter is absentDevice enumeration, driver, cable and whether the interface supports unmodified K-line pass-through. The cited release does not support Ross-Tech HEX-V2 or HEX-NET in that role.
Slow init failsConfirm the interface and connection, try the documented default slow-init settings, allow the specified interval between attempts, and examine the timing log. In-car K-line traffic and direct bench conditions differ.
Identification works but programming failsA successful identification session alone does not establish programming readiness. Check the ECU-specific supply, connection, session and layout requirements.

These checks are drawn from the project's getting-started guide and troubleshooting guide. Log a failure before changing settings; consult the fitted ECU's wiring information rather than transferring pin assignments from another variant.

Image size, layout and checksum are separate checks

In this release's flashing guide, the KWP workflow requires a selected flash layout; equal-capacity top-boot and bottom-boot chips place their small sectors differently. Matching a file's byte count alone does not establish the physical chip or the correct sector layout. A sampled mirror match is evidence of possible mirroring, not proof of chip size. Confirm the actual part and layout using appropriate evidence.

The same guide says Verify Checksums checks supported ME7 checksums in the loaded image; the tab does not provide a separate correction action. Read/write verification, image checksum validation and calibration correctness answer different questions. Use an independently supported correction and check process for the exact file where required. See ME7 reading, writing and checksums.

Recognise the RAM programming state

For the documented KWP process, identification containing THIS-IS-THE-RAM-PROGRAM indicates the ECU is running the programming kernel in RAM. The project notes that logging, fault-code access and engine start may not behave normally in that state. The text alone does not establish permanent ECU damage. NefMoto KWP2000 notes.

The project's instructions distinguish a completed write, after which it says to complete a power cycle before expecting normal flash operation, from a resumable aborted write, where it advises keeping power on and following its recovery procedure. Establish the actual operation and tool version before acting; do not generalise this ME7 guidance to another ECU family or a non-resumable fault.

A fault after programming

The project documents a programming-related flag that can cause P0602 or P1681 to recur on some of its supported software even after the visible fault list is cleared. Follow the exact tool and ECU procedure and investigate the underlying programming state; this does not establish the cause of every P0602/P1681. NefMoto P0602 guide.

For support, keep the session log around the first error together with the ECU, protocol, interface, layout and software version; remove personal information before sharing. Source: NefMoto contributors, troubleshooting, revision a9b8350; GPL-3.0-or-later.