Reading $F0 chip from '94 resulting in bad file?

[scorp508]

EDIT SOLVED: I had my buffers backwards for a 32KB program on a 64KB chip. My Chip Addressing and Buffer Addressing were reversed.

It needed to be.

Chip Addressing: 8000-FFFF
Buffer Addressing: 0000-7FFF

After fixing that the file looks good.


Good ole' web archive: https://web.archive.org/web/20201128...using-offsets/

--- original post below ---

I'm trying to make a backup of the custom chip in 1994 #150 (Corey Henderson tune) for archival purposes in case anything ever happened to it.

I purchased a new chip reader/writer as my old one I used for L98 tuning 20 years ago was not even USB based.

This is what I purchased and it's essentially a clone of the Moates version. After Craig closed up shop and retired these folks have been carrying the torch forward.

https://boostednw.com/chips-and-adpt...ner-programmer

It is a 27SF512 chip in the car in a Moates adapter, a pretty typical setup.

If I read the chip with a 0000-FFFF buffer I end up with a 64KB file, but my understanding is the $F0 program should be 32KB. I changed my buffer to 8000-FFFF to get a 32KB BIN file as I thought the correct buffer was the last 32KB of the chip. I do have the chip with its notch towards the ZIF handle and the opposite end of the chip aligned with the "bottom" of the reader/writer.

Loading the file into TunerPro looks.... odd. Tables aren't smooth and things like fuel cutoff RPM show "60", yes sixty, instead of ~7,000 the stock BINs show. Injector flow rate is "0.39" which is also obviously wrong.

It has probably been close to 10 years since I messed around with these things. Am I forgetting an obvious step? If I load a stock BMCB file with the same $F0.xdf file everything looks normal. I tried 8E, F0, and F0A on the file with all the same results.

I'll toss it back in the car to make sure it didn't somehow get zapped in the 15-foot walk from the car to the laptop.