Previous post...thought it was gonna work.
http://forums.corvetteforum.com/show....php?t=1822486

All I got was when I put the key in, the fans went on and it wouldn't run.

Here's what I did.

Unhook battery!!

on AT29C256 chip

Buffer start=00000 (automatically chosen by PP2)
Device start=00000
Device end=07FFF

I opened PP2 program.
I inserted chip properly.
Hit program compare on AT chip (cuz erase isn't an option shown)
Says can be programmed.
I loaded buffer and selected .bin file from PCMFORLESS.
Hit Program device.
Device starts to program and then verifies ok.
Then removed chip.

On 27SF512 chip

Buffer start=00000 (automatically chosen by PP2)
Device start=00000
Device end=0FFFF

Inserted chip properly.
Erase device (only seems to be shown on this kind of chip)
Erases ok.
Program compare and device can be programmed.
Load buffer file and selected .bin file from PCMFORLESS.
Program device and verified.

On both chips, they are installed onto a moates adapter correctly (as verified by viewing images on moates.net website.)

Now, I hook battery back up and advance key and hear fans running (triggers something isn't correct) and it starts up, runs choppy and doesn't idle.

What is the problem? Is it the device start and end numbers incorrect? PP2 chose these values automatically, I did not alter them any way.

****EDIT****
I later tried setting the device start at 07000 for the AT29C256 chip and device end at 07FFF with no luck.

I later tried setting the device start at 08000 for the 27SF512 chip and device end at 08FFF with no luck.

I tried posting this in C4 Scan and Tune but it seems they have the day off.

 

how is it dealing with this guy alvin?
I can't get him to answer emails or return phone calls???....

 

I can't comment on PP2, I use Moates Burn 1, can't get any easier.
The fan running is a sign of limp mode, due to a fault in the chip burn/install process.
Good luck

 

$6E doesn't start at 0000. If I recall, when using a 29c256 you need to
start it at 04000, OR double the bin.

-- Joe

 

Start address 4000 for 256, or C000 for 512, or stack the bins as required to fill the chip.

 

Thanks guys, I'll try the new device starts.

Do I adjust the device end box?

Leave buffer start at 00000 and only alter the device start?

 

Umm.. No because the buffer is still 32k vs 16k. So set both to start at 4000 and end at 7FFF and you should be all set.

Been a while since I've done this heh. been using ostrich for a few years now.

-- Joe

 

Thanks for the help guys. I also tried this in C4 Scan and Tune but as I said already , they must have a few days off.

I programmed the 256 chip no problem, but when I tried the 512 chip, when I set device start to 0C000 , the device end was 0FFFF and couldn't change it.

I'll try the 256 chip and let y'all know.

 

C000 to FFFF sounds correct for programming a 16k bin file onto a 27C512 chip or equivalent.

You're putting the 16k bin file (and 16k buffer) into the last 16k of the 64k device. FFFF is the end of the device.

Another method would be to stack the 16k bin file 4 times to create a 64k file and start programming from 0 so that the device is filled.

If you're putting an already stacked 16k bin (which is 32k) onto the 64k device then you would want to start programming at 8000.