Stuck on "Checking if kernel is already running..." while trying to read

[MayaVivs]

I was trying to read the stock rom off of my 2011 USDM wrx hatchback using a generic j2534 cable. No matter what I did, I could not get past the Checking if kernel is already running...

The log :

[2025-01-27 18:12:01.519] Read memory with flashmethod 'sub_ecu_denso_sh7058_can' and kernel 'C:/Users/mayaj/AppData/Local/FastECU/0.1.0-beta.4/kernels/ssmk_can_tp_sh7058.bin'
[2025-01-27 18:12:06.885] Connecting to Subaru 07+ 32-bit CAN bootloader, please wait...
[2025-01-27 18:12:06.885] Checking if kernel is already running...

I let it sit for a couple minutes but nothing changed, and based off of other users posts, this step should take less than a second. I do not have this issue with logging though, I can connect to the ECU using "f3" and log usable data and see the log data and my ECU ID.

[MayaVivs]

I figured it out! Digging through some code I figured out that the windows executable is actually looking for the kernels in the root directory of the project, instead of C:/Users/mayaj/AppData/Local/FastECU/0.1.0-beta.4/kernels/ssmk_can_tp_sh7058.bin. I cloned the repo and copied the contents of the "kernels" file to "C:\Program Files\FastECU" the same location as the executable. I opened an issue on github.

[MiikaS]

Tested today on freshly installed Windows 11 and had not this kind of issue so couldn't reproduce this... Also in Linux, Win7 32/64bit and Win10 virtual machines and Win10 on laptop works as they should.

App should look kernels from "C:\Users\<user\AppData\Local\FastECU\<version>\kernels", not where the app itself is.

Could you run it from cmdline with debug option (or make shortcut to do so) with command "FastECU.exe debug"? Then copy all text from cmdline window to file and attach it here.