Originally Posted by
Tanakrit
Hi all!
I'm incredibly new to all of these shenanigans, and was wondering how one would get started?
The vehicle:
What I know so far:
- It is unlikely that I can use OBDSTAR/other OBD port tools to alter the mileage
- The data is stored on an EEPROM on the back of the cluster
- People extract this information, and members on the forum seem to have software/algorithms to modify the file and mileage data
What I don't know:
- What is the recommended tool for for reading/writing the data from the EEPROM (Digiprog?)
- Is de-soldering the chip a requirement?
I'd essentially love to learn more, and would like to empower myself to be somewhat self-sufficient
If you have any guides and documents that I've somehow missed, I'd love to be linked them. Thanks in advance team!
I am in a similar situation, though i managed to read and write that eeprom with an arduino nano, which is probably not the recommended tool.
(i forked a project on github and added two examples that seem to work for my chip, username on github is the same as here, in case somebody wants to try)
Basically i took apart the dash of my ibiza 6k ('99) to see if i could replace the parking light with a small oled screen and maybe get some data from the radio to display it there, and then i saw that 93c66...
Worst of all is that i accidentally wrote to the chip, i tried a few different projects, had many arduino ide windows open, probably uploaded the wrong sketch... and lost about 220k kilometers in the process, which might sound hillarious, but that's what happened.
So i'm not sure, i could probably post my dump now and somebody would fix it i guess, but i'd prefer if i could understand the format of those bytes, after all, that's why i soldered wires to it... (the answer to de-soldering required is obviously no in my case, powered the chip from the arduino 5v pin, that obviously worked)
Dumb question now: Is this all only data? Or is part of that bytes a firmware that is read by some microcontroller?
i tried to fix the first 4 bytes with another, similar dump i found here on the forum, because i thought these were probably the ones i changed, but this didn't have the desired effect it seems. The beginning of my dump now, after my fixing attempt looks like this:
Code:
0009 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
B811 1CC9 1033 18D3 FFFF FFFF FFFF FFFF
FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
47EE E336 EFCC E72C FFFF FFFF FFFF FFFF
FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
0100 0603 0804 0006 0301 0406 0608 0100
0603 0804 FF06 C7F0 C7F1 C7F1 C7F1 C7F1
C7F1 C7F1 C7F1 0000 0000 0000 0111 0104
6400 2222 2822 0080 4356 4356 1400 0080
05DC 0000 0361 0EBF 0EBF 0704 0001 0000
and yes, i got the complete dump, and yes, i could convert it to a binary file, but as mentioned earlier, it would be great to understand the "why" and "how"?
Bookmarks