he has been looking for 2 weeks, so he is determined to learn ... I think.
He invested in a programmer ......
If it was an urgent matter, it would probably be over.
But I can be wrong - he has to determine himself.
Czy wolisz polską wersję strony elektroda?
Nie, dziękuję Przekieruj mnie tamglapsson wrote:Well, it's from a different barrel.
Question for mathematicians and programmers - but still on the topic of BSI (N0x)
I blurred VIN because nobody needs it for anything
I marked the area with the read PINs under the VIN number
I will add that the exchange of these areas between BSI makes the PIN migrate in full
Of course, I have a facebook what counts it from the machine, but the question arises from curiosity - HOW is it counted?
![]()
melas wrote:Hello. ..............
I'm sorry that I interfered with the thread
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].