Tony@NefMoto
Administrator
Hero Member
Karma: +130/-4
 Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
 |
« on: July 04, 2012, 10:43:38 PM »
|
|
|
This is the version 1.9.3.2 release of the NefMoto software.Changes in this version: -Removed Validate Memory Layout operation because flashing operations already validate the layout, and it could cause Programming Not Complete errors on some ECUs. -Made flash writing operations only validate sector checksums after flash writing has successfully started. This prevents Invalid Checksum errors on some ECUs that would enter programming mode but refuse to allow flash writing. -Fixed a bug with overwriting a file when saving a read flash causing the program to freeze. -Fixed a bug with negotiating timing parameters failing on some ECU types when entering programming mode. -Added better support for detecting supported baud rates on ECUs that don't respond to messages on unsupported baud rates. Fast data logging can read up to 84 variables at a time with samples rates as high as 50 samples per second. The sample rate defaults to 10 samples per second. High sample rates can overload the ECU and cause communication disconnections. This same problem effects the ME7 Logger when attempting to read too many variables with sample rates that are too high. I recommend only logging the variables you are interested in at sample rate you need. The data logging method that this software and ME7 Logger use are non-standard and as such are able to overload the ECU if used irresponsibly. You can read about the software on the wiki: http://www.nefariousmotorsports.com/wiki/index.php/NefMoto_ECU_Flashing_SoftwareAlso make sure you have the FTDI D2XX driver installed: http://www.ftdichip.com/Drivers/D2XX.htm[ed] Please see http://nefariousmotorsports.com/forum/index.php?topic=12861.0title= - nyet |
|
|
|
« Last Edit: June 27, 2018, 02:15:14 AM by nyet »
|
Logged
|
|
|
|
|
|
|
nyet
|
|
« Reply #2 on: July 06, 2012, 12:52:51 PM »
|
|
|
Success. Uninstalled everything, including vcds.
set devmgr_show_nonpresent_devices=1
Went to manage devices, deleted ALL unused usb drivers
rebooted
reinstalled latest ftdi drivers (2.08.24)
rebooted
reinstalled nefmoto 1.9.3.2
backed down to 52800 baud (which is the setting on my xp laptop)
connected slow init
success.
Haven't tried 124800 baud yet. I think tony mentioned the baudrate shouldn't affect download, but perhaps there is something about negotiating the connection that is timing sensitive.
|
|
|
|
« Last Edit: July 06, 2012, 03:39:21 PM by nyet »
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +130/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #3 on: July 06, 2012, 03:07:00 PM »
|
|
|
Let me know when you try 124800 baud.
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #4 on: July 06, 2012, 07:34:23 PM »
|
|
|
Yup. 124800 baud is the source of the problem.
The thing is, in order for it to work again (after failing at 124800), I have to cycle both the ecu and close/restart the program, then use 52800 baud.
I never tried that before, because init never fails, even if you don't restart the program.
|
|
|
|
|
Logged
|
|
|
|
EnIgMa
Newbie
Karma: +0/-0
Offline
Posts: 2
|
|
« Reply #5 on: July 07, 2012, 03:00:49 PM »
|
|
|
Will be there any chance to use it with an Me7 on a fiat car? In my case a Me7.9.10 if not, can you please explain in two words what's the difference from a me7 audi/vw and others manufacters? thank you  |
|
|
|
|
Logged
|
|
|
|
pusher
Newbie
Karma: +0/-0
Offline
Posts: 1
|
|
« Reply #6 on: July 12, 2012, 01:20:18 PM »
|
|
|
Hi! I am trying to Full Read flash on an ECU I got from a scrap yard. I have built a desktop flashing setup which worked fine to disable the immobilizer, read into it with VCDS and Galletto in boot mode, but I cannot get NefMoto to work. I am new to working with ECU's and I am not sure if NefMoto should work using KWP2000 on a desktop setup? Or if it is not working for some other reason, I have only got NefMoto to work once with a Full Flash Read and that was in my friends S3 with his original ECU. Log from reading into the ECU on the desk, I know the ECU works as it will run and drive a S3. 12/Jul/2012 08:56:31.860: LOG: Successfully read ECU identification information
12/Jul/2012 08:56:31.863: USER: 100% complete.
12/Jul/2012 08:56:31.874: USER: Read 4 ECU info entries:
12/Jul/2012 08:56:31.894: USER: 0x92, System Supplier ECU Hardware Number: 0261208221
12/Jul/2012 08:56:31.900: USER: 0x94, System Supplier ECU Software Number: 1037367220
12/Jul/2012 08:56:31.904: USER: 0x9B, Calibration Date: 1ML906032A , 0001, 0x0000290E, 0x00000000, 0x0000, 1.8l R4/5VT ,
12/Jul/2012 08:56:31.910: USER: 0x9C, Calibration Equiment Software Number: 0x00000000
12/Jul/2012 08:56:31.914: USER: Restoring Windows sleep mode.
12/Jul/2012 08:56:34.339: LOG: Sent message with service ID TesterPresent
12/Jul/2012 08:56:34.356: LOG: Received message with service ID: TesterPresentPositiveReponse
12/Jul/2012 08:56:36.843: LOG: Sent message with service ID TesterPresent
12/Jul/2012 08:56:36.862: LOG: Received message with service ID: TesterPresentPositiveReponse
12/Jul/2012 08:56:38.240: LOG: User Prompt - Title: Confirm Full Read ECU Flash Memory Message: If you are ready to read, confirm the following things:
1) You have loaded a valid memory layout for the ECU.
2) The engine is not running.
Note: Some non-standard flash memory chips may prevent reading the flash memory.
Click OK to confirm, otherwise Cancel. Result: OK
12/Jul/2012 08:56:38.245: USER: Disabling Windows sleep mode.
12/Jul/2012 08:56:38.256: USER: Reading ECU flash memory.
12/Jul/2012 08:56:38.280: LOG: Reading ECU identification option: 0x9C
12/Jul/2012 08:56:38.284: LOG: Sent message with service ID ReadECUIdentification
12/Jul/2012 08:56:38.305: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse
12/Jul/2012 08:56:38.307: LOG: Read ECU identification option: 0x9C
12/Jul/2012 08:56:38.310: LOG: Successfully read ECU identification information
12/Jul/2012 08:56:38.315: USER: ECU reports programming session preconditions have been met.
12/Jul/2012 08:56:38.318: USER: Negotiating communication timings.
12/Jul/2012 08:56:38.320: LOG: Reading current communication timings.
12/Jul/2012 08:56:38.323: LOG: Sent message with service ID AccessTimingParameters
12/Jul/2012 08:56:38.347: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
12/Jul/2012 08:56:38.349: LOG: Setting communication timing to defaults.
12/Jul/2012 08:56:38.353: LOG: Sent message with service ID AccessTimingParameters
12/Jul/2012 08:56:38.371: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
12/Jul/2012 08:56:38.373: LOG: Reading current communication timings.
12/Jul/2012 08:56:38.377: LOG: Sent message with service ID AccessTimingParameters
12/Jul/2012 08:56:38.427: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
12/Jul/2012 08:56:38.429: USER: Successfully changed to new communication timings.
12/Jul/2012 08:56:38.432: USER: Requesting security access.
12/Jul/2012 08:56:38.435: LOG: Sent message with service ID SecurityAccess
12/Jul/2012 08:56:38.472: LOG: Received message with service ID: NegativeResponse
12/Jul/2012 08:56:38.475: LOG: Received negative response for service ID: SecurityAccess, with response code: GeneralReject
12/Jul/2012 08:56:38.478: USER: ECU reports that security access request was rejected.
12/Jul/2012 08:56:38.481: LOG: Starting ProgrammingSession diagnostic session with 124800 baud rate.
12/Jul/2012 08:56:38.483: USER: Starting diagnostic session.
12/Jul/2012 08:56:38.486: LOG: Sent message with service ID StartDiagnosticSession
12/Jul/2012 08:56:38.532: LOG: Received message with service ID: NegativeResponse
12/Jul/2012 08:56:38.535: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
12/Jul/2012 08:56:38.574: LOG: Received message with service ID: NegativeResponse
12/Jul/2012 08:56:38.577: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
12/Jul/2012 08:56:38.614: LOG: Received message with service ID: NegativeResponse
12/Jul/2012 08:56:38.616: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
12/Jul/2012 08:56:38.654: LOG: Received message with service ID: NegativeResponse
12/Jul/2012 08:56:38.656: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
12/Jul/2012 08:56:38.694: LOG: Received message with service ID: NegativeResponse
12/Jul/2012 08:56:38.696: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
12/Jul/2012 08:56:48.487: LOG: Sent message with service ID TesterPresent
12/Jul/2012 08:56:50.490: LOG: Message received no replies.
12/Jul/2012 08:56:50.492: LOG: Resending message. Send attempts: 2
12/Jul/2012 08:56:50.495: LOG: Sent message with service ID TesterPresent
12/Jul/2012 08:56:52.497: LOG: Message received no replies.
12/Jul/2012 08:56:52.499: LOG: Resending message. Send attempts: 3
12/Jul/2012 08:56:52.501: LOG: Sent message with service ID TesterPresent
12/Jul/2012 08:56:54.503: LOG: Message received no replies.
12/Jul/2012 08:56:54.505: LOG: Failed to send message 3 times, message send failed.
12/Jul/2012 08:56:54.507: USER: Disconnecting because no response was received for the Tester Present message.
12/Jul/2012 08:56:54.509: USER: Disconnected
12/Jul/2012 08:56:54.521: USER: Reading ECU flash memory failed.
12/Jul/2012 08:56:54.531: LOG: Closing FTDI device.
12/Jul/2012 08:56:54.536: LOG: Send receive thread now terminated.
12/Jul/2012 08:56:55.593: LOG: User Prompt - Title: Reading ECU Flash Memory Complete Message: Reading ECU flash memory failed. Result: OK
12/Jul/2012 08:56:55.596: USER: 100% complete.
12/Jul/2012 08:56:55.603: USER: Restoring Windows sleep mode.
It fails shortly after saying "ECU reports that security access request was rejected." Using a Ross-Tech HEX-USB cable in dumb mode. Any help or advice would be greatly appreciated. |
|
|
|
|
Logged
|
|
|
|
|
pvl
|
|
« Reply #7 on: July 15, 2012, 06:00:12 AM »
|
|
|
@ pusher:
use KWP2000+ interface and the specific ME7edition software from AMT cartech, if you want to read the ecu on the bench, without opening it up.
Galletto is a last resort, using bootmode. Not nescessary.
Nefmoto mainly fails with ME7.5 ecu's on the bench.
Cheers,
PvL
|
|
|
|
« Last Edit: July 27, 2012, 02:32:11 AM by pvl »
|
Logged
|
|
|
|
passuff
Jr. Member
Karma: +3/-9
Offline
Posts: 48
|
|
« Reply #8 on: July 25, 2012, 12:18:25 PM »
|
|
|
I tried to read "4B0 907 551 G" (29f800bb) ECU in Boot Mode but it failed. After that I tried over OBD and it worked. Here is the log: 25.Jul.2012 09:03:36.640: LOG: FTDI device info - Description: FT232R USB UART Serial Number: A600K3R4 Device Type: FT_DEVICE_232R ID: 0x4036001 Device Flags: 0x0
25.Jul.2012 09:03:36.640: LOG: FTDI ChipID DLL is loaded, checking chip ID...
25.Jul.2012 09:03:36.656: LOG: FTDI device chip ID: 0x7D9A67C5
25.Jul.2012 09:03:36.687: LOG: Starting send receive thread.
25.Jul.2012 09:03:36.687: LOG: Send receive thread now started.
25.Jul.2012 09:03:36.687: USER: Disconnected
25.Jul.2012 09:03:36.703: USER: Connecting...
25.Jul.2012 09:03:36.718: USER: Starting bootstrap loader upload.
25.Jul.2012 09:03:36.734: USER: Sent bootstrap init zero byte.
25.Jul.2012 09:03:36.734: USER: Received device ID response for init zero byte.
25.Jul.2012 09:03:36.765: USER: Successfully uploaded bootstrap loader.
25.Jul.2012 09:03:36.765: USER: Received bootstrap loader started status message.
25.Jul.2012 09:03:36.765: USER: Starting upload of bootmode runtime.
25.Jul.2012 09:03:36.765: USER: Uploaded bootmode runtime data.
25.Jul.2012 09:03:36.765: USER: Sent baud rate detection byte.
25.Jul.2012 09:03:37.781: USER: Bootmode runtime upload failed. Failed to receive baud rate detection response message.
25.Jul.2012 09:03:37.781: USER: Disconnected
25.Jul.2012 09:03:37.796: USER: Connecting...
25.Jul.2012 09:03:37.812: USER: Starting bootstrap loader upload.
25.Jul.2012 09:03:37.828: USER: Sent bootstrap init zero byte.
25.Jul.2012 09:03:40.828: USER: Sent bootstrap init zero byte.
25.Jul.2012 09:03:43.828: USER: Sent bootstrap init zero byte.
25.Jul.2012 09:03:46.828: USER: Bootstrap loader upload failed. Failed to receive device ID response for init zero byte.
25.Jul.2012 09:03:46.828: USER: Disconnected
25.Jul.2012 09:03:46.859: USER: Connecting...
25.Jul.2012 09:03:46.875: USER: Starting bootstrap loader upload.
25.Jul.2012 09:03:46.875: USER: Sent bootstrap init zero byte.
25.Jul.2012 09:03:49.890: USER: Sent bootstrap init zero byte.
25.Jul.2012 09:03:51.890: USER: Sent bootstrap init zero byte.
25.Jul.2012 09:03:54.890: USER: Bootstrap loader upload failed. Failed to receive device ID response for init zero byte.
25.Jul.2012 09:03:54.890: USER: Disconnected
25.Jul.2012 09:03:54.906: LOG: Closing FTDI device.
25.Jul.2012 09:03:54.921: LOG: Send receive thread now terminated.
25.Jul.2012 09:04:38.796: LOG: Opened FTDI device.
25.Jul.2012 09:04:38.796: LOG: FTDI device info - Description: FT232R USB UART Serial Number: A600K3R4 Device Type: FT_DEVICE_232R ID: 0x4036001 Device Flags: 0x0
25.Jul.2012 09:04:38.796: LOG: FTDI ChipID DLL is loaded, checking chip ID...
25.Jul.2012 09:04:38.796: LOG: FTDI device chip ID: 0x7F0B3CF1
25.Jul.2012 09:04:38.828: LOG: Starting send receive thread.
25.Jul.2012 09:04:38.828: LOG: Send receive thread now started.
25.Jul.2012 09:04:38.843: USER: Disconnected
25.Jul.2012 09:04:38.843: USER: Connecting...
25.Jul.2012 09:04:38.859: USER: Starting bootstrap loader upload.
25.Jul.2012 09:04:38.875: USER: Sent bootstrap init zero byte.
25.Jul.2012 09:04:38.875: USER: Received device ID response for init zero byte.
25.Jul.2012 09:04:38.906: USER: Successfully uploaded bootstrap loader.
25.Jul.2012 09:04:38.906: USER: Received bootstrap loader started status message.
25.Jul.2012 09:04:38.906: USER: Starting upload of bootmode runtime.
25.Jul.2012 09:04:38.906: USER: Uploaded bootmode runtime data.
25.Jul.2012 09:04:38.921: USER: Sent baud rate detection byte.
25.Jul.2012 09:04:39.921: USER: Bootmode runtime upload failed. Failed to receive baud rate detection response message.
25.Jul.2012 09:04:39.921: USER: Disconnected
25.Jul.2012 09:04:39.937: USER: Connecting...
25.Jul.2012 09:04:39.953: USER: Starting bootstrap loader upload.
25.Jul.2012 09:04:39.953: USER: Sent bootstrap init zero byte.
25.Jul.2012 09:04:42.953: USER: Sent bootstrap init zero byte.
25.Jul.2012 09:04:44.968: USER: Sent bootstrap init zero byte.
25.Jul.2012 09:04:46.968: USER: Bootstrap loader upload failed. Failed to receive device ID response for init zero byte.
25.Jul.2012 09:04:46.968: USER: Disconnected
25.Jul.2012 09:04:46.984: USER: Connecting...
25.Jul.2012 09:04:47.000: USER: Starting bootstrap loader upload.
25.Jul.2012 09:04:47.015: USER: Sent bootstrap init zero byte.
25.Jul.2012 09:04:50.015: USER: Sent bootstrap init zero byte.
25.Jul.2012 09:04:53.015: USER: Sent bootstrap init zero byte.
25.Jul.2012 09:04:55.187: USER: Received device ID response for init zero byte.
25.Jul.2012 09:04:56.187: USER: Successfully uploaded bootstrap loader.
25.Jul.2012 09:04:57.187: USER: Failed to receive bootstrap loader started status message.
25.Jul.2012 09:04:57.187: USER: Disconnected
25.Jul.2012 09:04:57.218: LOG: Closing FTDI device.
25.Jul.2012 09:04:57.234: LOG: Send receive thread now terminated.
25.Jul.2012 09:05:24.875: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
25.Jul.2012 09:05:24.921: LOG: Opened FTDI device.
25.Jul.2012 09:05:24.921: LOG: FTDI device info - Description: FT232R USB UART Serial Number: A100enyw Device Type: FT_DEVICE_232R ID: 0x4036001 Device Flags: 0x0
25.Jul.2012 09:05:24.921: LOG: FTDI ChipID DLL is loaded, checking chip ID...
25.Jul.2012 09:05:24.937: LOG: FTDI device chip ID: 0x7F0B3CF1
25.Jul.2012 09:05:24.984: USER: Validated FTDI device is in dumb mode.
25.Jul.2012 09:05:25.000: LOG: Starting send receive thread.
25.Jul.2012 09:05:25.000: LOG: Send receive thread now started.
25.Jul.2012 09:05:25.000: USER: Disconnected
25.Jul.2012 09:05:25.031: LOG: Setting communication timings to defaults.
25.Jul.2012 09:05:25.031: LOG: Set timing parameters to defaults.
25.Jul.2012 09:05:25.031: USER: Connecting...
25.Jul.2012 09:05:25.046: LOG: Setting communication timings to defaults.
25.Jul.2012 09:05:25.046: USER: Starting slow init connection.
25.Jul.2012 09:05:27.656: USER: Connecting to address 0x01.
25.Jul.2012 09:05:29.828: USER: Slow init succeeded.
25.Jul.2012 09:05:29.828: LOG: Setting Address: 0x01 KeyByte1: 0x01 KeyByte2: 0x0A
25.Jul.2012 09:05:29.828: USER: Switching to KWP1281 session.
25.Jul.2012 09:05:30.000: LOG: KWP1281 read block
25.Jul.2012 09:05:30.062: LOG: KWP1281 sent block
25.Jul.2012 09:05:30.375: LOG: KWP1281 read block
25.Jul.2012 09:05:30.437: LOG: KWP1281 sent block
25.Jul.2012 09:05:30.609: LOG: KWP1281 read block
25.Jul.2012 09:05:30.687: LOG: KWP1281 sent block
25.Jul.2012 09:05:30.828: LOG: KWP1281 read block
25.Jul.2012 09:05:30.890: LOG: KWP1281 sent block
25.Jul.2012 09:05:30.921: LOG: KWP1281 read block
25.Jul.2012 09:05:31.000: LOG: KWP1281 sent block
25.Jul.2012 09:05:31.000: USER: KWP1281 connect info: 4B0907551G 2.7l V6/5VT 0001 ,ð
25.Jul.2012 09:05:32.500: USER: Connecting to address 0x01.
25.Jul.2012 09:05:34.703: USER: Slow init succeeded.
25.Jul.2012 09:05:34.703: LOG: Setting Address: 0x01 KeyByte1: 0x6F KeyByte2: 0x0F
25.Jul.2012 09:05:34.703: USER: Switching to KWP2000 session.
25.Jul.2012 09:05:34.703: USER: Connected
2Jul.2012 09:08:56.453: LOG: Sent message with service ID TransferData
25.Jul.2012 09:08:56.484: LOG: Received message with service ID: TransferDataPositiveResponse
25.Jul.2012 09:08:57.625: LOG: Received message with service ID: TransferDataPositiveResponse
25.Jul.2012 09:08:57.625: USER: 100% complete.
25.Jul.2012 09:08:57.625: USER: Data transfer complete.
25.Jul.2012 09:08:57.625: USER: Requesting data transfer exit.
25.Jul.2012 09:08:57.625: LOG: Sent message with service ID RequestTransferExit
25.Jul.2012 09:08:57.656: LOG: Received message with service ID: RequestTransferExitPositiveResponse
25.Jul.2012 09:08:57.656: USER: Successfully exited data transfer.
25.Jul.2012 09:09:00.140: LOG: Sent message with service ID TesterPresent
25.Jul.2012 09:09:00.156: LOG: Received message with service ID: TesterPresentPositiveReponse
25.Jul.2012 09:09:02.640: LOG: Sent message with service ID TesterPresent
25.Jul.2012 09:09:02.656: LOG: Received message with service ID: TesterPresentPositiveReponse
25.Jul.2012 09:09:05.140: LOG: Sent message with service ID TesterPresent
25.Jul.2012 09:09:05.156: LOG: Received message with service ID: TesterPresentPositiveReponse
25.Jul.2012 09:09:07.640: LOG: Sent message with service ID TesterPresent
25.Jul.2012 09:09:07.671: LOG: Received message with service ID: TesterPresentPositiveReponse
25.Jul.2012 09:09:10.140: LOG: Sent message with service ID TesterPresent
25.Jul.2012 09:09:10.156: LOG: Received message with service ID: TesterPresentPositiveReponse
25.Jul.2012 09:09:12.656: LOG: Sent message with service ID TesterPresent
25.Jul.2012 09:09:12.671: LOG: Received message with service ID: TesterPresentPositiveReponse
25.Jul.2012 09:09:15.078: USER: Saved ECU flash memory to: C:\Dokumente und Einstellungen\Michi\Desktop\ori.bin
25.Jul.2012 09:09:15.125: USER: Reading ECU flash memory succeeded in: 00:02:50.
25.Jul.2012 09:09:15.156: LOG: Sent message with service ID TesterPresent
25.Jul.2012 09:09:15.171: LOG: Received message with service ID: TesterPresentPositiveReponse
25.Jul.2012 09:09:17.546: LOG: User Prompt - Title: Reading ECU Flash Memory Complete Message: Reading ECU flash memory succeeded in: 00:02:50. Result: OK
25.Jul.2012 09:09:17.546: USER: Restoring Windows sleep mode.
25.Jul.2012 09:09:17.656: LOG: Sent message with service ID TesterPresent
|
|
|
|
|
Logged
|
|
|
|
scalp06
Jr. Member
Karma: +0/-0
Offline
Posts: 33
|
|
« Reply #9 on: July 31, 2012, 05:11:05 AM »
|
|
|
Hi, I leave in France and I see few C Box with 29F400.
I can't see this ecu on supported ecu list from nefmoto software.
I can read and write in bootmode with Magpro tool, it's working great but I would write over OBD for win time. I already test the writing over OBD with my tool but the procedure crash after erasing flash and writing 4%... (thank to bootmode for recovery!)
I haven't see in this board anything about obd writing for this kind oh ecu.
Off topic: I have to test in this car the eeprom read with soft me7_95040 but no issue too...
For Nefarious, do you plan to support this ecu or it's not possible with hardware of this generation ecu?
Regards.
|
|
|
|
|
Logged
|
|
|
|
quattro85
Full Member
Karma: +3/-0
Offline
Posts: 78
|
|
« Reply #10 on: August 22, 2012, 01:59:45 PM »
|
|
|
After failing while trying Full Read Flash - I try every speed, try with old VAG-COM cable also with VCDS 11.2 in dumb mode but no success. I can connect, and manage to read ECU info but can't read flash file.
Today I found original file from exactly same ECU version, and I make definition file with ME7info. After loading definitions I try to log some data but again with no success.
Any idea what to try next?
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #11 on: August 22, 2012, 03:10:36 PM »
|
|
|
After failing while trying Full Read Flash - I try every speed
When you switch speeds you MAY have to quit Nefmoto and restart... I was fighting this issue for a long time. Might be a bug in the program. Also, try cycling the ignition whenever you switch speeds as well. |
|
|
|
|
Logged
|
|
|
|
quattro85
Full Member
Karma: +3/-0
Offline
Posts: 78
|
|
« Reply #12 on: August 23, 2012, 02:05:55 AM »
|
|
|
Thank you nyet! I'll try to cycle ignition, after choosing new speed. But I've noticed that regardless of chosen speed, when I connect again speed is again at maximum 124 800, and after that I can choose slower speed from drop down. Another things that I've noticed - after attempt for Full Read Flash, ESP led on the dashboard is on, and both fuel trims was reset to 0 (like clearing fault codes in VCDS). Here is a Nefmoto log with Read ECU info 09:41:06.187: LOG: Opened NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
09:41:13.342: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
09:41:13.358: LOG: Opened FTDI device.
09:41:13.358: LOG: FTDI device info - Description: USB <-> Serial Serial Number: Device Type: FT_DEVICE_BM ID: 0x4036001 Device Flags: 0x0
09:41:13.359: LOG: FTDI ChipID DLL is loaded, checking chip ID...
09:41:13.360: LOG: Unable to read FTDI device chip ID
09:41:13.376: USER: Validated FTDI device is in dumb mode.
09:41:13.379: LOG: Starting send receive thread.
09:41:13.387: LOG: Send receive thread now started.
09:41:13.389: USER: Disconnected
09:41:13.397: LOG: Setting communication timings to defaults.
09:41:13.398: LOG: Set timing parameters to defaults.
09:41:13.399: USER: Connecting...
09:41:13.407: LOG: Setting communication timings to defaults.
09:41:13.410: USER: Starting slow init connection.
09:41:16.011: USER: Connecting to address 0x01.
09:41:18.168: USER: Slow init succeeded.
09:41:18.169: LOG: Setting Address: 0x01 KeyByte1: 0x6F KeyByte2: 0x0F
09:41:18.169: USER: Switching to KWP2000 session.
09:41:18.170: USER: Connected
09:41:20.695: LOG: Sent message with service ID TesterPresent
09:41:20.730: LOG: Received message with service ID: TesterPresentPositiveReponse
09:41:23.121: USER: Disabling Windows sleep mode.
09:41:23.126: USER: Reading all ECU info.
09:41:23.177: LOG: Starting StandardSession diagnostic session with 124800 baud rate.
09:41:23.179: USER: Starting diagnostic session.
09:41:23.201: LOG: Sent message with service ID StartDiagnosticSession
09:41:23.241: LOG: Received message with service ID: NegativeResponse
09:41:23.242: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SubFunctionNotSupported_InvalidFormat
09:41:23.247: LOG: Starting StandardSession diagnostic session with 52800 baud rate.
09:41:23.248: LOG: Start diagnostic session failed, ECU reports sub function not supported or invalid format. Trying again with a different format.
09:41:23.277: LOG: Sent message with service ID StartDiagnosticSession
09:41:23.321: LOG: Received message with service ID: NegativeResponse
09:41:23.321: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SubFunctionNotSupported_InvalidFormat
09:41:23.322: LOG: Starting StandardSession diagnostic session with 38400 baud rate.
09:41:23.322: LOG: Start diagnostic session failed, ECU reports sub function not supported or invalid format. Trying again with a different format.
09:41:23.354: LOG: Sent message with service ID StartDiagnosticSession
09:41:23.391: LOG: Received message with service ID: NegativeResponse
09:41:23.391: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SubFunctionNotSupported_InvalidFormat
09:41:23.392: LOG: Starting StandardSession diagnostic session with 10400 baud rate.
09:41:23.392: LOG: Start diagnostic session failed, ECU reports sub function not supported or invalid format. Trying again with a different format.
09:41:23.431: LOG: Sent message with service ID StartDiagnosticSession
09:41:23.472: LOG: Received message with service ID: NegativeResponse
09:41:23.472: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SubFunctionNotSupported_InvalidFormat
09:41:23.473: LOG: Starting StandardSession diagnostic session with 9600 baud rate.
09:41:23.473: LOG: Start diagnostic session failed, ECU reports sub function not supported or invalid format. Trying again with a different format.
09:41:23.508: LOG: Sent message with service ID StartDiagnosticSession
09:41:23.552: LOG: Received message with service ID: NegativeResponse
09:41:23.552: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SubFunctionNotSupported_InvalidFormat
09:41:23.552: LOG: Starting StandardSession diagnostic session without baud rate.
09:41:23.553: LOG: Start diagnostic session failed, ECU reports sub function not supported or invalid format. Trying again with a different format.
09:41:23.579: LOG: Sent message with service ID StartDiagnosticSession
09:41:23.621: LOG: Received message with service ID: NegativeResponse
09:41:23.622: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SubFunctionNotSupported_InvalidFormat
09:41:23.622: LOG: Starting StandardSession diagnostic session without baud rate.
09:41:23.622: LOG: Start diagnostic session failed, ECU reports sub function not supported or invalid format. Trying again with a different format.
09:41:23.651: LOG: Sent message with service ID StartDiagnosticSession
09:41:23.691: LOG: Received message with service ID: NegativeResponse
09:41:23.692: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SubFunctionNotSupported_InvalidFormat
09:41:23.692: LOG: Start diagnostic session failed, ECU reports sub function not supported or invalid format. Trying again with a different format.
09:41:23.718: LOG: Sent message with service ID StopDiagnosticSession
09:41:23.761: LOG: Received message with service ID: NegativeResponse
09:41:23.762: LOG: Received negative response for service ID: StopDiagnosticSession, with response code: ServiceNotSupported
09:41:23.762: USER: Unable to properly start diagnostic session, attempting to continue with current undefined session.
09:41:23.770: USER: Negotiating communication timings.
09:41:23.771: LOG: Reading current communication timings.
09:41:23.815: LOG: Sent message with service ID AccessTimingParameters
09:41:23.855: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
09:41:23.858: LOG: Set timing parameters to new values.
09:41:23.858: LOG: Reading communication timing limits.
09:41:23.913: LOG: Sent message with service ID AccessTimingParameters
09:41:23.955: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
09:41:23.956: LOG: Requesting communication at timing limits.
09:41:23.958: LOG: Sent message with service ID AccessTimingParameters
09:41:24.000: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
09:41:24.000: USER: Successfully changed to new communication timings.
09:41:24.001: LOG: Reading ECU identification option: 0x81
09:41:24.002: LOG: Sent message with service ID ReadECUIdentification
09:41:24.044: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse
09:41:24.045: LOG: Read ECU identification option: 0x81
09:41:24.045: LOG: Successfully read ECU identification information
09:41:24.051: USER: 0% complete.
09:41:24.051: LOG: Reading ECU identification option: 0x92
09:41:24.052: LOG: Sent message with service ID ReadECUIdentification
09:41:24.080: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse
09:41:24.080: LOG: Read ECU identification option: 0x92
09:41:24.081: LOG: Successfully read ECU identification information
09:41:24.083: USER: 20% complete.
09:41:24.084: LOG: Reading ECU identification option: 0x94
09:41:24.086: LOG: Sent message with service ID ReadECUIdentification
09:41:24.110: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse
09:41:24.110: LOG: Read ECU identification option: 0x94
09:41:24.111: LOG: Successfully read ECU identification information
09:41:24.111: USER: 40% complete.
09:41:24.111: LOG: Reading ECU identification option: 0x91
09:41:24.112: LOG: Sent message with service ID ReadECUIdentification
09:41:24.143: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse
09:41:24.144: LOG: Read ECU identification option: 0x91
09:41:24.145: LOG: Successfully read ECU identification information
09:41:24.145: USER: 60% complete.
09:41:24.145: LOG: Reading ECU identification option: 0x9B
09:41:24.146: LOG: Sent message with service ID ReadECUIdentification
09:41:24.204: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse
09:41:24.205: LOG: Read ECU identification option: 0x9B
09:41:24.205: LOG: Successfully read ECU identification information
09:41:24.206: USER: 80% complete.
09:41:24.207: LOG: Reading ECU identification option: 0x9C
09:41:24.209: LOG: Sent message with service ID ReadECUIdentification
09:41:24.234: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse
09:41:24.235: LOG: Read ECU identification option: 0x9C
09:41:24.235: LOG: Successfully read ECU identification information
09:41:24.236: USER: 100% complete.
09:41:24.247: USER: Read 5 ECU info entries:
09:41:24.263: USER: 0x92, System Supplier ECU Hardware Number: 0261208228
09:41:24.267: USER: 0x94, System Supplier ECU Software Number: 1037369311
09:41:24.270: USER: 0x91, Vehicle Manufacturer ECU Hardware Number: 0x0D, 8E0909018A , 0xFF
09:41:24.273: USER: 0x9B, Calibration Date: 8E0909518AL , 0003, 0x03002DBF, 0x0001010A, 0x81FE, 1.8L R4/5VT , G
09:41:24.287: USER: 0x9C, Calibration Equiment Software Number: 0x00004E00
09:41:24.295: USER: Restoring Windows sleep mode.
|
|
|
|
|
Logged
|
|
|
|
quattro85
Full Member
Karma: +3/-0
Offline
Posts: 78
|
|
« Reply #13 on: August 23, 2012, 02:07:46 AM »
|
|
|
And immediately after that attempt for Full Read Flash which failed 09:41:39.924: LOG: User Prompt - Title: Confirm Full Read ECU Flash Memory Message: If you are ready to read, confirm the following things:
1) You have loaded a valid memory layout for the ECU.
2) The engine is not running.
Note: Some non-standard flash memory chips may prevent reading the flash memory.
Click OK to confirm, otherwise Cancel. Result: OK
09:41:39.924: USER: Disabling Windows sleep mode.
09:41:39.939: USER: Reading ECU flash memory.
09:41:39.966: LOG: Reading ECU identification option: 0x9C
09:41:39.967: LOG: Sent message with service ID ReadECUIdentification
09:41:39.992: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse
09:41:39.993: LOG: Read ECU identification option: 0x9C
09:41:39.993: LOG: Successfully read ECU identification information
09:41:39.997: USER: ECU reports programming session preconditions have been met.
09:41:39.997: USER: Negotiating communication timings.
09:41:39.998: LOG: Reading current communication timings.
09:41:39.999: LOG: Sent message with service ID AccessTimingParameters
09:41:40.023: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
09:41:40.024: LOG: Setting communication timing to defaults.
09:41:40.026: LOG: Sent message with service ID AccessTimingParameters
09:41:40.048: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
09:41:40.049: LOG: Reading current communication timings.
09:41:40.051: LOG: Sent message with service ID AccessTimingParameters
09:41:40.103: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
09:41:40.104: USER: Successfully changed to new communication timings.
09:41:40.106: USER: Requesting security access.
09:41:40.108: LOG: Sent message with service ID SecurityAccess
09:41:40.152: LOG: Received message with service ID: SecurityAccessPositiveResponse
09:41:40.155: LOG: Received security seed, sending security key.
09:41:40.157: LOG: Sent message with service ID SecurityAccess
09:41:40.209: LOG: Received message with service ID: SecurityAccessPositiveResponse
09:41:40.210: USER: Security access granted.
09:41:40.210: LOG: Starting ProgrammingSession diagnostic session with 52800 baud rate.
09:41:40.210: USER: Starting diagnostic session.
09:41:40.212: LOG: Sent message with service ID StartDiagnosticSession
09:41:40.259: LOG: Received message with service ID: NegativeResponse
09:41:40.260: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
09:41:40.299: LOG: Received message with service ID: NegativeResponse
09:41:40.299: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
...
09:41:44.858: LOG: Received message with service ID: NegativeResponse
09:41:44.858: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
09:41:44.891: LOG: Received message with service ID: StartDiagnosticSessionPositiveResponse
09:41:44.891: LOG: Setting communication timings to defaults.
09:41:44.892: LOG: Set timing parameters to defaults.
09:41:44.892: LOG: Sent message with service ID TesterPresent
09:41:44.893: LOG: Changed diagnostic session type to: ProgrammingSession
09:41:44.893: LOG: ECU requesting specific baud rate: 52800
09:41:44.894: USER: Successfully started diagnostic session.
09:41:44.894: USER: Negotiating communication timings.
09:41:44.894: LOG: Reading current communication timings.
09:41:46.894: LOG: Message received no replies.
09:41:46.894: LOG: Resending message. Send attempts: 2
09:41:46.910: LOG: Sent message with service ID TesterPresent
09:41:46.947: LOG: Received message with service ID: TesterPresentPositiveReponse
09:41:47.008: LOG: Sent message with service ID AccessTimingParameters
09:41:47.048: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
09:41:47.048: LOG: Set timing parameters to new values.
09:41:47.049: LOG: Reading communication timing limits.
09:41:47.105: LOG: Sent message with service ID AccessTimingParameters
09:41:47.148: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
09:41:47.148: LOG: Requesting communication at timing limits.
09:41:47.150: LOG: Sent message with service ID AccessTimingParameters
09:41:47.187: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
09:41:47.187: USER: Successfully changed to new communication timings.
09:41:47.188: USER: Requesting security access.
09:41:47.189: LOG: Sent message with service ID SecurityAccess
09:41:47.208: LOG: Received message with service ID: SecurityAccessPositiveResponse
09:41:47.208: USER: Security access granted.
09:41:47.209: USER: Validating flash memory starts at 0x00800000 and ends at 0x00900000.
09:41:47.212: LOG: Sent message with service ID RequestUpload
09:41:47.227: LOG: Received message with service ID: NegativeResponse
09:41:47.227: LOG: Received negative response for service ID: RequestUpload, with response code: SecurityAccessDenied_SecurityAccessRequested
09:41:47.228: USER: Validation failed, ECU reports that security access is not granted.
09:41:47.229: USER: Memory layout validation failed.
09:41:49.715: LOG: Sent message with service ID TesterPresent
09:41:49.736: LOG: Received message with service ID: TesterPresentPositiveReponse
09:41:50.554: LOG: User Prompt - Title: Unable to validate memory layout Message: Unable to validate memory layout. Do you want to continue reading flash memory without validating the memory layout? Result: OK
09:41:50.555: USER: Starting to read data block.
09:41:50.557: USER: Requesting upload from ECU for address range 0x00800000 to 0x00803FFF.
09:41:50.558: LOG: Sent message with service ID RequestUpload
09:41:50.576: LOG: Received message with service ID: NegativeResponse
09:41:50.577: LOG: Received negative response for service ID: RequestUpload, with response code: SecurityAccessDenied_SecurityAccessRequested
09:41:50.579: USER: Request upload from ECU failed, ECU reports security access has not been granted.
09:41:50.580: USER: Reading ECU flash memory failed. Trying to force ECU to recognize read operation is complete.
09:41:50.581: LOG: Validating flashed data checksum for address range 0x00900000 to 0x00900001.
09:41:50.584: LOG: Sent message with service ID StartRoutineByLocalIdentifier
09:41:50.606: LOG: Received message with service ID: StartRoutineByLocalIdentifierPositiveResponse
09:41:50.611: LOG: Sent message with service ID RequestRoutineResultsByLocalIdentifier
09:41:50.626: LOG: Received message with service ID: NegativeResponse
09:41:50.627: LOG: Received negative response for service ID: RequestRoutineResultsByLocalIdentifier, with response code: BlockTransferDataChecksumError
09:41:50.627: LOG: Checksum is incorrect.
09:41:50.628: USER: Finished forcing ECU to recognize that failed read operation is complete.
09:41:50.632: USER: Reading ECU flash memory failed.
09:41:53.114: LOG: Sent message with service ID TesterPresent
09:41:53.135: LOG: Received message with service ID: TesterPresentPositiveReponse
09:41:53.625: LOG: User Prompt - Title: Reading ECU Flash Memory Complete Message: Reading ECU flash memory failed. Result: OK
09:41:53.626: USER: 100% complete.
09:41:53.639: USER: Restoring Windows sleep mode.
|
|
|
|
|
Logged
|
|
|
|
quattro85
Full Member
Karma: +3/-0
Offline
Posts: 78
|
|
« Reply #14 on: August 23, 2012, 02:27:24 AM »
|
|
|
And here is other part with log attempt 09:49:01.968: LOG: Sent message with service ID TesterPresent
09:49:01.984: LOG: Received message with service ID: TesterPresentPositiveReponse
09:49:03.731: USER: Disabling Windows sleep mode.
09:49:03.739: USER: Starting variable reading.
09:49:03.753: LOG: Starting DevelopmentSession diagnostic session with 52800 baud rate.
09:49:03.754: USER: Starting diagnostic session.
09:49:03.755: LOG: Sent message with service ID StartDiagnosticSession
09:49:03.775: LOG: Received message with service ID: NegativeResponse
09:49:03.776: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SecurityAccessDenied_SecurityAccessRequested
09:49:03.777: USER: Start diagnostic session failed, ECU reports security access is required.
09:49:03.783: USER: 100% complete.
09:49:03.785: USER: Stopped reading variables.
09:49:03.786: USER: Restoring Windows sleep mode.
09:49:06.257: LOG: Sent message with service ID TesterPresent
09:49:06.272: LOG: Received message with service ID: TesterPresentPositiveReponse
09:49:08.760: LOG: Sent message with service ID TesterPresent
09:49:08.772: LOG: Received message with service ID: TesterPresentPositiveReponse
09:49:09.693: USER: Disabling Windows sleep mode.
09:49:09.698: USER: Starting variable reading.
09:49:09.716: LOG: Starting DevelopmentSession diagnostic session with 52800 baud rate.
09:49:09.716: USER: Starting diagnostic session.
09:49:09.717: LOG: Sent message with service ID StartDiagnosticSession
09:49:09.734: LOG: Received message with service ID: NegativeResponse
09:49:09.735: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SecurityAccessDenied_SecurityAccessRequested
09:49:09.735: USER: Start diagnostic session failed, ECU reports security access is required.
09:49:09.736: USER: 100% complete.
09:49:09.737: USER: Stopped reading variables.
09:49:09.737: USER: Restoring Windows sleep mode.
09:49:12.219: LOG: Sent message with service ID TesterPresent
09:49:12.232: LOG: Received message with service ID: TesterPresentPositiveReponse
09:49:14.721: LOG: Sent message with service ID TesterPresent
09:49:14.741: LOG: Received message with service ID: TesterPresentPositiveReponse
09:49:17.223: LOG: Sent message with service ID TesterPresent
09:49:17.241: LOG: Received message with service ID: TesterPresentPositiveReponse
09:49:19.727: LOG: Sent message with service ID TesterPresent
09:49:19.741: LOG: Received message with service ID: TesterPresentPositiveReponse
09:49:22.230: LOG: Sent message with service ID TesterPresent
09:49:22.251: LOG: Received message with service ID: TesterPresentPositiveReponse
09:49:22.843: USER: Disabling Windows sleep mode.
09:49:22.850: USER: Starting variable reading.
09:49:22.854: LOG: Starting DevelopmentSession diagnostic session with 52800 baud rate.
09:49:22.855: USER: Starting diagnostic session.
09:49:22.857: LOG: Sent message with service ID StartDiagnosticSession
09:49:22.872: LOG: Received message with service ID: NegativeResponse
09:49:22.872: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SecurityAccessDenied_SecurityAccessRequested
09:49:22.873: USER: Start diagnostic session failed, ECU reports security access is required.
09:49:22.874: USER: 100% complete.
Now I noticed that reasons for failing in Read Flash and logging are different. In 2-nd log I saw this LOG: Sent message with service ID StartDiagnosticSession
LOG: Received message with service ID: NegativeResponse
LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SecurityAccessDenied_SecurityAccessRequested
USER: Start diagnostic session failed, ECU reports security access is required.
|
|
|
|
|
Logged
|
|
|
|
|
