Windows Marine ECU SOFTWARE
Budget: $10,000 – $20,000 USD
I have a legacy Windows desktop program that should read from and write to a marine ECU, but at the moment it simply does not work. I need an engineer who can open it up in OllyDbg (my preferred tool, though you’re welcome to cross-check in IDA Pro or Ghidra) and patch whatever is preventing normal operation.
The core fixes revolve around:
• Reliable data read/write operations to the ECU
• Correct handling of the communication protocol in place
• Accurate checksum calculations so flashes are accepted
You’ll be digging into x86 assembly, Windows API calls, and any protection or obfuscation that might be hiding the problem logic. Once you understand the flow, modify the binary so the software functions as originally intended with current ECU firmware versions.
Deliverables I need at the end:
• Patched executable (or a clean, repeatable patch file)
• A concise technical note describing the offsets changed and why—enough for me to validate and maintain later
• A quick video or screenshot proof showing a successful read, write, and checksum verification on the ECU
Please include examples of similar reverse-engineering or desktop-application patching work you’ve completed, especially anything involving hardware interfaces or checksum routines. Looking forward to getting this tool back in action.
The core fixes revolve around:
• Reliable data read/write operations to the ECU
• Correct handling of the communication protocol in place
• Accurate checksum calculations so flashes are accepted
You’ll be digging into x86 assembly, Windows API calls, and any protection or obfuscation that might be hiding the problem logic. Once you understand the flow, modify the binary so the software functions as originally intended with current ECU firmware versions.
Deliverables I need at the end:
• Patched executable (or a clean, repeatable patch file)
• A concise technical note describing the offsets changed and why—enough for me to validate and maintain later
• A quick video or screenshot proof showing a successful read, write, and checksum verification on the ECU
Please include examples of similar reverse-engineering or desktop-application patching work you’ve completed, especially anything involving hardware interfaces or checksum routines. Looking forward to getting this tool back in action.