29C256 prom will not program
29C256 prom will not program
Using fileprom, I changed the start and end file to 004000 and 007FFF. The proms will not program. This is a $6E code bin. Any ideas?
Jason
------------------
89 Six Speed FX3 coupe
More Performance 396cid specs:
Callies 4340 crank 3.875 stroke
Lunati Pro-Mod 5.85" rods
SRP Pistons 14cc dish
Comp Cams Custom cam 550 lift 220/229 duration
10.8:1 compression
AFR 195 competition ported heads
Miniram and TPIS 1 3/4" headers
Jason
------------------
89 Six Speed FX3 coupe
More Performance 396cid specs:
Callies 4340 crank 3.875 stroke
Lunati Pro-Mod 5.85" rods
SRP Pistons 14cc dish
Comp Cams Custom cam 550 lift 220/229 duration
10.8:1 compression
AFR 195 competition ported heads
Miniram and TPIS 1 3/4" headers
Jason,
I have a problem progamming my 29c256's when i FIRST turn the fileprom on, it will say that it programs, even does a checksum, but when i do a blank check of the chip it is still written. The way i get around this is to change the chip id to a 27c256, then i write the chip. Then i switch the chip type back to the at29c256. Then i proceed to with the chip with an FF.bin(the bin writes all sectors as ff(or blank), thanks glenn!). After i do the FF write i then write my intended chip. It works fine everytime.
I only have to do the 27c256 write wheneve i INITIALLY open the fileprom, if i write a chip and then leave it runnning and come back it will erase and rewrite the flash proms fine everytime. You may want to try it.
Let me know whats happening.
Brendan
------------------
1987 IROC-Z L98,SuperRam,EB 6085's,LPE 219/219 Roller, Crane 1.6RR, EB TPI Base, 58mm TB, ADS 24#, AFPR, K&N, EB TES, Catco Cat, 3" Borla Cat-Back, Accel cap,rotor,distro/other crap, MSD 6AL, MSD Blaster 3, Aluminum DS, 94 Disk Rear, Adjustable Valve, Precision 3.73 Gears, Sub-Frame Connectors, Hotchkis Lower Control Arms, KYB Shocks/Struts, Suspension Techniques Lowering Springs, Polyurethan Bushings all over the place, Moog Upper/Lower Ball joints and Tie Rods ends/Idler Arm,
To see the ROC, Check out the webpage Here
I have a problem progamming my 29c256's when i FIRST turn the fileprom on, it will say that it programs, even does a checksum, but when i do a blank check of the chip it is still written. The way i get around this is to change the chip id to a 27c256, then i write the chip. Then i switch the chip type back to the at29c256. Then i proceed to with the chip with an FF.bin(the bin writes all sectors as ff(or blank), thanks glenn!). After i do the FF write i then write my intended chip. It works fine everytime.
I only have to do the 27c256 write wheneve i INITIALLY open the fileprom, if i write a chip and then leave it runnning and come back it will erase and rewrite the flash proms fine everytime. You may want to try it.
Let me know whats happening.
Brendan
------------------
1987 IROC-Z L98,SuperRam,EB 6085's,LPE 219/219 Roller, Crane 1.6RR, EB TPI Base, 58mm TB, ADS 24#, AFPR, K&N, EB TES, Catco Cat, 3" Borla Cat-Back, Accel cap,rotor,distro/other crap, MSD 6AL, MSD Blaster 3, Aluminum DS, 94 Disk Rear, Adjustable Valve, Precision 3.73 Gears, Sub-Frame Connectors, Hotchkis Lower Control Arms, KYB Shocks/Struts, Suspension Techniques Lowering Springs, Polyurethan Bushings all over the place, Moog Upper/Lower Ball joints and Tie Rods ends/Idler Arm,
To see the ROC, Check out the webpage Here
It doesn't work at all. I called Intronics and they told me to send back the programmer with a chip so they can see whats going on. If I try to write as a 27C256 it says it programs but it still is blank. If I program as a 29C256, I get a programming error when it tries to program the first block of 64 bytes. I was so excited to get these new chips. What is let dowm.
Anymore ideas before I ship this programmer off? It programs a 27C128 just fine.
Jason
------------------
89 Six Speed FX3 coupe
More Performance 396cid specs:
Callies 4340 crank 3.875 stroke
Lunati Pro-Mod 5.85" rods
SRP Pistons 14cc dish
Comp Cams Custom cam 550 lift 220/229 duration
10.8:1 compression
AFR 195 competition ported heads
Miniram and TPIS 1 3/4" headers
Anymore ideas before I ship this programmer off? It programs a 27C128 just fine.
Jason
------------------
89 Six Speed FX3 coupe
More Performance 396cid specs:
Callies 4340 crank 3.875 stroke
Lunati Pro-Mod 5.85" rods
SRP Pistons 14cc dish
Comp Cams Custom cam 550 lift 220/229 duration
10.8:1 compression
AFR 195 competition ported heads
Miniram and TPIS 1 3/4" headers
hmm, your using the fileprom.exe while in dos , correct?
The prom type is a flash prom, and is selected as a at29c256 chip correct? programming at 5v's? and have you tried to just program on the entire chip? Not just 4000 to 7FFF?
The prom type is a flash prom, and is selected as a at29c256 chip correct? programming at 5v's? and have you tried to just program on the entire chip? Not just 4000 to 7FFF?
Trending Topics
Yes to all those questions. Even got the new version of 3.6 from intronics.
Jason
------------------
89 Six Speed FX3 coupe
More Performance 396cid specs:
Callies 4340 crank 3.875 stroke
Lunati Pro-Mod 5.85" rods
SRP Pistons 14cc dish
Comp Cams Custom cam 550 lift 220/229 duration
10.8:1 compression
AFR 195 competition ported heads
Miniram and TPIS 1 3/4" headers
Jason
------------------
89 Six Speed FX3 coupe
More Performance 396cid specs:
Callies 4340 crank 3.875 stroke
Lunati Pro-Mod 5.85" rods
SRP Pistons 14cc dish
Comp Cams Custom cam 550 lift 220/229 duration
10.8:1 compression
AFR 195 competition ported heads
Miniram and TPIS 1 3/4" headers
do you have any extra flash chips? maybe try a different one? You said that it does program if specified as a 27c256? Thats good, but it should work on the flash setting. Try programming two or 3 different times on a 27c256 and then go back to the at29c256?
I have a dozen of the chips. None work. If I program to a 27C256 it goes through the motions and says its programmed. If I then do a blank check, it says its erased which leads me to beleive its not really programmed.
Jason
Jason
Either your programming is broken or ALL of your chips are junk. Its really hard to say. If you were closer i'd drop by and see if my chips worked.. Don't know man, have you tried to program them on another computer if you have one available? I'm just tossing up ANY ideas.
well the only way i could think that 12 chips could be bad would be that they got damaged in shipping? It almost has to be a software issue or something with the programmer that is bad... but i am just guessing at this point.
This is a pocket programmer is it not? the reason to ask is that i seem to recall someon else saying that they were having probelms with their 27C256's. my understanding is that there is a windows program & a dos program & that the dos program was more reliable. I think that this same person also said that to make the windows program work they had to close ALL windows programs (like battery monitor & all that, garbage) & then the likelyhood of the programming went up. this is from memory, maybe there is something in the archives about this similar thing.
BW
BW
TGO Supporter
Joined: Jul 1999
Posts: 10,907
Likes: 5
From: The Bone Yard
Car: Death Mobile
Engine: 666 c.i.
The problem is you are trying to program a 16K bin onto a 32K bin. You need to "concatenate" a 16K hex 00 bin on the first x'0-3FFF and the 16K Bin on the remainder x'4000-7FFF.
I do find with FILEPROM that it also prefers to have a 32K x'FFs written first to make it think it is blank.
To create a 16K hex 00 file, use EPROM to read a 27C128 eprom and fill the buffer with 00. Then save that file as 00.BIN and make sure it is only 16K large.
Then use the MS-DOS command COPY/B 00.BIN+YOUR16K.BIN = NEW32K.BIN
Then use FILEPROM to write FF32K.BIN on your eprom (if you don't have a FF32K.BIN, you can create one with EPROM using the 27C256 as your eprom, fill the buffer with FF and then save the buffer as FF32K.BIN).
Use FILEPROM to check if it is Blank (use option 1). The Hex FFs should make it think its blank. Then program your NEW32K.BIN onto the eprom and use the verify option.
If everything is working right and you are selecting the right eprom option, etc, you can most definitely program an AT29C256 with a 16K MAF BIN. The above is exactly how I did it today for a buddy that has a MAF car.
Remember, you are trying to make a 16K BIN work on a 32K eprom. Just offsetting won't work. And it appears that MAF cars prefer Hex 00s in the lower 16K part of the 32K 29C256 Flash Prom. Just trying to offset it like you are doing will not set the lower 16K memory the proper way.
[This message has been edited by Glenn91L98GTA (edited May 18, 2001).]
I do find with FILEPROM that it also prefers to have a 32K x'FFs written first to make it think it is blank.
To create a 16K hex 00 file, use EPROM to read a 27C128 eprom and fill the buffer with 00. Then save that file as 00.BIN and make sure it is only 16K large.
Then use the MS-DOS command COPY/B 00.BIN+YOUR16K.BIN = NEW32K.BIN
Then use FILEPROM to write FF32K.BIN on your eprom (if you don't have a FF32K.BIN, you can create one with EPROM using the 27C256 as your eprom, fill the buffer with FF and then save the buffer as FF32K.BIN).
Use FILEPROM to check if it is Blank (use option 1). The Hex FFs should make it think its blank. Then program your NEW32K.BIN onto the eprom and use the verify option.
If everything is working right and you are selecting the right eprom option, etc, you can most definitely program an AT29C256 with a 16K MAF BIN. The above is exactly how I did it today for a buddy that has a MAF car.
Remember, you are trying to make a 16K BIN work on a 32K eprom. Just offsetting won't work. And it appears that MAF cars prefer Hex 00s in the lower 16K part of the 32K 29C256 Flash Prom. Just trying to offset it like you are doing will not set the lower 16K memory the proper way.
[This message has been edited by Glenn91L98GTA (edited May 18, 2001).]
TGO Supporter
Joined: Jul 1999
Posts: 10,907
Likes: 5
From: The Bone Yard
Car: Death Mobile
Engine: 666 c.i.
BTW, you CANNOT program an AT29C256 with 27C256. You must use FILEPROM with the Flash Prom option and Option 8 of the Flash Prom menu (AT29C256).
The PP will READ an AT29C256 like a 27C256, but it cannot program it EXCEPT as an AT29C256.
The PP will READ an AT29C256 like a 27C256, but it cannot program it EXCEPT as an AT29C256.
Thanks for all the info. I'll try it. I can still program a 27C128 prom fine. I have a few 32k bin files for 90 Vettes and they won't program either in the 29C256 proms. I'm using the updated dos version of Fileprom without windows running at all. I even turned off all power saving functions as Intronics said and it still does not work. As soon as it tries to program the first 64 bites, it errors out.
I find it hard to beleive that the PP is bad if if is still works on 27C128's just fine.
Jason
------------------
89 Six Speed FX3 coupe
More Performance 396cid specs:
Callies 4340 crank 3.875 stroke
Lunati Pro-Mod 5.85" rods
SRP Pistons 14cc dish
Comp Cams Custom cam 550 lift 220/229 duration
10.8:1 compression
AFR 195 competition ported heads
Miniram and TPIS 1 3/4" headers
I find it hard to beleive that the PP is bad if if is still works on 27C128's just fine.
Jason
------------------
89 Six Speed FX3 coupe
More Performance 396cid specs:
Callies 4340 crank 3.875 stroke
Lunati Pro-Mod 5.85" rods
SRP Pistons 14cc dish
Comp Cams Custom cam 550 lift 220/229 duration
10.8:1 compression
AFR 195 competition ported heads
Miniram and TPIS 1 3/4" headers
I tried to do what you said but couldn't figure out how to fill the buffer with 0's. That funtion did not appear in Eprom. Just fill buffer with FF's. If I stick the 29C256 from in the programmer and try and program a 32K bin file from say a 90 Vette, it still does not work. I get a programming error. Carl at Intronics wants the unit back to see what's going on. This is disappointing for sure. I don't think I'm going to be tuning much more till I get the speed densiy hooked up.
Jason
Jason
Glenn,
can i not just take the file name (prom) & copy it with a different name (prom1) & then add the two together?
copy/b prom.bin + prom1.bin = prom2.bin
just wondering, I dont have a PP & the resident guru (well kinda), said that this would be an easier way to do it with the software that we have.
thanks
BW
------------------
Bobalos
aka Bob W.
www.r71camaro.homestead.com
r71chevy@earthlink.net
<><
can i not just take the file name (prom) & copy it with a different name (prom1) & then add the two together?
copy/b prom.bin + prom1.bin = prom2.bin
just wondering, I dont have a PP & the resident guru (well kinda), said that this would be an easier way to do it with the software that we have.
thanks
BW
------------------
Bobalos
aka Bob W.
www.r71camaro.homestead.com
r71chevy@earthlink.net
<><
TGO Supporter
Joined: Jul 1999
Posts: 10,907
Likes: 5
From: The Bone Yard
Car: Death Mobile
Engine: 666 c.i.
Bobalos, that is exactly what I do, except the first 16K bin is a "null" bin filled with Hex 00s. I actually use the command:
copy/b 00-16K.bin + my16K.bin = new32k.bin
I earlier suggested just copying "my16K.bin" twice to make a new32k.bin, but someone that was able to test it before I tried it said it didn't work, but the null 16K bin loaded first did.
When I finally had an opportunity to test this on a buddy's 89 MAF car, I only tested the null16K + my16K.bin, as we had only a limited amount of time. If I had more time, I would have tried "doubling up" the actual 16K bin into a 32K bin to see if it was just something that the other individual had done wrong, or if doubling up didn't actually work. Logically, doubling up should work IMO.
copy/b 00-16K.bin + my16K.bin = new32k.bin
I earlier suggested just copying "my16K.bin" twice to make a new32k.bin, but someone that was able to test it before I tried it said it didn't work, but the null 16K bin loaded first did.
When I finally had an opportunity to test this on a buddy's 89 MAF car, I only tested the null16K + my16K.bin, as we had only a limited amount of time. If I had more time, I would have tried "doubling up" the actual 16K bin into a 32K bin to see if it was just something that the other individual had done wrong, or if doubling up didn't actually work. Logically, doubling up should work IMO.
OK, I am going to give it a try here in a minute. the problem that i am having (& mind my ignorance is doing the copy command @ the DOS prompt. can i goto the dos promt through windows, or am I going to have to boot to DOS?
I have been using:
copy/b SyTy1.bin + SyTy2.bin = SyTy1comb.bin
do i have a space where it ought not be or the other way around? I hate DOS, I was born on Windows & am totally lazy that way now.
thanks amigo
BW
------------------
Bobalos
aka Bob W.
www.r71camaro.homestead.com
r71chevy@earthlink.net
<><
I have been using:
copy/b SyTy1.bin + SyTy2.bin = SyTy1comb.bin
do i have a space where it ought not be or the other way around? I hate DOS, I was born on Windows & am totally lazy that way now.
thanks amigo
BW
------------------
Bobalos
aka Bob W.
www.r71camaro.homestead.com
r71chevy@earthlink.net
<><
one more thing. can i use windows explore to create the Bin2 from the bin1? i did a copy, paste, rename of "copy of bin1.bin" to create the second one. I know a bit ugly but, i am an idiot when it comes to this stuffs.
thanks
BW
------------------
Bobalos
aka Bob W.
www.r71camaro.homestead.com
r71chevy@earthlink.net
<><
thanks
BW
------------------
Bobalos
aka Bob W.
www.r71camaro.homestead.com
r71chevy@earthlink.net
<><
TGO Supporter
Joined: Jul 1999
Posts: 10,907
Likes: 5
From: The Bone Yard
Car: Death Mobile
Engine: 666 c.i.
I am usually already in Dos when I am doing it, but you should be able to run it from a Dos prompt while remaining in Windows.
When I execute it I do it without any spaces, but a space SHOULD not be a problem.
I do it like:
COPY/B FILE1.BIN+FILE2.BIN=NEWFILE.BIN
Don't be afraid to play with it. I use to work a lot in DOS, but I haven't had a need until I got into PROM burning.
Wait till you try Assembly Language Programming...I am amazed how much I forgot about DOS.
When I execute it I do it without any spaces, but a space SHOULD not be a problem.
I do it like:
COPY/B FILE1.BIN+FILE2.BIN=NEWFILE.BIN
Don't be afraid to play with it. I use to work a lot in DOS, but I haven't had a need until I got into PROM burning.
Wait till you try Assembly Language Programming...I am amazed how much I forgot about DOS.
Member

Joined: Mar 2000
Posts: 409
Likes: 0
From: Land O Lakes, FL
Engine: 5.7
Transmission: 700R4
Axle/Gears: 3.27
Glen, I have been using the flash prom 29C256 for a while now and never had to do what you're saying. I just programmed the bin to the correct half of the chip and presto.
Anyways....
------------------
87 Iroc 5.7, AFR190, SLP Cam(218/224), SLP 1 5/8 headers & cat back, Random CAT, SLP Runners, 48mm TB, custom chip(by me), Vigilante & Probuilt trans.
Anyways....
------------------
87 Iroc 5.7, AFR190, SLP Cam(218/224), SLP 1 5/8 headers & cat back, Random CAT, SLP Runners, 48mm TB, custom chip(by me), Vigilante & Probuilt trans.
Thanks amigo. I just got on line here @ home. I am going to give it a wack & see what happens. I tried it a few times earlier & could not make it work. dont know what i am doing wrong. No sweat, I will finger it out eventually.
It looks like the DIY list is back up & hopefully that is a good sign that the server will be back up soon. so that i can get the Sy/Ty bin that i am looking for.
BW
------------------
Bobalos
aka Bob W.
www.r71camaro.homestead.com
r71chevy@earthlink.net
<><
It looks like the DIY list is back up & hopefully that is a good sign that the server will be back up soon. so that i can get the Sy/Ty bin that i am looking for.
BW
------------------
Bobalos
aka Bob W.
www.r71camaro.homestead.com
r71chevy@earthlink.net
<><
TGO Supporter
Joined: Jul 1999
Posts: 10,907
Likes: 5
From: The Bone Yard
Car: Death Mobile
Engine: 666 c.i.
87, are you using FILEPROM or the Windows version? I am using FILEPROM which appears to have issues with the version that came with my PP. For example, it appears users of certain versions of FILEPROM must pre-program the 29C256 with Hex FFs prior to storing your BIN on it, for the ECM to like it. The feedback I hear is the Windows version doesn't have this problem. I cannot say if some of these "nuances" have been fixed in the latest version of FILEPROM.
Personally, I think it's a bit of a burn that I have to pay for the latest version of FILEPROM, that has a release date earlier than when I got my PP.
But, the method I use definitely works with the older version of FILEPROM.
Personally, I think it's a bit of a burn that I have to pay for the latest version of FILEPROM, that has a release date earlier than when I got my PP.
But, the method I use definitely works with the older version of FILEPROM.
I am @ work & we have a hilo systems programmer (just an fyi). I just programmed into the 29C256 both the 8D (256K) & 58 (128K) .bin. when i did the 128K prom i set the start of the prom @ 4000 & it did not seem to mind a bit. I will find out tomorrow if the car is happy with it. it appeared much to easy to work. I told it that i wanted the prom to start @ 4000 & it did it. It filled the first 128K with FF & put the .bin into the second 128K.
unfortunatly the burner is @ work & the car is @ home. makes it kind of hard. Hopefully this will be as difficult as it gets, but not likely
.
BW
------------------
Bobalos
aka Bob W.
www.r71camaro.homestead.com
r71chevy@earthlink.net
<><
unfortunatly the burner is @ work & the car is @ home. makes it kind of hard. Hopefully this will be as difficult as it gets, but not likely
.BW
------------------
Bobalos
aka Bob W.
www.r71camaro.homestead.com
r71chevy@earthlink.net
<><
Member

Joined: Mar 2000
Posts: 409
Likes: 0
From: Land O Lakes, FL
Engine: 5.7
Transmission: 700R4
Axle/Gears: 3.27
Glen, I have used both with no problem. The dos version seems to be more reliable. Sometimes it will not program all the way in windows due to background programs running (make sure everything is closed). I'm running version 1.10. I called the intronics guys and explained to them some of the initial problems I was experiencing with my programmer and flash chip. They gave me the updated copy for free. No problems since.
------------------
87 Iroc 5.7, AFR190, SLP Cam(218/224), SLP 1 5/8 headers & cat back, Random CAT, SLP Runners, 48mm TB, custom chip(by me), Vigilante & Probuilt trans.
------------------
87 Iroc 5.7, AFR190, SLP Cam(218/224), SLP 1 5/8 headers & cat back, Random CAT, SLP Runners, 48mm TB, custom chip(by me), Vigilante & Probuilt trans.
TGO Supporter
Joined: Jul 1999
Posts: 10,907
Likes: 5
From: The Bone Yard
Car: Death Mobile
Engine: 666 c.i.
87, it appears that different people are experiencing quite few problems when using FILEPROM or even the Windows Version with the AT29C256.
Some cannot get neither to work, some only work with FILEPROM, some only with the Windows Version.
Some people have "zipped" up there programs and sent them to me to see if they would work on my machines. And can say that they behave differently on the two machines I have at home. The Windows version would work on one of my computers the , yet will not work on my other computer.
Conversely, FILEPROM will crash one of my systems if I do not just shutdown and reboot, while the other computer (which the Windows Version won't run) runs fine.
And then there are people that can use EPROM and FILEPROM to program 27C128s/256s; but they cannnot get the AT29C256 to program.
There is a definite inconsistency here that goes beyond the typical "your system must not be set up right". I have chatted with a number of guys via e-mail where for whatever reason they have not been able to get the 29C256 to work - some later did get it to work, others are getting a new PP.
My feeling is, IF you can get your PP to work with the AT29C256 and you have no problems or have to do anything "funny", consider yourself lucky. All I know is that the version of FILEPROM that I have (Version 3.55), it MUST pre-initialize my AT29C256 to with Hex FFs for my 7730 ecm to accept it. Without the Hex FFs, my 7730 ecm just does not like it and it rewards me with an SES light and I cannot even grab data off the ALDL.
And YES, my systems are all set up fine (for their particular vintage). The one which FILEPROM works best on, but cannot use the Windows Verison is a Windows 95 machine, and the one which runs the Windows Version fine but will crash my system when I exit the DOS version is a Windows 98SE machine. Both with the latest updates.
The Windows 95 machine is the one I prefer to use my eprom burning stuff as that is all it does (along with running Diacom). FILEPROM V 3.55 works fine (except having to initalize with Hex FFs for my 7730 ecm), so I consider myself lucky compared to some of the problems others are experiencing.
The problem is beyond a simple "setting" problem. It is within the software itself IMO, given the large number of people encounter similar (or worst) problems.
Some cannot get neither to work, some only work with FILEPROM, some only with the Windows Version.
Some people have "zipped" up there programs and sent them to me to see if they would work on my machines. And can say that they behave differently on the two machines I have at home. The Windows version would work on one of my computers the , yet will not work on my other computer.
Conversely, FILEPROM will crash one of my systems if I do not just shutdown and reboot, while the other computer (which the Windows Version won't run) runs fine.
And then there are people that can use EPROM and FILEPROM to program 27C128s/256s; but they cannnot get the AT29C256 to program.
There is a definite inconsistency here that goes beyond the typical "your system must not be set up right". I have chatted with a number of guys via e-mail where for whatever reason they have not been able to get the 29C256 to work - some later did get it to work, others are getting a new PP.
My feeling is, IF you can get your PP to work with the AT29C256 and you have no problems or have to do anything "funny", consider yourself lucky. All I know is that the version of FILEPROM that I have (Version 3.55), it MUST pre-initialize my AT29C256 to with Hex FFs for my 7730 ecm to accept it. Without the Hex FFs, my 7730 ecm just does not like it and it rewards me with an SES light and I cannot even grab data off the ALDL.
And YES, my systems are all set up fine (for their particular vintage). The one which FILEPROM works best on, but cannot use the Windows Verison is a Windows 95 machine, and the one which runs the Windows Version fine but will crash my system when I exit the DOS version is a Windows 98SE machine. Both with the latest updates.
The Windows 95 machine is the one I prefer to use my eprom burning stuff as that is all it does (along with running Diacom). FILEPROM V 3.55 works fine (except having to initalize with Hex FFs for my 7730 ecm), so I consider myself lucky compared to some of the problems others are experiencing.
The problem is beyond a simple "setting" problem. It is within the software itself IMO, given the large number of people encounter similar (or worst) problems.
Senior Member
Joined: Jul 1999
Posts: 888
Likes: 0
From: Houston, TX
Car: '87+'02 Z28
Engine: 454 LSX
Transmission: T-56, Viper output shaft
Axle/Gears: Strage 12-bolt 3.73:1
Where do most of you buy your chips from? If you could please let me know. I need P/N's for the 27C128 and I might try the 29C256 proms.
Thanks.
Oh, 87iroc350, where in Katy are you? A friend of mine owns a performance shop out there and I am out there quite often.
------------------
1987 383 cu.in. IROC-Z: TPIS MiniRamIII / GM FastBurn heads/ 10.6:1 compression
Comp cams custom grind: Dur'n 224/236 Lift .536/.555
Strange 12Bolt Diff./ Neil's Home-Built BulletProof 700R4+Vigilante 2800 stall converter
MSD Billet Distributor, Dig 6+, & Blaster coil
Hooker Supercomp Long tube headers
Thanks.
Oh, 87iroc350, where in Katy are you? A friend of mine owns a performance shop out there and I am out there quite often.
------------------
1987 383 cu.in. IROC-Z: TPIS MiniRamIII / GM FastBurn heads/ 10.6:1 compression
Comp cams custom grind: Dur'n 224/236 Lift .536/.555
Strange 12Bolt Diff./ Neil's Home-Built BulletProof 700R4+Vigilante 2800 stall converter
MSD Billet Distributor, Dig 6+, & Blaster coil
Hooker Supercomp Long tube headers
I got me new programmer today. I will try to program the 29C256 tonight. Transtronics sees no reason why it should not work under DOS or Windows version. Apparently some of the old programmers had some trouble and some of the earlier windows software. Wish me luck!
------------------
89 Six Speed FX3 coupe
More Performance 396cid specs:
Callies 4340 crank 3.875 stroke
Lunati Pro-Mod 5.85" rods
SRP Pistons 14cc dish
Comp Cams Custom cam 550 lift 220/229 duration
10.8:1 compression
AFR 195 competition ported heads
Miniram and TPIS 1 3/4" headers
Speed Density conversion in process
------------------
89 Six Speed FX3 coupe
More Performance 396cid specs:
Callies 4340 crank 3.875 stroke
Lunati Pro-Mod 5.85" rods
SRP Pistons 14cc dish
Comp Cams Custom cam 550 lift 220/229 duration
10.8:1 compression
AFR 195 competition ported heads
Miniram and TPIS 1 3/4" headers
Speed Density conversion in process
There is a bit of confusion about pre loading FFs in flash parts – What you really want to do is to have FF’s in the buffer before you load the file. – This is because flash parts will only erase 64byte blocks if they are being programmed – thus what is left in the chip / or buffer will get put in the chip and effect the check sum.
There is an FAQ on our site about running Toshiba laptops.
Some 'green' or power saving bios routines can interfere with programming 29Cxxx parts as the interupt the fast timing. Turn them off in both windows and you CMOS BIOS settings.
Many other programming issues are covered at http://xtronics.com/memory/faq.htm
There is an FAQ on our site about running Toshiba laptops.
Some 'green' or power saving bios routines can interfere with programming 29Cxxx parts as the interupt the fast timing. Turn them off in both windows and you CMOS BIOS settings.
Many other programming issues are covered at http://xtronics.com/memory/faq.htm
Thread
Thread Starter
Forum
Replies
Last Post





