Bin and code help - what's best way forward ?

This is where the BIN Hackers and definition junkies discuss the inner workings of the EEC code and hardware. General tuning questions do not go here. Only technical/hardware-specific/code questions and discussions belong here.

Moderators: cgrey8, EDS50, Jon 94GT, 2Shaker

Post Reply
tvrfan
Tuning Addict
Posts: 368
Joined: Sat May 14, 2011 11:41 pm
Location: New Zealand

Bin and code help - what's best way forward ?

Post by tvrfan » Wed Nov 11, 2015 2:28 pm

I thought I would start a new topic , and ask the questions about helping with disassembly. Suggestions welcome.

I want to set a reasonable point where you guys can learn and gain, but I don't want to give too much away for free, not because I'm mean,
but because normally it means it won't stick in your brain. So you should do SOME work to get the 'lightbulb' moment

DOES the "here is a snippet of code....what does it do" (i.e. what we have done so far) work for you, ***OR***
would it be better so say, for example "here is the entire function/1D lookup from bin xxxx, now you work out the steps" ?

THEN possibly go back to parameter extract parts, knowing it links in with lookups ?

DO you guys need more insights into binary maths, opcodes, timing issues, scaling ?

Happy to do those things if it helps, but we need to stay 'tight' and not wander off too far....

(Yeah I know, I'm probably as guilty as others of wandering off....)
TVR, Triumph (cars), kit cars, classics. Ex IT geek, development and databases.

https://github.com/tvrfan/EEC-IV-disassembler

User avatar
cgrey8
Administrator
Posts: 10565
Joined: Fri Jun 24, 2005 5:54 am
Location: Acworth, Ga (Metro Atlanta)
Contact:

Re: Bin and code help - what's best way forward ?

Post by cgrey8 » Wed Nov 11, 2015 2:42 pm

For me, I just completely forgot about what the opcodes and the terminology looked like. The reason I was so confused in the last post was because I COMPLETELY forgot that you could reference a register with an offset. So with the other post and the ad2w instruction, I thought 0xF0 was being added to the value held in R34 then the result put in R32. But after it was explained that 0xF0 was an offset, I had immediate deja vu of when I once knew that. I had forgotten that the length of arguments changed with short and long offsets...or I never knew that to start with.

As to the answer to your question, I honestly don't know.
...Always Somethin'

89 Ranger Supercab, 331 w/GT40p heads, ported Explorer lower, Crane Powermax 2020 cam, 1.6RRs, FMS Explorer (GT40p) headers, Slot Style MAF, aftermarket T5 'Z-Spec', 8.8" rear w/3.27s, Powertrax Locker, Innovate LC-1, GUFB, Moates QuarterHorse tuned using BE&EA

Member V8-Ranger.com

jsa
Tuning Addict
Posts: 519
Joined: Sat Nov 23, 2013 7:28 pm
Location: 'straya

Re: Bin and code help - what's best way forward ?

Post by jsa » Sat Nov 14, 2015 2:25 am

tvrfan wrote: I want to set a reasonable point where you guys can learn and gain, but I don't want to give too much away for free, not because I'm mean,
but because normally it means it won't stick in your brain. So you should do SOME work to get the 'lightbulb' moment
Yes I agree easy answers are not retained as well as brain testers.
DOES the "here is a snippet of code....what does it do" (i.e. what we have done so far) work for you,
Writing stuff works for me. Also gives a reference to return to.

would it be better so say, for example "here is the entire function/1D lookup from bin xxxx, now you work out the steps" ?
In time, but the nuances of how opcodes and operands play out needs to be understood.
I'm thinking I understand, subject to critique of my latest post of MPaton's example.
THEN possibly go back to parameter extract parts, knowing it links in with lookups ?
Sure.
DO you guys need more insights into binary maths, opcodes, timing issues, scaling ?
I feel comfortable with binary math and opcodes.

Timing issues, I know nothing of.

I guess scaling is a binary shift right deal ?
Happy to do those things if it helps, but we need to stay 'tight' and not wander off too far....

(Yeah I know, I'm probably as guilty as others of wandering off....)
The wandering has helped fill the knowledge gaps, allowing progress instead of confusion.

Thank you for offering to take us forward. Lead us where you please.
Cheers

John

95 Escort RS Cosworth - GHAJ0 / ANTI on a COSY box code
Moates QH & BE
ForDiag

Post Reply

Who is online

Users browsing this forum: No registered users and 9 guests