Pages: 1 ... 4 5 [6]
Author Topic: ME7.5 Eeprom read and write  (Read 102094 times)
Bische
Sr. Member
****

Karma: +25/-4
Offline Offline

Posts: 397



WWW
« Reply #75 on: October 27, 2011, 02:16:09 AM »

I did read my eeprom sucessfully last night with vag commander 2.5 and the blue ebay cable.

Now i have to learn where to find my SKC lol
Logged
pvl
Sr. Member
****

Karma: +32/-1
Offline Offline

Posts: 350


« Reply #76 on: October 29, 2011, 05:29:57 AM »

would you be so kind to post a picture of that cable over here ?

Is it a generic KKL vagcom donglecable, or a SPECIFIC v2.5 vag k-can commander cable ?

Thanks,

PvL
Logged
littco
Hero Member
*****

Karma: +52/-7
Offline Offline

Posts: 903


« Reply #77 on: October 29, 2011, 11:12:08 AM »

I did read my eeprom sucessfully last night with vag commander 2.5 and the blue ebay cable.

Now i have to learn where to find my SKC lol

I've got vag+commander 1.6 and if you log into the engine management page it shows the SKC code for you in a seperate box. Does 2.5 not do the same?

Also I tried last night to use the Immo off option on vag commander but this was on a bench. It seems to change the hex ok, and seemed to write back ok, but when you remove pin 3 to simulate the ignition off/on it looses the setting so I guess it doesn't work. But then I have no way of checking anyway as my keys are coded to the ecu anyway!

Logged
Dobermann
Full Member
***

Karma: +7/-0
Offline Offline

Posts: 80


« Reply #78 on: October 31, 2011, 09:37:12 AM »

so update

i tryed to write the eeporm on bench with simulating the ingintion off

i make a switch on pin 3 on the ecu cable  !!!

i write the file and switch off pin 3 for simulate but for the moment it will not work !!

i dont know why !! in the netxt weeks i will make some tests !!

it must be possible to write the eeprom !! by obd it works without problem !!!

maybe someone knows more about this problem !!

best regards

ps: maybe my cable is the problem !!

i looked what pins are conectet !!

pin 21 is not conectet in my cable !! that must have 12V it is for the immobilizer

i will check that !!!

12 Volt must be on pin 3 pin 21 pin 62 and only pin 3 must be turn off for simulating ignition on/off
« Last Edit: October 31, 2011, 09:51:04 AM by Dobermann » Logged
chienliu1972
Full Member
***

Karma: +5/-0
Offline Offline

Posts: 50


« Reply #79 on: November 12, 2011, 05:44:56 AM »

Have you turn off the immo on bench successfully with Vag K+CAN Commander?
Logged
Dobermann
Full Member
***

Karma: +7/-0
Offline Offline

Posts: 80


« Reply #80 on: November 13, 2011, 04:47:20 AM »

Have you turn off the immo on bench successfully with Vag K+CAN Commander?


vag comander will not work on bench !!! i tryed it !! immo off work over OBD but the vag commander read not the full file from the m95040

Logged
Swat Cat
Newbie
*

Karma: +2/-0
Offline Offline

Posts: 8


« Reply #81 on: November 23, 2011, 05:41:04 AM »

what software for KKL shoud i use to read eeprom?
Logged
bbernd
Guest
« Reply #82 on: July 15, 2012, 07:50:16 AM »

At the moment the only way to read the entire serial eeprom in it's raw format is to read it using an SOIC 8 adapter and hooking that up to an eeprom reader.

I used a willem eeprom programmer and an SOIC 8 adapter to read mine.

You don't have to remove the serial eeprom chip from the circuit board to read it, you can just clip the SOIC 8 test clip onto the serial eeprom.

bringing this up because ... only read or also writing with the Pomona 5250 Adaptor without removing the eeprom from the board??
Logged
Rick
Hero Member
*****

Karma: +63/-4
Offline Offline

Posts: 704


« Reply #83 on: July 16, 2012, 03:43:12 PM »

Write is usually possible.
Logged
bbernd
Guest
« Reply #84 on: July 17, 2012, 12:38:40 AM »

I will try ...
Logged
grey
Full Member
***

Karma: +4/-1
Offline Offline

Posts: 146


« Reply #85 on: October 01, 2013, 02:49:11 PM »

Thanks for you reply.

I know about the chip in the ecu already.
I use Winols and the ols300 to emulate the 29F800 chip during tuning of the car. It is a known problem that when you use the emulator on specific the ME7.5.x ecu the Eeprom contents can change and lock the ecu. It will set a fault code that cannot be reset. Only possible way to correct this problem, other than buy a new ECU is to remove the Eeprom soic8 95040 from the backside of the ecu and read it before you use the emulator. in case the ecu lock you can always read back the Eeprom to what ever it was before, and it will run again. The problem is that you have to unsolder it every time, and that is not fun when this happens in the night far from home.
I could get the Alientech flash software, that one read the Eeprom also. But its expencive. I was hoping to find somthing to read and write the Eeprom without have to remove it from the print everytime.

Thanks



I have to this damn problem! Any solution?
Logged
JPower
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 24


« Reply #86 on: November 10, 2013, 11:52:12 AM »

Sorry for bringing this up again ....

Since the ignition on/off simulation via a switch wasn't successful I wanted to ask if the situation would change with using an direct VAG ECu cable for ME7.x.x? Would it then be the same reading as via OBD?
Logged
walt
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 16


« Reply #87 on: August 05, 2015, 10:58:25 PM »

Hello!
I have same problems with eeprom and the checksum verification, can sombody help me to turn off the checksum validation on the attached dump?
It's from audi RS4_2,7TT
thanks a lot

Hello, apologies for flying in from left field. I spent the day looking at eeprom data,
specifically for ME7.8. I found some patterns that might be of interest (or might not).
I checked the quoted file above and it seemed to match the pattern, specifically for
the last 2 bytes of each line. Here's the findings:

The first 14 bytes are data, the last 2 bytes seem to be checksums (sort of).

Definition: alpha = row_addr -> right shifted by 1 position
Example: if row address starts at 140h, then alpha = 14h

Rule 1:
======
If 14 data bytes are all 00h:

byte_15 = FF - alpha + 1
byte_16 = FF

Example:

start addr
   1A0             00 00 00 00 00 00 00 00 00 00 00 00 00 00 E6 FF
alpha = row_addr -> right shifted by 1 position = 1A0h - > 1Ah
Byte_15 = FF - 1A + 1 = E6h

Rule 2
======
Row has data

Definition:
sum14 = sum of row's first 14 bytes
sum14_2c = 2's complement of sum14, then only use lower 3 bytes
End definition...

Last 2 bytes:
byte_15 = lower_2_digits(sum14_2c) - alpha
byte_16(high nibble) = F
byte_16(low nibble) = upper_digit(sum14_2c)

Example:

row_addr                14 data bytes                         Byte_15  Byte_16
--------   ----------------------------------------- ------    ------ 
010         05 01 01 00 84 1C 00 00 00 00 69 C1 00 A5   89        FD

alpha = row_addr -> right shifted by 1 position = 010h -> 01h
sum14 = sum of row's first 14 bytes = 276h
sum14_2c = 2's complement of sum14 -> only use lower 3 bytes = FD8A -> D8Ah

byte_15 = lower_2_digits(sum14_2c) - alpha = 8A - 01 = 89h
byte_16(high nibble) = F
byte_16(low nibble) = upper_digit(sum14_2c) = D

Unknowns:
========
None of this seems to apply to first 16 bytes of eeprom.
Apparently a whole row of FFh is ok

That's it Smiley.
Logged
Pages: 1 ... 4 5 [6]
  Print  
 
Jump to:  

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