BASSr

Hope the moderator does not mind, but since the subject line where this was did not really convey where this had gone, I started a new thread!


Ok, still having trouble with the burning of the new chips!

I have tried the starting/ending values of 00C000-00FFFF and still having trouble reading the chip when I put it in the MEMCAL and in the ECM.

I did do a little trouble shooting to make sure this is where the issue is.

I can take the stock MEMCAL with the stock ABWN chip in it and put it in the ECM, start the car up, runs fine with no SERVICE ENGINE light on. I also can link to the ECM via the Rhinda cable and DIACOM software and read what is going on. I also try the HyperTech chip I had from my Monte Carlo and that also gets the same results, so I am sure that the issue is not the HyperTech MEMCAL I am using, not the Rhinda cable, nor the DIACOM software.

What I am doing is taking the 27FS512 chip in my burner, selecting the 32b$ bin which I have modified from the original ABWN bin (only the TCC tables at this point have been changed), burn the chip with the start/end values of 00C000-00FFFF and do a verify, so according to my burner, all seems fine!

When I put this chip in the Hypertech MEMCAL and put this in the ECM, as soon as I start the car the SERVICE ENGINE light is lite and when I try to read the ECM via the Rhinda cable with the DIACOM software, it can not link to the ECM. Assumption here is that the starting/ending address I am using is the culprit!

Any ideas on how to proceed? I am lost at this point on what to do next!

HELP GUYS!

BTW, the reason I am using the Hypertech MEMCAL is that it is setup so I can insert/remove the chips without any soldering, works fine. Also, the Monte Carlo Hypertech chip is very modified for a 406 TPI MAF setup and I am running a much leaner configuration with this 305 TPI MAF setup.

ALso, I am using a TOP 2009 Burner

BASSr

Well? No one have any idea's or comments for me?

Come on, someone has to have some idea of what the issue is here?

No one else ever run into problems trying to burn 16k onto the 27FS512 chips?

JP86SS

iTrader: (1)

Is checksum updated correctly with your changes?
Sure the chip is erased prior to reburning?
Try stacking it in TP first, then burn a full chip and verify.
Try saving in TP to recalculate checksum then use burner.
Are you able to put AA for the mask ID?
Are you sure of the range that is set in the definition file for the checksum to be calculated on?
Tossing them out there.

BASSr

JP,

Thanks for the info. Much appreciated, but I do have a number of points to clarify from what you asked:

Is checksum updated correctly with your changes? I assume so, as verify comes back good!

Sure the chip is erased prior to reburning? Yes!

Try stacking it in TP first, then burn a full chip and verify. TP, I assume you mean Tuner Pro? Stacking, not sure I follow what stacking is? When burning, I do the full chip and the process does a "verify", that is with the burner, not the editor. I am using TunerCat as an editor.

Try saving in TP to recalculate checksum then use burner. Again, TunerCat, not TP. So I'll have to check what I am doing in TC to see if I am doing it right.

Are you able to put AA for the mask ID? Please explain, not sure I understand what you mean here?

Are you sure of the range that is set in the definition file for the checksum to be calculated on? Again, please explain further, not aware of this process.


I am a newbie to this, so sorry if I do not understand all you are asking here.


Now, some updates:


I rechecked all of what I was doing and before you replied, I re-burned the same chip with same modified ABWN .bin.


The changes I am making at this point are simple, changing values to TCC tables since that seemed most basic. Axle ratio I am running is different that original ABWN .bin and the lockup was happening earlier than needed so when ECM cable was plugged into trans, stock TCC values were making the lockup happen earlier and car was lugging when over 30 mph, so I disconnected the ECM to trans cable, made the TCC table changes and that is the V1 modified ABWN .bin I have been trying to burn.


Installed chip earlier today and first thing I noticed after starting motor was that the service engine light did not come on. Took it for ride after reconnecting the ECM to trans cable, trans with lockup was much better (still not quite right, need to change some of the TCC table values) but I did see changes, so I can only assume that the modified chip was being seen.

I tried to communicate from my PC DIACOM software, still would not link up, so there is still an issue there.


The 305 is modified so before I start making changes to tables for injectors and modifed cam, I want to get the trans TCC changes correct. ONE THING AT A TIME!


Help me out with some clarification from your questions and I think I can say I am making some progress! :-)


Somebody remind me that I am having FUN doing this and why I want to change from a stock setup?

JP86SS

iTrader: (1)

Verify only means what you burned matched the file on your computer.
The checksum is a calculated value based on all the calibration values in your bin file. This checksum value will change with ANY modification to a value in the bin.
If the value stored as the checksum does not match the total calculated value, you will get an error.
The chip can still verify fine but the program throws an error because it is assumed to be corrupted if the two numbers don't match.

There is a "range" of addresses in the binary editor's definition.
This range is what is added up to make the checksum value.
This is setup normally and users never need to change this.
Some definitions in the wild could be incorrect, that's why I mentioned it.

Putting "AA" in the mask ID position in the bin file bypasses the checksum routine so it is a quick way to see if that is indeed the problem.
For the bin program to be active in the ECM, it must be placed at the end of the chip. TP has a "stacking" arrangement to place multiple copies onto the chip to ensure there is one at the end.
Not needed if you are familiar with the positioning addresses (offset) on the chip.
Again, it is a quick way to see if that was the problem.

TP recalculates the checksum automatically whenever you save the bin file. Not sure if TC does the same or not or if it is an option setting.

BASSr

JP,

Thanks. I just loaded TP and got the XDF file setup, so let me get familiar with it and try all youy said. Probably not until next weekend since work will be FUN this week!

Bruce

Bram

Hi, I'm very new (green as grass) to all this and have been doing a lot of reading recently and somewhere, I can't remember where, maybe Moates, maybe GM-ECM but I recall an article that explained trying to put $16 bit stuff on a $32 bit chip, one needs to use offsets. Does this sound right? If I'm totally out to lunch, please be gentle. I hope to get into this stuff in more detail soon.

Bram