Loud and clear, I hear you nyet!
I have actually fully re-written this tool in C for eeprom read/writing/check-summing and verification.
It is now much more reliable and stable (at least for me) than it ever was before as I use high resolution timers for delays.
Plus I've implemented some additional useful features like ;
> Eeprom checksum calculations
> Verification of eeprom writing by reading back and comparing the differences.
> Automatically detecting the eeprom pins and sizes - this works by parsing that information directly out of the accompanying firmware so its fully automatic in use, you don't really need to know anything to use it.
> It supports differential analysis too if you load in 2 different eeprom files to see what's changed.
> Finally it also can parse out of the firmware the page table too.
I use the exact same mechanism as the original tool in that I upload bootstrap loader so you need to start it in "boot mode", then I upload a small C167/ST10 eeprom driver in memory and send commands to read/write blocks between the pc and ecu.
I'll see if I can clean this lot up and put it on github as soon as I get some free time...
It would be pretty easy to also implement the virginizing of eeprom too but its going to be firmware specific (I already support it for my targets but didn't look into this for any other cars like VAG)
Will this work with CH340 cables / general uart or you made use of ftdi drivers/dll's requiring ftdi based cables? Sounds good regardless, well done.
