Hi kur4o,
I'm glad to do some experimenting with you guys. I'm going to order some flash(Is it same for obd2 too?) and sockets in a few minutes for future but we can play with on-board till all the smoke comes out. I'll keep a smoke vac handy so I can put it back in
-Carl
after flashhack has stabilized i do plan to catch this spare ECM on fire attempting to do it.There is also some header left that have most of the flash chip pins. Wring the header and adding vpp to the board will be really cool experiments we are trying to do for a long time.[Recovering without removing the chip.
i do think its possible, because the tunercat/winflash guy has offered a very cheap repair service, and someone i know used it, opened the ECM, and found the chips untouched, so he must have built some hardware to do it...? (either that or traded a core, but i doubt it)
Originally Posted by In-Tech
Hi kur4o,
I'm glad to do some experimenting with you guys. I'm going to order some flash(Is it same for obd2 too?) and sockets in a few minutes for future but we can play with on-board till all the smoke comes out. I'll keep a smoke vac handy so I can put it back in
96-97 have 128kb tside chip intel an28f010, eside is an28f512
Thanks for the reply, getting ready to order...are any of these "B" chips that read from the bottom or just as your part numbers?
Also, do I use only intel brand or does it matter since it's flash? I ask because I might already have some NOS in my stash pile/box.
-Carl
Look for N28f010 or N28f512 , Intel brand in PLLC32 package. a is for automotive application, extended temp range, but they are nowhere to be found
Brand matters because of different command set. The pcm is set for use with intel brand.
There is different access time, the lower the better, anything below -120 ns will do the job.
You can also get the 128kb from a 96-97 blackbox pcm.
If you have something available give it a try, they will work. I am sure your onboard` ones will work too. So you might not really need them.
Thank You
-Carl
flashhack is really behaving well with extreme testing. i unplugged the usb cable and then restarted the program, and it flashed again like nothing was wrong. i will do a resume flash feature too to avoid re-erasing.
even if your car battery goes low, if you keep ECM powered enough to stay running, you can go plug a battery charger in and try again, even days later. you just have to be careful not to drop ignition power.
if kur4o's ecm patch works i'm going to be so happy and it'll be insanely hard to brick one of these things.
fixed some more bugs. i'm not very good at math so this is all a struggle. the block mapping algorithm had a off-by-one error that took forever to track down (when you have tons of offsets/sizes/lengths its bound to happen) but it's finally writing all the blocks without re-rewriting anything.
one cool thing that testing has revealed, is re-writing a block doesn't seem to cause trouble (since you're setting a bit that's already set, and the it passes verification no problem) so if you failed a write due to a communication error or power failure, you could probably just safely continue on without re-erasing and causing further risk.
i'm also writing a new progress display that will show you more clearly what's going on, but since it uses matrix transforms and i suck with math, it's not going well yet. will be testing kur4o's recovery patch again tonight and lets hope for the best. once that's working i'll release a beta and let people try it out.
Posting Permissions
Reply With Quote
Bookmarks