Pages: 1 ... 6 7 [8] 9
Author Topic: MED9sum: Correct those MED9 eeprom checksums!  (Read 133644 times)
IamwhoIam
Hero Member
*****

Karma: +52/-115
Online Online

Posts: 1070


« Reply #105 on: June 27, 2019, 06:14:07 AM »

There are 2 EEPROMs that mirror each other. Some tools just read it once but the protocol is clever enough to ensure both EEPROMs are written. Other tools will back up verbatim and read both in serial.

Quote
• Memory array
– 16 Kbit (2 Kbyte) of EEPROM

Facepalm! The only reason pasta tools read 2 and save the eeprom twice is because they're ret@rded, especially when it says black on white in the datasheet of the physical eeprom that it only contains 2kb worth of data.
Logged

I have no logs because I have a boost gauge (makes things easier)
rysiektr
Jr. Member
**

Karma: +3/-3
Offline Offline

Posts: 47


« Reply #106 on: March 13, 2020, 06:53:31 AM »

Today I do a tests of eeprom dump 95160 (2kb) from MED9.1 8E0910155J 0010. Ktag (clone) is reading this memory as 95320 (4kb) only, can't read as 95160 protocol.
When I do immo off via eeprom_v2.1.1 that file and then wrote eeprom via ktag, immo is still ON. Ktag (clone) wrong read and write that file in my opinion.
So i desolder 95160 from ECU PCB, read via programmer as 95160, then do immooff and solder again to ecu PCB, after that immo is off.

Sorry for m y english, it is not my native language.

Enjoy  Wink
Logged
IVANVXR
Newbie
*

Karma: +0/-3
Offline Offline

Posts: 24


« Reply #107 on: April 07, 2020, 11:19:29 AM »

I test this program and try to kill immo on 9.1.1 but immo is still on.
Read with original KTAG --2 kb value
Logged
rysiektr
Jr. Member
**

Karma: +3/-3
Offline Offline

Posts: 47


« Reply #108 on: April 08, 2020, 12:45:49 AM »

I test this program and try to kill immo on 9.1.1 but immo is still on.
Read with original KTAG --2 kb value

Try to desolder and read immo eeprom via external programmer and then do immo off.
Logged
IVANVXR
Newbie
*

Karma: +0/-3
Offline Offline

Posts: 24


« Reply #109 on: April 13, 2020, 12:58:28 PM »

Yeah but my KTAG ORI read 2kb dump, not 4 kb.
I can try..
Logged
yxx499
Full Member
***

Karma: +4/-10
Offline Offline

Posts: 106


« Reply #110 on: April 13, 2020, 04:44:30 PM »

I don`t know what KTAG do you use, ORI or Clone but my KTAG - even pizza / pasta and whatever you want is reading 4kb of data and never had any issues with IMMO off, or ,when i had, was my personal fault, not KTAG.

Yes, Flex Bench mode is reading 2kb....
Logged
IVANVXR
Newbie
*

Karma: +0/-3
Offline Offline

Posts: 24


« Reply #111 on: April 18, 2020, 01:11:50 PM »

Try to desolder and read immo eeprom via external programmer and then do immo off.

This is 100 % true story.
Today I was desolder ST95160 and read with programmer any found there some missing parts.
After immo off solutuion written by KTAG damage eprom then KTAG won't comunicate with ecu again.
I will try to fix my eprom manually and write by probrammer and try first to get comunicate with car/diag
This is first time in my life when KTAG makes me shit day/week
« Last Edit: April 18, 2020, 01:14:47 PM by IVANVXR » Logged
IVANVXR
Newbie
*

Karma: +0/-3
Offline Offline

Posts: 24


« Reply #112 on: April 24, 2020, 01:42:53 PM »

NEWS

As I said before, first ecu stop working,why,I don't know,don't have idea..first time in my life.I think MPC was broken
Today i buyed spared ecu-same HW,another SW and flash backup from previous ecu.
After I try once more time this software, put .EPR read by KTAG, write after IMMO off solution also with KTAG and now solution working.
Adaptations---> immo status---> 1(deactivate)
Car running proper.

I don't know why solution doesn't work first time on first ecu. Read/write with KTAG ORI

May this help something...
Regards

Logged
bamofo
Sr. Member
****

Karma: +34/-3
Offline Offline

Posts: 420


« Reply #113 on: September 24, 2020, 07:10:33 AM »

Is there a Github for this or opencode to make updates? looks like MED9.1.1 has differences in the S5 and other platforms where there are 3 sets of Vins and its not picking it up right. Would like to update it if possible, without recreating the whole thing...
Logged
Hollywood
Full Member
***

Karma: +6/-1
Offline Offline

Posts: 60


« Reply #114 on: October 12, 2020, 03:09:56 PM »

Do you know how to immo off the s5 med9.1.1? The eeprom is encrypted and standard immo off methods dont work.,
Logged
Michael28
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 9


« Reply #115 on: March 20, 2021, 12:52:50 PM »

I have 2 blocks  MED9.5.1 on my table. And both blocks contain 95080. Ktag counts them as 95320. This is certainly not true for our purposes. So I'm reading this block mode BDM programmer TNM5000
Logged
elektronik13
Full Member
***

Karma: +10/-36
Offline Offline

Posts: 204


« Reply #116 on: March 22, 2021, 12:23:09 PM »

I have 2 blocks  MED9.5.1 on my table. And both blocks contain 95080. Ktag counts them as 95320. This is certainly not true for our purposes. So I'm reading this block mode BDM programmer TNM5000
share eeprom to Crc we will count for you
Logged
solo786
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 3


« Reply #117 on: November 16, 2022, 08:40:23 AM »

HELP Please

I have a problem with TTRS MED9.1.2
I wrote by autotuner OBD and VR, then after some miles the dreaded P0601 error appears (internal memory checksum error)

After some research it says this is a problem because of anti tuning protection and RSA key calculation not done correctly with autotuner.

I have read back with KTAG and then used MED9 sum to redo chk, and i wrote back to ecu, but this problem still exists.

I have another full dump from an 8J0907404M 0020 ecu with older sw version , can I modify this EEP with vin data and IMMO off and write this version to my ecu which have a newer sw version?

Thank you
Logged
elektronik13
Full Member
***

Karma: +10/-36
Offline Offline

Posts: 204


« Reply #118 on: November 17, 2022, 01:13:03 PM »

HELP Please

I have a problem with TTRS MED9.1.2
I wrote by autotuner OBD and VR, then after some miles the dreaded P0601 error appears (internal memory checksum error)

After some research it says this is a problem because of anti tuning protection and RSA key calculation not done correctly with autotuner.

I have read back with KTAG and then used MED9 sum to redo chk, and i wrote back to ecu, but this problem still exists.

I have another full dump from an 8J0907404M 0020 ecu with older sw version , can I modify this EEP with vin data and IMMO off and write this version to my ecu which have a newer sw version?

Thank you
why didn't you share the eeprom here
Logged
solo786
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 3


« Reply #119 on: November 22, 2022, 04:14:36 AM »

Hey , I am not so sure how to attach files.

In the meantime Ive discovered that the FLS and MPC needs to be tuned and ck must fixed then you write by BDM
Logged
Pages: 1 ... 6 7 [8] 9
  Print  
 
Jump to:  

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