[2024-12-19 05:16:45.634] Read memory with flashmethod 'sub_ecu_denso_sh7055_02' and kernel 'kernels/ssmk_kline_sh7055.bin'
[2024-12-19 05:16:48.370] Connecting to Subaru 02 32-bit K-Line bootloader, please wait...
[2024-12-19 05:16:49.112] Sent to bootloader: 4d ff b4
[2024-12-19 05:16:49.316] Response from bootloader:
[2024-12-19 05:16:49.318] Bad response from bootloader
[2024-12-19 05:16:49.320] Cannot connect to bootloader, testing if kernel is alive
I tried sub_ecu_denso_sh7055_04 as well. I am using a Tactrix on Linux.
Now this ecu probably has been flashed before, is that an issue? How do I flash over whatever is in there? I have no idea what the previous owner did.
[2024-12-20 06:11:48.421] Read memory with flashmethod 'sub_ecu_denso_sh7055_04' and kernel 'kernels/ssmk_kline_sh7055.bin'
[2024-12-20 06:11:50.946] Connecting to Subaru 04 32-bit K-Line bootloader, please wait...
[2024-12-20 06:11:51.124] Checking if kernel is already running...
[2024-12-20 06:11:51.825] Kernel NOT running, requesting access
[2024-12-20 06:11:51.981] Initializing bootloader
[2024-12-20 06:11:51.982] SSM init
[2024-12-20 06:11:52.492] ECU ID = 3712485006
[2024-12-20 06:11:52.534] Start communication ok
[2024-12-20 06:11:52.588] Request timing parameters ok
[2024-12-20 06:11:52.649] Seed request ok
[2024-12-20 06:11:52.662] Sending seed key
[2024-12-20 06:11:52.745] Seed key ok
[2024-12-20 06:11:52.802] Start diagnostic session ok
[2024-12-20 06:11:52.816] Initializing Subaru 04 32-bit K-Line kernel upload, please wait...
[2024-12-20 06:11:52.819] Unable to open kernel file for reading
I talked to a tuner and he claimed it was stock and not locked. CVN is 433CAF44/2F5E6197, although I doubt I have anyone to compare this checksum against.
Last edited by scooobydu on Sat Dec 21, 2024 6:41 am, edited 1 time in total.
and it seemed to find it when it was in the same directory as the appimage.
I got a strange ecu image out of it, doesn't seem to match the stock rom "tomsbaja.hex" on romraider at all with lower boost values and really strange zeroed tables (zeroed idle c? negative base timing values?). I'd attach it but it seems the forum doesn't allow bin or hex extensions.
Good you got it working! I need to check dirs again to make sure that it looks for right place as it was working when I test it some time ago. I'll take a look at the ROM tomorrow.
scooobydu wrote: Sat Jan 11, 2025 10:27 pm
I got a strange ecu image out of it, doesn't seem to match the stock rom "tomsbaja.hex" on romraider at all with lower boost values and really strange zeroed tables (zeroed idle c? negative base timing values?). I'd attach it but it seems the forum doesn't allow bin or hex extensions.
Looked at the ROM and what I see, looks normal. Base advance values are many times negative on high load/low rpm area. That corner is an area where it would never be, so basicly it doesn't matter what the values are but it looks nicer that way Idle Target C table shows normal idle values for me. All other tables also looks quite normal.
Can you get kernel from development branch, there was a problem that those were changed to older versions for some unknown reason. Kernels from development branch should work.
MiikaS wrote: Sun Apr 06, 2025 8:47 am
Can you get kernel from development branch, there was a problem that those were changed to older versions for some unknown reason. Kernels from development branch should work.
MiikaS wrote: Sun Apr 06, 2025 8:47 am
Can you get kernel from development branch, there was a problem that those were changed to older versions for some unknown reason. Kernels from development branch should work.
MiikaS wrote: Sun Apr 06, 2025 8:47 am
Can you get kernel from development branch, there was a problem that those were changed to older versions for some unknown reason. Kernels from development branch should work.
. I now get a different error:
Idle Target C table shows normal idle values for me. All other tables also looks quite normal.