Skip to content
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

Supported ISAs? #1508

Open
billy-1-brown opened this issue Mar 12, 2025 · 2 comments
Open

Supported ISAs? #1508

billy-1-brown opened this issue Mar 12, 2025 · 2 comments
Labels
EMBA question Further information is requested

Comments

@billy-1-brown
Copy link

Which ISAs (ARM, x86, etc.) are currently supported by Emba?

Copy link

Thank you for contributing an issue!

Welcome to the EMBA firmware analysis community!

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.

@m-1-k-3 m-1-k-3 added question Further information is requested EMBA labels Mar 12, 2025
@m-1-k-3
Copy link
Member

m-1-k-3 commented Mar 12, 2025

Hi @billy-1-brown

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

if [[ "${lBIN_FILE}" == *"x86-64"* ]]; then

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.

Hope this helps

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
EMBA question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants