ok here is the deal I am usin a 7747 ecm and trying to upload the factory chip in tuinerpro I cannot get it to work properly for some reason...... It says it reads the chip just fine, and when I try to view it in tunerpro the settings are all wrong for instance anything that has to do with spark, wether it is a table or a constant reads 89.65 everywhere!!!!! I have tried half a dozen .ecu files and get the same issues so I have to think that it is in some way reading the chip wrong........... I am reading the chip as a 27c512 and using the hex address settings that tunerpro automatically sets (however I have tried reading it using all of the other options in tunerpro and many different adresses) Can someone please enlighten me as to what I am doing wrong.

 

You need to read the device at starting at F000. Mr. Moates has a nice writeup about what offsets are needed for what size chips on his website.

http://www.moates.net/documentation....entation_id=20

 

If it's factory 7747 then it's a 2732 chip.
What are you using to read the bin from the chip?


Have you tried to just load any $42 bin file from the net?
Or find the BCC for yours and just down load it and see if it works.

What's your BCC?

Here's what I just did to read a BCC of ASDU9567.

Open tunerpro.
select XDF button.
select import....from ECU
Pick your location for the 7747-mine.ecu file
go back to xdf button
select save xdf
name the file 7747
then go to file....
open bin

select your 7747($42) bin

 

Just a silly comment, but did you click save buffer to file after reading the chip? Also, do you have the chip oriented correctly? (notch up w/ empty slots to the top...Top being where the handle is on the AP Zif).

If you're not reading the stock 2732 chip, make sure your offsets are correct (see moates' web site).

 

ok, It is the stock chip that I am trying to read and I did finally get it to read using 27c512 chip settings in tunerpro and everything looks correct but none of the changes that I do are making a bit of difference on it. Am I still reading the chip wrong??? I have been emulating with this thing for the past hour and no changes to anything seem to happen when I try to. I am also completely not used to this 7747 ecu. I have been using a 6395 with an $od bin and not having any issues to speak of, but this 7747 seems a bit dumber than the 6395........ or maybe the operator

 

Why are you trying to force your programmer to read the 2732 as a 27c512? This makes no sense. Read it as a 2732!
Then, when you're programming it onto a larger chip you need to offset the programming. Be SURE, if using the 27sf512 chips, to earse them first before programming. The only reason you would be using the 27sf512 chips on a 7747 is if you've got a g2 adaptor or one of Craig's older 8 in 1 switching adaptors (been discontiuned for a while).
It would be a lot easier if you just listed all the hardware you're using.

 

ohhhhh.....thats some need to know info right there. Yeah, just read it as a 2732

 

Somebody start a pot of coffee!!!
Didn't we say that 3 hrs ago?

 

I don't see where you said "Somebody start a pot of coffee!!!" 3 hours ago

 

Sorry...I just woke up!

 

sorry I was ASSuming that he had 27c512 chips since thats what he told us. But I'll take a cup of joe if your making

 

I tried reading it as everything that it listed for the chip selections as I stated earlier....... and I stated that it is the factory chip in the first sentence of my original post....... The reason that
I was trying to read it as a 27c512 is In one of my many searches That is what someone said that the factory chip is apparently they were wrong, I am a mechanic I didnt know this.............. I build engines and transmissions and frankly carburetors are boreing and crude so I am playing with efi......... I will be the first to admit that I know nothing about the internals of the computer but I am trying to learn. That being said I figured out this P.O.S. It appears that something to do with my laptop being windows 2000 or just an ancient pile of crap didn't agree with something. I grabbed my other one (win xp and not from the stone age) and everthing plays nice. thanks for trying to help.

and screw the coffee..... gimme a beer

 

Nothing wrong with learning!!
I don't even mess with carbs anymore!!

It would help if you posted all the equipment your using.

Then the next guy that searches will have the info too.

 

tunerpro, usb autoprom, g2 adapter with a27sf512 chip and a 122747 ecm

 

I'm using the same stuff, but I've got the AT29C256 chip.

 

I have a couple of them but I have never used them what is the difference???? other than the ##s

 

The 27sf512 is an electronically erasable eprom. EEPROM if you would. The 29C256 is a flash prom. The 29C256 can be written over in parts/banks where as the 27sf512 needs to be completely erased before it'll reprogram successfully.
Also, not sure if you had a typo or not but your ecm is a 1227747, there's an extra 7 in there.
With the Flash & Burn software (for the Autoprom) you can read the stock chip as a 2732A. Once the chip is in the autoprom's zif socket lined up at the bottom with pin 1 facing up (away from your body and towards the zif handle), click the Read chip button. Once it's done reading the data from the chip will be in the buffer. Now save buffer to file. Open it with TunerPro and the 7747 ecu file, change whatever you wanted to change, safe it as a different file name, go back into Flash & Burn, select the 27sf512 as your chip, load file to buffer (once this is done the program will automatically offset the burn), *erase chip* important step, program chip, then verify. The chip won't verify with buffer IF YOU HAVEN'T ERASED THE CHIP! It would have said program sucessful when in fact it wasn't. In my opinion, this is a problem that needs to be addressed. With my xtronics programmer and software there is an autoverify routine right after the programming of a chip. If it doesn't verify it tells me outright where as this software says it was done correctly.
Craig, if you're reading this, mind adding an autoverify to your software?

 

yup I missed a 7 in there its a 1227747. Thanks for the explanation on the different chips I knew that you had to erase one and not the other and now I understand why.

 

One item I did not see is what is the 7747 being read with. A Prominator, Ostrich ???????


Did I miss it?

 

Yes you did. He said usb Autoprom.

 

I knew I should have cleaned my glasses.

 

So, I'm a little lost here. Are you trying to read the original stock chip (which would definately be a 2732A), or are you trying to read the 27SF512 you bought from Craig with your G2?

If the former, read it in TunerPro as a 2732A. Once you've read it, open the hex editor (from the chip IO tool) and make sure there is actually data there (not all 00's or FF's). If there is, save the buffer to file, then in TunerPro, open the file in the main editor.

Make sure you're using a valid XDF file to edit this bin.

If the latter (trying to read/write the 27SF512), you need to adhere to the following policies:

1) Offsets - you need to burn the (4k byte) bin to the proper offset in the (64kb) chip.
2) Before writing, you must erase the entire chip.

Good luck!

Mark