Hi guys, ok so i've slung up a few posts so far asking for advice with regards to burning chips and i've spoke to Craig moates, but still i cant get it to work.

I'm not too sure whats happened but my stock chip isn't happy anymore and wont run the car. It did up untill a few days ago however. When its in place it just wont start. When I take it out the car starts up in Limp Home Mode. I do have a copy of the chip that i made with Pocket Programmer II.

So where I'm at.

Ive got tuner Pro (free) and PPII and its software: Reprogramable chips 27SF512. I've copied the chip that was in the car and changed a few things (speed limiter ect.) then I saved this Bin. Then in TunerPro I went to the bin stacker and set it to...

16k bin size. 512k chip size. 16k block size.

Then i set each of the blocks to copy from the saved Bin and set another Bin as an output file. I then Clicked stack and it seemed to work. The output file was 512k as expected.

Next I went to PPII and loaded the Stacked Bin, Blanked a chip. set the buffer to start at 00000, chip start 00000 chip end 0FFFF. Then hit program device. It all seemed to work, but still the car wont start.

I have done this several times now. I also tried not stackin the chip and telling the PPII to burn from 04000 to 07FFF. still to no avail, however I wonder if I did not set the buffer start point aswell. Should I have?

Am I missing something obvious?

Sorry if this seems a pile,

Thanks for any help at all.

JAmes

 

Hehe

You did the same thing as me.

Stacker in Tunerpro should be set for
32 64 32


Remember to change the names of your input files, or else you use the same ones as previous. I keep forgetting to do this...

Good luck.

 

Actually, this depends on what mask. Looking at the pic in your icon, looks like you're running either $32 or $6E.

If $6E, you shoudl set the stacker to 16k bin, 64k chip (27SF512), and 32k block (if using a switcher).

If you're burning one 16k bin onto a 64k chip (27SF512), you want to set the stacker to 16k bin, 64k chip, 64k block.

hope that helps.

the 27SF512 is a 64KB (512 megaBIT) chip. Therefore if you choose to not use the stacker, the 16k bin should be burned to address C000.

 

Ok. I'm not too sure what a switcher is. From what i have found it appears to be some way of holding multipl bins and being able to switch between them? Is this right? How do they work?

I'll go give it a bash.

Thanks guys *hands over 1 e-beer to each *

JAmes

 

Ok big meaty problems now!

I have tried what was suggested. Firstly i'll give more details about everything we have.

165 ECM - trying to burn chips with $6E mask.

Dell laptop with XP (could this be a problem?)

PPII and the software that came with it. 27SF512 chips

TunerPro free.

From what i can work out, someone tell me i'm wrong and i'll be happy:

a bin should be 16k. this should be writen within the last 4000 spaces on a chip. Ie- stock chip goes from 0000 -> 4000. So writing onto the 27SF512 should go C000 -> FFFF.

Yes?

I tried stacking the chip so that it repeated the bin every 4000 spaces. I tried stacking it so that it did Blank for 4000 then bin, then blacnk for 4000 then bin from C000 -> FFFF.

This was with an Image off the original chip in the car.

I downloaded a stock bin from somewhere... forgot... its a 350ci with 3.27 gears bin. it says its 16k but when i put it into the PPII it has stuff for 8000 then blank for 4000 then stuff from C000 -> FFFF. I burnt this directly to the chip. No result. I tried stacking this like i mentioned above. No result.

All that is happening is the car will start up with no chip in it. (limp home mode, yes?) When i put the original chip in now no start, it just tries to turn over and sounds bad. But it did work up untill last week. Could this have been blanked?

When i put in my burnt chips it does the exact same. No SES light comes on in either situation.

Is the car gubbed or is it my burning methods?

A wee question aswell. WHen it has no chip in it will the Altanator charge? Please say no. As you may have noticed this sounds rush and has many typo's. This is because we took it out in LHM as we needed fuel fast, and didnt realise we had not charge untill it was too late then had to stand about in the rain and nurse the baby home with about 3 jump starts.

Sorry if this is asking too much, but the car owner's wife is about to kill him and sell the car or set fire to it if its not working perfectly soon.

Thanks

JAmes

PS. I can e-mail people copies of all the bins we have and are trying to use. or I can host them and you can Dl them. I dont have them on me now or i'd host them but can get them off the laptop.

 

Correct, start at C000. If NOT using the stacker. In other words, start at C000 if you're burning hte raw 16KB bin to the 27SF512.

OR do the following:

1) Open tunerpro and hit F5 to load the stacker
2) enter 16k bin size, 64k chip size, 64k block size
3) browse to your bin for input
4) browse to the desired output bin
5) hit stack - the resulting bin should be 64KB
6) place the 27SF512 in your PP2
7) erase the 27SF512.
8) Load the 64KB stacked bin into the buffer
9) Make sure correct chip type is selected
10) make sure you're burning in 8 bit Byte mode (Byte Program)
11) make sure the start address is 0000 and end address is 10000
12) click "program device"
13) put the chip in your adapter (which you should be using), making sure you've placed it correctly with Pin 1 towards the outside edge.
14) go for a drive.

If that doesn't work, I'd suspect your bin being invalid (checksum, perhaps).

Yes, it sounds like your stock bin has become erased.

 

My bad.

Sorry.

 

Mangus,

Once again many thanks for all your help and please keep it coming.

firstly:

I did all of the above, but set the block size to 16k, So i set the input files as the stock downloaded bin, 4 times.

The output file was then a random bin i created on the computer.

I hit stack and got a file size of 64k

Put this into PPII and burnt it. I never checked to see that i was in 8 byte mode, however i made sure i was using the correct chip.

set the buffer start to 0000, chip start to 0000 chip end to 7FFFF.

Hit program.

Took chip out, put it in the car. Car did not start.

This seems to be about as far as i've managed to get.

But, I had a look through the moates stuff and found I had Atmel 29C256 chips. I tried using this and did the exact same as above and also tried the burning location for the 16k file to 4000->7FFF.

When I put this in the car the car did start. However, I cannot tell if it is running in LHM or not AND the SES light stays on and will not give us a reading when we bridge pins A&B.

Can you tell me what you mean by Checksum?

I got the Stock BIN from http://www.truspeed.org/bins.html the 350 auto with 3.27 gears.

Again, thanks for all the help, here's hoping we get there soon.

JAmes

 

you *need* to make sure you're burning correctly. Make sure you're using 8 bit bytes. I've seen/helped others through this exact error.

7FFFF is the incorrect end address (that is a 512KB address).

a 27SF512 has an address range of 0-FFFF. YOu want to burn 16k to C000-FFFF.

You say the car starts when you burn from 4000-7FFF. this tells me you may actually be using a 29C256. Can you verify?

 

When i use the 512 i burn from c000 > FFFF and the car will not start.

When i use the 256 i burn from 4000>7FFF and the car starts, however the SES light stays on and will not read out a code. We also aren't too sure if the car is in LHM or not.


Cheers
JAmes

 

not sure what to tell you then. bad chip maybe (27SF512).

Sounds like maybe the 29C256 is working. If it was in LHM, you'd know with $6E (the car would barely run if at all).

The SES light might be a result of something incorrect in the bin. Why not start with your stock bin?

Have access to a scanner? If so, validate taht you're getting ALDL data from the 29C256.

 

PS - if, when you power up the car (key on, engine off) with the chip in it, the fans DO NOT come on, the chip/program itself is fine. If the fans come on, you don't have a valid bin (corrupt, incomplete, burned incorrectly, bad chip, etc).

So, with the 29C256, if the fans don't spin up key on engine off, the bin is fine and burned correctly.

 

Ok, well I've spent all day burning chips on both the 256 and the 512 and the car starts up the same with the chip as it does without it installed, there is no SES blink, and no ALDL data and the fans come on when the engine isn't on. I have tried both Moates adaptors aswell.

As I said above, the original chip that was in the car was working until last week, but isn't now. I have tried reading this chip again with PPII and then put it into TunerPro. It still comes up with all that was there before, strange dip in spark advance table, speed limiter, ect.

Is it possible that i could e-mail someone this Bin of the original chip and they could try it out for me? this would let me see if its possible the ECM box has somehow died but still reads th memcal.

Thanks again

JAmes

 

That same thing happened to me with my 8746 ECM. It just croaked. No ALDL data, but the car would run. I discovered on accident one day when I accidentally started the engine without the chip in the ECM.
One ECM later and the thing runs great. I use the Moates G2 adapter with a 24-pin ZIF and a 29C256 chip. I'll be outside in a few minutes doing some more tuning.

 

I have found once that if I forgot to re-caculate the checksum the car would start and I would get a constant SES light without the ability to check the codes.

 

I did that a couple of times yesterday, I think. I kept getting a very quickly flashing SES. The engine would start, but it would run like crap.

 

Should the checksum be different for every chip? how do you make sure that the checksum is alright for the chip you've modified?

JAmes

 

I don't really know for your set up. I am using TunerPro RT and it automatically calculates a checksum each time you save the BIN to a file. Not sure on this one either, but can't you put $AA into your PROM ID location and have the ECM ignore checksum errors?

 

Yes. 2 choices:

1) open the bin in tunerpro, click save (or save-as). the CS will be re-calculated

2) disable the checksum by placing AA in the mask ID byte (offset 0x08).

 

Sounds like all the right advice is getting kicked around...