Sudden random problem burning chip with Willem
#1
Guest
Posts: n/a
Sudden random problem burning chip with Willem
I just got my new engine in and have to burn a new basemap for it. I am using the Willem dual power burner and an SST 27SF512 chip. I can erase the chip fine. For some reason I cannot get a bin to burn to the chip after I load it in the program now. I am using an offset of 8000 (same error with no offset) and the error message I get when I try to burn the chip is "Error at0x000000 Chip=0xFF buffer=0x22". I can do a blank test after this and the chip is still blank. If I load an "empty" bin (FF in every location) the chip will burn normally. Help I wanna drive my car!
#4
Re: Sudden random problem burning chip with Willem
Maybe the burner is fried?
I loaned my functioning-that-day Batronix to a kid only to get a phone call that same evening...
"Dude. Your burner is fucked up! It won't burn any chips! I keep getting these errors!"
I got the burner back from him and found that it would write a blank file just fine, but I would get write errors if I tried to burn an actual program to the chip. Upon closer inspection, I found that the main voltage regulator was sitting somewhere near the temperature of the sun. Somehow the kid had burned up a couple of FETs on the board, causing the regulator to be overloaded. A couple of new parts and some soldering later and the burner was good as new.
I loaned my functioning-that-day Batronix to a kid only to get a phone call that same evening...
"Dude. Your burner is fucked up! It won't burn any chips! I keep getting these errors!"
I got the burner back from him and found that it would write a blank file just fine, but I would get write errors if I tried to burn an actual program to the chip. Upon closer inspection, I found that the main voltage regulator was sitting somewhere near the temperature of the sun. Somehow the kid had burned up a couple of FETs on the board, causing the regulator to be overloaded. A couple of new parts and some soldering later and the burner was good as new.
#5
Guest
Posts: n/a
Re: Sudden random problem burning chip with Willem
Originally Posted by Rory
Maybe the burner is fried?
I loaned my functioning-that-day Batronix to a kid only to get a phone call that same evening...
"Dude. Your burner is fucked up! It won't burn any chips! I keep getting these errors!"
I got the burner back from him and found that it would write a blank file just fine, but I would get write errors if I tried to burn an actual program to the chip. Upon closer inspection, I found that the main voltage regulator was sitting somewhere near the temperature of the sun. Somehow the kid had burned up a couple of FETs on the board, causing the regulator to be overloaded. A couple of new parts and some soldering later and the burner was good as new.
I loaned my functioning-that-day Batronix to a kid only to get a phone call that same evening...
"Dude. Your burner is fucked up! It won't burn any chips! I keep getting these errors!"
I got the burner back from him and found that it would write a blank file just fine, but I would get write errors if I tried to burn an actual program to the chip. Upon closer inspection, I found that the main voltage regulator was sitting somewhere near the temperature of the sun. Somehow the kid had burned up a couple of FETs on the board, causing the regulator to be overloaded. A couple of new parts and some soldering later and the burner was good as new.
Oh, and I can't see anything physically wrong with the burner. No black marks, ripped traces, or anything like that. sheeeeeeit any more input?
#6
Re: Sudden random problem burning chip with Willem
Aside from burning my finger on the regulator, there was no physical evidence that the burner was damaged.
If it's been sitting in a box, untouched...I have no idea. Maybe it just sucks and randomly died. :P
If it's been sitting in a box, untouched...I have no idea. Maybe it just sucks and randomly died. :P
#7
Guest
Posts: n/a
Re: Sudden random problem burning chip with Willem
Originally Posted by Rory
If it's been sitting in a box, untouched...I have no idea. Maybe it just sucks and randomly died. :P
Thread
Thread Starter
Forum
Replies
Last Post
green91
Engine Management
1
08-23-2004 01:40 PM