Print Page - Flashing issues, Nothing seems to work!

Title: Flashing issues, Nothing seems to work!
Post by: AmIdYfReAk on March 01, 2011, 10:34:04 PM

Hello all,

I've tried to get 3 ECU's of mine to read Via Nefmoto, but i always hit the same wall when trying to validate the memory.

They're all IMMO defeated, They're 06a 906 032 LP, HS and HF ECUs

The only thing that i can think of listing, Tried it both on my laptop and desktop, Both windows 7. The Desktop is 64-bit, while the laptop is 32.
The cable is the Silver cable, Blue OBD e-bay dumb cable.

Heres the Log.

Code:

01/Mar/2011 11:11:17.025: LOG: Opened FTDI device.
01/Mar/2011 11:11:17.026: LOG: FTDI device info - Description: USB <-> Serial Serial Number:  Device Type: FT_DEVICE_BM Device ID: 0x4036001 Device Flags: 0x0
01/Mar/2011 11:11:17.027: LOG: FTDI ChipID DLL is loaded, checking chip ID...
01/Mar/2011 11:11:17.027: LOG: Unable to read FTDI device chip ID
01/Mar/2011 11:11:17.086: LOG: Starting send receive thread.
01/Mar/2011 11:11:17.091: LOG: Send receive thread now started.
01/Mar/2011 11:11:17.092: USER: Disconnected
01/Mar/2011 11:11:17.115: LOG: Set timing parameters to defaults.
01/Mar/2011 11:11:17.117: USER: Connection attempt number 1.
01/Mar/2011 11:11:17.118: USER: Connecting...
01/Mar/2011 11:11:17.139: LOG: Set timing parameters to defaults.
01/Mar/2011 11:11:17.142: USER: Starting slow init connection.
01/Mar/2011 11:11:17.446: USER: Connecting to address 0x01.
01/Mar/2011 11:11:19.610: USER: Slow init succeeded.
01/Mar/2011 11:11:19.611: USER: Switching to KWP1281 session.
01/Mar/2011 11:11:19.792: LOG: KWP1281 read block
01/Mar/2011 11:11:19.856: LOG: KWP1281 sent block
01/Mar/2011 11:11:20.184: LOG: KWP1281 read block
01/Mar/2011 11:11:20.248: LOG: KWP1281 sent block
01/Mar/2011 11:11:20.426: LOG: KWP1281 read block
01/Mar/2011 11:11:20.490: LOG: KWP1281 sent block
01/Mar/2011 11:11:20.636: LOG: KWP1281 read block
01/Mar/2011 11:11:20.700: LOG: KWP1281 sent block
01/Mar/2011 11:11:20.738: LOG: KWP1281 read block
01/Mar/2011 11:11:20.802: LOG: KWP1281 sent block
01/Mar/2011 11:11:20.802: USER: KWP1281 connect info: ?6A906032LP 1.8L R4/5VT     G   0007 :? B
01/Mar/2011 11:11:22.411: USER: Connecting to address 0x01.
01/Mar/2011 11:11:24.568: USER: Slow init succeeded.
01/Mar/2011 11:11:24.570: USER: Switching to KWP2000 session.
01/Mar/2011 11:11:24.873: LOG: Sent message with service ID StartCommunication
01/Mar/2011 11:11:24.915: LOG: Received message with service ID StartCommunicationPositiveResponse
01/Mar/2011 11:11:24.915: USER: Connected
01/Mar/2011 11:11:27.432: LOG: Sent message with service ID TesterPresent
01/Mar/2011 11:11:27.467: LOG: Received message with service ID TesterPresentPositiveReponse
01/Mar/2011 11:11:29.982: LOG: Sent message with service ID TesterPresent
01/Mar/2011 11:11:30.022: LOG: Received message with service ID TesterPresentPositiveReponse
01/Mar/2011 11:11:32.537: LOG: Sent message with service ID TesterPresent
01/Mar/2011 11:11:32.576: LOG: Received message with service ID TesterPresentPositiveReponse
01/Mar/2011 11:11:33.935: USER: Disabling Windows sleep mode.
01/Mar/2011 11:11:33.938: USER: Validating memory layout.
01/Mar/2011 11:11:33.947: USER: Reading ECU identification option: calibrationEquipmentSoftwareNumber
01/Mar/2011 11:11:33.966: LOG: Sent message with service ID ReadECUIdentification
01/Mar/2011 11:11:34.010: LOG: Received message with service ID ReadECUIdentificationPositiveResponse
01/Mar/2011 11:11:34.019: USER: Read ECU identification option with unknown scaling record.
01/Mar/2011 11:11:34.021: USER: Successfully read ECU identification information
01/Mar/2011 11:11:34.025: USER: ECU reports programming session preconditions have been met.
01/Mar/2011 11:11:34.028: USER: Requesting security access.
01/Mar/2011 11:11:34.088: LOG: Sent message with service ID SecurityAccess
01/Mar/2011 11:11:34.128: LOG: Received message with service ID NegativeResponse
01/Mar/2011 11:11:34.128: LOG: Received negative response for service ID: SecurityAccess, with response code: ServiceNotSupported
01/Mar/2011 11:11:34.130: USER: ECU reports that security access is not supported.
01/Mar/2011 11:11:34.132: LOG: Starting diagnostic session type: ProgrammingSession
01/Mar/2011 11:11:34.132: USER: Starting diagnostic session.
01/Mar/2011 11:11:34.209: LOG: Sent message with service ID StartDiagnosticSession
01/Mar/2011 11:11:34.248: LOG: Received message with service ID NegativeResponse
01/Mar/2011 11:11:34.248: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
01/Mar/2011 11:11:34.288: LOG: Received message with service ID NegativeResponse
01/Mar/2011 11:11:34.288: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
01/Mar/2011 11:11:34.328: LOG: Received message with service ID NegativeResponse
01/Mar/2011 11:11:34.328: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
01/Mar/2011 11:11:34.367: LOG: Received message with service ID NegativeResponse
01/Mar/2011 11:11:34.367: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
01/Mar/2011 11:11:34.409: LOG: Received message with service ID NegativeResponse
01/Mar/2011 11:11:34.409: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
01/Mar/2011 11:11:44.425: LOG: Sent message with service ID TesterPresent
01/Mar/2011 11:11:44.528: LOG: Message received no replies.
01/Mar/2011 11:11:44.528: LOG: Resending message. Send attempts: 2
01/Mar/2011 11:11:44.540: LOG: Sent message with service ID TesterPresent
01/Mar/2011 11:11:44.643: LOG: Message received no replies.
01/Mar/2011 11:11:44.643: LOG: Resending message. Send attempts: 3
01/Mar/2011 11:11:44.655: LOG: Sent message with service ID TesterPresent
01/Mar/2011 11:11:44.758: LOG: Message received no replies.
01/Mar/2011 11:11:44.758: LOG: Failed to send message 3 times, message send failed.
01/Mar/2011 11:11:44.758: USER: Disconnecting because no response was received for the Tester Present message.
01/Mar/2011 11:11:44.761: USER: Disconnected
01/Mar/2011 11:11:44.766: USER: 100% complete.
01/Mar/2011 11:11:44.768: USER: Validating memory layout failed.
01/Mar/2011 11:11:44.773: LOG: Closing FTDI device.
01/Mar/2011 11:11:44.794: LOG: Send receive thread now terminated.

anyone have any ideas?

Title: Re: Flashing issues, Nothing seems to work!
Post by: Tony@NefMoto on March 01, 2011, 11:34:19 PM

Are you using the new version 1.7.0.0 of the NefMoto ECU Flasher?

You could try this latency fix:
http://www.nefariousmotorsports.com/forum/index.php?topic=409.0

Did you try a fast init in addition to the slow init?

It appears as though the ECU no longer responds after trying to start the programming session.

Title: Re: Flashing issues, Nothing seems to work!
Post by: kls on March 02, 2011, 04:52:51 AM

Are they running stock software or are they tuned?

Title: Re: Flashing issues, Nothing seems to work!
Post by: AmIdYfReAk on March 04, 2011, 08:14:36 PM

Sorry about the Long delay in a reply.

To answer the questions, I've got this error no matter what release of software I've tried. ( starting at 1.5X ), Everything is done in Slow, Fast wont connect to the ECU.

I'll try that patch/Fix tonight and report back.

The Ecu's are Stock as far as i know, Unless three junkyard ECU's are all tuned :)

Title: Re: Flashing issues, Nothing seems to work!
Post by: AmIdYfReAk on March 04, 2011, 08:46:10 PM

Ah, now that i've started up my other computer, I've already done that.

Here is a new log, showing fastinit

Code:

04/Mar/2011 09:42:05.901: LOG: Closing NefMoto VW Audi ME7 ECU Flasher BETA 1.7.0.0
04/Mar/2011 09:43:01.827: LOG: Opening NefMoto VW Audi ME7 ECU Flasher BETA 1.7.0.0
04/Mar/2011 09:43:02.010: LOG: Cannot load license file, file does not exist.
04/Mar/2011 09:43:02.202: LOG: Opened NefMoto VW Audi ME7 ECU Flasher BETA 1.7.0.0
04/Mar/2011 09:43:12.707: LOG: Opened FTDI device.
04/Mar/2011 09:43:12.708: LOG: FTDI device info - Description: USB <-> Serial Serial Number:  Device Type: FT_DEVICE_BM Device ID: 0x4036001 Device Flags: 0x0
04/Mar/2011 09:43:12.708: LOG: FTDI ChipID DLL is loaded, checking chip ID...
04/Mar/2011 09:43:12.709: LOG: Unable to read FTDI device chip ID
04/Mar/2011 09:43:12.767: LOG: Starting send receive thread.
04/Mar/2011 09:43:12.773: LOG: Send receive thread now started.
04/Mar/2011 09:43:12.775: USER: Disconnected
04/Mar/2011 09:43:12.799: LOG: Set timing parameters to defaults.
04/Mar/2011 09:43:12.801: USER: Connection attempt number 1.
04/Mar/2011 09:43:12.802: USER: Connecting...
04/Mar/2011 09:43:12.823: LOG: Set timing parameters to defaults.
04/Mar/2011 09:43:12.827: USER: Starting slow init connection.
04/Mar/2011 09:43:13.130: USER: Connecting to address 0x01.
04/Mar/2011 09:43:15.302: USER: Slow init succeeded.
04/Mar/2011 09:43:15.304: USER: Switching to KWP1281 session.
04/Mar/2011 09:43:15.484: LOG: KWP1281 read block
04/Mar/2011 09:43:15.548: LOG: KWP1281 sent block
04/Mar/2011 09:43:15.876: LOG: KWP1281 read block
04/Mar/2011 09:43:15.940: LOG: KWP1281 sent block
04/Mar/2011 09:43:16.116: LOG: KWP1281 read block
04/Mar/2011 09:43:16.182: LOG: KWP1281 sent block
04/Mar/2011 09:43:16.328: LOG: KWP1281 read block
04/Mar/2011 09:43:16.392: LOG: KWP1281 sent block
04/Mar/2011 09:43:16.428: LOG: KWP1281 read block
04/Mar/2011 09:43:16.494: LOG: KWP1281 sent block
04/Mar/2011 09:43:16.495: USER: KWP1281 connect info: ?6A906032LP 1.8L R4/5VT     G   0007 :? B
04/Mar/2011 09:43:18.003: USER: Connecting to address 0x01.
04/Mar/2011 09:43:20.149: USER: Slow init succeeded.
04/Mar/2011 09:43:20.151: USER: Switching to KWP2000 session.
04/Mar/2011 09:43:20.452: LOG: Sent message with service ID StartCommunication
04/Mar/2011 09:43:20.495: LOG: Received message with service ID StartCommunicationPositiveResponse
04/Mar/2011 09:43:20.495: USER: Connected
04/Mar/2011 09:43:23.012: LOG: Sent message with service ID TesterPresent
04/Mar/2011 09:43:23.049: LOG: Received message with service ID TesterPresentPositiveReponse
04/Mar/2011 09:43:24.245: USER: Disabling Windows sleep mode.
04/Mar/2011 09:43:24.249: USER: Validating memory layout.
04/Mar/2011 09:43:24.260: USER: Reading ECU identification option: calibrationEquipmentSoftwareNumber
04/Mar/2011 09:43:24.279: LOG: Sent message with service ID ReadECUIdentification
04/Mar/2011 09:43:24.320: LOG: Received message with service ID ReadECUIdentificationPositiveResponse
04/Mar/2011 09:43:24.328: USER: Read ECU identification option with unknown scaling record.
04/Mar/2011 09:43:24.329: USER: Successfully read ECU identification information
04/Mar/2011 09:43:24.332: USER: ECU reports programming session preconditions have been met.
04/Mar/2011 09:43:24.333: USER: Requesting security access.
04/Mar/2011 09:43:24.399: LOG: Sent message with service ID SecurityAccess
04/Mar/2011 09:43:24.438: LOG: Received message with service ID NegativeResponse
04/Mar/2011 09:43:24.438: LOG: Received negative response for service ID: SecurityAccess, with response code: ServiceNotSupported
04/Mar/2011 09:43:24.440: USER: ECU reports that security access is not supported.
04/Mar/2011 09:43:24.442: LOG: Starting diagnostic session type: ProgrammingSession
04/Mar/2011 09:43:24.442: USER: Starting diagnostic session.
04/Mar/2011 09:43:24.519: LOG: Sent message with service ID StartDiagnosticSession
04/Mar/2011 09:43:24.558: LOG: Received message with service ID NegativeResponse
04/Mar/2011 09:43:24.558: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
04/Mar/2011 09:43:24.598: LOG: Received message with service ID NegativeResponse
04/Mar/2011 09:43:24.598: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
04/Mar/2011 09:43:24.638: LOG: Received message with service ID NegativeResponse
04/Mar/2011 09:43:24.638: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
04/Mar/2011 09:43:24.680: LOG: Received message with service ID NegativeResponse
04/Mar/2011 09:43:24.680: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
04/Mar/2011 09:43:24.720: LOG: Received message with service ID NegativeResponse
04/Mar/2011 09:43:24.720: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
04/Mar/2011 09:43:34.736: LOG: Sent message with service ID TesterPresent
04/Mar/2011 09:43:34.839: LOG: Message received no replies.
04/Mar/2011 09:43:34.839: LOG: Resending message. Send attempts: 2
04/Mar/2011 09:43:34.851: LOG: Sent message with service ID TesterPresent
04/Mar/2011 09:43:34.954: LOG: Message received no replies.
04/Mar/2011 09:43:34.954: LOG: Resending message. Send attempts: 3
04/Mar/2011 09:43:34.966: LOG: Sent message with service ID TesterPresent
04/Mar/2011 09:43:35.069: LOG: Message received no replies.
04/Mar/2011 09:43:35.069: LOG: Failed to send message 3 times, message send failed.
04/Mar/2011 09:43:35.069: USER: Disconnecting because no response was received for the Tester Present message.
04/Mar/2011 09:43:35.071: USER: Disconnected
04/Mar/2011 09:43:35.077: USER: 100% complete.
04/Mar/2011 09:43:35.079: USER: Validating memory layout failed.
04/Mar/2011 09:43:35.082: LOG: Closing FTDI device.
04/Mar/2011 09:43:35.092: LOG: Send receive thread now terminated.
04/Mar/2011 09:43:38.022: USER: Restoring Windows sleep mode.
04/Mar/2011 09:43:42.024: USER: Switching to KWP2000 session.
04/Mar/2011 09:43:42.071: LOG: Opened FTDI device.
04/Mar/2011 09:43:42.071: LOG: FTDI device info - Description: USB <-> Serial Serial Number:  Device Type: FT_DEVICE_BM Device ID: 0x4036001 Device Flags: 0x0
04/Mar/2011 09:43:42.071: LOG: FTDI ChipID DLL is loaded, checking chip ID...
04/Mar/2011 09:43:42.071: LOG: Unable to read FTDI device chip ID
04/Mar/2011 09:43:42.120: LOG: Starting send receive thread.
04/Mar/2011 09:43:42.120: LOG: Send receive thread now started.
04/Mar/2011 09:43:42.121: USER: Disconnected
04/Mar/2011 09:43:42.144: LOG: Set timing parameters to defaults.
04/Mar/2011 09:43:42.145: USER: Connection attempt number 1.
04/Mar/2011 09:43:42.147: USER: Connecting...
04/Mar/2011 09:43:42.168: LOG: Set timing parameters to defaults.
04/Mar/2011 09:43:42.170: USER: Starting fast init connection.
04/Mar/2011 09:43:42.171: USER: Connecting to address 0x01.
04/Mar/2011 09:43:42.575: LOG: Sent message with service ID StartCommunication
04/Mar/2011 09:43:42.577: LOG: Idle end: 325ms Low end: 350ms High end: 375ms Message Send Time: 375ms
04/Mar/2011 09:43:42.577: USER: Fast init succeeded, sending start communication request.
04/Mar/2011 09:43:42.678: LOG: Message received no replies.
04/Mar/2011 09:43:42.678: LOG: Failed to send message 1 times, message send failed.
04/Mar/2011 09:43:42.678: USER: Disconnected
04/Mar/2011 09:43:42.700: LOG: Set timing parameters to defaults.
04/Mar/2011 09:43:42.703: USER: Connection attempt number 2.
04/Mar/2011 09:43:42.704: USER: Connecting...
04/Mar/2011 09:43:42.726: LOG: Set timing parameters to defaults.
04/Mar/2011 09:43:42.727: USER: Starting fast init connection.
04/Mar/2011 09:43:42.730: USER: Connecting to address 0x01.
04/Mar/2011 09:43:43.134: LOG: Sent message with service ID StartCommunication
04/Mar/2011 09:43:43.137: LOG: Idle end: 325ms Low end: 350ms High end: 375ms Message Send Time: 375ms
04/Mar/2011 09:43:43.137: USER: Fast init succeeded, sending start communication request.
04/Mar/2011 09:43:43.236: LOG: Message received no replies.
04/Mar/2011 09:43:43.236: LOG: Failed to send message 1 times, message send failed.
04/Mar/2011 09:43:43.236: USER: Disconnected
04/Mar/2011 09:43:43.257: LOG: Set timing parameters to defaults.
04/Mar/2011 09:43:43.260: USER: Connection attempt number 3.
04/Mar/2011 09:43:43.261: USER: Connecting...
04/Mar/2011 09:43:43.283: LOG: Set timing parameters to defaults.
04/Mar/2011 09:43:43.284: USER: Starting fast init connection.
04/Mar/2011 09:43:43.285: USER: Connecting to address 0x01.
04/Mar/2011 09:43:43.689: LOG: Sent message with service ID StartCommunication
04/Mar/2011 09:43:43.692: LOG: Idle end: 325ms Low end: 350ms High end: 375ms Message Send Time: 375ms
04/Mar/2011 09:43:43.692: USER: Fast init succeeded, sending start communication request.
04/Mar/2011 09:43:43.791: LOG: Message received no replies.
04/Mar/2011 09:43:43.791: LOG: Failed to send message 1 times, message send failed.
04/Mar/2011 09:43:43.791: USER: Disconnected
04/Mar/2011 09:43:43.812: LOG: Set timing parameters to defaults.
04/Mar/2011 09:43:43.816: LOG: Closing FTDI device.
04/Mar/2011 09:43:43.826: LOG: Send receive thread now terminated.
04/Mar/2011 09:43:51.582: LOG: Closing NefMoto VW Audi ME7 ECU Flasher BETA 1.7.0.0
04/Mar/2011 09:43:53.450: LOG: Opening NefMoto VW Audi ME7 ECU Flasher BETA 1.7.0.0
04/Mar/2011 09:43:53.569: LOG: Cannot load license file, file does not exist.
04/Mar/2011 09:43:53.695: LOG: Opened NefMoto VW Audi ME7 ECU Flasher BETA 1.7.0.0

Title: Re: Flashing issues, Nothing seems to work!
Post by: Tony@NefMoto on March 05, 2011, 12:13:59 AM

At this point, I'm really not sure what could be going wrong. The ECU seems to be entering programming mode, and then just stops responding. Either the ECU has locked up, or the communication baud rate changed. Those are the only two things I can think of, unless it is a problem with your USB cable.

Can you try using the default baud rate?

Title: Re: Flashing issues, Nothing seems to work!
Post by: AmIdYfReAk on March 05, 2011, 07:57:44 AM

It is on default, it will show 10400 on the bottom, and that is the only option on the drop down box other then MAX.

Title: Re: Flashing issues, Nothing seems to work!
Post by: Tony@NefMoto on March 05, 2011, 02:23:33 PM

Have you had any luck getting into programming mode with other ECU types?
Do you have another USB cable you could test?
Can you flash these ECUs over OBD with Galletto or another tool?

Title: Re: Flashing issues, Nothing seems to work!
Post by: AmIdYfReAk on March 05, 2011, 03:45:06 PM

I've dumped all of my ECU's Via Galetto.

Its currently connected to a Bench harness because i do not have a ME7.5 based car, or anything newer then ME3 :)

The only other cable that i have in my possession is a Vag-tacho cable that seems to be sketchy, But I'll give you a try.

Title: Re: Flashing issues, Nothing seems to work!
Post by: AmIdYfReAk on March 05, 2011, 08:49:46 PM

After fixing the LED that was snapped off of the Vag-tacho, and installing the BL drivers for the FTDI i got this:

(http://img291.imageshack.us/img291/5681/ftdib.jpg)

Title: Re: Flashing issues, Nothing seems to work!
Post by: AmIdYfReAk on March 05, 2011, 08:54:36 PM

trying out my Galetto cable yields,

Code:

05/Mar/2011 09:43:44.645: LOG: Cannot load license file, file does not exist.
05/Mar/2011 09:43:44.656: LOG: Opened NefMoto VW Audi ME7 ECU Flasher BETA 1.7.0.0
05/Mar/2011 09:49:45.299: LOG: Opened FTDI device.
05/Mar/2011 09:49:45.301: LOG: FTDI device info - Description: EOBD2 Serial Number: 47514789 Device Type: FT_DEVICE_232R Device ID: 0x4036001 Device Flags: 0x0
05/Mar/2011 09:49:45.301: LOG: FTDI ChipID DLL is loaded, checking chip ID...
05/Mar/2011 09:49:45.309: LOG: FTDI device chip ID: 0xB896ADF1
05/Mar/2011 09:49:48.366: USER: Failed to read test echo from FTDI device. Make sure the cable is in dumb mode and connected to the OBD port.
05/Mar/2011 09:50:14.079: LOG: Closing FTDI device.
05/Mar/2011 09:50:14.107: LOG: Could not open FTDI device
05/Mar/2011 09:50:14.107: USER: Could not open FTDI device.

fun times had by all :)

Title: Re: Flashing issues, Nothing seems to work!
Post by: kls on March 05, 2011, 09:40:13 PM

Nefmoto doesn't support a Galletto cable or a VagTacho cable.

Title: Re: Flashing issues, Nothing seems to work!
Post by: AmIdYfReAk on March 05, 2011, 11:08:28 PM

Oh, well then.... I don't have another cable to try... :)

Title: Re: Flashing issues, Nothing seems to work!
Post by: Tony@NefMoto on March 07, 2011, 11:54:33 AM

It could be related to the ECU not being in the car. Does the ECU have an immobilizer?

If it has an immobilizer, then you could disable it, and try programming again.

My thought is that the ECU is reporting the flashing preconditions have been met even though the haven't, and then the ECU locks up going into programming mode.

Title: Re: Flashing issues, Nothing seems to work!
Post by: AmIdYfReAk on March 08, 2011, 04:30:01 PM

The IMMO has been defeated on each of them.

I can post dumps if you'd like to see the programming.

Title: Re: Flashing issues, Nothing seems to work!
Post by: Tony@NefMoto on March 08, 2011, 06:19:24 PM

Did you ever try adjusting the latency in your FTDI device settings?

Title: Re: Flashing issues, Nothing seems to work!
Post by: AmIdYfReAk on March 08, 2011, 07:15:07 PM

4, 8, 16, and 24 respectively.

Title: Re: Flashing issues, Nothing seems to work!
Post by: AmIdYfReAk on March 08, 2011, 08:00:31 PM

tried a fresh and known stock ECU,

Ecu: 4b0906018da ( Me 7.5 2003 passat Auto )
Ecu : 0261207931
S/W: 363929

Log attached below, to large to post: tried to validate memory layout.

Below is the bin files from both the 95040 and 29F800BB

Title: Re: Flashing issues, Nothing seems to work!
Post by: Tony@NefMoto on March 10, 2011, 02:25:49 PM

At this point I would say it would be best to try a different USB cable.

Do you know if anyone else has been able to flash these ECU types with the NefMoto software?

Title: Re: Flashing issues, Nothing seems to work!
Post by: AmIdYfReAk on March 10, 2011, 03:26:58 PM

Sadly, No...

I'll see if i can get my hands on a different cable and try it out.

Thanks for the help so far tony.

Title: Re: Flashing issues, Nothing seems to work!
Post by: AmIdYfReAk on March 13, 2011, 08:57:06 PM

new cable, sadly same chipset, Same outcome.

Title: Re: Flashing issues, Nothing seems to work!
Post by: Tony@NefMoto on March 14, 2011, 03:37:58 PM

Here are some thoughts:
-It's possible that the ECU has entered programming mode, but for some reason we stop receiving messages.
-It's possible the ECU has entered programming mode, but is expecting the tester to reconnect.
-It's possible the ECU needs to be in the car talking to another component like the instrument cluster to properly enter programming mode.

Can you try to reconnect again immediately after entering programming mode fails and disconnects?

Can you program this ECU through the OBD port using Galletto? It would be interesting to see if Galletto is using the KWP1281 or the KWP2000 protocol.

Title: Re: Flashing issues, Nothing seems to work!
Post by: AmIdYfReAk on March 14, 2011, 07:31:35 PM

Tried to reconnect immediately after the failure, ended in the same overall failure.

I've tried all 5 ECU's that i own, All of them give the same outcome.
They've all been dumped via Galletto, none of them programed however ( no need yet )

is there a way for me to check to see what KWP the program is using? if so, name it and I'll get back to you.

Title: Re: Flashing issues, Nothing seems to work!
Post by: AmIdYfReAk on March 14, 2011, 07:43:48 PM

Also I'd note, Is this chipset known to work? or am i spinning my wheels trying?

I'll continue to poke at it and see how far we get, but if i just need a different cable at the end of the day... then i can also try that out.

Title: Re: Flashing issues, Nothing seems to work!
Post by: Tony@NefMoto on March 14, 2011, 09:02:20 PM

I don't recall if anyone with the same ECU type has used the NefMoto software to flash their ECU. It has all become a blur to me.

I will try to find some time to do some tests with my Galletto and KWP2000Plus flasher myself to see if they are doing something I'm not.

If we could get a data log of the communication that Galletto does, then we could find out how it is working and what protocol they are using. You would need a datalogger like the Saleae Logic, or the OpenPort Logic Analyzer.

Title: Re: Flashing issues, Nothing seems to work!
Post by: AmIdYfReAk on March 15, 2011, 07:53:01 AM

Granted, i dont see the ECU that i posted the dump of above.

But one of the other ecu's that I've tried was a 06A906032HS and another was a LP.
Both of those are listed within the supported/tried in the following link:
http://nefariousmotorsports.com/wiki/index.php?title=NefMoto_ECU_Flashing_Software

That is why I'm starting to think there is an issue with the chipset/drivers.

Also, if you have a link or anything to get a hold of one of those programs, i'll log it and post the results.

Title: Re: Flashing issues, Nothing seems to work!
Post by: Tony@NefMoto on March 18, 2011, 05:26:27 PM

I guess I would suggest getting one of the recommended FTDI232R USB cables. All of the logic analyzers I recommended cost $50 and up and require you to buy the hardware to use them.

NefMoto

Technical => Flashing and Chipping => Topic started by: AmIdYfReAk on March 01, 2011, 10:34:04 PM