EFIDynoTuning Forum

Andy,

If i may, can I request to have the auto populated subroutine labels be the actual address and not numbered?

for example

subr_84EFD is much much much easier for me to follow than subr_12345.

If I'm understanding right, the later V4 versions do this already. Try the ones in 'development' subdirectory.
Yeah, looking back, it was a bad idea.

For everyone -

SAD V5 list is to try to -

Add proper math calcs instead of just divide. (allow stuff like = 4/(x*16) for example)
Allow for sub fields within bytes/words/longs (e.g. timer structures do this for bit flags)
Allow for word tables
Allow data items to be printed more than once (in some bins pointer/offsets are used more than once, into different queues/pointers)
Fix problem with FM20M06 etc. (where Ford break their own hardware rules....) requires a new bank detect trick.
Improve comment options.
Improve detection of data and code.
do argument sizes better (by checking more code)
[I'm sure I've forgotten some stuff...]

I've changed a lot of code already.

Hopefully I'll release a 5.0.1 alpha soon

Happy to take other suggestions.

V4.012 does name by address.
Not sure if 4.07.16 from here got updated to the b revision I put forward.
https://github.com/tvrfan/EEC-IV-disass ... evelopment

V4.07.16b also
https://github.com/jsa2340/EEC-IV-disas ... evelopment

Both have different limitations, so may be useful in combination.

I downloaded it and it seems to work good. I've been using 3.08 as its the only one that could handle some of the odd cals. READ0 was one as well as TAUF0 or one of the AQxxx IIRC. I'll put the new one through the paces but it seems to be working fine.

As always thanks for what you do.

Decipha,

You obviously have huge experience on actual tuning, from the work you do here. When you mention 'odd' tunes, I would like to get as much as possible working for all bins, (eventually..), so if you do get a weird one then I will be interested in it. SAD is an ongoing project, as we are still learning some of the finer details. Even the Ford manuals don't tell everything. Plus some of the special chips.. e.g. DUCE etc. are still a bit vague.
As an retired IT guy I can see why Ford did some of the code the way they did, but it doesn't make it any easier to disassemble.

examples - SAD not working for -
The RZASA series, because they had a second RAM area high up in Bank 1. (sorted now)
FM20M06 breaks Fords own hardware rules (no interrupt vectors in Bank 1). Not done yet.

I'm sure you will know of others...

I use 4.07.16, works flawless for me for single bank bins.

16b adds support for word size tables found in later multi banks.

Word tables by user command work (added for jsa request) , but auto detect isn't done yet.

yeah its just 2 bank and 4 bank that gives issues if ever. single bank has never been a problem

I'll let you know as I come across them. Right now I have no development time.

Yes, single banks are MUCH easier to sort out, multibanks are trickier, the order in the bin file cannot always be worked out, sometimes SAD has to guess. There are definitely still bugs lurking in both the multibank and single bank decodes.

Decipha, no worries, just flagging my interest. I've got a lot to sort out for SAD version 5 ...