Welcome to the North American Subaru Impreza Owners Club Friday November 22, 2019
Home Forums WikiNASIOC Products Store Modifications Upgrade Garage
NASIOC
Go Back   NASIOC > NASIOC Technical > Engine Management & Tuning

Welcome to NASIOC - The world's largest online community for Subaru enthusiasts!
Welcome to the NASIOC.com Subaru forum.

You are currently viewing our forum as a guest, which gives you limited access to view most discussions and access our other features. By joining our community, free of charge, you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is free, fast and simple, so please join our community today!

If you have any problems with the registration process or your account login, please contact us.







* As an Amazon Associate I earn from qualifying purchases. 
* Registered users of the site do not see these ads. 
Reply
 
Thread Tools Display Modes
Old 04-26-2018, 09:23 PM   #251
mikeyPSF
NASIOC Supporter
 
Member#: 236475
Join Date: Jan 2010
Chapter/Region: BAIC
Location: San Francisco
Vehicle:
2002 WRX
Black

Default

I didn't get a notification of a reply either. That's odd. I'll try to see if I can figure this out tomorrow for you. Yes, I do recall us swapping a support email last week.
* Registered users of the site do not see these ads.
mikeyPSF is offline   Reply With Quote
Sponsored Links
* Registered users of the site do not see these ads.
Old 04-27-2018, 10:31 AM   #252
TyranosaurusWRX
Scooby Specialist
 
Member#: 25731
Join Date: Oct 2002
Chapter/Region: MWSOC
Location: Ft Wayne, IN
Vehicle:
02 wrx(sold)/2005
Sti/ 93 Leg Wag

Default

Thanks!

I'm anxiously awaiting my DLP....
TyranosaurusWRX is offline   Reply With Quote
Old 04-30-2018, 08:03 PM   #253
TyranosaurusWRX
Scooby Specialist
 
Member#: 25731
Join Date: Oct 2002
Chapter/Region: MWSOC
Location: Ft Wayne, IN
Vehicle:
02 wrx(sold)/2005
Sti/ 93 Leg Wag

Default

My 05 ECU is unbricked (albeit not worth much atm) and my 04 is unCobbed, I'm super grateful! After 7 years this thread still provides.
TyranosaurusWRX is offline   Reply With Quote
Old 04-30-2018, 09:35 PM   #254
teds-rex
Scooby Specialist
 
Member#: 400886
Join Date: Sep 2014
Chapter/Region: NESIC
Location: outside Boston, MA
Vehicle:
2004 STi
PSM

Default

Quote:
Originally Posted by TyranosaurusWRX View Post
Actually that was my original ecu, I have an 05. There are about 6 different wires to move to make the 04 work per the pinouts. So to clarify, the 05 ecu is burnt, the 04 from the scrap yard appears to be locked.
Yeah but I don't think that the 04 is "locked"... The 04 didn't have an emobilizer and the 05 does, so not sure on compatibility.
teds-rex is offline   Reply With Quote
Old 04-30-2018, 10:23 PM   #255
TyranosaurusWRX
Scooby Specialist
 
Member#: 25731
Join Date: Oct 2002
Chapter/Region: MWSOC
Location: Ft Wayne, IN
Vehicle:
02 wrx(sold)/2005
Sti/ 93 Leg Wag

Default

Quote:
Originally Posted by teds-rex View Post
Yeah but I don't think that the 04 is "locked"... The 04 didn't have an emobilizer and the 05 does, so not sure on compatibility.
Yeah the 04 was locked. I couldn't even connect to it via ecuflash, it would reject it every time. I can ID it now and I flashed my speed density map. The car is running on the 04 as we speak. With the 04 not having the immobilizer it bypasses it in the newer models as long as you rewire the harness per the 2004 pinouts, which was 6 wires. You just cant go the other way, and use a 2005+ without the chipped key, key barrel, and immobilizer box to go with it.
TyranosaurusWRX is offline   Reply With Quote
Old 06-28-2018, 10:01 PM   #256
Scotty4
Scooby Newbie
 
Member#: 487723
Join Date: Jun 2018
Chapter/Region: NWIC
Location: Olympic Penninsula
Vehicle:
2004 STI
Blue

Default

Anyone still available to unbrick a 2004 STI ECU? I haven't got the time to build a kit.
Scotty4 is offline   Reply With Quote
Old 07-12-2018, 08:45 PM   #257
MadmanSean
Scooby Newbie
 
Member#: 488256
Join Date: Jul 2018
Location: Melbourne Australia
Default

Quote:
Originally Posted by Scotty4 View Post
Anyone still available to unbrick a 2004 STI ECU? I haven't got the time to build a kit.
Hi Scotty, this may or may not help you.

I'm able to do this, however i'm located in Australia. For anyone that might be interested and needs help with a bricked ECU please feel free to PM me

Here's a link to more Info: Subaru ECU Unbrick, Unlock, Recovery Service
http://forum.liberty.asn.au/viewtopic.php?f=56&t=35489
MadmanSean is offline   Reply With Quote
Old 07-12-2018, 10:14 PM   #258
teds-rex
Scooby Specialist
 
Member#: 400886
Join Date: Sep 2014
Chapter/Region: NESIC
Location: outside Boston, MA
Vehicle:
2004 STi
PSM

Default

Quote:
Originally Posted by Scotty4 View Post
Anyone still available to unbrick a 2004 STI ECU? I haven't got the time to build a kit.
Where are you located? No info in your profile
teds-rex is offline   Reply With Quote
Old 07-23-2018, 06:23 PM   #259
Noah
( ͡° ͜ʖ ͡°)
Moderator
 
Member#: 111510
Join Date: Apr 2006
Chapter/Region: MWSOC
Location: Chicago area
Vehicle:
04 WRX 16 Xtrek
19 XSR900

Default

Had an interesting one today. 2011 WRX. Tried using FDT and got the following:

Code:
Configuration:
'BOOT Mode' connection - using emulated interface
Opening port 'COM3' ...
Loading Comms DLL
Loaded Comms DLL
Initiating BOOT SCI sequence
Attempting 9600
Received immediate response from device: 0x80
Attempting 4800
Received immediate response from device: 0x80
Attempting 2400
Attempting 1200
Error No 15024: Boot failed
Error No 16132: Device does not support Protocol C
The board on this ECU is different from others I've done. I gave the ECUFlash SH boot mode recovery a shot but I got an error about
there are more memory areas in this CPU that will be erased than the ROM file you have has data for. write process aborted.

This is the 2nd ECU that I've had troubles reflashing. Has anyone seen a similar issue?


Noah is offline   Reply With Quote
Old 09-13-2018, 11:24 PM   #260
badfrogg
Scooby Newbie
 
Member#: 376447
Join Date: Dec 2013
Chapter/Region: South East
Location: Clearwater Florida
Vehicle:
2004 Legacy GT

Default

Trying to unlock a Cobb/ECUtec Flash on my 08 WRX. I bought the car with this already done and it is running very poorly. No shops around me will unlock it.
was wondering if I can use FT232R board. If so what pins on this board do i jumper? they are not quite the same names.

badfrogg is offline   Reply With Quote
Old 09-18-2018, 01:20 PM   #261
rozsko
Scooby Newbie
 
Member#: 442541
Join Date: Mar 2016
Default

First of all, thanks for all the information contained in this thread.
I already had to unbrick my ecu twice and I thought to share an updated schematic for UM232R as 232M is not available any more.
UM232R has a little more components and features built into it, so the circuit is more simple overall as there are less external components.
For me Ecuflash did not work, but Reneas FTD worked like charm.
Also, I did not want to mess with powering the ECU externally, so I did the whole process while the ECU was connected to the car.

rozsko is offline   Reply With Quote
Old 09-23-2018, 01:35 AM   #262
MichaelStansell
Scooby Newbie
 
Member#: 489489
Join Date: Aug 2018
Location: Tulsa, OK
Vehicle:
2010 Impreza 2.5i

Subaru Stars electrical malfunction

My Impreza 2.5i Premium will not crank. The engine temperature "dummy light" on the dash is alternately flashing blue and red. All the lights on the dash illuminate when the key is turned to the ON position. Also, my generic OBD II scanner, which used to connect without issue to the car no longer displays it's initial screen when connected to my OBD II port.

What does the alternating blue/red flashing coolant light on the dash indicate? I emailed SOA and they quoted the owner's manual back to me saying that there "may be an electrical malfunction." Hoping someone has some experience to provide a more concrete idea about what to check.

Yes, I can take it to a dealership for diagnosis if I must, but my experience with the local dealership has been poor in the past.
MichaelStansell is offline   Reply With Quote
Old 09-25-2018, 02:01 PM   #263
legacy_majdi
Scooby Newbie
 
Member#: 491919
Join Date: Sep 2018
Default

Quote:
Originally Posted by The board on this ECU is different from others I've done. I gave the ECUFlash SH boot mode recovery a shot but I got an error about
there are more memory areas in this CPU that will be erased than the ROM file you have has data for. write process aborted.

This is the 2nd ECU that I've had troubles reflashing. Has anyone seen a similar issue?

[IMG
https://i.imgur.com/5REUHYs.png[/IMG]
Any solution for these type of ecu? I got one and it wont work with SH Boot. Do you mind to share FDT software?
legacy_majdi is offline   Reply With Quote
Old 09-29-2018, 10:15 PM   #264
kasipong
Scooby Newbie
 
Member#: 492098
Join Date: Sep 2018
Default

Anybody have link Flash Development Toolkit for 7055?

Renesas can't download.


Thanks for help
kasipong is offline   Reply With Quote
Old 10-03-2018, 10:36 PM   #265
MadmanSean
Scooby Newbie
 
Member#: 488256
Join Date: Jul 2018
Location: Melbourne Australia
Default

Quote:
Originally Posted by legacy_majdi View Post
Any solution for these type of ecu? I got one and it wont work with SH Boot. Do you mind to share FDT software?
Edit: All the test points are there, you're doing something wrong. I've successfully flashed this type of ecu many times.

Check the file size of the rom you are trying to flash make sure it is 1MB file.

Last edited by MadmanSean; 10-03-2018 at 10:43 PM.
MadmanSean is offline   Reply With Quote
Old 10-21-2018, 07:47 PM   #266
legacy_majdi
Scooby Newbie
 
Member#: 491919
Join Date: Sep 2018
Default

Quote:
Originally Posted by MadmanSean View Post
Edit: All the test points are there, you're doing something wrong. I've successfully flashed this type of ecu many times.

Check the file size of the rom you are trying to flash make sure it is 1MB file.
Flasing is ok, but somehow it got flashed with wrong version file. Now it bricked. And cannot be un brick. Do you have facing these type ecu bricked?
legacy_majdi is offline   Reply With Quote
Old 08-16-2019, 02:21 PM   #267
surpip06
Scooby Newbie
 
Member#: 399917
Join Date: Aug 2014
Vehicle:
2013 STi
greay

Default MY06 help

Hello guys,
First off, thank you for all the info in this thread it has been very informative and helpful. I am trying to un brick my MY06 WRX and i think i have my board and connections done correctly but i think my .bin file might be wrong. i have tried programming both with ECUFlash and the Renesas FDT 4.09 below is the read-back i get from ECU Flash:

[11:46:20.303] J2534 API Version: 04.04
[11:46:20.303] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[11:46:20.303] Device Firmware Version: 1.16.4769
[11:46:20.303] Device Serial Number: TA3PWfF6
[11:46:24.942] sending bit rate sync bytes...
[11:46:26.836] no bit rate adjust response
[11:46:26.843] interface close
[11:46:43.452] FTDI Driver Version 2.12.28
[11:46:44.466] sending bit rate sync bytes...
[11:46:44.587] received bit rate adjust response
sending boot command
[11:46:45.113] got boot response
[11:46:45.255] 1 supported device(s):
[11:46:45.262] 0601 HD64F7058
[11:46:45.279] selecting device 0601
[11:46:45.534] 1 supported clock mode(s):
[11:46:45.541] 0
[11:46:45.553] selecting clock mode 0
[11:46:45.812] 2 supported clock type(s):
[11:46:45.819] 1 ratios for clock type 1
[11:46:45.827] x4
[11:46:45.835] 1 ratios for clock type 2
[11:46:45.842] x2
[11:46:45.982] 2 supported clock frequency range(s):
[11:46:45.990] 1 20000000-40000000
[11:46:45.998] 2 10000000-20000000
[11:46:46.134] 1 user boot MAT area(s):
[11:46:46.141] 1 00000000-00001fff
[11:46:46.284] 2 user MAT area(s):
[11:46:46.292] 1 00000000-0007ffff
[11:46:46.299] 2 00080000-000fffff
[11:46:46.440] programming unit is 128
[11:46:46.572] one MAT programming supported at 00000000
[11:46:46.585] setting baud rate to 62500
[11:46:46.850] there are more memory areas in this CPU that will be erased than the ROM file you have has data for. write process aborted.
[11:46:46.873] interface close

And this is the feedback from FDT 4.09:

OS: Windows 7 [Non-Admin]
FCF Settings Applied: SH/7058F, (C:\Program Files (x86)\Renesas\FDT4.09\kernels\ProtC\7058\Renesas\1 _0_00\)
FDT API initialised: version 4, 09, 02, 000
Clock Frequency (External) = 10.0000MHz, Clock Mode = 0, CKM = 4, and CKP = 2
Connecting to device 'SH/7058F' on 'COM3'
Configuration:
'BOOT Mode' connection - using emulated interface
Opening port 'COM3' ...
Loading Comms DLL
Loaded Comms DLL
Initiating BOOT SCI sequence
Attempting 9600
Received immediate response from device: 0xE6
Detected generic boot device
Sending inquiry for getting line size
Buffer size has been set to default (128 bytes)
Sending selection of device command
Selection of Device - Device selected, code 0601
Sending selection of clock mode
Sending selection of clock mode
Selection of Clock Mode - Clock selected, code 0
Changing baud rate to 57600 bps
Set baud rate value = 57600
Determining block usage
Connection complete
Warning - download 06WRX stock dada.bin file which exceeds the flash ROM size of SH/7058F device.
Processing file :"C:\Users\surpip06\Desktop\06WRX stock dada.bin"
Loading image file : 'C:\Users\surpip06\Desktop\06WRX stock dada.bin'
Operation on User Flash
Loaded the Write operation module
Writing image to device... [0x00000000 - 0x000010FF]
Writing image to device... [0x00001180 - 0x000020FF]
Writing image to device... [0x00002180 - 0x00096E7F]
Writing image to device... [0x000BD980 - 0x000BEEFF]
Writing image to device... [0x000BF180 - 0x000BF4FF]
Writing image to device... [0x000C0180 - 0x000C96FF]
Writing image to device... [0x000C9700 - 0x000D0AFF]
Writing image to device... [0x000DB980 - 0x000DC67F]
Writing image to device... [0x000DF980 - 0x000DF9FF]
Writing image to device... [0x000FFC80 - 0x000FFCFF]
Writing image to device... [0x000FFD00 - 0x000FFFFF]
Data programmed at the following positions:
0x00000000 - 0x000010FF Length : 0x00001100
0x00001180 - 0x000020FF Length : 0x00000F80
0x00002180 - 0x00096E7F Length : 0x00094D00
0x000BD980 - 0x000BEEFF Length : 0x00001580
0x000BF180 - 0x000BF4FF Length : 0x00000380
0x000C0180 - 0x000C96FF Length : 0x00009580
0x000C9700 - 0x000D0AFF Length : 0x00007400
0x000DB980 - 0x000DC67F Length : 0x00000D00
0x000DF980 - 0x000DF9FF Length : 0x00000080
0x000FFC80 - 0x000FFCFF Length : 0x00000080
0x000FFD00 - 0x000FFFFF Length : 0x00000300
680.25 K programmed in 141 seconds
Image written to device

Both say that my original file is too large. but this is the stock file i pulled from my car before my computer crashed during tuning. Dose anyone have a stock file for SH7058 the would be willing to send me? or any suggestions for me to try? I also tested the outputs coming out of my board i have 144Hz come out going to P407 have correct power and ground and have continuity between the TX/RX to the 232 chip. thanks for the help



https://imgur.com/V98dOaX

https://imgur.com/cnI5uzP

Last edited by surpip06; 08-16-2019 at 02:35 PM.
surpip06 is offline   Reply With Quote
Old 08-16-2019, 04:40 PM   #268
TyranosaurusWRX
Scooby Specialist
 
Member#: 25731
Join Date: Oct 2002
Chapter/Region: MWSOC
Location: Ft Wayne, IN
Vehicle:
02 wrx(sold)/2005
Sti/ 93 Leg Wag

Default

You should be able to pull the stock ROM from here under he US section:

http://www.scoobypedia.co.uk/index.p...patibilityList

I believe A8DH201X is the most recent version.
TyranosaurusWRX is offline   Reply With Quote
Old 08-17-2019, 12:58 PM   #269
surpip06
Scooby Newbie
 
Member#: 399917
Join Date: Aug 2014
Vehicle:
2013 STi
greay

Default

thanks for the response TWRX, so i downloaded that file and i got this message from ECUFlash i used the "w" version since i have an auto.

Quote:
[11:08:31.045] using metadata XML ID A8DH200W from file C:/TACTRIX/EcuFlash/rommetadata/subaru/Impreza WRX/A8DH200W.xml
which inherits XML ID 32BITBASE from file C:/TACTRIX/EcuFlash/rommetadata/subaru/Bases/32BITBASE.xml
[11:08:31.045] ---notes for 32BITBASE---
2014/06/20 [Tactrix] Tactrix definition auto cleaned|merged w/ RomRaiderGitHubAlphaMay2014.
---notes for A8DH200W---
2014/05/22 [Tactrix] Tactrix definition auto cleaned|merged w/ RomRaiderGitHubAlphaMay2014.
[11:08:34.246] FTDI Driver Version 2.12.28
[11:08:35.532] sending bit rate sync bytes...
[11:08:35.669] received bit rate adjust response
sending boot command
[11:08:36.200] got boot response
[11:08:36.346] 1 supported device(s):
[11:08:36.354] 0601 HD64F7058
[11:08:36.377] selecting device 0601
[11:08:36.632] 1 supported clock mode(s):
[11:08:36.640] 0
[11:08:36.654] selecting clock mode 0
[11:08:36.958] 2 supported clock type(s):
[11:08:36.966] 1 ratios for clock type 1
[11:08:36.974] x4
[11:08:36.982] 1 ratios for clock type 2
[11:08:36.994] x2
[11:08:37.143] 2 supported clock frequency range(s):
[11:08:37.154] 1 20000000-40000000
[11:08:37.162] 2 10000000-20000000
[11:08:37.302] 1 user boot MAT area(s):
[11:08:37.309] 1 00000000-00001fff
[11:08:37.460] 2 user MAT area(s):
[11:08:37.468] 1 00000000-0007ffff
[11:08:37.476] 2 00080000-000fffff
[11:08:37.618] programming unit is 128
[11:08:37.753] one MAT programming supported at 00000000
[11:08:37.767] setting baud rate to 62500
[11:08:38.033] there are more memory areas in this CPU that will be erased than the ROM file you have has data for. write process aborted.
[11:08:38.058] interface close
On FDT however, the warning went away and it went through the programming but it still wont work.

Quote:
OS: Windows 7 [Non-Admin]
FDT API initialised: version 4, 09, 02, 000
FCF Settings Applied: SH/7058F, (C:\Program Files (x86)\Renesas\FDT4.09\kernels\ProtC\7058\Renesas\1 _0_00\)
Opening file C:\Users\surpip06\Desktop\read image_stock.bin
File loaded: 0x00000000 -> 0x000FFFFF [User Flash]
File loaded: 0x00000000 -> 0x00001FFF [User Boot Flash]

Clock Frequency (External) = 10.0000MHz, Clock Mode = 0, CKM = 4, and CKP = 2
Connecting to device 'SH/7058F' on 'COM3'
Configuration:
'BOOT Mode' connection - using emulated interface
Opening port 'COM3' ...
Loading Comms DLL
Loaded Comms DLL
Initiating BOOT SCI sequence
Attempting 9600
Received immediate response from device: 0x12
Attempting 4800
Received immediate response from device: 0x01
Attempting 2400
Attempting 1200
Received immediate response from device: 0x42
Error No 15024: Boot failed


Clock Frequency (External) = 10.0000MHz, Clock Mode = 0, CKM = 4, and CKP = 2
Connecting to device 'SH/7058F' on 'COM3'
Configuration:
'BOOT Mode' connection - using emulated interface
Opening port 'COM3' ...
Loading Comms DLL
Loaded Comms DLL
Initiating BOOT SCI sequence
Attempting 9600
Received immediate response from device: 0xE6
Detected generic boot device
Sending inquiry for getting line size
Buffer size has been set to default (128 bytes)
Sending selection of device command
Selection of Device - Device selected, code 0601
Sending selection of clock mode
Sending selection of clock mode
Selection of Clock Mode - Clock selected, code 0
Changing baud rate to 57600 bps
Set baud rate value = 57600
Determining block usage
Connection complete

Processing file :"C:\Users\surpip06\Desktop\read image_stock.bin"
Loading image file : 'C:\Users\surpip06\Desktop\read image_stock.bin'
Operation on User Flash
Loaded the Write operation module
Writing image to device... [0x00000000 - 0x00000EFF]
Writing image to device... [0x00000F80 - 0x00001EFF]
Writing image to device... [0x00001F80 - 0x00096C7F]
Writing image to device... [0x000BD800 - 0x000BED7F]
Writing image to device... [0x000BF000 - 0x000BF2FF]
Writing image to device... [0x000C0000 - 0x000D097F]
Writing image to device... [0x000DB800 - 0x000DC47F]
Writing image to device... [0x000DF800 - 0x000DF87F]
Writing image to device... [0x000FFA80 - 0x000FFAFF]
Writing image to device... [0x000FFB80 - 0x000FFFFF]
Data programmed at the following positions:
0x00000000 - 0x00000EFF Length : 0x00000F00
0x00000F80 - 0x00001EFF Length : 0x00000F80
0x00001F80 - 0x00096C7F Length : 0x00094D00
0x000BD800 - 0x000BED7F Length : 0x00001580
0x000BF000 - 0x000BF2FF Length : 0x00000300
0x000C0000 - 0x000D097F Length : 0x00010980
0x000DB800 - 0x000DC47F Length : 0x00000C80
0x000DF800 - 0x000DF87F Length : 0x00000080
0x000FFA80 - 0x000FFAFF Length : 0x00000080
0x000FFB80 - 0x000FFFFF Length : 0x00000480
679.88 K programmed in 142 seconds
Image written to device

After i got the program in the ecu from FDT i started up ECUFlash and it will still not connect to the ecu. or accept a nother tune.

Quote:
[11:15:54.815] J2534 API Version: 04.04
[11:15:54.815] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[11:15:54.815] Device Firmware Version: 1.16.4769
[11:15:54.815] Device Serial Number: TA3PWfF6
[11:15:57.488] kernel get version
[11:15:57.708] interface close
[11:15:57.761] J2534 API Version: 04.04
[11:15:57.761] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[11:15:57.761] Device Firmware Version: 1.16.4769
[11:15:57.761] Device Serial Number: TA3PWfF6
[11:15:58.056] VIN read not supported
[11:15:58.172] interface close
[11:15:58.211] J2534 API Version: 04.04
[11:15:58.211] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[11:15:58.211] Device Firmware Version: 1.16.4769
[11:15:58.211] Device Serial Number: TA3PWfF6
[11:15:58.387] SSM2 init
[11:15:58.807] SSM2 init
[11:15:59.222] SSM2 init
[11:15:59.659] SSM2 init
[11:16:00.107] SSM2 init
[11:16:00.522] SSM2 init
[11:16:00.957] SSM2 init
[11:16:01.372] SSM2 init
[11:16:01.807] SSM2 init
[11:16:02.222] SSM2 init
[11:16:02.760] interface close
[11:16:02.772] interface close

this is what i get when i try to read the ROM via ECUFlash. any ideas?

Last edited by surpip06; 08-17-2019 at 01:23 PM.
surpip06 is offline   Reply With Quote
Old 08-23-2019, 01:29 AM   #270
surpip06
Scooby Newbie
 
Member#: 399917
Join Date: Aug 2014
Vehicle:
2013 STi
greay

Default

I figured out m problem with help from sick chips in AU, don't forget to pull your leads off the ecu before attempting to crank!! haha what a stupid thing to forget, but otherwise my adapter worked like a champ! Thanks to everyone who provided info to this thread so happy i was able to save my ecu!!
surpip06 is offline   Reply With Quote
Old 09-17-2019, 07:59 PM   #271
luizguccione
Scooby Newbie
 
Member#: 220786
Join Date: Aug 2009
Default 2005 USDM STI ECU Recovered

Hello.
Thank you very much for this thread.
I was great to be able to unbrick 2005 USDM STI ECU SH7058.
Fortunatelly I found all the components needed and just assembled the whole thing with the assistance of a Electronic Services Shop. I did all in the bench. Used an external 12v power supply.
I couldnt get it to work with Ecuflash (Latest Version).
So I tried Renesas and it was flawless.
Thank you again.
luizguccione is offline   Reply With Quote
Old 10-29-2019, 04:37 AM   #272
jhkoka
Scooby Newbie
 
Member#: 507631
Join Date: Oct 2019
Default

I succeeded to re-flash MY09 Impreza 2.5 using Renesas Flash Toolkit, disconnected all the wires from ecu pins. But when I start the car, it runs very poorly. It wobbles (like cylinders are missing ignitions), rich petrol smell, doing max 2600 rpm when gas pedal is pushed to the floor, engine light on, cruise control blinking, no power at all but super slowly drivable.
Tried both tuned and stock original ROM .bin file. Same result.

And what's also weird, is that I cannot use my geniuine Tactrix Openport 2.0 cable anymore, because whenever I try to flash something, it will brick the ecu again and I had to do the Renesas bootmode flash again.

I've done several flashes before, but one day when I flashed a scaled MAF map with Tactrix, then the flash process timed out half-way and car didn't start. Then tried to flash stock rom, but no connection with Openport anymore. That's why I had to deal with un-bricking in the first place.

ECU is: R4F70580S (but because Renesas Toolkit didn't have this exact chip in the list, I chose Generic Boot Device, although then it did identify my exact chip)


Anyway, any suggestions of what could have happened? Feels like something is horribly wrong (car runs poorly and Tactix can't be used anymore, although I can READ with Tactrix)
jhkoka is offline   Reply With Quote
Old 10-29-2019, 12:48 PM   #273
mikeyPSF
NASIOC Supporter
 
Member#: 236475
Join Date: Jan 2010
Chapter/Region: BAIC
Location: San Francisco
Vehicle:
2002 WRX
Black

Default

That's really odd. My first thought a couple sentences in that maybe you didn't have the stock ROM, but then I saw were you specified it was what you're using. I'm working from home this morning ahead of potential jury duty service so I don't have my instance of the Renesas software in front of me to check the settings, but in my notes I see I use SH/7055F for the 'device' setting when flashing a 7055. I've never actually used the Renesas tool on the 7058 but I would imagine it would be similar. Can you clarify what you used for a 'device' setting?

-Mike
Tactrix
mikeyPSF is offline   Reply With Quote
Old 10-30-2019, 04:16 AM   #274
jhkoka
Scooby Newbie
 
Member#: 507631
Join Date: Oct 2019
Default

I selected the very last option: "Generic BOOT Device". Then it identified my device R4F70580S and I was able to hit the Program Flash button.
FreeSSM shows those errors after flashing:


My only thought is that maybe I have accidentally touched some wrong pins on the ecu with voltage in my cables and killed some parts of the ecu.
jhkoka is offline   Reply With Quote
Old 10-30-2019, 03:44 PM   #275
mikeyPSF
NASIOC Supporter
 
Member#: 236475
Join Date: Jan 2010
Chapter/Region: BAIC
Location: San Francisco
Vehicle:
2002 WRX
Black

Default

That's odd. I don't know what else to add at the moment but if you do suspect the ECU is physically damaged, you can use a replacement ECU (same year/model/market is best) and swap the immobilizer EEPROM from your original ECU. It's the one circled in red in the attached photo. More info can be found here:

http://romraider.com/forum/viewtopic...46&f=7&t=11379

From Sasha_A80 “Just resolder 93C56 or 93C86 8pin chip from old ecu to a new one if both ecu's are Denso and use the same chip.”
Attached Images
File Type: jpg SubaruImmobilizerChip.JPG (90.2 KB, 2 views)
mikeyPSF is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
How to Make an STI Look Like a Sleeper? FostersAFB General Community 92 10-12-2017 10:24 PM
How to remove an ecu Quackyboy Newbies & FAQs 9 04-22-2010 10:26 AM
How bad is it on the tranny to treat an auto like a manual? thrillho Transmission (AT/MT) & Driveline 8 06-07-2004 09:23 AM
Want to learn how to tune an ECU...and actually do it on a real dyno? 2000vfr800 Engine Management & Tuning 9 03-19-2003 03:20 PM
How long for an ECU to reset w/ no flash? Keith99RS New England Impreza Club Forum -- NESIC 0 08-22-2002 04:28 PM

All times are GMT -4. The time now is 04:09 PM.


Powered by vBulletin® Version 3.7.0
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
Powered by Searchlight © 2019 Axivo Inc.
Copyright ©1999 - 2019, North American Subaru Impreza Owners Club, Inc.

As an Amazon Associate I earn from qualifying purchases.