KTAG EDC 17 E2P modification after writing

**Smart66** · 21st January, 2022, 01:54 PM

It's BOSCH EDC17 CP(14) ECU with TC1796 E2P. FLASH is same after rechecking so that difference only exists in EEPROM. I don't know if KTAG calculates E2P checksums because I've already compared these files and difference is from 8B80 to 8DF0. VIN number is added a few times and something other which you can notice in these files and pictures.
Can anyone check checksums of modified E2P? Is that E2P made well?
Why does KTAG do that? Is it necessary?

Difference in HEX : https://i.postimg.cc/jRhzzXmk/Web-1920-1.jpg

**Panathaole** · 21st January, 2022, 02:52 PM

Originally Posted by Smart66

It's BOSCH EDC17 CP(14) ECU with TC1796 E2P. FLASH is same after rechecking so that difference only exists in EEPROM. I don't know if KTAG calculates E2P checksums because I've already compared these files and difference is from 8B80 to 8DF0. VIN number is added a few times and something other which you can notice in these files and pictures.
Can anyone check checksums of modified E2P? Is that E2P made well?
Why does KTAG do that? Is it necessary?

Difference in HEX : https://i.postimg.cc/jRhzzXmk/Web-1920-1.jpg

Hi

in your ktag modify e2p dump, cks are correct....

the eeprom is not physical, is virtual, the processor create new one....

**Smart66** · 21st January, 2022, 03:19 PM

Originally Posted by Panathaole

Hi

in your ktag modify e2p dump, cks are correct....

the eeprom is not physical, is virtual, the processor create new one....

E2P read is different only if I switch off 12V from KTAG and start KSUITE again. If rechecking is done immediately after writing there is no difference. Probably, KTAG recognizes same E2P in other way

Does it mean that all these different E2P's produce same result although dumps are a little bit different?
What is presented repeating these VIN nubmers ??? ECU won't mind these lines of dump??

**antwnhszr** · 21st January, 2022, 04:31 PM

hi dear.the vin number is and in flash file.and is eeprom file.if you change the vin only in one file the mcu compare the files and turn in before mode.....try to write the flash first and after the eeprom.

**Smart66** · 21st January, 2022, 04:40 PM

Originally Posted by antwnhszr

hi dear.the vin number is and in flash file.and is eeprom file.if you change the vin only in one file the mcu compare the files and turn in before mode.....try to write the flash first and after the eeprom.

I've never mentioned VIN changing or anything like this. Read my previous post same VIN is added in E2P sequence after writing...

**Smart66** · 22nd January, 2022, 09:17 AM

Anyonee with similar experience ???

**figani** · 22nd January, 2022, 01:06 PM

Originally Posted by Smart66

Anyonee with similar experience ???

mate, ksuite/ktag is not calculating cksum on EE....
equal what kind of EE...

use hex Editor...
try to figure out by search if VIN is also present in Flash...
if it´s present in flash edit it by hex editor and ksuite/ktag will calculate cksum through writing process...

if you edit VIN in EE...

YOU MUST do CKSUM ALONE before you write it...
if you don´t know how to do it...
post here ORI and MOD...
and someone will calculate CHKSUM...

very easy...

**Smart66** · 22nd January, 2022, 01:26 PM

You don't understand what I'm asking for. I don't need any VIN modification not in FLASH nor E2P. The EEPROMS' difference is presented in picture above and I posted both files too.
The main question is : Why does KTAG read different E2Ps of same ECU for two attempts?

**Panathaole** · 22nd January, 2022, 11:15 PM

I had face that in ford edc17.....

Not just few bits difference, but almost all eeprom was different.....

In one reading starts with 00 00 and in the other starts with letters....

But car starts fine in both cases....