DIY PROMDo It Yourself PROM chip burning help. No PROM begging. No PROMs for sale. No commercial exchange. Not a referral service.
Welcome to ThirdGen.org!
Welcome to ThirdGen.org.
You are currently viewing our forum as a guest, which gives you limited access to view most discussions and access our other features. By joining our community, at no cost, you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is free, fast and simple, join the ThirdGen.org community today!
Originally posted by 32V_DOHC Today I uploaded the $40 mask to http://moates.net/fileman/index.php
This is for 1228079 and is named 8079.src. This mask was used with most if not all 87 and 88 CCC carbs.
Darned if I can find it.
What file name is it under, and in what category?.
Wow! This is wicked awesome! Different ECM than I have, but would be easy to make one work! Is the original bin out there, too? I would be willing to do SOME work on a ECU file....... In fact, I'm starting one.......
Actually I have good starts on the 84, 85, and 86 ECM's also. The Knock stategy changed for later years and the early stuff is still a mystery. One of these days I'll destroy an ECM to find out what it really is.
I've got the 88 SS bin. I also have the 85 SS and a couple of LG4's. Kinda be cool if we could get people to pull and post them. Maybe we can get a ZZ4 bin posted. Posted the 88 bin under stock bins. It is called 88ss_l69. The 85 SS bin is called 85ssCPY.
I'd be willing to contribute my '87 LG4 bin file, if I can find time to get it read from someone. I'm new to this yet, but I'd like to get into it now that theres actually a starting point to go from (a.k.a. it seems more possible to me now) for these CC Qjet systems.
32V_DOHC, not to steal any secrets or anything, but how do you people come up with this stuff?? I mean, seriously, where'd you get it from or how did you figure it out?? I'm really curious.
I have a few items coming our right in my ecu file that I'm working on, but some things look weird. It looks like it's pulling all the timing out as the MAP Kpa and rpms both go up. I thought it was just how I had the ECU file, but the values in the hac reflect the same. Anyone know anything about this? If that's how it's working, it would explain how my carbed car is running!
__________________ http://www.jpteck.com/efi
------------------------------
ASE Certified Master Tech
Originally posted by JP84Z430HP I have a few items coming our right in my ecu file that I'm working on, but some things look weird. It looks like it's pulling all the timing out as the MAP Kpa and rpms both go up. I thought it was just how I had the ECU file, but the values in the hac reflect the same. Anyone know anything about this? If that's how it's working, it would explain how my carbed car is running!
These engines can't use much timing. I converted an '85 LG4 over to TBI and the timing is minimal.
At 2,400 RPM & 100 KPa 12-13 degrees is about right. This is with 87 octane fuel.
Originally posted by RBob These engines can't use much timing. I converted an '85 LG4 over to TBI and the timing is minimal.
At 2,400 RPM & 100 KPa 12-13 degrees is about right. This is with 87 octane fuel.
RBob.
That makes more sense than ever! That's probably most of my problem with the 350. With the alumnum heads and more compression, I'm sure it wants more timing, maybe not a bunch, but that may be why it "falls down" at WOT.
I need to do some more work and start trying stuff!
Originally posted by 87Formula4bbl 32V_DOHC, not to steal any secrets or anything, but how do you people come up with this stuff?? I mean, seriously, where'd you get it from or how did you figure it out?? I'm really curious.
No secrets to steal. Most of how to do a hack is in the source code stickies. There are several good hacks out there to use as models. Becoming familiar with ECMguy's hacks and Rbobs hack are good starts. Getting the Pink book and the ALDL info files will allow you to see what is going on with the code and give you names of a few variable to start with. The rest is the tedious task of unraveling what is what.
Originally posted by anesthes Is the '83 carb ecm the same?
-- Joe
No it is not. However it is very similiar. You may read the 83 chip by getting a long pin (wire wrap) socket and bending pin 18 outward. Jumper pin 18 to VCC and read as 2732. If you send me an 83 bin I can probably give you a good start on programming the 83 computer.
Originally posted by 3.8TransAM Any word on a version for Olds engines?(or is ther mask the same)
We have bnever been able to get anythign worth a hoot :-) lol
I know the ecm's and pintouts were slightly different?
Any info please let me know?
later
Jeremy
Send me a bin (see above) and I will tell you how different they are. Most of the bins I have seen lead me to believe that they started with source code and made minor changes. Each new change was a new service number. They seem to be enough alike to be able to find most tables without destroying an ECM to get at the code.
I've uploaded (moates) the CPK bin & txt file (stock bins dir). This bin is from an '85 LG4 w/a CCC Quadrajet. The beginning portion of the bin is similar to the '8079 stuff. Didn't look much further then that.
If it wasn't for this thread I wouldn't even had read it
I have a quick question. Not to sound dumb here (because I'm still quite new to this, but I have done some assembly language with Intel chipsets), what is next? I could not get the source code to compile (didnt expect it to) and I havent done any compiling in a while, and I dont even know where to start with the 7xxx errors, because it has been a while since I've even looked at AL. So, does this source file need assembled at all, or can it just be read through to make the ECU file, and then just load the .bin file (assuming its the correct .bin file for the ECU definitions) into TunerPro or whatever your using? I've already started on the ECU file but I'm not REAL sure I'm doing the right thing yet. I've only gotten to about address location 0007 so far, just to see if I'm doing it correctly. Seems to read the values in just fine, so far. Is this the next step? Or does something else need done or 'checked over' first? (aka, the source file?).
Also, how do I go abouts finding the checksum size and address?
I'd assume the checksum start address and end address are just the start and end of the file address (what you have labeled in the source file as 'file start' and 'file end' or 'disassembly start' and 'disassembly end' addresses?
Ok, maybe that wasnt such a quick question, sorry. I've already learned a bit just from reading the source file, and things are becoming more clear here, so bear with me if you can!
Oh, I used Hex workshop to read the binary file, and did a checksum calculation, and it gives it in -8, -16, -32, -64. Do I use one of these values, or one of the other (CRC-16, etc)?
Will I come across the checksum address in the source somewhere? Or is that defined elsewhere?
The posted hack is far from ready to assemble. It wasnot done with that in mind. If one was to go to source code with this the board would need to be made romless and the calibration part moved to $C000 or something like that. If I were going to do that I would start with a code seeking disassembler that allowed for commenting from the control file and with scripts.
As far as a checksum there is not one. Just acheck byte to identify that that PROM goes with that ECM. Since the CCC carb proms were BPROMs checksum protection was not needed. If one was to source code this mask for romless a checksum routine should be added to insure the bits don't change.
Originally posted by 32V_DOHC The posted hack is far from ready to assemble. It wasnot done with that in mind. If one was to go to source code with this the board would need to be made romless and the calibration part moved to $C000 or something like that. If I were going to do that I would start with a code seeking disassembler that allowed for commenting from the control file and with scripts.
As far as a checksum there is not one. Just acheck byte to identify that that PROM goes with that ECM. Since the CCC carb proms were BPROMs checksum protection was not needed. If one was to source code this mask for romless a checksum routine should be added to insure the bits don't change.
HTH
John
Ok, so what is a BPROM? Is it a program once device? To burn chips for it, what chip would it take? If this is too much trouble, I'll just use a timing only setup with a 730 (since I have one sitting here). Also, to edit in tunerpro, what would you tell it for the checksum address?
Sorry, but I'm not all that technical at this level.....
Was the 8079 ECM architected like the 7747? By this I mean were *all* of the contents in the 8079.src file located on the removable chip? Or, did you have to come up with a way to download the portions of code located in some of the "permanently soldered" chips within the ECM? Rbob, was the '85 CCC stuff this way, too? My impression is that the 7747 has software located within the bowels of the non-removable chips that make source code changes difficult without some intensive engineering changes to the hardware.
It would seem that in the event all the source code was located on the removable chip, it would be relatively easy to implement source code changes for these applications. (Not withstanding the effort to come up with an appropriate understanding of the software! ) The biggest difference would be programming an 81S181 rather than a 2732/27128/27256. Given this condition, I don't think we'd have to move any of the calibrations around within the memory itself?
Let me know if this is just wishful thinking! Thanks!!
Originally posted by JP84Z430HP Ok, so what is a BPROM? Is it a program once device? To burn chips for it, what chip would it take? If this is too much trouble, I'll just use a timing only setup with a 730 (since I have one sitting here). Also, to edit in tunerpro, what would you tell it for the checksum address?
Sorry, but I'm not all that technical at this level.....
I have been using the 2532 eprom in that computer. It works fine. Several of the crossfire guys have used these in their early C3 computers.
For the checksum I started by using winbin and having it ignore the checksum. My latest thought to try is telling tunerpro the checksum is the promid. Run the checksum on all but the last two bytes and let it fill in those. They are never referenced so it will be cool.
Was the 8079 ECM architected like the 7747? By this I mean were *all* of the contents in the 8079.src file located on the removable chip? Or, did you have to come up with a way to download the portions of code located in some of the "permanently soldered" chips within the ECM? Rbob, was the '85 CCC stuff this way, too? My impression is that the 7747 has software located within the bowels of the non-removable chips that make source code changes difficult without some intensive engineering changes to the hardware.
It would seem that in the event all the source code was located on the removable chip, it would be relatively easy to implement source code changes for these applications. (Not withstanding the effort to come up with an appropriate understanding of the software! ) The biggest difference would be programming an 81S181 rather than a 2732/27128/27256. Given this condition, I don't think we'd have to move any of the calibrations around within the memory itself?
Let me know if this is just wishful thinking! Thanks!!
The code part is on the RAM/ROM/IO chips. They must be removed from the board to be read or you would need a board that would provide Eprom reader type capabiltiy from the edge card. I don't know of anyone who has done the latter.
If you wanted to do source code the easiest way is to convert the board to romless and use a 27128/27256/27512. Once you have source coded the code and cal you could easily move the cal to have all the code and cal fit within a 27128 with plenty of room to spare.
Originally posted by 32V_DOHC The code part is on the RAM/ROM/IO chips. They must be removed from the board to be read or you would need a board that would provide Eprom reader type capabiltiy from the edge card. I don't know of anyone who has done the latter.
If you wanted to do source code the easiest way is to convert the board to romless and use a 27128/27256/27512. Once you have source coded the code and cal you could easily move the cal to have all the code and cal fit within a 27128 with plenty of room to spare.
HTH
John
I don't think I'll be the one to go through all that! I plan to go with EFI sometime in the not so distant future (ok, far off enough that I can't see it yet) but I will like being able to play with the timing!
If only I could use an Autoprom, or Prominator in it......
I'm still debating whether I really want to buy a chip burner to mess with this, especially since when I do start into the EFI, I plan to use a Prominator, or Autoprom.
) The biggest difference would be programming an 81S181 rather than a 2732/27128/27256. Given this condition, I don't think we'd have to move any of the calibrations around within the memory itself? 
