Has it happend yet?
I have just tested my Pocket PC logger and running on the PC it connects to the car at my custom baud rate of 19200 baud on COM1 virtual serial port. The graphing doesn't work when run on the Windows PC, but it connects and logs. I intend to transfer the fuel and timing editing to this app and then post it as a starting point so we can all see what is required. It would be better to rewrite it to use FTDI, but I need to keep my list of things to do sensible for a first go.
CPU is SH7052 on Evo 7/8, SH7055 of Evo 9. KPIT Cummins do a free and good asm, which I have used to produce relocatable code which I patch in using a hex editor. This sounds fussy, but is much easier than trying to compile a whole image. Bez Bashni has posted some disasms on Aktivematrix.
ACD ECU uses a different series of CPUs and no image has been posted yet.
CPU is SH7052 on Evo 7/8, SH7055 of Evo 9. KPIT Cummins do a free and good asm, which I have used to produce relocatable code which I patch in using a hex editor. This sounds fussy, but is much easier than trying to compile a whole image. Bez Bashni has posted some disasms on Aktivematrix.
ACD ECU uses a different series of CPUs and no image has been posted yet.
If you wanted to do an open source standalone tuning app I'm guessing you couldn't use the mitsulogger interface code and would have to start over from scratch. Unless you could convince Jack to allow you to distribute that part of the source code.
When you say "each ECU" do you mean every individual ECU or each of the several different ROM codes out there? If it has to do with different ROM codes you handle it like ECUFlash does and use a definition file.
Speaking of which, what Renesas CPUs are in the Evo? I found a boatload of data sheets and manuals and wanted to start looking at disassembly of the source code, but I don't know which series of chips they're using. Are there any free disassemblers out there so I don't have to write my own? And has anyone posted the assembly code with notes as to what's been figured out and what hasn't?
Is anyone looking at disassembling the ACD controller on the IX?
When you say "each ECU" do you mean every individual ECU or each of the several different ROM codes out there? If it has to do with different ROM codes you handle it like ECUFlash does and use a definition file.
Speaking of which, what Renesas CPUs are in the Evo? I found a boatload of data sheets and manuals and wanted to start looking at disassembly of the source code, but I don't know which series of chips they're using. Are there any free disassemblers out there so I don't have to write my own? And has anyone posted the assembly code with notes as to what's been figured out and what hasn't?
Is anyone looking at disassembling the ACD controller on the IX?
That would be the way to do it if there is some general common thing about them. Then it would be a matter of defining a common XML schema to represent the tables. Then you write XML defs for the known roms (start with your own of course). XML parsing in .Net is pretty simple so that would be the easy part.
Last edited by codgi; Dec 5, 2007 at 10:47 PM.
From what I could tell looking at the assembly code I think it uses static RAM addressing so that should be feasible.
I downloaded Bez's disassembly of the 0015 ROM and there's still a ****load of stuff that isn't defined, as far as code goes. I'm still muddling my way through the assembly syntax. The last time I worked in assembly it was in MIPS and it was about 7 years ago, so I was pretty lost last night (thus the headache).
I downloaded Bez's disassembly of the 0015 ROM and there's still a ****load of stuff that isn't defined, as far as code goes. I'm still muddling my way through the assembly syntax. The last time I worked in assembly it was in MIPS and it was about 7 years ago, so I was pretty lost last night (thus the headache).
Thread
Thread Starter
Forum
Replies
Last Post
GrabbinGears
General Engine Management / Tuning Forum
2
Jul 7, 2016 02:19 PM








