29C256 on a '165 ECM?
Thread Starter
Member
Joined: Oct 1999
Posts: 358
Likes: 1
From: Southern Indiana
Car: 87 IROC-Z
Engine: 383 HSR $8D
Transmission: T56
Axle/Gears: 3.42
29C256 on a '165 ECM?
Someone suggested that you can use this chip on a '165 ECM no problem. IS this true? I have a couple I bought for a friends '730 ecm...and would love to use them on a 165 if I can.
Anyone else? I wouldn't buy anything from the guy...(I think it was that Edmond guy that commented on it)...but if he is right on the chip...I'll go for it.
Thanks,
Anyone else? I wouldn't buy anything from the guy...(I think it was that Edmond guy that commented on it)...but if he is right on the chip...I'll go for it.
Thanks,
Joined: Jan 2001
Posts: 285
Likes: 14
From: the sticks of NJ...
Car: 89 Firebird Formula
Engine: 389
Transmission: T56
Axle/Gears: Moser 4.11
Yeah, I use them all the time. You just have to start at 04000. I think that's the address - my burner and software are at home.
Thread Starter
Member
Joined: Oct 1999
Posts: 358
Likes: 1
From: Southern Indiana
Car: 87 IROC-Z
Engine: 383 HSR $8D
Transmission: T56
Axle/Gears: 3.42
04000? Is that a variable I can set in the old version of my Pocket Programmer software?
I'd appreciate it if you could let me know the exact address.
Also, could you run through a quick procedure or any changes you have to do when using these chips for a 165 ecm. Mainly just how to set it up to start burning at 04000?
I appreciate it.
I'd appreciate it if you could let me know the exact address.
Also, could you run through a quick procedure or any changes you have to do when using these chips for a 165 ecm. Mainly just how to set it up to start burning at 04000?
I appreciate it.
TGO Supporter
Joined: Jul 1999
Posts: 10,907
Likes: 5
From: The Bone Yard
Car: Death Mobile
Engine: 666 c.i.
If you have the newer Windows Version of the Pocket Programmer software, then you just have to set the starting address for the device to x'4000.
If you are using the older DOS version, then you just "double up" the bin or load "hex 00" in the bottom half...either way works.
to "double" you do the following command:
>COPY/B NEW.BIN=OLD.BIN+OLD.BIN
Where NEW.BIN is the name of the new BIN file you want to create and OLD.BIN is the name of the old 16K BIN you want to "doubel up".
If you are using the older DOS version, then you just "double up" the bin or load "hex 00" in the bottom half...either way works.
to "double" you do the following command:
>COPY/B NEW.BIN=OLD.BIN+OLD.BIN
Where NEW.BIN is the name of the new BIN file you want to create and OLD.BIN is the name of the old 16K BIN you want to "doubel up".
I'm using that chip on my 165. I fill the bottom half with 00's then start at 04000 with the bin file. I think some people double the bin file by burning it on the lower and upper half. I believe the lower half is 000000 to 03ffff and the upper half is 040000 to 07ffff for a 256 chip but don't quote me on that. Sorry but I'm not using a pocket programer so I can not tell you exactly how it does it, but this is what works for me and they work great. Hope this helps.
Thread Starter
Member
Joined: Oct 1999
Posts: 358
Likes: 1
From: Southern Indiana
Car: 87 IROC-Z
Engine: 383 HSR $8D
Transmission: T56
Axle/Gears: 3.42
Thanks for the info guys. Glenn, that dos command really helps...
I have the older dos version of the pocket prog stuff.
Last night I tried just burning from 004000 to 007fff and it failed. I am going to try combining 2 bins next.
Of course, I tried burning a 730 bin to the chip and it failed also...so I might be doing something else wrong. Or I toasted the chip when I screwed up with the 165 burn.
Was LS1thunder right with his lower half address? 000000 to 003fff? It sounds right.
Thanks,
Greg
I have the older dos version of the pocket prog stuff.
Last night I tried just burning from 004000 to 007fff and it failed. I am going to try combining 2 bins next.
Of course, I tried burning a 730 bin to the chip and it failed also...so I might be doing something else wrong. Or I toasted the chip when I screwed up with the 165 burn.
Was LS1thunder right with his lower half address? 000000 to 003fff? It sounds right.
Thanks,
Greg
Trending Topics
TGO Supporter
Joined: Jul 1999
Posts: 10,907
Likes: 5
From: The Bone Yard
Car: Death Mobile
Engine: 666 c.i.
When I used the DOS Version, I found that I had to "prep" the Flash Prom with Hex FFs. I just created a 32K File with filled with Hex FFs, which lets the Dos Version of the PP know the Flash Prom is erased. But this is ONLY with the DOS version that I had to do this.
With the Windows Version, I just "rewrite" directly on the Flash Prom with nothing "funny". You may want to look at purchasing the Windows Version. I did and I much prefer it over the Dos Version - I don't have to "flip" back and forth between DOS and Windows on my Computer. Much easier to use IMO.
With the Windows Version, I just "rewrite" directly on the Flash Prom with nothing "funny". You may want to look at purchasing the Windows Version. I did and I much prefer it over the Dos Version - I don't have to "flip" back and forth between DOS and Windows on my Computer. Much easier to use IMO.
Thread Starter
Member
Joined: Oct 1999
Posts: 358
Likes: 1
From: Southern Indiana
Car: 87 IROC-Z
Engine: 383 HSR $8D
Transmission: T56
Axle/Gears: 3.42
Thanks for the info guys. I will try all this out as soon as I get the car back on the road.
I will upgrade to the win version of the pocket programmer software soon...maybe that will solve some of my issues.
I will upgrade to the win version of the pocket programmer software soon...maybe that will solve some of my issues.
Thread
Thread Starter
Forum
Replies
Last Post
efiguy
Engine/Drivetrain/Suspension Parts for Sale
0
Sep 27, 2015 01:30 PM





