Pages: [1]
Author Topic: Trying to read flash file Nefmoto ME7 flashlogger  (Read 2462 times)
martin9400
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 3


« on: August 05, 2019, 07:24:35 AM »

Hey guys, I'm trying to get the file out of my ECU and I get connected successfully. I can read the ECU info successfully. But when I press the "full read flash"-button I get "Reading ECU-flash memory failed"-error message. I've tried multiple Baud-speed settings and I've opened up my ECU to check the chip that's in it so I use the correct memory layout.

The car is a 2.7T Audi A6 AJK engine put into an B5 A4, 1.8TQ originally, ECU number 4b0907551G.

Log from Nefmoto software=
Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init failed.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP1281 session.
KWP1281 connect info: 4B0907551G  2.7l V6/5VT         0002
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP2000 session.
Connected
Reading all ECU info.
Starting diagnostic session.
Successfully started diagnostic session.
Negotiating communication timings.
Successfully changed to new communication timings.
0% complete.
25% complete.
50% complete.
75% complete.
100% complete.
Read 4 ECU info entries:
   0x92, System Supplier ECU Hardware Number: 0261206380
   0x94, System Supplier ECU Software Number: 1037354065
   0x9B, Calibration Date: 4B0907551G  , 0002, 0x00001678, 0x00000000, 0x0190, 2.7l V6/5VT    ,     
   0x9C, Calibration Equiment Software Number: 0x800F0000
Starting saving of info.
Successfully saved info to file.
Reading ECU flash memory.
ECU reports programming session preconditions have been met.
Negotiating communication timings.
Successfully changed to new communication timings.
Requesting security access.
ECU reports that security access is not supported.
Starting diagnostic session.
Successfully started diagnostic session.
Negotiating communication timings.
Successfully changed to new communication timings.
Requesting security access.
Security access granted.
Validating flash memory starts at 0x00800000 and ends at 0x00900000.
Memory layout is valid.
Starting to read data block.
Requesting upload from ECU for address range 0x00800000 to 0x00803FFF.
Request upload from ECU succeeded.
Starting data transfer.
Reading ECU flash memory failed. Trying to force ECU to recognize read operation is complete.
Disconnecting because no response was received for the Tester Present message.
Disconnected
Reading ECU flash memory failed.
100% complete.
Logged
Blazius
Hero Member
*****

Karma: +89/-40
Offline Offline

Posts: 1280



« Reply #1 on: August 05, 2019, 07:37:54 AM »

try 0x00 protocol
Logged
martin9400
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 3


« Reply #2 on: August 05, 2019, 08:34:56 AM »

try 0x00 protocol

Could you elaborate? Can't find anything in the search-bar, tried putting 0x00 in the security seed under kwp2000 settings-bar in the software, but it failed also
Logged
martin9400
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 3


« Reply #3 on: August 05, 2019, 09:03:18 AM »

Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x00.
Slow init failed.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x00.
Slow init failed.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x00.
Slow init failed.
Disconnected
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.039 seconds with 17 queries. (Pretty URLs adds 0.001s, 0q)