Loading…
Xzonn
Translation changed |
|
None
String updated in the repository |
|
Loading…
Xzonn
Translation changed |
|
None
String updated in the repository |
|
RAM:02033818 PUSH {R3-R9,LR}
RAM:0203381C LDR R2, =dword_20A9AB0
RAM:02033820 MOV R6, R0
RAM:02033824 LDR R1, [R2]
RAM:02033828 LDR R0, =aFiletblLoadSta ; "--- filetbl_load start <%d> ---\n"
RAM:0203382C ADD R1, R1, #0x3F ; '?'
RAM:02033830 BIC R3, R1, #0x3F
RAM:02033834 MOV R1, R6
RAM:02033838 STR R3, [R2]
RAM:0203383C BL dbg_print20228DC
```
These definitely aren’t file offsets (the differences between them are too small```arm– for example, a file between offsets 0xB2E and 0xB32 would only be four bytes
long), but it’s possible they might _map_ to file offsets somehow since they’re
steadily increasing. That would suggest that maybe there is one of these values
per file – so just how many are there? The values are two bytes long and spaced
two bytes apart for a total of four bytes per iteration. The sequence begins at
0x20 and ends at 0x950. Therefore:
RAM:02033818 PUSH {R3-R9,LR}
RAM:0203381C LDR R2, =dword_20A9AB0
RAM:02033820 MOV R6, R0
RAM:02033824 LDR R1, [R2]
RAM:02033828 LDR R0, =aFiletblLoadSta ; "--- filetbl_load start <%d> ---\n"
RAM:0203382C ADD R1, R1, #0x3F ; '?'
RAM:02033830 BIC R3, R1, #0x3F
RAM:02033834 MOV R1, R6
RAM:02033838 STR R3, [R2]
RAM:0203383C BL dbg_print20228DC
```