The comments are intended. But you can't find any strings after ldr/add/sub is pointer to pointer ... my script doesn't look up that, yet. But should easy to hack. I haven't thought about this.Any more ideas for the next script version?
ff9367dc: e24f10b0 sub r1, pc, #176 ; ff936734: (e92d4010)ff9367e0: e28f0f41 add r0, pc, #260 ; ff9368ec: (776f6853) *"ShowSDStatus"ff9367e4: ebfcccf3 bl ff869bb8 <_binary_dump_bin_start+0x59bb8>ff9367e8: e24f10ac sub r1, pc, #172 ; ff936744: (eafbade2)ff9367ec: e28f0f42 add r0, pc, #264 ; ff9368fc: (53746547) *"GetSDDetect"ff9367f0: ebfcccf0 bl ff869bb8 <_binary_dump_bin_start+0x59bb8>ff9367f4: e24f10b4 sub r1, pc, #180 ; ff936748: (eafbade3)ff9367f8: e28f0f42 add r0, pc, #264 ; ff936908: (53746547) *"GetSDProtect"
qemu: fatal: Trying to execute code outside RAM or ROM at 0xe59ff014
e92d4010 ... eafbade2
It seems that 0xEnnnnnnn is opcodes, not addresses...Quotee92d4010 ... eafbade2
Use IDA .
How about 0xffaa4c98 in the sd1100 dump ... whats that?
ROM:FFAA4C98 sub_FFAA4C98 ; CODE XREF: sub_FF813C40+24pROM:FFAA4C98 ; sub_FF821C58+40p ...ROM:FFAA4C98 SUBS R2, R2, #0x20ROM:FFAA4C9C STMFD SP!, {R4,LR}ROM:FFAA4CA0 BCC loc_FFAA4CBCROM:FFAA4CA4ROM:FFAA4CA4 loc_FFAA4CA4 ; CODE XREF: sub_FFAA4C98+20jROM:FFAA4CA4 LDMCSIA R1!, {R3,R4,R12,LR}ROM:FFAA4CA8 STMCSIA R0!, {R3,R4,R12,LR}ROM:FFAA4CAC LDMCSIA R1!, {R3,R4,R12,LR}ROM:FFAA4CB0 STMCSIA R0!, {R3,R4,R12,LR}ROM:FFAA4CB4 SUBCSS R2, R2, #0x20ROM:FFAA4CB8 BCS loc_FFAA4CA4ROM:FFAA4CBCROM:FFAA4CBC loc_FFAA4CBC ; CODE XREF: sub_FFAA4C98+8jROM:FFAA4CBC MOVS R12, R2,LSL#28ROM:FFAA4CC0 LDMCSIA R1!, {R3,R4,R12,LR}ROM:FFAA4CC4 STMCSIA R0!, {R3,R4,R12,LR}ROM:FFAA4CC8 LDMMIIA R1!, {R3,R4}ROM:FFAA4CCC STMMIIA R0!, {R3,R4}ROM:FFAA4CD0 MOVS R12, R2,LSL#30ROM:FFAA4CD4 LDMFD SP!, {R4,LR}ROM:FFAA4CD8 LDRCS R3, [R1],#4ROM:FFAA4CDC STRCS R3, [R0],#4ROM:FFAA4CE0 MOVEQ PC, LRROM:FFAA4CE4ROM:FFAA4CE4 loc_FFAA4CE4 ; CODE XREF: sub_FFAA4B30+4jROM:FFAA4CE4 ; sub_FFAA4B30+40j ...ROM:FFAA4CE4 MOVS R2, R2,LSL#31ROM:FFAA4CE8 LDRMIB R2, [R1],#1ROM:FFAA4CEC LDRCSB R3, [R1],#1ROM:FFAA4CF0 LDRCSB R12, [R1],#1ROM:FFAA4CF4 STRMIB R2, [R0],#1ROM:FFAA4CF8 STRCSB R3, [R0],#1ROM:FFAA4CFC STRCSB R12, [R0],#1ROM:FFAA4D00 MOV PC, LRROM:FFAA4D00 ; End of function sub_FFAA4C98
Quote from: chr on 07 / August / 2008, 21:17:08How about 0xffaa4c98 in the sd1100 dump ... whats that? Code: [Select]ROM:FFAA4C98 sub_FFAA4C98 ; CODE XREF: sub_FF813C40+24p...
ROM:FFAA4C98 sub_FFAA4C98 ; CODE XREF: sub_FF813C40+24p...
1. BUG im my disassemble.pl: unaligned strings are not handled ...ffb114a1 GetCurrentAvValueffb114b3 Bat_Saveffb114bc StopBDrive
Quote from: chr on 07 / August / 2008, 18:27:581. BUG im my disassemble.pl: unaligned strings are not handled ...ffb114a1 GetCurrentAvValueffb114b3 Bat_Saveffb114bc StopBDriveAre they ever referenced to with those addresses? I.e. could the strings file be preprocessed to align them?ffb114bc is aligned, isn't it?
Started by Daniel Moore Feature Requests
Started by Hardware_Hacker General Discussion and Assistance
Started by pigeonhill Creative Uses of CHDK