Code analysing

I would like to learn all about codetypes, memory ranges, codeparts, bits, values, breaktpoints and so on. I have seen that there many codes with different parts, like here:
Teleporter -PAL- [Bully@Wiiplaza]
C23BAB14 0000000B
3D408065 614AB89A
A14A0000 3D608170
2C0A100C 4082001C
81990000 918B1500
81990004 918B1504
81990008 918B1508
2C0A200C 4082001C
818B1500 91990000
818B1504 91990004
818B1508 91990008
EC4007F2 00000000
*Press C+Z+D-PAD_DOWN to save position*
*Press C+Z+D-PAD_UP to teleport*
Why 81, it is the adress? Which is the memory range?
Know anyone tutorials? I would like to learn ALL about ASM and so on...

I explained this in the other thread but I will repeat my explanation here.

This code is a C2 Codetype

C23BAB14 0000000B
This entire code is replacing the original ASM instruction at address 803BAB14 with the next 11 lines in the code which are all ASM instructions. B = 11

You can use PyiiASMH to see these ASM instructions which are:
lis r10,-32667
ori r10,r10,47258
lhz r10,0(r10)
lis r11,-32400
cmpwi r10,4108
bne- 0x001C
lwz r12,0(r25)
stw r12,5376(r11)
lwz r12,4(r25)
stw r12,5380(r11)
lwz r12,8(r25)
stw r12,5384(r11)
cmpwi r10,8204
bne- 0x001C
lwz r12,5376(r11)
stw r12,0(r25)
lwz r12,5380(r11)
stw r12,4(r25)
lwz r12,5384(r11)
stw r12,8(r25)
fmuls f2,f0,f31

Each instruction represents 8 digits of the code.
For example, these two instruction are the 16 digits on the second line of the code.
lis r10,-32667 = 3D408065
ori r10,r10,47258 =614AB89A

The 81 "codetypes" you are seeing are the lwz instructions.



This code also gave me a question of my own. I am curious to which part of the ASM are making the button activators work. I'm guessing it has something to do with the cmpwi instructions. Maybe Bully will let me know.

Really complicated, especially for me, because my English is not so well...

Sincerely

Xylon wrote:Really complicated, especially for me, because my English is not so well...

Sincerely

Well that is the only language I know. I tried.

It´s useful to turn every ASM code into it´s "0x" syntax, also replacing branch offsets with labels to see things better.

Remember to keep a copy when your code is longer, like I did. The "source" (how I call that format) code can be recovered again, but it´s more convenient to keep it.

Code:

lis r10, 0x8065
ori r10,r10, 0xB89A
lhz r10,0(r10) #r10 now contains the value from the button activator address#

lis r11, 0x8170 #we load the first 16bit of a ramdom RAM location for the store#

cmpwi r10, 0x100C #compare if that button combo has been pressed#
bne- _END1 #if not, jump to the second compare#

lwz r12,0(r25)
stw r12,0x1500(r11)
lwz r12,4(r25)
stw r12,0x1504(r11)
lwz r12,8(r25)
stw r12,0x1508(r11) #this part loads your 3 coords and stores it to the RAM (save)#

_END1: #branch label#

cmpwi r10, 0x200C
bne- _END2

lwz r12,0x1500(r11)
stw r12,0(r25)
lwz r12,0x1504(r11)
stw r12,4(r25)
lwz r12,0x1508(r11)
stw r12,8(r25) #this part reads the stored coords and writes them back (teleport)#

_END2:

fmuls f2,f0,f31 #original instruction at this address#

You should see greatly what the code is doing now.

Note:
- It doesn´t matter how many blanks you insert into your ASM code
- The code can still be converted (!) even with the comments in it (yes, it will be equal to the code I made, even with all the optical changes)

I think I should start slowly...I just started to hack