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!
ok i have been working with this m6811 disassembler for quite some time. Disassebling the (im going to call it the corvette bin) from the 165 $6E works quite well. We've established that. However, disassembling my choise of bin file seems to be a worthy task. Knowing that the labels are NOT my problem in the control file, im not going to look for a problem in it, as i did what the PDF file told me to do, INPUT file....OUTPUT file.....entry address. However, it does not work. Gives me GARBAGE.dis file. I feel that using the m6811 ive gone back in time,(possibly 1979) hence not many windows based programs avalible (possibly windows 3.0, but not 3.11, not yet). Not here to bash anyone, but doing things the hard way? when do we stop. Im going to attach some files here, again doing this the hard way, one post at a time since i cant get 3 on one post. CATS cross disassembler picked it right off (maybe m6811 should have, or possibly cant). This thread will tell the tale. A.txt is my control file, A.dis is the disassembled of A.bin file, and BMU(cats).scr is tha CATS disassembled of A.bin.
----------
a.txt (control file)
----------
ok this is redundant, ud think that in 2007 it was possible to attach a txt file. well just take my word for things, if anyone wants to look over my files ill have to send them to you, meanwhile, im gonna look over my CATS disassembled files
Last edited by escort_ford84; 06-11-2007 at 02:51 AM.
Reason: Automerged Doublepost
It may just be me guys, im just not sure. 2 years with DIY prom stuff and this disassembler and nothing, absolutly nothing. I just need to make sure that the disassembler can do this bin, if not, that would answer my question. I may just go back with ECU stuff like before, but like i said, im not getting "THE" answer i need. Ive read the posts. Going threw 100's of them just isnt cutting it, this one will solve it. The bin file just might be too old for the disassembler.
ok after reading some corvette forums this may have been a dead issue. IMO hac'ing this bin file might actually be imposible, or defiantly not feasible. Perhaps i was asking to much from members or the disassembler. i will now start to hac what has already been hac'ed such as what everyone else has done and start matching, just as ive seen before. Perhaps everyone is right, whats done has been done, there is no more. Hac whats been hac'ed and start coding. More referenceing would be helpful here, since ive done all the rest. If the corvette guys couldnt get this one, it doesnt look good. exactally.
The code can be disassembled, and reassembled again. But, this does require time, and above all, patience, to clean it and eliminate any extranous labels and such. You also need to make all the addressing inherent. In other words, instead of using $34BC as a label, use L34BC, or LABEL50, or something. This means that the assembler will know to always point to that label rather then an address, even if it moves in teh addressable memory so the code will execute properly. After writing lots and lots of code, I can tell you that this is important to get right prior to assembling. The labeling needs to be perfect. After that, you need to reassemble and compare it to the source to make sure its correct. You should be able to recreate it perfectly. .
To assemble, try the miniIDE assembler. There are others that work well in addition, but this one has worked without issue for me. Dont use the windows GUI, its horribly slow, especially with large source codes. The dos based 32-bit ASM11 assembler works well with the source code for my PCM, and thats about 5-6x the size (64K total) of the early CFI ECMs and also runs under the later iterations of XP.
See one of my earlier $0D hacks in the "TBI guys, its time to update!" thread. That shows what it should look like to make it assemble properly. Its a real PITA, but if you take it one step at a time, it can be done with some patience, swearing and hair pulling is optional.
Last edited by dimented24x7; 06-11-2007 at 10:46 AM.
Escort, are you familiar with assembly yet? I ask because prior to doing assemblies, you should become familiar with the assembly and instruction set. Itll make things alot easier.
Possibly, could the processor in the 1222550 not be a 6811? OK, I'm not familiar with Assembly yet, i was trying to get the disassembly down, but i will look at assembly now, and I'm going to read that thread "TBI guys, its time to update". I'm going to find miniIDE assembler. I think ive tried leaving the $ off of it once, ill try that L34BC. I'll try to attach the CATS disassembled file, looks to me like its a disassembled bin file to me. I'll zip it, that may have been the problem before. Those bin files are 1K in size for the 1222550 and the 1222570.
The file you attached is a disassembly of the EPROM portion only. With a C3 style ECM, the calibration bins that are download-able are not code complete. The ECM circuit board contains 2 ROM chips that also need to be dumped (to the same file). The combination of the 2 ROMs and the 1 EPROM (removable) is what makes the complete firmware that the ECM runs. It is this complete copy of the firmware that you need to disassemble...
See the section on dumping the C3 Rom. I did this on my C3 and it works. It would probably take some modifying on an old CFI ECM, though, to get it to work.
You must have missed where I told you about needing the Rom for a C3 to work.......
As far as fixing the indirect addressing. You need to get it to disassemble and assemble correctly first. Then you can go back and make it relocatable. This is actually a bigger step than getting it to dis first.
The dewtronics package works well for this since the dis file is already setup to work with the assembler. Not address fixing needed.
As long as your entries and indirects are correct it will go back togethor.
Even if you miss and entry it will still assemble and compare IIRC. That's what the clump posts were about in the orignal dummies thread.
