FastECU is a very good project thankyou. How can I download my ECU ROM please? I tried all of the vehicle options but I think that my JDM ROM (D2PH410Q) should be SH7058 CAN. I am using Tactrix Openport 2.0 on Windows and can download the ROM via the ECUFlash software. Please see the image below for a recent attempt to capture the ECU ROM.
How can I download ECU ROM please
Moderator: Global Moderator
Re: How can I download ECU ROM please
It look like it is using wrong kernel, should be ssmk_CAN_SH7058.bin. What version of software are you using and what protocol?
Re: How can I download ECU ROM please
Thank you for the reply. When I use ssmk_CAN_SH7058 I receive the message below. I am using the precomplied exe on Github.
[attach id=28]Screenshot 2023-07-02 at 3.58.26 PM.png[/attach]
[attach id=28]Screenshot 2023-07-02 at 3.58.26 PM.png[/attach]
Re: How can I download ECU ROM please
As on the first line, it says what kernel to use, but somehow it is missing prefix 'kernels/' in name, that you can see is present on your first posts log, so it tries to lookup kernel from root folder and cannot find and open it. Could be missing statement in protocols file or else, need to check.
For a quick fix, copy kernel to application root folder and test again, I will check files.
Could you please post selected protocol which you used in both cases?
For a quick fix, copy kernel to application root folder and test again, I will check files.
Could you please post selected protocol which you used in both cases?
Re: How can I download ECU ROM please
I copied the kernel files to the application root directory and now the connection continues further, please see the log file below which shows page data request failed. I am using car model 'All SH705x Denso CAN models' with protocol family 'sub_sh7058_denso_can'.
[2023-07-02 17:43:17.502] Read memory with flashmethod 'sh7058_denso_can' and kernel 'ssmk_CAN_SH7058.bin'
[2023-07-02 17:43:22.024] Connecting to Subaru 02+ 32-bit Denso CAN bootloader, please wait...
[2023-07-02 17:43:22.040] Checking if kernel is already running...
[2023-07-02 17:43:22.294] Initializing bootloader
[2023-07-02 17:43:22.512] Connecting to bootloader
[2023-07-02 17:43:22.715] Connected to bootloader, start kernel upload
[2023-07-02 17:43:22.715] Initializing Subaru 02+ 32-bit Denso CAN kernel upload, please wait...
[2023-07-02 17:43:22.715] Starting kernel upload, please wait...
[2023-07-02 17:43:22.919] Uploading kernel, please wait...
[2023-07-02 17:43:31.656] Kernel uploaded, starting kernel...
[2023-07-02 17:43:31.656] Requesting kernel ID
[2023-07-02 17:43:31.969] Kernel ID: ��0
[2023-07-02 17:43:31.969] Reading ROM from Subaru 02+ 32-bit Denso using CAN
[2023-07-02 17:43:31.969] Start reading ROM, please wait...
[2023-07-02 17:43:32.016] Kernel read addr: 0x00000000 length: 0x00000400, 1 B/s 8681 s remaining
[2023-07-02 17:43:32.047] Page data request failed!
[2023-07-02 17:43:32.047] Received msg: 73 0e 23 e1 72 c0 22 e1
[2023-07-02 17:43:17.502] Read memory with flashmethod 'sh7058_denso_can' and kernel 'ssmk_CAN_SH7058.bin'
[2023-07-02 17:43:22.024] Connecting to Subaru 02+ 32-bit Denso CAN bootloader, please wait...
[2023-07-02 17:43:22.040] Checking if kernel is already running...
[2023-07-02 17:43:22.294] Initializing bootloader
[2023-07-02 17:43:22.512] Connecting to bootloader
[2023-07-02 17:43:22.715] Connected to bootloader, start kernel upload
[2023-07-02 17:43:22.715] Initializing Subaru 02+ 32-bit Denso CAN kernel upload, please wait...
[2023-07-02 17:43:22.715] Starting kernel upload, please wait...
[2023-07-02 17:43:22.919] Uploading kernel, please wait...
[2023-07-02 17:43:31.656] Kernel uploaded, starting kernel...
[2023-07-02 17:43:31.656] Requesting kernel ID
[2023-07-02 17:43:31.969] Kernel ID: ��0
[2023-07-02 17:43:31.969] Reading ROM from Subaru 02+ 32-bit Denso using CAN
[2023-07-02 17:43:31.969] Start reading ROM, please wait...
[2023-07-02 17:43:32.016] Kernel read addr: 0x00000000 length: 0x00000400, 1 B/s 8681 s remaining
[2023-07-02 17:43:32.047] Page data request failed!
[2023-07-02 17:43:32.047] Received msg: 73 0e 23 e1 72 c0 22 e1
Re: How can I download ECU ROM please
Hi again!
Have you made any more testing?
Today I had time to look up this problem. What I was doing was:
- Running Windows 7 32-bit on VirtualBox top of Linux Mint
- Downloaded precompiled Windows version from github
- Copied kernel "ssmk_CAN_SH7058.bin" to root folder
- Using "All SH705x Denso CAN models" with both SH7058 and SH7058S
- ECU is AZ1G202G (2008 STi)
Attached picture from result, powered off ECU after starting ROM download. Note that there should be "Kernel ID" shown as in picture after succesful kernel upload.
Have you made any more testing?
Today I had time to look up this problem. What I was doing was:
- Running Windows 7 32-bit on VirtualBox top of Linux Mint
- Downloaded precompiled Windows version from github
- Copied kernel "ssmk_CAN_SH7058.bin" to root folder
- Using "All SH705x Denso CAN models" with both SH7058 and SH7058S
- ECU is AZ1G202G (2008 STi)
Attached picture from result, powered off ECU after starting ROM download. Note that there should be "Kernel ID" shown as in picture after succesful kernel upload.
Re: How can I download ECU ROM please
Hi I am doing the same steps that you are, but still receive the error shown in post #4. Is it strange that the Kernel Id displayed on my log has special characters?MiikaS wrote: Hi again!
Have you made any more testing?
Today I had time to look up this problem. What I was doing was:
- Running Windows 7 32-bit on VirtualBox top of Linux Mint
- Downloaded precompiled Windows version from github
- Copied kernel "ssmk_CAN_SH7058.bin" to root folder
- Using "All SH705x Denso CAN models" with both SH7058 and SH7058S
- ECU is AZ1G202G (2008 STi)
Attached picture from result, powered off ECU after starting ROM download. Note that there should be "Kernel ID" shown as in picture after succesful kernel upload.
Re: How can I download ECU ROM please
Yes it is strange indeed. And as it shows, it has no trouble of starting and connecting to bootloader nor uploading kernel, it is strange that it failed to communicate with kernel...