88gunmetalgta

iTrader: (1)

My car has been behaving weirdly since I burned my last chip, so I tried to burn a new one.
Using Moates Flash n Burn, and a Burn 1 programmer. Done this many many times before.

Erased chip fine,
blank check is good (even read the chip to verify after this step.)

program chip, successful

verify bin with buffer, failed (not matched)

WTF?

I read the chip again, and it has data written to it, but I haven't compared to find where the differences lie.

I'm thinking this is to blame for my car's recent weird behavior. Since when I put the chip in, it reads fine and my car will run. I'm guessing its a hardware problem with the Moates burner.

Anyone else run into a similar issue?

88gunmetalgta

iTrader: (1)

Ok tried it again.

Burned a bin to the chip.
Read the chip, saved to a file.
read it again, and saved it to a different file.
used a bin compare utility to check for differences
Burned bin to read bin was WAAAY different.
There were differences between the two read bin files too. Not too many, but enough to screw something up I'm sure.

Really suspecting a hardware problem at this point.

88gunmetalgta

iTrader: (1)

Figured it out. That's what happens when a small rock gets jammed in the zif, and prevents it from closing around the pin all the way.