-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ihex:// does not work properly on ARMv7 LE? #15211
Comments
I guess that loading the right SVD for this IC and getting Perhaps related issues: #1843, https://github.com/radareorg/radare2/issues/8467 |
you have to define anal.from and anal.to, otherwise its trying to analyze 64GB of code, which obv takes some time, so please, if r2 takes more than 5 mminutes to analyze something stop it because there's something wrong for sure. You can check this with |
Still very few functions for this :/ |
Giving it a try to r2svd:
|
try installing this module :P |
I know, but it should work out of the |
After installing and flaggin all the things:
The
|
he flags loaded with r2svd dont specify code or functions at all, it just maps the devices.. well just create flags to point at them.totally unrelated to aa , etc.. just use afr with anal.hasnext
… On 25 Feb 2020, at 12:59, Roman Valls Guimera ***@***.***> wrote:
After installing and flaggin all the things:
[0x00000000]> !r2svd STMicro STM32F103xx.svd
CC Flexible static memory controller @ 0xa0000000
f FSMC 512 0xa0000000
f FSMC.BCR2 512 0xa0000001
f FSMC.BTR2 512 0xa0000001
f FSMC.BCR3 512 0xa0000002
f FSMC.BTR3 512 0xa0000002
f FSMC.BCR4 512 0xa0000003
(...)
The aae command does not pick up a single function :_/
[0x00000000]> s 0x08008000
[0x08008000]> aae
[0x08008000]> afl
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#15211?email_source=notifications&email_token=AAG75FQU3MSZ6V47C2EXQZLREUBZZA5CNFSM4I55Y22KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEM3WEBY#issuecomment-590832135>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAG75FTHSB5TWR3KOTAMQC3REUBZZANCNFSM4I55Y22A>.
|
|
cant repro, mho you have a broken r2 installation
… On 3 Mar 2020, at 12:16, Roman Valls Guimera ***@***.***> wrote:
[0x00000000]> e anal.hasnext=true
[0x00000000]> afr
[0x00000000]> afl
[0x00000000]> aaa
[x] Analyze all flags starting with sym. and entry0 (aa)
[x] Analyze function calls (aac)
[x] find and analyze function preludes (aap)
[x] Analyze len bytes of instructions for references (aar)
[x] Check for objc references
[x] Check for vtables
[x] Finding xrefs in noncode section with anal.in=io.maps
[x] Analyze value pointers (aav)
[x] Value from 0x08008000 to 0x0801ab89 (aav)
[x] 0x08008000-0x0801ab89 in 0x8008000-0x801ab89 (aav)
[x] Emulate code to find computed references (aae)
[x] Type matching analysis for all functions (aaft)
[x] Propagate noreturn information
[x] Use -AA or aaaa to perform additional experimental analysis.
[0x00000000]> afl | wc -l
572
[0x00000000]> Vvjjj
0x0801a036 114 fcn.0801a036
0x0801a0a8 90 fcn.0801a0a8
0x0801a102 18 fcn.0801a102
...
Segmentation fault: 11
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#15211?email_source=notifications&email_token=AAG75FW6PWHJNU7UXSIHFY3RFTRI3A5CNFSM4I55Y22KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENTDEMQ#issuecomment-593900082>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAG75FVJZ7THPTMBJQKE5HLRFTRI3ANCNFSM4I55Y22A>.
|
Kabooom!! |
Possibly related to #15093 ? |
And backtrace:
|
This whole issue had little to do about the casual segfault I found along the way, but ok... :) |
In fact, can you reopen it? I'm getting 572 funcs now... vs the 396 that Ghidra finds ... but Vv looks very broken now:
|
Work environment
Expected behavior
Sweet, valid 32-bit ARMv7 code and plenty of functions appearing in my lovely r2 console.
Actual behavior
Steps to reproduce the behavior
Additional information
Entry point seems to be
0x0801c6a4
.And my
.radare2rc
looks like:The text was updated successfully, but these errors were encountered: