Toyota 4Runner ECU - Remove, Reflash and Reinstall 93c56 EEPROM to learn new ignition keys. 

Thanks brother. Your kind words are much appreciated!

Sorry, I don't know anything about how Ford ECUs work.

Generally all eeproms are recommended to be near the main processor. Start there. Also see online on how smd I2C eeproms look. 90% of the times i2c is used.

Thanks for your help 🙂.

When an EEPROM is blank, the bytes are all FF. If you look at the screen in the video around time 11:25 you'll see the 4 bytes that need to be changed from FF at offset 003A, 003B, 00BA and 00BB.

Thanks, I did try that first but I was getting bad data when reading the EEPROM so I pulled the chip. Could have just been a limitation to my reader.

No I don't think I did, but thats a great idea and probably would have saved me desoldering!

@@retrotechinsanity Thanks! But I can't take credit for the idea. I saw someone do it on YT. It worked, but the guy in the video did say not to get too upset if it didn't work for you. I take it that it's a coin-toss as to its' success rate.

That Xhorse tool looks pretty cool and would certainly make this easier, but it's quite expensive!

@@retrotechinsanity I will definitely invest in it if it makes it a lot easier. My only concern is that I heard when you try to read it directly off the board, it can corrupt the file? That’s why I’m a little hesitant to purchase and use it

@@Cali415 I tried to read the chip without removing it from the board and had corruption issues which is why I wound up desoldering the chip

@@retrotechinsanity Do you mind me asking what you used to try reading it from the board?

@@Cali415 I had tried one of those CHA341 based clip on devices as well as building my own circuit on a bread board (think it was a few diodes and resistors) and wiring it into the XGpro. Both had a similar result where the data read was different every time. I imagine it was because when powering the board with 5v to read the chip, other devices on the data bus came to life and caused problems.

i 'm newbie about read epprom sir..my device is ezl 2019 .i can read this ecu epprom but i don't no what to do with the data sir ..i replace my ecu smartkey but i don't have ignition on sir..i think i want copy this data to ecu smartkey.can i do it sir to get ignition on? thanks you very very much sir if you give that infomation...

I don't know if the 93's work the same way as these slightly later models which have this type of ECU. My understanding is that the key itself isn't programmable, it just has an RFID type of device that has to be learned by the ECU. So when you blank the ECU, you re-learn that key to the ECU but the content of key's RFID doesn't change.

There is no "file", you just need to manually edit the correct bytes to the correct values and write it back to the chip.

Thank you, sir. But you did show a file there. Anyhow, forgive my probable ignorance, but even with that, what is your reference in what to do with what bytes for any given make and model?

@@engineereuler1762 Sorry, I have no idea what to do with any other makes or models. I just know this is how you zero out the learned key data for this particular ECM. I did this as a favor for a friend and don't normally do this kind of work. Most of the rom programming I do is for old 8 and 16 bit computers. All the other videos I ran across used the chip clip method to reprogram the eeprom while it was still on board the pcb. For whatever reason, the clip method wouldnt work with two ECMs of this model. I guess it was the wrong clip or a poorly made one, hence the need for desoldering. I created the file that was used here based on documentation I found on the net somewhere. I would imagine its a similar method for other ECM's utilizing this eeprom chip.

@@engineereuler1762 As for the file, I created it. It's only 4 bytes of data and the rest are zeros. Just recreate it based on what's seen on the screen. I may still have that file somewhere but the computer I used is packed away right now. As for the make/model comment - different makes and models of vehicles may use a similar process but the data you need to enter will vary.

@@retrotechinsanity can you please show the 4 bytes and explain their bits and what they mean?

drive.google.com/file/d/1qyAsnRbADn-IPb1UGoesQJQYbm4k9-ZL/view?usp=sharing

Sorry for the delay, have been in the process of moving and am just getting caught up on everything.

Hello, can i get that bin file, please.

​@nandotobar51 not a good link.