Ghidra Prep
Skip the setup. Start reversing.
Upload an EDC17 flash read and get a ready Ghidra project back. Open it with File → Import and go straight to the logic.
Accepts: .bin full read · Bosch EDC17CP44 (more ECUs coming) · Free
Upload the flash read on the start page; the file page shows the button when the tool takes your ECU.
Why a plain import isn't enough
Load an EDC17 dump into Ghidra, run auto-analysis, and a big part of the code is simply not there. Routines that are only reached through tables never get found. Calls end in empty stubs. Calibration data shows up as fake instructions. You spend your first hours repairing the project — and you're still not sure you set it up right.
What you get
- About a quarter more code than Ghidra's own analysis finds (measured on EDC17CP44).
- Functions in place — including the ones only reached through tables.
- Calls that lead somewhere: no empty stubs in the decompiler.
- 97 % of map groups linked to the code that reads them — see which routine uses which calibration.
- Maps left as data: no fake code on top of your calibrations.
- The same preparation we use in our own reverse-engineering work.
How it works
- Upload a full flash read (.bin).
- We prepare it on our server.
- Download the .gzf and open it in Ghidra: File → Import.
Who it's for
- Calibrators ready to move from maps to logic. You calibrate maps. Engineers change ECU logic.
- Ghidra students who want to practise on their own files.
- Tuners who need answers from the firmware fast: switches, limiters, fault logic.
Requirements: Ghidra 12.0.1 or newer · Tuners Guild TriCore language files (included with your result)