EEC V file conversion

[decipha]

yeah post the bin i'll tell you what it is

I'm just about finished up on the datalogging for READ0 and will be posting it soon as I can get some free time.

yeah any info you have could be helpful shoot it over and i'll take a look

[BOOSTEDEVERYTHING]

Here you go. Thanks

[decipha]

yep thats read0

how did you get those ram addresses? I spent months figuring out those addresses and you already have them ?

[BOOSTEDEVERYTHING]

I’m not sure if everything is correct. I have just been going through comparing in my spare time. The spreadsheet helped a lot as well. Once I found the similarities with RZASA I just went to the software manual to make sure it looked to be doing the same thing. But like I said, could be a ton of errors. JSA and TVRFan have been a huge help as well helping me learn. I want to try and tackle some more of OMAE2 when I am a little further along with READ0 as well. I have to try and figure out exactly how to get a dir file from the definition file but I hope to be able to add as much as I can. I have a Harley truck that I am using SCT on right now but I do t think all the tables and parameters are correct in the software. My next endeavor is to try and start a definition file for READ0 so I can see if I can get a better definition than the one I am using in BE right now. I am using a Core Tuning def and it seems ok but I feel like it’s missing some things. And I would also like to add some code to it as well.

[jsa]

From the disassembly;

Code: Select all

9ff06: 52,45,41,44,30,41,37,2e,48,45,58,2a  text                                   "READ0A7.HEX*"

9ff12: ff,00              ???   

9ff14: 58,55,37,41,41,46,41  text                                                  "XU7AAFA"

Add the 12A650 to get XU7A-12A650-AFA.
http://www.obdtester.com/ford-ecu-updat ... 12A650-AFA
http://www.obdtester.com/ford-ecu-info/ml2_8a1

Going back early in this thread, it started from a RZASA disassembly using a DIR generated from a DMR file. Equivalent subroutines were identified between RZASA and this FLN0 bin. The address names in RZASA were transferred to the FLN0 (EQE3) DIR equivalent addresses.

[BOOSTEDEVERYTHING]

Guess I need to rename my files. LOL. Crap, It even gives you the strategy 2 lines up. Guess I should have named it correctly to start with. Thanks for the clarification.

Going back early in this thread, it started from a RZASA disassembly using a DIR generated from a DMR file. Equivalent subroutines were identified between RZASA and this FLN0 bin. The address names in RZASA were transferred to the FLN0 (EQE3) DIR equivalent addresses.

And yes...Jsa got me going on it like this and I am still extra new but it seems to be a very efficient way of doing it. I am mainly going back and forth to the software manual to try and learn exactly what each subroutine is doing and why. I am after making definition files, but I also really want to learn more about how it all works and what it is exactly doing. I really would love to see a newer PCM disassembly as well. Like a 2016 up car. All the software solutions I am seeing are pretty expensive though. I really just want to see if I can fully grasp it before I invest in expensive software that I have no idea how to use yet.

[decipha]

its pretty useless to disassemble anything newer without anything already broken out and provided. It would take about 10-15 years to actually get a complete disassembly broken out doing it the way we have to do it.

eec-v on its own takes about 4 years to break out a single full disassembly

[BOOSTEDEVERYTHING]

Ok, so I know we have covered this in the past, but I have a question about argument sizes. Here is a section of the OMAE2 disassembled code for reference, or example of what I am asking about....

Code: Select all

063af: ef,1f,99           call  0fcd1            Sub451 (
063b2: 76                       #arg 1              76,
063b3: 09                       #arg 2              9 );
063b4: ef,1a,99           call  0fcd1            Sub451 (
063b7: 78                       #arg 1              78,
063b8: 09                       #arg 2              9 );
063b9: b3,ec,c6,2a        ldb   R2a,[Rec+c6]     TEMP3L = [11746];
063bd: 9b,ff,31,11,2a     cmpb  R2a,[Rfe+1131]   
063c2: d1,0b              jleu  063cf            if (TEMP3L > [19479])  {
063c4: 36,42,08           jnb   B6,R42,063cf     if (B6_TMP8L = 1)  {
063c7: 71,bf,42           an2b  R42,bf           B6_TMP8L = 0;
063ca: ef,74,96           call  0fa41            Sub249 (
063cd: 76                       #arg 1              76,
063ce: 09                       #arg 2              9 ); } }
063cf: b3,ec,c7,2a        ldb   R2a,[Rec+c7]     TEMP3L = [11747];
063d3: 9b,ff,32,11,2a     cmpb  R2a,[Rfe+1132]   
063d8: d1,0b              jleu  063e5            if (TEMP3L > [1947a])  {
063da: 35,42,08           jnb   B5,R42,063e5     if (B5_TMP8L = 1)  {
063dd: 71,df,42           an2b  R42,df           B5_TMP8L = 0;
063e0: ef,5e,96           call  0fa41            Sub249 (
063e3: 78                       #arg 1              78,
063e4: 09                       #arg 2              9 ); } }

So, in the above I believe the argument sizes are wrong and need to be word sized, instead of byte sized. Do I need to define each arg in the dir file that I find that SAD has found the incorrect size for? There are a ton of these args in this code and I want to make sure I have to do an entry for each one of them or can I just define a range of code for sad to find the byte sized args to be word sized args?
If you need me to post the dir file and bin file for this I will, with Decipha's permission of course. He provided me with a good start to a DIR file for OMAE2. I am using SAD V 4.012 for this one.

Side note: I started to do the OMAE2 code because I was loosing a bit of traction in the READ0 code and was hoping I could find more in common between the 3 different code examples than I was finding between the 2. I hope anyways.....LOL

[jsa]

Sub 0FCD1 "Sub0FCD1" :WN
Sub 0FA41 "Sub0FA41" :WN
That will define the subs with one word argument and apply names to the argument.

It will do every instance with a single command.
Individual arg command are useful where a sub has different numbers of args determined by some variable in the code.

4.012 cool. Yeah 5.08 is not ready for prime time on multibanks.

[BOOSTEDEVERYTHING]

Awesome, Thank you. So every time I come across a Subroutine with Args that are supposed to be one word instead of 2 byte I just use the above commands with the proper Sub names and address?

4.012 cool. Yeah 5.08 is not ready for prime time on multibanks

Yeah, I noticed that for sure. I did try it a bit and reported some stuff on the other thread but figured I would wait until the next release to try it out again. LOL. Being a newbie and all, I didn't want to overstep on bug reporting or anything like that.