Locking down a ECUFLash map?
![Post Post](./styles/maxthon/imageset/icon_post_target.gif)
Are there any hooks in ECUFlash or accompanying open source tools that allows this? I believe there are a two primary ways to do this (but please correct me if I'm off):
- Lock down the OBD-II authentication protocol via changing the passkey in the challenge/passkey sequence when you connect a unit
- Lock down the MATs on the SH flashing area themselves?
I remember reading Renesas doc on this and that you can specify some kind of FKEY that you need to enter to reflash a MAT. I originally thought this is what say EcuTek does but I'm not so sure.
Any ideas? I think the first one can be done through OBD-II spec and a library that can send commands (I suppose you could extract some of the logging code from various projects as a basis). But I want confirmation from someone who has done it that it works and there is a recoverable process (even if that means having Cobb install, then de-installing, then tuning agian).
The second one I think would require changes to ECUFlash's kernel.
Any takers?
- Lock down the OBD-II authentication protocol via changing the passkey in the challenge/passkey sequence when you connect a unit
- Lock down the MATs on the SH flashing area themselves?
I remember reading Renesas doc on this and that you can specify some kind of FKEY that you need to enter to reflash a MAT. I originally thought this is what say EcuTek does but I'm not so sure.
Any ideas? I think the first one can be done through OBD-II spec and a library that can send commands (I suppose you could extract some of the logging code from various projects as a basis). But I want confirmation from someone who has done it that it works and there is a recoverable process (even if that means having Cobb install, then de-installing, then tuning agian).
The second one I think would require changes to ECUFlash's kernel.
Any takers?