You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are glad you are here and appreciate your contribution. Please keep in mind our contributing guidelines here and here.
Also, please check existing open issues and consider to open a discussion in the dedicated discussion area.
Additionally, we have collected a lot of details around EMBA, the installation and the usage of EMBA in our Wiki.
If you like EMBA you have the chance to support us by becoming a Sponsor or buying some beer here.
To show your love for EMBA with nice shirts or other merch you can check our Spreadshop.
This is an automatic message. Allow for time for the EMBA community to be able to read the issue and comment on it.
EMBA only partly depends on dedicated architectures. So, for the most modules the target architecture does not matter. On other modules we support only some architectures. For example the module S13 needs a supported architecture and checks for it here
Nevertheless, as this module depends on objdump and readelf it supports every architecture (with some little tweaks) which is supported by objdump. If you are missing your architecture it should be quite easy to implement it.
Some further examples:
Module S15 uses r2 and supports every architecture that r2 supports.
Module s16 is the same just with Ghidra
Module s115 needs a static compiled qemu and supports currently some architectures but if needed it can be tweaked easily.
The L modules are depending on a pre-compiled kernel. I think we have support for some MIPS, ARM and x86 architectures. You can check the wiki for further details.
Which ISAs (ARM, x86, etc.) are currently supported by Emba?
The text was updated successfully, but these errors were encountered: