im tryin to get and run the dissasembler to view source code to apply patches and try and see how the code goes togather...im new to prom burning yes but i just wanna see how this stuff goes togather and i want to apply a couple of patches like egr, and forced knock test. i read the patch article as well as the source code article w/ directions on the dissasembler...i tried that method and get this message when trying to open in dos: C:/Windows/system32/cmd.exe-C;/m6811dis.exe
..... the system file is not suitable for running ms-dos and microsoft windows applications. choose close to terminate the application. is there another program to dissasemle or even better yet a already dissasembled file for the 8746 $61 please help i wanna get the easier stuff out of the way before dataloggin like the egr, rpm limit, and knock test patch. and smog delete etc....thanks for any help u guys can offer
John

 

oh and i also found rbob dissasembly but its just a web page dont i need a dl file to actually change??

 

There should be a disassembly of the '8746 ($61 mask) on moates.net/fileman. In a zip format that can be downloaded. Unzipped will be the 8746.dsm file. Can't assemble it in the provided form, but don't need to. It has all of the addresses and binary listed in the left hand columns.

RBob.

 

but to apply the patches dont i need to assemble it dont i need to assemble it if not then i will have to go back and read your patch thread!! great thread by the way after about five times i dimly understood it...lol....but thats okay as long as it starts to make since that means i will eventually get it. thanks
John

 

i was just searching through some of my many files i have save and found a dissasembly of a 8746 $61 ecm but it says that its for a anlu is this the one your talkin about i will check but if thats the one i need one for one or all of these ANTT AXKT ANTS AXKS cause these will be the ones i use to patch and use in my car since i have a 305 w/ a 700r4 sorry i should of been more specific in my requests
John

 

Here is how the patches are "installed"
https://www.thirdgen.org/techbb2/sho...hreadid=108380

If you have a compatible bin (they won't just work in any code) you can have the change done in a matter of seconds without having to do "the code" yourself. That's a much steeper hill to climb.

I know you've found it but it is worth reading again
There is another called "Source code for dummies" that will get you started and shows all the tools needed.

 

The way I make the dos stuff go in xp is....
Right click on the as6811.exe and select properties.
Then make it look like the pic.
You need to make sure the path for everything is set correctly.
Make sure you use as6811 as the name not the ashc11.
This will also work for the other dos programs.
Then make a batch file in notepad and save it with bat as the extension. The file names have to be 8? or less
letters plus the extension.
I make my bat file put up the cmd lines for all the different programs I use as a hint.
Then I use what I want at the time by typing the correct cmds and file I want to asm etc.
Make sure to hit apply save etc. Then click on the MS short cut every time you want to run that batch file.
I'd show my bat file but it's not with me and it's a bit messy with REM's.

 

if that is the patch demo thread i have read that and have a copy also but i need a dissasembled source code....to dissemble the bin and dissemble the patch to make sure my addresses are the same and if not to change the patch cause some patches i find dont say what bin names they work w/. im very new to this but hopefully i can get this part figured out it dosent seem to hard when i have a patch to already work w/ and just have to make the adresses work w/ my bin....and i will try that on the dissesmbler but when i couldnt even open it i didnt read the directions the rest of the way on how i have to make those files so i dont really understand that part yet i will have to read it. thanks all this should help me to figure this out so i can get the pre datalog changes out of the way. i need to get w/ jon to see if that .xdf or the stock bins i got from him already has the patches added to it.
John

 

Do a search on XVI32. (Thanks Trax)
It will allow you to cut & paste strings of code into it's search feature.
So you copy a section of bin A to the clipboard.
Open bin B and paste to the Hex search.
It will find the section of code if it exists in bin B.
This will allow you to find the offsets for code in the different bins of the same mask.
I had to do this on the WB patch on 7 8D bins. You can get a little cross eyed after a while.

 

sounds good i will have to look into that

 

hey z69 i just got home and looked at what u said to do i have m6811dis is it still the same way

 

i just tried that and %SystemRoot%\system32\cmd.exe thing on the program i have and it still has an error message when im in dos i put: cd M6811DIS and it says ....the system file is not suitable for running MS-Dos and Microsoft Windows applications. Choose 'close' to terminate the application...am i doing something wrong?? is there a dissasembler thats free and just as good that dosent have to be run in dos? this is killing me.

 

CD is a dos command for Change Directory.
Are your files in a directory called m6811xxx?
The cmd lines are exact. You can only change the names.
Not the punctuation.
It should be CD C:\xxxx
With xxx being the full path to your files.
It's easiest if you have them in the root directory. Or in a directory right off the root.
Did you use a batch file too?
The root% cmd.exe opens a dos window.
The batch file process keeps the window open till you hit close.
Keep trying settings. There are some in the other tabs related to dos. Might have to click those check marks too.

 

no i just have them in my computer/c:/ drive and i titled the cmd line just like u had it does that mean i need to find the system 32 folder and place them there?? i havent had a chance to read about the batch file part of it yet i was just tryin to get the M6811DIS to open in dos....do i need to have a batch file set up before this will work. i will read the file that comes w/ it again when i get home the evening cause im at work right now.

 

Dos programs don't like long file names.
But they will work if done correctly.
It would look something like this in the properties box.
C:\MYDOCU~1\ECM\AS11\AS11.BAT
No you don't need them in the system dir.
IIRC, it won't work right w/o the batch file.
I'm on my 98se machine so I can't test.

 

sounds good i will read about making a batch file this evening when i get home after i work on the heads a lil bit...id love to have a dissembled version so i can compare patches and make sure all the adresses r correct for mine. thanks ill let u know if i dont get it for some reason and thanks for hangin in there tryin to teach me because im not familar w/ dos other than pinging and collecting info to set up my router.
John

 

; control file for axkt.bin

input C:\1\AXKT.BIN
output C:\1\AXKT1.DIS

addresses
OPCODES



this is as far as i could get on the batch file but i dont really understand anything else it says since im not familar w/ hex yet....i will be using the axkt.bin to dissemble and it was a .bin for the 1228746 the adress range is 000000 to 00010F
but i dont know if that includes ram or not and if so how to leave out the ram part in the dissasembly. if u want to explain it or dissemble this file i will send it to u but im having a hard time but do wanna understand it if u would break it down to newb terms. im not sure if i can actually run the dissembler yet because now i cant get a batch file made. thanks
John

all i want to do is use it to compare the changed adresses in some patches that are labeled for a 89 caprice cop car .bin and its a different .bin name

 

The hac should tell you the start of the code section.
That # will be your first entry.
You need a load command too.
IDK what it is for a 746 bin. Might be $4000.
You need to follow the format of the ctl files listed in the Dummies thread. That is how the 6811 works.
Once you can get the DOS window to stay open in XP.
Then you can start using the 6811 cmds or add them into your original batch file.
Once you get it to dis, follow the clues in the dummies thread on what to do with the "clumps". I don't think you'll have too many since it's a 4k bin.

All you'll have to start with is a load and entry lines.
You'll need to figure out the indirects.

If you look at a bin, the very last word will be the address for your first entry. And all the words above it will be your indirects. 8D has some blank space near the end of the file.
So it's real easy to see as a beginner.
Not sure if a tbi bin does. I also found the addresses for all the indirects on DIY_EFI.org. It was under memory map or something. Not sure if a C3 list is there or not.

 

I was sitting here disassembling a couple bin files i have thinking how great this disassembled information would be if there was a way to discernthe actual source code.

 

Im thinking it would be easier to open the bin file in tunerpro, and just make an xdf file from that, using an xdf file that already exists as a reference. Somehow i thought the BMU.bin file from an 82 crossfire vette (1225550) would be easy to hac. Silly me.

 

The problem is with the text file, the APYP file doesnt work

 

Hi there,
I think that you need to re-read the thread as is here advised "Source code for dummies"
You will find all most all the questions you have.
If you say that APYP text file doesn't work, it is logical because it is for APYP bin and you need to find out your own Text File that normaly should be a CTL = Control File.

Regards,
Cobra289

 

Well, i see alot on the '165 ecu. I will read it again. I disassembled the ANLU bin that has already been done, however mine makes no sense and isnt close to the Hac thats already out. Making the control file is what im having trouble with. I want an ECU or XDF file for tuner pro for the 1222550 bmu9405.bin file.

 

I dont even think the bin has the whole code in it. Most of it is likely to be on internal roms of some sort.

If you cant find any def files for your ECM, it may be easier to just use a newer ECM from a later year TBI car or truck in place of the current one. That CFI ECM is as stone age as it gets, so its not really worth the effort to try and reverse it just to be able to get some tuning defs. If your in it for the challange, though, those old ECMs are the coders equivelent of training wheels, so they're a great place to start.

 

I agree. I use the 8746 ecu, just because my 7747 failed. I used to have a couple of 82 crossfire camaros and i liked the way they ran, as far as throttle response went. i was just curious about the AE settings really AND i thought that would be the simplest and easy to tackle first disassembly. i think i have everything down except my control file. I just dont see anyway possible to just "come up with" a control file, the 165 ecu is easy because theres one already made for it.

 

OK, 1 more time im going to read the source code for dummies. I think there is a limit for how many times i can read something before my brains starts to bleed. I think the things im missing in my control file is the labels. I dunno, makes sense. Here i go again.

 

Read the entire source code for dummies thread. A whole bunch of us just "came up" with control files. That was one of the reasons for the whole thread. The basic info wasn't posted anywhere and "we" all did it online so others would have an easier time starting out on their own project and learning how to do assembly for these ecm's. I admit the thread is a little confusing.
And some of the posted info for the CTL addresses used was already widely known. But if you know what the address is for and when it is referenced by the code. You will know how to find it in any of the bins. You can also look at similar hacs first to give you an idea of where to start with your ctl.
Take notes of the steps involved and then do it yourself. You may have to do one of the bins mentioned in the thread 1st by yourself to get the hang of it. And from my understanding, you will need the rom code for it to work right on a C3. I've never tried a C3. But all the crossfire people had to DIY it so I suspect they don't want to give away their work for free.

 

1225550
Description: Same ROM as 1225570
Application: 1982 5.0 V8 CFI “7” LU5
1982 5.7 V8 CFI “8” L83
MEMPAK IDs: “7”: TO, ALX, ASY
“8”: TS, ARY, ARZ, BMU, BPB
Program ID: 3 ($03)
Pgm ID Addr: $3002
Scan ID Addr: $33F8:$33F9
PROM type: N82S181
PROM offset: $3000