[tvrfan]

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....)

[cgrey8]

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.

[jsa]

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.