arap problem burn
06-20-2001, 07:37 PM
#1
Senior Member
Thread Starter
Join Date: May 2001
Location: springfield,IL
Posts: 745
Likes: 0
Received 0 Likes
on
0 Posts
Car: T/A / Grand Am
Engine: 383 SBC
Transmission: glide
Axle/Gears: 9" ford 5.67
arap problem burn
Hi Guys. I burned a 27c256 with a modified arap bin. fed the first half and started with 04000 for the file. Seemed to program ok. Then I checked it with winbin. All flags are now checked and most of the numbers were changed to 255. Anybody else have this screwy thing happen? I also programed the chip lower half program upper half ffff and it checked out just like I modified it. Going to use this in 165 ecm in the car below. THANKS.
------------------
87 GTA 355/700r4
ported&polished 083 heads
xe268h comp cam
1 5/8 blackjack alumicote
homebuilt y pipe,pasesetter 3in mandrel cat back.
ported/manifold,upper plentum, tpis maf.
airfoil, 24# svo injectors, hypertech stage 3 chip, underdrive pulleys, erson roller rockers, chromemolley pushrods,2100 stall, shiftkit, 373 10 bolt.
------------------
87 GTA 355/700r4
ported&polished 083 heads
xe268h comp cam
1 5/8 blackjack alumicote
homebuilt y pipe,pasesetter 3in mandrel cat back.
ported/manifold,upper plentum, tpis maf.
airfoil, 24# svo injectors, hypertech stage 3 chip, underdrive pulleys, erson roller rockers, chromemolley pushrods,2100 stall, shiftkit, 373 10 bolt.
06-21-2001, 06:24 AM
#2
Member
Join Date: Oct 1999
Location: Southern Indiana
Posts: 358
Likes: 0
Received 0 Likes
on
0 Posts
Car: 87 IROC-Z
Engine: 383 HSR $8D
Transmission: T56
Axle/Gears: 3.42
Isn't this the wrong chip for the 165 ecm? I use 27C128 or some derivitive of this...is there some 'trick' that you are trying to do?
------------------
GregF
87 IROC
------------------
GregF
87 IROC
06-21-2001, 05:00 PM
#3
Senior Member
Thread Starter
Join Date: May 2001
Location: springfield,IL
Posts: 745
Likes: 0
Received 0 Likes
on
0 Posts
Car: T/A / Grand Am
Engine: 383 SBC
Transmission: glide
Axle/Gears: 9" ford 5.67
<font face="Verdana, Arial" size="2">Originally posted by gsf-87IROC:
Isn't this the wrong chip for the 165 ecm? I use 27C128 or some derivitive of this...is there some 'trick' that you are trying to do?
</font>
Isn't this the wrong chip for the 165 ecm? I use 27C128 or some derivitive of this...is there some 'trick' that you are trying to do?
</font>
------------------
87 GTA 355/700r4
ported&polished 083 heads
xe268h comp cam
1 5/8 blackjack alumicote
homebuilt y pipe,pasesetter 3in mandrel cat back.
ported/manifold,upper plentum, tpis maf.
airfoil, 24# svo injectors, hypertech stage 3 chip, underdrive pulleys, erson roller rockers, chromemolley pushrods,2100 stall, shiftkit, 373 10 bolt.
06-21-2001, 11:11 PM
#4
Senior Member
Thread Starter
Join Date: May 2001
Location: springfield,IL
Posts: 745
Likes: 0
Received 0 Likes
on
0 Posts
Car: T/A / Grand Am
Engine: 383 SBC
Transmission: glide
Axle/Gears: 9" ford 5.67
<font face="Verdana, Arial" size="2">Originally posted by cp87GTA:
Hi Guys. I burned a 27c256 with a modified arap bin. fed the first half and started with 04000 for the file. Seemed to program ok. Then I checked it with winbin. All flags are now checked and most of the numbers were changed to 255. Anybody else have this screwy thing happen? I also programed the chip lower half program upper half ffff and it checked out just like I modified it. Going to use this in 165 ecm in the car below. THANKS.
</font>
Hi Guys. I burned a 27c256 with a modified arap bin. fed the first half and started with 04000 for the file. Seemed to program ok. Then I checked it with winbin. All flags are now checked and most of the numbers were changed to 255. Anybody else have this screwy thing happen? I also programed the chip lower half program upper half ffff and it checked out just like I modified it. Going to use this in 165 ecm in the car below. THANKS.
</font>
OK I found out that when writing to the 04000 to 07FFF doesn't seem to work on a 27C256 chip. So how do you write it so it will? I was planning on useing the 29C256 chip, and just playing with these till I can get the 29s. Thanks.
------------------
87 GTA 355/700r4
ported&polished 083 heads
xe268h comp cam
1 5/8 blackjack alumicote
homebuilt y pipe,pasesetter 3in mandrel cat back.
ported/manifold,upper plentum, tpis maf.
airfoil, 24# svo injectors, hypertech stage 3 chip, underdrive pulleys, erson roller rockers, chromemolley pushrods,2100 stall, shiftkit, 373 10 bolt.
[This message has been edited by cp87GTA (edited June 21, 2001).]
06-21-2001, 11:29 PM
#5
Supreme Member
Join Date: Jun 2000
Location: In reality
Posts: 7,554
Likes: 0
Received 1 Like
on
1 Post
Car: An Ol Buick
Engine: Vsick
Transmission: Janis Tranny Yank Converter
<font face="Verdana, Arial" size="2">Originally posted by cp87GTA:
Hi Guys. I burned a 27c256 with a modified arap bin. fed the first half and started with 04000 for the file. Seemed to program ok. Then I checked it with winbin. All flags are now checked and most of the numbers were changed to 255. Anybody else have this screwy thing happen? I also programed the chip lower half program upper half ffff and it checked out just like I modified it. Going to use this in 165 ecm in the car below. THANKS.
</font>
Hi Guys. I burned a 27c256 with a modified arap bin. fed the first half and started with 04000 for the file. Seemed to program ok. Then I checked it with winbin. All flags are now checked and most of the numbers were changed to 255. Anybody else have this screwy thing happen? I also programed the chip lower half program upper half ffff and it checked out just like I modified it. Going to use this in 165 ecm in the car below. THANKS.
</font>
06-22-2001, 07:13 AM
#6
Supreme Member
Join Date: Jul 1999
Location: Baton Rouge, LA, USA
Posts: 1,577
Likes: 0
Received 0 Likes
on
0 Posts
Car: 87 T/A
Engine: 441 SBC 12.5:1 0.680" Lift
Transmission: T-56
Axle/Gears: 4.10 TruTrac Moser 9"
I had good luck by taking the edited file saved from WinBin, loading it into a hex editor, and then pasting a copy of it onto the end of itself, so that it was like two 128 images appended together. Then saved it from the hex editor and burned the resulting image to the 256 chip using 256 settings in the PocketProgrammer s-ware. The resulting 27C256 chip worked fine in my 165 MAF car, no problems.
If you want to cross-check, you probably want to read the image from the chip, save it as a file, go back in with the hex editor, cut it back in half, save it as two files, compare those two files, and then load one of them with WinBin to cross-check. However, a 'verify' on the PP program ought to get you there as well.
If you want to cross-check, you probably want to read the image from the chip, save it as a file, go back in with the hex editor, cut it back in half, save it as two files, compare those two files, and then load one of them with WinBin to cross-check. However, a 'verify' on the PP program ought to get you there as well.
06-22-2001, 11:12 PM
#7
Senior Member
Thread Starter
Join Date: May 2001
Location: springfield,IL
Posts: 745
Likes: 0
Received 0 Likes
on
0 Posts
Car: T/A / Grand Am
Engine: 383 SBC
Transmission: glide
Axle/Gears: 9" ford 5.67
<font face="Verdana, Arial" size="2">Originally posted by Craig Moates:
I had good luck by taking the edited file saved from WinBin, loading it into a hex editor, and then pasting a copy of it onto the end of itself, so that it was like two 128 images appended together. Then saved it from the hex editor and burned the resulting image to the 256 chip using 256 settings in the PocketProgrammer s-ware. The resulting 27C256 chip worked fine in my 165 MAF car, no problems.
If you want to cross-check, you probably want to read the image from the chip, save it as a file, go back in with the hex editor, cut it back in half, save it as two files, compare those two files, and then load one of them with WinBin to cross-check. However, a 'verify' on the PP program ought to get you there as well.</font>
I had good luck by taking the edited file saved from WinBin, loading it into a hex editor, and then pasting a copy of it onto the end of itself, so that it was like two 128 images appended together. Then saved it from the hex editor and burned the resulting image to the 256 chip using 256 settings in the PocketProgrammer s-ware. The resulting 27C256 chip worked fine in my 165 MAF car, no problems.
If you want to cross-check, you probably want to read the image from the chip, save it as a file, go back in with the hex editor, cut it back in half, save it as two files, compare those two files, and then load one of them with WinBin to cross-check. However, a 'verify' on the PP program ought to get you there as well.</font>
[This message has been edited by cp87GTA (edited June 22, 2001).]
Trending Topics
06-22-2001, 11:26 PM
#8
Member
Join Date: Apr 2000
Location: Wilmington, IL Age: 35
Posts: 223
Likes: 0
Received 0 Likes
on
0 Posts
Charles,
Did you try the bin that i sent you on your 256 EPROMS yet?...I't should work with no problems....I'm at work right now, so maybe you already emailed me about the further problems you've been having.
As said earlier, you need to concatenate a 00 bin and your ARAP bin to get things to work out correctly with a 256. Many guys on here do it that way, and have no problems.
Let me know.
[This message has been edited by Steves ZZ5 (edited June 22, 2001).]
Did you try the bin that i sent you on your 256 EPROMS yet?...I't should work with no problems....I'm at work right now, so maybe you already emailed me about the further problems you've been having.
As said earlier, you need to concatenate a 00 bin and your ARAP bin to get things to work out correctly with a 256. Many guys on here do it that way, and have no problems.
Let me know.
[This message has been edited by Steves ZZ5 (edited June 22, 2001).]
06-22-2001, 11:30 PM
#9
Member
Join Date: Apr 2000
Location: Wilmington, IL Age: 35
Posts: 223
Likes: 0
Received 0 Likes
on
0 Posts
Okay, here's how I did it....This is directly from Glenn from a previous post, and it'll work for you. The BIN i sent you is done in this way.
<font face="Verdana, Arial" size="2">
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.</font>
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.</font>
06-22-2001, 11:44 PM
#10
Senior Member
Thread Starter
Join Date: May 2001
Location: springfield,IL
Posts: 745
Likes: 0
Received 0 Likes
on
0 Posts
Car: T/A / Grand Am
Engine: 383 SBC
Transmission: glide
Axle/Gears: 9" ford 5.67
<font face="Verdana, Arial" size="2">Originally posted by Steves ZZ5:
Okay, here's how I did it....This is directly from Glenn from a previous post, and it'll work for you. The BIN i sent you is done in this way.
Okay, here's how I did it....This is directly from Glenn from a previous post, and it'll work for you. The BIN i sent you is done in this way.
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.</font>
"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.</font>
07-08-2001, 10:17 PM
#12
Senior Member
Thread Starter
Join Date: May 2001
Location: springfield,IL
Posts: 745
Likes: 0
Received 0 Likes
on
0 Posts
Car: T/A / Grand Am
Engine: 383 SBC
Transmission: glide
Axle/Gears: 9" ford 5.67
<font face="Verdana, Arial" size="2">Originally posted by Steves ZZ5:
Charles,
Did you try the bin that i sent you on your 256 EPROMS yet?...I't should work with no problems....I'm at work right now, so maybe you already emailed me about the further problems you've been having.
As said earlier, you need to concatenate a 00 bin and your ARAP bin to get things to work out correctly with a 256. Many guys on here do it that way, and have no problems.
Let me know.
[This message has been edited by Steves ZZ5 (edited June 22, 2001).]</font>
Charles,
Did you try the bin that i sent you on your 256 EPROMS yet?...I't should work with no problems....I'm at work right now, so maybe you already emailed me about the further problems you've been having.
As said earlier, you need to concatenate a 00 bin and your ARAP bin to get things to work out correctly with a 256. Many guys on here do it that way, and have no problems.
Let me know.
[This message has been edited by Steves ZZ5 (edited June 22, 2001).]</font>
------------------
87 GTA 355/700r4
ported&polished 083 heads
xe268h comp cam
1 5/8 blackjack alumicote
homebuilt y pipe,pasesetter 3in mandrel cat back.
ported/manifold,upper plentum, tpis maf.
airfoil, 24# svo injectors, hypertech stage 3 chip, underdrive pulleys, erson roller rockers, chromemolley pushrods,2100 stall, shiftkit, 373 10 bolt.
07-08-2001, 10:50 PM
#13
TGO Supporter
Join Date: Jul 1999
Location: The Bone Yard
Posts: 10,907
Likes: 0
Received 3 Likes
on
3 Posts
Car: Death Mobile
Engine: 666 c.i.
I remember that "quote" 
I should add that further testing has revealed that "offsetting" x'4000 works quite well if you are using the Windows Version from Pocket Programmer. Also, some guys have successfully gotten "doubling" up of the 16K bins to a single 32K bin has worked, which logically should work all the time.
I find you have to "play" with things. There is usually a couple of different ways to do things. All SHOULD work, but at least one or two of the methods will for sure. I think a lot has to do with your setup.
I still cannot get the Windows Version for the Pocket Programmer to work on one of my notebooks (which happens to be my PROM burning notebook). But if you can get the Windows Version to work on your setup, it simplifies a lot of things.
I should add that further testing has revealed that "offsetting" x'4000 works quite well if you are using the Windows Version from Pocket Programmer. Also, some guys have successfully gotten "doubling" up of the 16K bins to a single 32K bin has worked, which logically should work all the time.
I find you have to "play" with things. There is usually a couple of different ways to do things. All SHOULD work, but at least one or two of the methods will for sure. I think a lot has to do with your setup.
I still cannot get the Windows Version for the Pocket Programmer to work on one of my notebooks (which happens to be my PROM burning notebook). But if you can get the Windows Version to work on your setup, it simplifies a lot of things.
07-08-2001, 11:32 PM
#14
Senior Member
Thread Starter
Join Date: May 2001
Location: springfield,IL
Posts: 745
Likes: 0
Received 0 Likes
on
0 Posts
Car: T/A / Grand Am
Engine: 383 SBC
Transmission: glide
Axle/Gears: 9" ford 5.67
<font face="Verdana, Arial" size="2">Originally posted by Glenn91L98GTA:
I remember that "quote"
I should add that further testing has revealed that "offsetting" x'4000 works quite well if you are using the Windows Version from Pocket Programmer. Also, some guys have successfully gotten "doubling" up of the 16K bins to a single 32K bin has worked, which logically should work all the time.
I find you have to "play" with things. There is usually a couple of different ways to do things. All SHOULD work, but at least one or two of the methods will for sure. I think a lot has to do with your setup.
I still cannot get the Windows Version for the Pocket Programmer to work on one of my notebooks (which happens to be my PROM burning notebook). But if you can get the Windows Version to work on your setup, it simplifies a lot of things. </font>
I remember that "quote"
I should add that further testing has revealed that "offsetting" x'4000 works quite well if you are using the Windows Version from Pocket Programmer. Also, some guys have successfully gotten "doubling" up of the 16K bins to a single 32K bin has worked, which logically should work all the time.
I find you have to "play" with things. There is usually a couple of different ways to do things. All SHOULD work, but at least one or two of the methods will for sure. I think a lot has to do with your setup.
I still cannot get the Windows Version for the Pocket Programmer to work on one of my notebooks (which happens to be my PROM burning notebook). But if you can get the Windows Version to work on your setup, it simplifies a lot of things. </font>
Thanks.
07-09-2001, 12:01 AM
#15
TGO Supporter
Join Date: Jul 1999
Location: The Bone Yard
Posts: 10,907
Likes: 0
Received 3 Likes
on
3 Posts
Car: Death Mobile
Engine: 666 c.i.
You are aware that you will often get some knock counts when you start the engine. As long as they are in "single digits" I wouldn't worry about the "start up". But it stop immediately after the engine is started. If it continues, then you need to play somemore.
Look at the "start up" spark advance vs coolant temp.
Those AT29C256s need to be played with a little. A few people have problems initially programming them, but usually get them working after "playing" with their system a bit. But it's great when you do get the AT29C256 to work.
Look at the "start up" spark advance vs coolant temp.
Those AT29C256s need to be played with a little. A few people have problems initially programming them, but usually get them working after "playing" with their system a bit. But it's great when you do get the AT29C256 to work.
Thread
Thread Starter
Forum
Replies
Last Post
GeneralIesrussi
Tech / General Engine
0
09-03-2015 03:23 AM