Ultimate Chip Help? Stock Syclone

JnJSpdShop

New member
I have a whole bunch of older PROM / MEMCAL burning equipment and have a friend that just purchased a stock 91 syclone (40,000 miles). I found the ultimate files on powerplus and tried to burn a few of them to some 27SF512 EEPROMS and used the a older moates adapter I had laying around. No matter what I do none of these files will start the vehicle. The truck will just catch a bit but never really start up. I swapped out the stock 2 bar MAP for a 3 bar I had laying around (tested good 0-30 psi)

I am burning a single 16kb program using Moates Flash and Burn with these setting:

16k (16384)
27SF512
Buffer - 000000 -> 003FFF
Chip - 00C000 -> 00FFFF

Am I missing something or doing something wrong??
 

Quickstop [UK]

Combating adversyty.
Re: Ultimate Chip Help? Stock Syclone

What are you burning with - have you got the right .xdf file? Do you have a stock chip to start it with?
 

fivetodrive

CRISPY
Re: Ultimate Chip Help? Stock Syclone

You have to burn it to the end of the chip. So your offset is wrong. I don't know what it is off the top on my head.
 

JnJSpdShop

New member
Re: Ultimate Chip Help? Stock Syclone

What are you burning with - have you got the right .xdf file? Do you have a stock chip to start it with?

Using the Moates Flash N Burn USB burner. Yes I have the stock MEMCAL from the vehicle

You have to burn it to the end of the chip. So your offset is wrong. I don't know what it is off the top on my head.

I was just following the directions from Moates.net site on the offsets when using the 27SF512

http://support.moates.net/2010/04/05/programming-chips-using-offsets/
 

ZavzTy547

Senior Member

fivetodrive

CRISPY
Re: Ultimate Chip Help? Stock Syclone

I get a 404 on moates site but after a 30 second google search I came up with this on a mopar site.

Offsets: Here’s where things can get confusing. I’ll try to explain as simply as possible, without confusing you with too much HEX or hacker jargon. Interrupt vectors are special subroutines called when certain outside events happen (for example, the HEP input is triggered). The microprocessor expects the end of the memory space to contain the locations of these special routines. If these are NOT at the correct address, the code will likely not run at all. The address of these routines is always located at the end of the .bin file. So, the offset is required when the .bin file is smaller than the chip size. For example, if the .bin is 16k (LM or T2/S60 SMEC), and you’re burning it to a 32k chip, you need to offset the .bin by 16k – to put it at the end. If you are burning a 16k .bin to a 64k chip (27SF512), you need to offset the .bin by 48k. Here’s a breakdown:

.bin size Chip size offset (hex)
16k 16k 0 (0x0000)
16k 32k 16k (0x4000)
16k 64k 48k (0xC000)

32k 32k 0 (0x0000)
32k 64k 32k (0x8000)

This is the offset you put into the programmer when you load it. Here’s where it can get more confusing – this is different from the D-Cal ‘offset’ due to the location of the chip in the microprocessors memory space. Don’t get the 2 offsets confused.

Once you get the offset configured correctly, simply load up the chip and burn it according to your burners’ instructions.

Now, just load the chip into your newly socketed ECU, plug it back into the car, and give it a try. I’d suggest starting with the stock .bin for your car first, before trying to tune. This will help rule out any problems with the chip or ECU modification.

Edit - it looks like your buffer is ok but I dont have a flash and burn so I dont know if there is something else you need to do but this is helpful as well... My programmer is on the fritz so I have a new one coming soon and will play as soon as I get it.
 
Last edited:
Top