Investigate why a firmware build no longer fits in Flash or SRAM.
Compare two firmware builds to see which symbols grew or shrank.
Generate a shareable memory usage report for a hardware project.
Browse and search every symbol in a compiled program by size and location.
| dhanush777x/elfyzer | alchaincyf/doubao-search-mcp | algorave-dave/fail-safe | |
|---|---|---|---|
| Stars | 22 | 22 | 22 |
| Language | JavaScript | JavaScript | JavaScript |
| Setup difficulty | — | easy | easy |
| Complexity | — | 2/5 | 1/5 |
| Audience | developer | developer | general |
Figures from each repo's GitHub metadata at analysis time.
Elfyzer is a tool for engineers who build firmware for small devices, such as embedded systems and Edge AI hardware, where memory is tight and every byte matters. When a device runs out of flash storage or working memory, developers normally have to dig through huge, hard to read files produced by the compiler's linker to figure out what is taking up space. Elfyzer replaces that manual digging with an interactive dashboard that shows the same information visually and lets you search and filter it. The tool reads a compiled program file, called an ELF binary, and pulls out everything it can find about how memory is organized: which parts of memory hold code, which hold data, which named pieces of the program, called symbols, live where, and which source file each symbol came from. All of this comes directly from information already stored inside the file itself, so nothing is guessed or estimated. Once loaded, elfyzer opens a local web dashboard with several views. You can see an overview of address space usage as visual charts, browse a searchable table of every symbol with its size and location, look at sections split into writable, read only, and executable groups, and drill down by source file or by compiled object file. A report feature lets you define named memory regions, such as Flash or SRAM, and generate a shareable report showing how much of each region is used and which symbols take the most space, exportable as Markdown or CSV. A diff feature compares two versions of the same firmware side by side and highlights symbols that were added, removed, or changed in size, which is useful for tracking whether a build has grown too large. The README notes elfyzer is meant to work alongside familiar command line tools rather than replace them. To use it, you install it with pip, then run a single command to launch the dashboard, either empty for manual upload or pointed directly at a firmware file. It is written in Python for the backend with a JavaScript and HTML dashboard for the frontend.
A local dashboard that turns compiled firmware files into visual charts of memory usage, so embedded developers can see what is taking up space.
Mainly JavaScript. The stack also includes Python, JavaScript, FastAPI.
Mainly developer.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.