Analysis

Decompile this ESP32-S3 flash image and provide source

Analysis:
Parsed partition table, extracted app image, converted to ELF, ran decompilation and static analysis until tool error interrupted final pass
Conclusion:
Identified firmware as MeshCore-based MeshOS Repeater (ESP-IDF v4.4.7) for Heltec V3; decompilation produced ~9192 functions but final full-source extraction/re

Tools: skill, skill:ghidra-analysis, run_sandbox, inspect_binary, todo_write, write_file, edit_file, dump_data

Run it yourself
MeshOS-Repeater-HeltecV3-v1.6.3-merged.bin

Decompile this fully binary and provide the source

Dr.Binary
run_sandbox
inspect_binary

This is an ESP32 flash image (ESP32-S3 — Heltec V3), not an ELF. Let me set up a plan and unpack it first.

todo_write
run_sandbox
run_sandbox
run_sandbox

Partition table parse looks misaligned — let me dump it raw.

run_sandbox

Now the layout is clear. Let me parse it correctly and extract the images.

run_sandbox
run_sandbox

The merged file contains bootloader + partition table + app0 (app1/spiffs/coredump are empty in this image). Let me examine the app0 header/app descriptor.

run_sandbox

App descriptor recovered. Now let me extract the app cleanly and survey its strings to identify what "MeshOS" actually is.

run_sandbox
run_sandbox

This is a MeshCore-based "MeshOS Repeater" (meshcore.co.uk), Arduino-ESP32 (ESP-IDF v4.4.7) build for the Heltec V3 (ESP32-S3). Now let me prepare for decompilation — first check the Ghidra setup and Xtensa support in the sandbox.

run_sandbox

Ghidra runs inside the dump_data tool environment. Let me first convert the ESP image into a proper ELF with correct load addresses so decompilation maps cleanly.

write_file
run_sandbox
edit_file
run_sandbox

ELF is recognized as Xtensa. Now regenerate the bootloader artifacts and start the full Ghidra decompilation of the app.

run_sandbox
dump_data
Error calling tool 'dump_data': (404)
Reason: Not Found
HTTP response headers: <CIMultiDictProxy('Audit-Id': '3835f675-70b0-43b0-a527-958125003513', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Kubernetes-Pf-Flowschema-Uid': 'd97e6236-ab34-4ae9-b97f-49df98485bfc', 'X-Kubernetes-Pf-Prioritylevel-Uid': '9ee593ac-d0ab-475d-a6b6-7ed18cce4d58', 'Date': 'Thu, 12 Nov 2026 23:11:55 GMT', 'Content-Length': '248')>
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods \"ghidra-da3cc3c1a771bfca-56f5fcfb7b1cb0dc\" not found","reason":"NotFound","details":{"name":"ghidra-da3cc3c1a771bfca-56f5fcfb7b1cb0dc","kind":"pods"},"code":404}

The Ghidra backend pod is unavailable — let me retry, and meanwhile check local disassembly options for Xtensa.

run_sandbox
dump_data

Ghidra decompilation completed. Let me survey the results.

run_sandbox

Full decompilation produced 9192 functions (171 MB). Let me orient with the table of contents and suspicious-function triage.

run_sandbox
run_sandbox

This turn could not finish: harness turn emitted an error

Send your message again to retry.