[PhilipM]

M5.2 = EWS2
M5.2.1 = EWS3

ISN (EWS2) in M5.2 is written at 0xFD3D, 4 Decimal digits in ascii, which need to be converted to hex
ISN (EWS3) in M5.2.1 is written just after this at 0xFD41, raw hex from the dump, 2 bytes repeated three times.
Address offsets are for full reads from the flash, part read will not show the EWS3 ISN, only EWS2 ISN from M5.2

[LeparaiN]

Now i´ve got the pictures of the DME



Someone can tell me where i have to connect? I have X-Prog, Galleto, K-Tag , UPA Porgrammer....

Thanks all for help

---

M5.2 = EWS2
M5.2.1 = EWS3

ISN (EWS2) in M5.2 is written at 0xFD3D, 4 Decimal digits in ascii, which need to be converted to hex
ISN (EWS3) in M5.2.1 is written just after this at 0xFD41, raw hex from the dump, 2 bytes repeated three times.
Address offsets are for full reads from the flash, part read will not show the EWS3 ISN, only EWS2 ISN from M5.2

BMW Scanner said to the EWS 3 algorithm .... EWS 3 (like EWS2). Which ISN i need now?

[bawareca]

Check the Ktag help, the connection is there. Also the 2 bytes isn in dme are swapped in the ews.

[LeparaiN]

Guys... i think i´ve got it !






is this dump correct?

---

ISN Number is now? 232F232F232F
How it should be in the EWS?

[PhilipM]

yes, that's correct.
with the order swapped, I believe it should be 2F23 in the EWS box, and then rolling code sync will be needed.

The older EWS2 ISN is written just before this, these are just serial numbers programmed into all of the M5.2.X ecus, and they don't get used anymore.

In Ascii, this was 000044473, you would take the last 4 digits, "4473", convert to hexidecimal = 1179 and discard the first digit so the EWS2 ISN would be 179.

Anyway, as you know, this is EWS3 so you can ignore that bit about EWS2!

[LeparaiN]

BIG THANKS !!!

It´s running now

I took one used EWS and wrote the right ISN on it....

One more time... THANKS !!!