Search found 419 matches
- Tue Dec 10, 2019 3:36 pm
- Forum: EECGeeks
- Topic: SAD disassembler progress
- Replies: 24
- Views: 3011
Re: SAD disassembler progress
So reverse scan is different to stepping back through the code? Yeah in my head anyway. I originally kept a 'pile' of previous opcodes for conditional jumps, and stepped back through them, but now I've changed the code so that it can simply feed in ANY (valid) opcode start address and get it decode...
- Tue Dec 10, 2019 3:18 pm
- Forum: EECGeeks
- Topic: SAD disassembler progress
- Replies: 24
- Views: 3011
Re: SAD disassembler progress
OK, sorry about further delay, I ran into a tricky bug... Anyway, I've now got SAD v4 to work correctly for variable arguments, and it also is able to size and decode those arguments. (decode is where the argument has a value like 0xd040 which equates to address [0xfa] + 40 ). I've found FOUR versio...
- Wed Oct 30, 2019 10:53 pm
- Forum: EECGeeks
- Topic: SAD disassembler progress
- Replies: 24
- Views: 3011
Re: SAD disassembler progress
Ah Yes, a good reminder.
I couldn't get that to work either !!
In the end I added a special extra emulate pass/block, flagged/created from the push, which executes before the 'final' return (this is where the args are)
so that gets more args if required.
and it seems to work !!
I couldn't get that to work either !!
In the end I added a special extra emulate pass/block, flagged/created from the push, which executes before the 'final' return (this is where the args are)
so that gets more args if required.
and it seems to work !!
- Wed Oct 30, 2019 4:54 pm
- Forum: EECGeeks
- Topic: SAD disassembler progress
- Replies: 24
- Views: 3011
Re: SAD disassembler progress
More - Problem with loops was for tabs and funcs (2D and 1D lookups). SAD did originally rescan those blocks to get the parameters (address and size) out (from the call tree), but that caused loops when trying to link it with emulate (complicated by the fact that the function lookup code has JUMPS i...
- Wed Oct 30, 2019 1:45 pm
- Forum: EECGeeks
- Topic: SAD disassembler progress
- Replies: 24
- Views: 3011
Re: SAD disassembler progress
the code now has 2 distinct 'phases'. It scans the binary as a 'tree' (i.e. jumps and calls create a new 'branch' as a block to be scanned), but keeps a fake stack of 'callers' up to date. and if it finds a POP or LDX [STACK+n] command, it flags that scan branch as an argument getter, and then flags...
- Tue Oct 29, 2019 1:48 pm
- Forum: EECGeeks
- Topic: SAD disassembler progress
- Replies: 24
- Views: 3011
New SAD version soon
Update after being far too long getting next version ready, here's my announcement Where I am up to - I have FINALLY got a method which seems to work for all my 'test binaries' collection, including variable argument decodes. The variable arg analysis proved HUGELY harder than I expected, and I agai...
- Sat Oct 19, 2019 4:02 am
- Forum: Hardware Discussions
- Topic: I/O count of modern EECs
- Replies: 6
- Views: 488
Re: I/O count of modern EECs
Ah right - sorry. My 'standard' stuff' was the HEGOs and emission stuff, base sensors, basically what's on all engines. I don't know if VVT sensor replaces the 'standard' cam sensor or not, I think probably not as it's a 'cyl 1' marker Yes ?? I really DO mean Lotus. The Evora uses the 2GR-FE engine ...
- Fri Oct 18, 2019 7:33 pm
- Forum: EECGeeks
- Topic: Why auto disassembly is tough
- Replies: 310
- Views: 71764
Re: Why auto disassembly is tough
Right - Yep, some complex addressing there indeed ............
OK. I never expected more than one offset (or special attribute etc.) per argument, so it was coded that way.
Hmmm..... I need to see if I can work out what it's doing.
have you cracked it ?? Any help appreciated !
Andy.
OK. I never expected more than one offset (or special attribute etc.) per argument, so it was coded that way.
Hmmm..... I need to see if I can work out what it's doing.
have you cracked it ?? Any help appreciated !
Andy.
- Fri Oct 18, 2019 2:50 pm
- Forum: EECGeeks
- Topic: Why auto disassembly is tough
- Replies: 310
- Views: 71764
Re: Why auto disassembly is tough
No.
It seems a bit weird to me, in fact. Where is the code ? I'll have a look.
Andy.
It seems a bit weird to me, in fact. Where is the code ? I'll have a look.
Andy.
- Fri Oct 18, 2019 2:13 pm
- Forum: Hardware Discussions
- Topic: I/O count of modern EECs
- Replies: 6
- Views: 488
Re: I/O count of modern EECs
Just spotted this.......... NB. 1. whether or not the I/O is direct or via a bus, the EEC still has to receive/generate it, so all those events still have to happen in the code. 2. CAN bus as I understand was its own acronym Cheap, Adequate, Nasty, and was really because it's now cheaper to have a c...
- Mon Aug 19, 2019 3:23 pm
- Forum: Lounge
- Topic: Spamming with Private VPNs
- Replies: 14
- Views: 928
Re: Spamming with Private VPNs
It's a catch-22, like much of the internet. me - I don't have a fixed IP on my account, and don't use a VPN for this site. As default, I use Firefox with NoScript to switch off most/all of the JavaScript to stop ads,popups,trackers, which it does well, but it does stop some things working on many si...
- Tue Jul 02, 2019 5:43 pm
- Forum: EECGeeks
- Topic: Proposed GUFB patch tweak
- Replies: 33
- Views: 1928
Re: Attn: CGrey8 - proposed GUFB patch tweak
On reading this thread, an idea occurs to me... If you have an engine that can climb up the revs really fast (as you stated), then could it also be that the 'rolling average' calculations need to change? have you already thought of that ? Why - On the A9L bins, (GUFB) the rolling average calcs actua...
- Sun Jun 30, 2019 7:23 pm
- Forum: EECGeeks
- Topic: Meaning of disassembly underscore.
- Replies: 4
- Views: 375
Re: Meaning of disassembly underscore.
From me, the SAD author... I had to come up with some kind of default name, so I chose Bx_Ry, meaning "Bit x of Register y". In a typical binary there are many,many 'flag' states (i.e. ON or OFF), used for all sorts of things, and the CPU has the opcodes JB JNB (jump if bit set/not set) to support f...
- Mon Jun 24, 2019 3:28 pm
- Forum: EECGeeks
- Topic: Added useful docs into openEEC in github
- Replies: 12
- Views: 1083
Re: Added useful docs into openEEC in github
In that case I hereby claim ALL THE KUDOS for writing good clean 'C' code, which isn't easy !!! (Joking !! - - for some weird reason, smilies don't seem to work for me in this BB. Linux/Firefox issue ? Hmmm....No, smilies not disabled.) Seriously, I'm truly glad it DID compile and run, as it does he...
- Sat Jun 22, 2019 10:04 pm
- Forum: EECGeeks
- Topic: Added useful docs into openEEC in github
- Replies: 12
- Views: 1083
Re: Added useful docs into openEEC in github
Another just in case - please don't think I'm 'knocking' anything there - I just want to help stop any misunderstandings and confusion. It's already hard enough to look at low level machine code, especially some of the multibank tricks. (ooh - an unintended pun there...) I'm lucky as I've done this ...
- Sat Jun 22, 2019 4:36 pm
- Forum: EECGeeks
- Topic: Added useful docs into openEEC in github
- Replies: 12
- Views: 1083
Re: Added useful docs into openEEC in github
Just a note here - I had a look too, some of those docs are now superceded, and the bank swop one (written by me) is WRONG at the detail level (but the analysis of how the code works is still correct). This was before I saw the Ford Handbook, which gives the true answer. For Techies/Advanced/IT geek...
- Wed Jun 12, 2019 2:49 pm
- Forum: EECGeeks
- Topic: Why auto disassembly is tough
- Replies: 310
- Views: 71764
Re: Why auto disassembly is tough
Guys, Just for completeness, it's worth a quick review of the PSW on 8065 CPUs and bank operation. Whilst the 8065 PSW lower byte contains the various status flags for conditional jumps (zero, negative, etc), the upper byte contains current program bank (which I take to mean 'code bank'), the curren...
- Tue Jun 11, 2019 7:07 pm
- Forum: EECGeeks
- Topic: Why auto disassembly is tough
- Replies: 310
- Views: 71764
Re: Why auto disassembly is tough
John, Just discovered a bug in the way code blocks are queued for scanning, which may also explain some of the undecoded sections in CARD. Effectively this bug means some block scan combos are lost entirely. Found it when working on the multibank argument emulate/decode. So I'll fix that first and r...
- Thu Jun 06, 2019 2:24 pm
- Forum: EECGeeks
- Topic: Why auto disassembly is tough
- Replies: 310
- Views: 71764
Re: Why auto disassembly is tough
Thanks John, Methods 1) already thought about possible endless loop, so emulation has an 'opcodes executed' maximum, currently at 1000 (may change this) 2) Interesting idea. I admit I had not thought that way at all. I already have a 'called by' chain, which is necessary for subroutines (and argumen...
- Wed Jun 05, 2019 10:18 pm
- Forum: EECGeeks
- Topic: Why auto disassembly is tough
- Replies: 310
- Views: 71764
Re: Why auto disassembly is tough
<code snipped> Load a word, push it later and return is a common theme for overlooked code. Maybe scan any for code any time a load push return sequence is encountered. Yes, A9L does that, and I've been stuck on how to handle it properly. The problem is that a register is loaded with an address in ...
- Wed Jun 05, 2019 4:16 pm
- Forum: EECGeeks
- Topic: Why auto disassembly is tough
- Replies: 310
- Views: 71764
Re: Why auto disassembly is tough
Thanks. I have mentioned previously how all the blocks of code are overlooked and how fixing one detail snowballed a pile of code. I will try to find it. The start of many structues are found. Good that it finds the start points at least !! I have been playing with the idea of some kind of 'data pa...
- Wed Jun 05, 2019 3:23 pm
- Forum: EECGeeks
- Topic: Why auto disassembly is tough
- Replies: 310
- Views: 71764
Re: Why auto disassembly is tough
John, I found the bug with the 4456 and 4459 args. I think that's all working right now. Here is a new listing in case it's any use to you. Code should be right (I hope!), but data isn't ! I see there are still some blocks which look like code but are not decoded, along with some obvious all-data st...
- Wed Jun 05, 2019 12:12 am
- Forum: EECGeeks
- Topic: Why auto disassembly is tough
- Replies: 310
- Views: 71764
Re: Why auto disassembly is tough
Thanks John, that's fantastic - will check out your issues spotted. Possibly some new code trick I didn't see. Often, one example of a faulty args decode, will apply to all those subr calls, so improvement can be quite large from one fix. I hope. I see that some of the 4459 calls show 6 args correct...
- Tue Jun 04, 2019 5:54 pm
- Forum: EECGeeks
- Topic: Why auto disassembly is tough
- Replies: 310
- Views: 71764
PROTOTYPE SAD with variable arguments
Jsa - John, VARIABLE ARGS !!!!! I think I may finally have cracked a method to get the arguments working, with a part-scan, part emulate approach, which is a 'merge and modify' of a couple of previous attempts. I have attached a CARD listing done with NO COMMANDS by current development SAD, so it's ...
- Thu May 30, 2019 8:47 pm
- Forum: EECGeeks
- Topic: Why auto disassembly is tough
- Replies: 310
- Views: 71764
Re: Why auto disassembly is tough
Taking a break from m0m2 since it's useable, so I'm focused on some SD tunes that I've cloned. One in particular is 8SD, which doesn't seem to follow conventional wisdom with Rbases. Certain subroutines have their own offsets defined which makes for a hell of a time disassembling them. Does SAD hav...
- Thu May 23, 2019 3:15 pm
- Forum: EECGeeks
- Topic: Why auto disassembly is tough
- Replies: 310
- Views: 71764
Re: Why auto disassembly is tough
'Console present' Yes - quite a few bins have that style of check where 0xd00 (or similar addresses) appear to be a console status flag, and there are various other 'set' addresses around for plug in or special function chips/peripherals. But like the cal console (0xd000 or d006 or d009 or e000 or ....
- Thu May 23, 2019 3:03 pm
- Forum: EECGeeks
- Topic: Why auto disassembly is tough
- Replies: 310
- Views: 71764
Re: Why auto disassembly is tough
No, I designed the 'signature' routine after the unix regular expression (= RE), up to a point, but even that isn't flexible enough. If you've never used this, the RE is embedded in a wide range of unix/linux edit and search applications, and although a more complex RE looks like gobbledegook, the s...
- Thu May 23, 2019 12:31 am
- Forum: EECGeeks
- Topic: Why auto disassembly is tough
- Replies: 310
- Views: 71764
Re: Why auto disassembly is tough
While testing, I ran into a problem with vects (not same as reported by jsa, but still....) and I discovered yet more CRAZY stuff. first - I changed vector list detection in 3.08 as it wasn't working with later binaries - so I changed the 'signature' options for a 'detect' type (when SAD arrives at ...
- Thu May 16, 2019 2:52 pm
- Forum: EECGeeks
- Topic: Why auto disassembly is tough
- Replies: 310
- Views: 71764
Re: Why auto disassembly is tough
The post was about a cold turkey 1st run of SAD against a bin, yeah understood 2nd step of creating a dir with args set would improve 3.08 results for the changes you describe. Pondering Bank8, have any been sighted that; * Don't start with FF FA * Don't have Checksum at 0x200A Is more required tha...
- Wed May 15, 2019 3:56 pm
- Forum: EECGeeks
- Topic: Why auto disassembly is tough
- Replies: 310
- Views: 71764
Re: Why auto disassembly is tough
Ahhh. OK, could be a screw up in the command parser then....motorhead1991 wrote: ↑Wed May 15, 2019 3:53 pm
It was this command:
It complained of a fill address out of bounds despite removing the "fill" commands from the dir file.Code: Select all
bank 0 0 dfff
Thanks.