vince59 wrote:...should I try to read the original eeprom as 25080?...maybe using EZP2019 as well?
As above said, try reading as 25C80 or even try with another programmer
When you have full read we can make your new file for your 95080 chip
wbr
vince59 wrote:...should I try to read the original eeprom as 25080?...maybe using EZP2019 as well?


Shooting wrote:vince59 wrote:...should I try to read the original eeprom as 25080?...maybe using EZP2019 as well?
As above said, try reading as 25C80 or even try with another programmer
When you have full read we can make your new file for your 95080 chip
wbr



vince59 wrote:...one mistake in previuos post....flash 5P08C3 as 95040.
So just for clarification:
- read original 5P08C3 as 95P08 with colibrì and CH431;
- flash the original dump into donor 5P08C3 with TL866II as 95040.
This worked for me. No more red engine warning light.
Next to solve recover the bricked 29f400 :evil: :twisted:
@ Shooting: your fixed file was correct. The issue was still present because some bits were different due to mismatch in the dump when reading the 5P08C3 as 95040 with TL866.

Shooting wrote:Told you, you needed a good read :D .. so glad it worked :D
wbr

vince59 wrote:Shooting wrote:Told you, you needed a good read :D .. so glad it worked :D
wbr
Thank you and the others for the given help!
Just one question for my knowledge. After solving the issue I still have another ECU left (the one waiting for 29f400 fix) and I am playing with another 5P08C3 eeprom. I am testing reading/writing the eeprom with the programmer I have and I wonder why I often get a slightly different reading. I mean, I flash the file and the reading gives me three bits with different value. Is this a hw problem or what?



Users browsing this forum: No registered users and 2 guests