I will read your PIN and see what's recorded there.
I will read your PIN and see what's recorded there.
Czy wolisz polską wersję strony elektroda?
Nie, dziękuję Przekieruj mnie tamgrzesiekw12 wrote:GORO35, since you have the motorola eeprom reading, this is where the pin sits. Put on the forum and it will be read what you need. What happened to the processor? You pulled out some legs or the power supply vice versa. Like the legs, you can read the cut on the casing. What was the purpose of the intervention in BSI? Ps These motoroles in BSI sometimes give a false reading and you have to raise one BDM resistance
TL;DR: “100 % read success” was achieved after desoldering the 95128 EEPROM on Delphi EL5 BSI, yet on-board pads returned only FF bytes in 3 of 3 initial attempts [Elektroda, glapsson, post #18338259] "Read on pads, write on pads" is possible once HW is mapped [Elektroda, glapsson, post #18338655]
Why it matters: Correctly extracting EEPROM data prevents immobiliser lockouts and €600+ ECU/B S I replacement costs.
• EEPROM package: 8-pin SOIC 95128/25C128; density 128 kbit [Elektroda, glapsson, post #18338259] • Typical bench supply: 12 V / ≥2 A; UPA-S input must stay >4.5 V (drops to 3.7 V cause read FF) [Elektroda, glapsson, post #18371587] • PSA “tokens” for online coding cost €42 per VIN for 7 days [Elektroda, glapsson, post #18338655] • HW generations: D5 (2013-2016), D6 (≈2017-) – socket layout differs, algorithm identical [Elektroda, glapsson, post #19022682] • Commercial readers confirmed: UPA-S, SeeProg, VP-390, Xprog-M, CarProg, Obdstar H108 [Elektroda, multiple posts].