2010 Subaru Outback 2.0D EURO5

[gnif]

Hi,

I have a 2010 Subaru Outback 2.0D EURO5 as released in Australia, it runs the firmware JE5F231A on a Denso ECU powered by the SH7059. It seems this model has been overlooked as the only option that is even close is the Forester EURO5 diesel, which is configured to use K-Line.

The 2010 outback however seems to only use iso15765 at 500kbit. Altering the configuration to use iso15765 results in good communication with the vehicle, but there doesn't seem to be a viable kernel for this ecu. Once it's been uploaded to RAM, FastECU reports an error, and the dash indicator lights start flashing like a Christmas tree (a sign that the ECU has hung).

Is there a solution for this specific vehicle?
Could it be that my cheap Mini VCI J2534 cable doesn't support K-Line?

I have tried both the `ssmk_can_tp_sh7059d_euro5.bin` and `ssmk_can_sh7059d_euro5.bin` kernels with the same results.

[SergArb]

Mini VCI J2534 is not good choice for flashing. It have very small CAN buffer. Try to use other J2534 device first.

[gnif]

Thanks, I have ordered a Openport 2.0 clone to try (real ones are no longer available) as I already suspected this device is rather basic.

[MiikaS]

ssmk_can_sh7059d_euro5.bin is for used with sub_ecu_denso_sh7059_diesel_densocan protocol
ssmk_can_tp_sh7059d_euro5.bin is for used with sub_ecu_denso_sh7059_can_diesel protocol
These kernels differs the addresses they are loaded and also CAN setup so can't be mixed.

What version of FastECU do you use? If beta.4, you can test beta.5 from here:
https://drive.google.com/file/d/1ublgG9 ... drive_link

There's lots of differences between these two, CAN kernel rewrites etc.

Also, it could be possible that it also want to disable comms from other modules like newer Hitachi's, as I have only tested it in bench, not in car.

[MiikaS]

Also what comes to K-Line, it might work for logging but with reading and writing you have to use iso15765 as with K-Line you can't get into diagnostic (programming) mode.

[gnif]

Thanks. Yes I will give beta5 a try.

I have done more research and testing and have confirmed that the k-line is not used at all on this car. To confirm I used a DSO and can see zero return traffic from the ECU for any commands on the k-line. Unless I change the config to use iso for the logging, it won't even connect.

[gnif]

Here are the results with Beta 5. Note I am still using the Mini VCI adapter.
What is also strange is the VIN reported is blank.

Edit: This is also in stdout

Code: Select all

"[2026-01-23 10:37:38.845] (DD) Data bytes sent: 0x6528"
"[2026-01-23 10:37:38.861] (II) Kernel uploaded, starting..."
"[2026-01-23 10:37:38.876] (DD) Sent: 00 00 07 e0 37 "
"[2026-01-23 10:37:38.876] (DD) Battery: 12.000 V"
"[2026-01-23 10:37:38.986] (DD) Response: 00 00 07 e8 7f 37 22 "
"[2026-01-23 10:37:39.017] (EE) Wrong response from ECU: Unknown error code"

[MiikaS]

Code: Select all

"[2026-01-23 10:37:38.986] (DD) Response: 00 00 07 e8 7f 37 22 "

Somehow it can't start kernel. I need to check that there is nothing changed or missed during updates.

And some ECUs I have seen that VIN request does not return VIN, don't know why is that.

[gnif]

After switching to a Openport 2.0 clone the kernel now uploads properly and I am able to download the firmware.

Please be aware though that you have the EURO5 diesel listed has having K-Line support. I have confirmed without a doubt that K-Line support is non-existent on this car and does not work for logging.

[SergArb]

@gnif if you want, I can upload a patched MiniVCI firmware with extended buffer for testing.

[MiikaS]

After switching to a Openport 2.0 clone the kernel now uploads properly and I am able to download the firmware.

Please be aware though that you have the EURO5 diesel listed has having K-Line support. I have confirmed without a doubt that K-Line support is non-existent on this car and does not work for logging.

Nice!