I am new at this so hopefully this is a good question. I want to get the information from my Fastchip chip to compare with my stock bin to see what is changed. I was wanting to do a bin dump but when searching I can only find being able to do it with ECM 852. My laptop runs XP so it does not work. What other programs could I use? I have Datamaster, Freescan, WinAldl.

Thanks
Chris

Edit: I forgot to mention I do have an Autoprom & Steve Ruse max232 cable and a cable as made per instructions on the WinAldl page.

 

TunerPro RT has a hex editor built in. Also Hex Workshop. Both work with XP.

 

I have tried to read a "Fastchip", but many of those prom-writers disable the ability to read the eprom for obvious reasons.

Just warning you.

 

How does the ECM read the chip if the prom reader can't read it?

 

Maybe they rearrange stuff so it looks garbled with a standard xdf or .ecu. Just a guess.

 

The ECM doesn't read an eprom...it executes the code inside the eprom. Loading the contents of eprom into the eprom burner's buffer (so we can read/modify it) works differently than executing the code within it.

 

I was able to remove it from the memcal & read it with Autoprom & Tunerpro RT. Trying to decipher it now. thanks for the help!

Chris

 

A standard parallel EEPROM/EPROM/PROM/FLASH has one read port and one write port. Both the EPROM reader and ECM excercise the read port. A microcontroller READS the EPROM and then interprets the bits (execution phase). The ERPOM reader/writer can also excersize the write port.

A microcontroller interprets bits. An tuner/editor tool interprets bits. A disassembler interprets bits.

The EPROM reader can read the chip if an ECM can. One can re-arrange the code and/or re-write it so the tables are moved and the code is moved. To a tuner/editor, the info will look garbled.....but the EPROM has still been read at this point. Just like the stock GM BIN has been disassembled, so can the aftermarket bin. What is the difference between disassembling a GM bin and an aftermarket bin? GM spent more creating the code than the aftermarket vendor did. Also, an aftermarket bought chip is a waste of time and money.

EDIT: If the EEPROM is inside the microcontroller chip.......like say an Atmel AVR then the code can be protected so that it is un-readable. I bet if you tried to read some of the so-called emulators out there using an AVR you would find that they have been "locked" and the bit stream updates for firmware updates has been "encoded" so that the microcontroller decodes it before writing to the internal EEPROM. Although, when coding with assembly, I bet the "encoding" is easily broken using a standard desktop PC.