NefMoto

Hi everyone,

Has anyone removed their Eeprom, put in a zif socket for ease and programmed directly to the chip through for example a tl866?

Is there a reason or theoretical reason this wouldn't work?

I can appreciate through obd is easier in some respects and hence why this might not have been done commonly.

Define "Eeprom"

An ST M95160 Soip 8pin from a Bosch ME7.9.10

Out of a Fiat 500 Abarth


https://www.google.com/url?sa=t&source=web&rct=j&url=https://www.st.com/resource/en/datasheet/m95160-r.pdf&ved=2ahUKEwibm4WfjebqAhUJQhUIHSrkDFgQFjAAegQIARAB&usg=AOvVaw0wdD23pYBckbxwuoGEdqwQ

https://uk.rs-online.com/mobile/p/products/6862330/

Thanks for the reply that was hella fast

What's the reason to flashing it more than once?

I partly chose this route to hopefully minimise read and write errors partially through precise voltage control but also so I can have multiple chips to easily test different tunes and alter one whilst the other is on the Dyno for example.

That and it seemed an uncluttered way of getting information from A to B, as direct and simple as I could think to make the process whilst also being a standardized process that others might be able to easily follow.

If OBD flashing isn't option, and you're willing to put in the effort to put in a zif socket, why not try a rom emulator?

I had a look for example at the Ostrich and for sure an emulator would be a better way of changing data quickly I like the idea of trying that later down the line thanks nyet.

I'm in the midst of doing all this and I'm just waiting for more chips to arrive so I've always got my unfettled oem one to fall back on.

The biggest hole in my knowhow (there's a few I'll be the first to say) is decompiling the oem read data to pick out tables and single cell variables, hats off to you all for doing that the sheer time involved.

When I've got this all together Ill put some pics up and it might help someone out at some point.

Ive done this you need a sioc8 sockett

Cheers Marty,

I'm going to take the surface mount pin legs bend them 90 degrees and stick them straight into a dip socket to start, then faff with a zif and like nyet mentioned maybe an emulator, the walk before run approach to hopefully avoid cockups.

If anyone gets a spare minute and could take a look at this I'd really appreciate it.

This seems to be all I can pull off the prom, I gotta be doing something surely?

Wait a second. 95160 is a 16Kbit (2KByte) EEPROM, so your dump makes sense. Here's the thing... this stores the NVRAM-style volatile vehicle specific data (VIN, Immo, DTCs, etc.) for the ECU, not the dataflash containing the code and calibration. I don't think you're reading / writing the part of the system you think you are...

If I style it out and pretend I wasn't reading the wrong chip I'm sure no-one will notice...

Thankyou very much d3irb. That's exactly what I've be doing haha

On the plus side I'm getting somewhere...i identified that chip albeit incorrectly just based on info I could find about people reading chips on this ecu and lots mentioned that one, it would appear for a different purpose though, immo related?

I'm not entirely sure how to identify the one I need to read for the map, I'll try and work it out over the next couple of evenings.

Which map? Motronic has several thousand :P

None of them are in the eeprom.

I bought these for my ecm's.