In short: ECU flashing over UDS is coming soon. Ecuhawk already has UDS sessions, tester present and diagnostic requests over ISO-TP. Flashing will add the full programming sequence as one test step, with progress, checks and a report.
The flash sequence
- Switch to the programming session (0x10 02).
- Security access with your seed and key (0x27), using your own key DLL or Python function.
- Erase memory with a routine (0x31).
- Download and transfer the data (0x34, 0x36, 0x37) from HEX, S-record or binary files.
- Check the result, such as a checksum routine.
- Reset the ECU (0x11) and read back the software version.
Where it will be used
- Development: flash a new build before a test run.
- End of line: flash and verify every unit, with a report per serial number.
- Service: update ECUs in the field with operator mode.
Questions
Can Ecuhawk flash ECUs?
Flashing over UDS on CAN is planned. Ecuhawk already supports UDS sessions and diagnostic requests, which flashing builds on.
Which file formats will flashing support?
Intel HEX, Motorola S-record and binary files are planned.
Will I need to share my security keys?
No. Seed and key calculation will use your own key DLL or Python function on your machine.