Welcome to the North American Subaru Impreza Owners Club Thursday December 14, 2017
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.
* Registered users of the site do not see these ads. 
Reply
 
Thread Tools Display Modes
Old 01-27-2017, 05:18 PM   #226
yfz460
Scooby Newbie
 
Member#: 167143
Join Date: Dec 2007
Chapter/Region: Tri-State
Location: Colonie, NY
Vehicle:
2011 SWP WRX Hatch
2007 SWP STi

Default

Quote:
Originally Posted by jlangholzj View Post
2014 USDM wrx. Built everything as-advertised (sans a different FDTI widget) and I'm getting the below in my log. The only reference I was able to find with the last lines was on an FT86 forum and it didn't sound too good Only other thing I can think of is that my fluke is telling me my 555 is outputing 230Hz and not 150, despite the values being correct. I guess I don't have a scope to see if it's ACTUALLY at 230 or if its because it's too low a voltage for the fluke to read reliably.

Anyway, got an email into tactrix but I'm assuming because of the long weekend they'll probably be out. Figured I'd toss up something on here and see if anyone knew what was up. thanks all.

Code:
[12:55:21.048] Logging to file C:/Users/John/AppData/Roaming/OpenECU/EcuFlash/logs/ecuflash_log_20160703t125521.txt
[12:55:21.048] EcuFlash Version 1.44.4799
[12:55:21.048] OS Version Windows 8.1
[12:55:21.048] Kernel Type winnt
[12:55:21.048] Kernel Version 6.3.9600
[12:55:21.048] CPU i386
[12:55:21.048] Product Name Windows 8.1
[12:55:21.048] Product Type windows
[12:55:21.048] Product Version 8.1
[12:55:21.048] Qt Version 5.6.0
[12:55:21.048] Qwt Version 6.1.2
[12:55:21.048] QwtPlot3D Version 0.2.6
[12:55:21.048] Boost Version 1.60
[12:55:21.048] FTDI Library Version 3.02.11
[12:55:21.048] Openport J2534 Library Version 1.02.4798
[12:55:21.079] 67 memory models read.
[12:55:21.079] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata
[12:55:21.532] 745 ROM metadata models scanned.
[12:55:21.532] checksum module "subarudbw" loaded.
[12:55:21.532] checksum module "subarudiesel" loaded.
[12:55:21.532] checksum module "subaruhitachi" loaded.
[12:55:21.532] checksum module "mitsucan" loaded.
[12:55:21.532] checksum module "mitsuh8" loaded.
[12:55:21.532] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[12:55:21.532] patch module "Mitsu CAN RAM Parameter Logging" loaded.
[12:55:21.548] using metadata XML ID read_subarush7058can from file C:/Program Files/OpenECU/EcuFlash/rommetadata/read templates/read_subarush7058can.xml
[12:55:21.610] flashing tool "wrx02" loaded.
[12:55:21.626] flashing tool "wrx04" loaded.
[12:55:21.626] flashing tool "sti04" loaded.
[12:55:21.642] flashing tool "sti05" loaded.
[12:55:21.642] flashing tool "mitsucan" loaded.
[12:55:21.642] flashing tool "mitsukernel" loaded.
[12:55:21.642] flashing tool "mitsukernelocp" loaded.
[12:55:21.642] flashing tool "mitsubootloader" loaded.
[12:55:21.642] flashing tool "shbootmode" loaded.
[12:55:21.642] flashing tool "shaudmode" loaded.
[12:55:21.657] flashing tool "subarucan" loaded.
[12:55:21.657] flashing tool "subarucand" loaded.
[12:55:21.673] flashing tool "subarubrz" loaded.
[12:55:21.673] flashing tool "subaruhitachi" loaded.
[12:55:21.720] FTDI Driver Version 2.12.16
[12:55:21.720] Using interface FT232R USB UART A50285BI
[12:55:21.720] interface close
[12:55:21.782] FTDI Driver Version 2.12.16
[12:55:21.782] Using interface FT232R USB UART A50285BI
[12:55:21.782] interface close
[12:55:21.845] FTDI Driver Version 2.12.16
[12:55:21.845] Using interface FT232R USB UART A50285BI
[12:55:21.845] interface close
[12:55:21.907] FTDI Driver Version 2.12.16
[12:55:21.907] Using interface FT232R USB UART A50285BI
[12:55:21.907] interface close
[12:55:21.970] FTDI Driver Version 2.12.16
[12:55:21.970] Using interface FT232R USB UART A50285BI
[12:55:21.970] interface close
[12:55:22.032] FTDI Driver Version 2.12.16
[12:55:22.032] Using interface FT232R USB UART A50285BI
[12:55:22.032] interface close
[12:55:30.830] opening rom file C:/Users/John/Google Drive/ROMS/USDM_2014_WRX.bin
[12:55:31.158] AE5Q100L (365 tables) inheriting 32BITBASE (1237 tables)
[12:55:31.251] 1048576 byte image read.
[12:55:31.345] using metadata XML ID AE5Q100L from file C:/Program Files/OpenECU/EcuFlash/rommetadata/subaru/Impreza WRX/AE5Q100L 2014 USDM Impreza WRX MT.xml
                which inherits XML ID 32BITBASE from file C:/Program Files/OpenECU/EcuFlash/rommetadata/subaru/Bases/32BITBASE.xml
[12:55:31.345] ---notes for 32BITBASE---
               2014/06/20 [Tactrix] Tactrix definition auto cleaned|merged w/ RomRaiderGitHubAlphaMay2014.
               ---notes for AE5Q100L---
               2014/05/22 [Tactrix] Tactrix definition auto cleaned|merged w/ RomRaiderGitHubAlphaMay2014.
[12:55:36.736] FTDI Driver Version 2.12.16
[12:55:39.033] sending bit rate sync bytes...
[12:55:39.143] received bit rate adjust response
               sending boot command
[12:55:39.659] got boot response
[12:55:39.800] 1 supported device(s):
[12:55:39.800]    1n01 R4F70580S
[12:55:39.800] selecting device 1n01
[12:55:40.034] 1 supported clock mode(s):
[12:55:40.034]    0
[12:55:40.034] selecting clock mode 0
[12:55:40.269] 2 supported clock type(s):
[12:55:40.269] 1 ratios for clock type 1
[12:55:40.269]    x8
[12:55:40.269] 1 ratios for clock type 2
[12:55:40.269]    x2
[12:55:40.394] 2 supported clock frequency range(s):
[12:55:40.394] 1 40000000-80000000
[12:55:40.394] 2 10000000-20000000
[12:55:40.519] 1 user boot MAT area(s):
[12:55:40.519] 1 00000000-00002fff
[12:55:40.628] 1 user MAT area(s):
[12:55:40.628] 1 00000000-000fffff
[12:55:40.753] programming unit is 128
[12:55:40.878] one MAT programming supported at 00000000
[12:55:40.878] setting baud rate to 62500
[12:55:41.128] there are more memory areas in this CPU that will be erased than the ROM file you have has data for. write process aborted.
[12:55:41.128] interface close
Did you ever resolve this issue? Currently in the same boat, built with FTDI 6-wire cable, 555 only verified at 2.4vdc with RMS meter (no access to o-scope). My original issue was after unmarrying an AP V2, I was never able to flash again. Car runs and drives fine, and can log data/reset without issue. Here's my log from ECUflash:
Quote:
[15:56:53.905] using metadata XML ID AE5I910L from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/subaru/Impreza WRX/AE5I910L 2011 USDM WRX MT.xml
which inherits XML ID 32BITBASE from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/subaru/Bases/32BITBASE.xml
[15:56:53.905] ---notes for 32BITBASE---
2014/06/20 [Tactrix] Tactrix definition auto cleaned|merged w/ RomRaiderGitHubAlphaMay2014.
---notes for AE5I910L---
2012/11/30 [Tactrix] Experimental definition from RomRaider.
2012/12/05 [Tactrix] Visually examined a portion of tables for obvious errors, but no in-car verification has been done. Standardized file name.
2014/05/22 [Tactrix] Tactrix definition auto cleaned|merged w/ RomRaiderGitHubAlphaMay2014.
[15:57:48.423] FTDI Driver Version 2.12.24
[15:57:50.615] sending bit rate sync bytes...
[15:57:51.473] received bit rate adjust response
sending boot command
[15:57:54.343] received bit rate adjust response
sending boot command
[15:57:58.399] no bit rate adjust response
[15:57:58.399] interface close
[15:58:11.299] FTDI Driver Version 2.12.24
[15:58:16.149] sending bit rate sync bytes...
[15:58:16.273] received bit rate adjust response
sending boot command
[15:58:16.788] got boot response
[15:58:16.913] 1 supported device(s):
[15:58:16.913] 1n01 R4F70580S
[15:58:16.913] selecting device 1n01
[15:58:17.163] 1 supported clock mode(s):
[15:58:17.163] 0
[15:58:17.163] selecting clock mode 0
[15:58:17.397] 2 supported clock type(s):
[15:58:17.397] 1 ratios for clock type 1
[15:58:17.397] x8
[15:58:17.397] 1 ratios for clock type 2
[15:58:17.397] x2
[15:58:17.521] 2 supported clock frequency range(s):
[15:58:17.521] 1 40000000-80000000
[15:58:17.521] 2 10000000-20000000
[15:58:17.631] 1 user boot MAT area(s):
[15:58:17.631] 1 00000000-00002fff
[15:58:17.755] 1 user MAT area(s):
[15:58:17.755] 1 00000000-000fffff
[15:58:17.865] programming unit is 128
[15:58:17.989] one MAT programming supported at 00000000
[15:58:17.989] setting baud rate to 62500
[15:58:18.255] query complete
[15:58:18.255] interface close
[15:58:27.971] FTDI Driver Version 2.12.24
[15:58:30.699] sending bit rate sync bytes...
[15:58:31.026] no bit rate adjust response
[15:58:31.026] interface close
[15:58:44.152] FTDI Driver Version 2.12.24
[15:58:47.249] sending bit rate sync bytes...
[15:58:47.374] received bit rate adjust response
sending boot command
[15:58:47.888] got boot response
[15:58:48.013] 1 supported device(s):
[15:58:48.013] 1n01 R4F70580S
[15:58:48.013] selecting device 1n01
[15:58:48.263] 1 supported clock mode(s):
[15:58:48.263] 0
[15:58:48.263] selecting clock mode 0
[15:58:48.512] 2 supported clock type(s):
[15:58:48.512] 1 ratios for clock type 1
[15:58:48.512] x8
[15:58:48.512] 1 ratios for clock type 2
[15:58:48.512] x2
[15:58:48.622] 2 supported clock frequency range(s):
[15:58:48.622] 1 40000000-80000000
[15:58:48.622] 2 10000000-20000000
[15:58:48.746] 1 user boot MAT area(s):
[15:58:48.746] 1 00000000-00002fff
[15:58:48.871] 1 user MAT area(s):
[15:58:48.871] 1 00000000-000fffff
[15:58:48.980] programming unit is 128
[15:58:49.105] one MAT programming supported at 00000000
[15:58:49.105] setting baud rate to 62500
[15:58:49.370] there are more memory areas in this CPU that will be erased than the ROM file you have has data for. write process aborted.
[15:58:49.370] interface close
* Registered users of the site do not see these ads.
yfz460 is offline   Reply With Quote
Sponsored Links
* Registered users of the site do not see these ads.
Old 01-27-2017, 05:49 PM   #227
jlangholzj
Scooby Newbie
 
Member#: 377640
Join Date: Jan 2014
Chapter/Region: MWSOC
Location: Lincoln, NE
Vehicle:
2014 WRX hatch
DGM

Default

Quote:
Originally Posted by yfz460 View Post
Did you ever resolve this issue? Currently in the same boat, built with FTDI 6-wire cable, 555 only verified at 2.4vdc with RMS meter (no access to o-scope). My original issue was after unmarrying an AP V2, I was never able to flash again. Car runs and drives fine, and can log data/reset without issue. Here's my log from ECUflash:
Negative mate, sorry. I've still got the ECU pigeonholed away in a box for future fiddling but for the time being I found a good used ECU on flebay and had a local dealership reprogram the immobilizer.
jlangholzj is offline   Reply With Quote
Old 04-04-2017, 12:52 AM   #228
leandropim
Scooby Newbie
 
Member#: 465484
Join Date: Apr 2017
Location: Sao Paulo - Brazil
Vehicle:
2015 STI
Blue

Default

Someone can help me with powering a STI 2015 ECU (SH7058)
112331-7390

thank you
leandropim is offline   Reply With Quote
Old 04-04-2017, 12:22 PM   #229
leandropim
Scooby Newbie
 
Member#: 465484
Join Date: Apr 2017
Location: Sao Paulo - Brazil
Vehicle:
2015 STI
Blue

Default

i would like to know if a 0.6w 47.5Kohms 1% will work? or will i need 1w or more?
leandropim is offline   Reply With Quote
Old 04-06-2017, 12:44 AM   #230
leandropim
Scooby Newbie
 
Member#: 465484
Join Date: Apr 2017
Location: Sao Paulo - Brazil
Vehicle:
2015 STI
Blue

Default

"there are more memory areas in this CPU that will be erased than the ROM file you have has data for. write process aborted."


*** Use Renesas FDT and write the ROM on the User Area

https://www.renesas.com/pt-br/software/D3017335.html

Last edited by leandropim; 04-10-2017 at 12:01 PM. Reason: solution
leandropim is offline   Reply With Quote
Old 04-10-2017, 12:01 PM   #231
leandropim
Scooby Newbie
 
Member#: 465484
Join Date: Apr 2017
Location: Sao Paulo - Brazil
Vehicle:
2015 STI
Blue

Default

Quote:
Originally Posted by jlangholzj
"there are more memory areas in this CPU that will be erased than the ROM file you have has data for. write process aborted."


*** Use Renesas FDT and write the ROM on the User Area

https://www.renesas.com/pt-br/software/D3017335.html

Last edited by leandropim; 04-10-2017 at 12:06 PM.
leandropim is offline   Reply With Quote
Old 04-10-2017, 01:31 PM   #232
yfz460
Scooby Newbie
 
Member#: 167143
Join Date: Dec 2007
Chapter/Region: Tri-State
Location: Colonie, NY
Vehicle:
2011 SWP WRX Hatch
2007 SWP STi

Default

I'll have to check that out, I don't recall doing anything specific to try and flash via FDT, just clicked through the program as it was set up.

Thanks!
yfz460 is offline   Reply With Quote
Old 07-29-2017, 12:07 AM   #233
Counti41
Scooby Newbie
 
Member#: 471893
Join Date: Jul 2017
Default

Need to recover my 05 LGT ecu as well. Anyone that can help.
Counti41 is offline   Reply With Quote
Old 10-02-2017, 06:24 PM   #234
BoxerLove
Scooby Newbie
 
Member#: 411441
Join Date: Jan 2015
Default

Im ready to give this a shot on my 05 STI as the ecu has to be locked up. My car has the immobilizer, would flashing with the Shboot method require me to have the immobilizer portion reprogrammed? Does the ecu store that data in whats being force flashed over?
BoxerLove is offline   Reply With Quote
Old 10-02-2017, 07:45 PM   #235
Noah
( ͡ ͜ʖ ͡)
Moderator
 
Member#: 111510
Join Date: Apr 2006
Chapter/Region: MWSOC
Location: Chicago area
Vehicle:
05 WRX 16 Xtrek
03 SV650S

Default

Quote:
Originally Posted by BoxerLove View Post
Im ready to give this a shot on my 05 STI as the ecu has to be locked up. My car has the immobilizer, would flashing with the Shboot method require me to have the immobilizer portion reprogrammed? Does the ecu store that data in whats being force flashed over?

I haven't had any issues with immobilizers on all of the ECUs that I've done. It's just overwriting the engine parameters, nothing to do with the immobilizer.
Noah is offline   Reply With Quote
Old 10-03-2017, 04:22 PM   #236
BoxerLove
Scooby Newbie
 
Member#: 411441
Join Date: Jan 2015
Default

Quote:
Originally Posted by Noah View Post
I haven't had any issues with immobilizers on all of the ECUs that I've done. It's just overwriting the engine parameters, nothing to do with the immobilizer.
Awesome man. Thanks. Wanted to make sure I didn't back myself into paying a tow bill to get it to the dealer lol. I decided to try purchasing an adjustable ne555 board and using my usb uart I already had to test on a spare ecu I have before flashing my presumed locked one in the car now. Will report the results!
BoxerLove is offline   Reply With Quote
Old 10-04-2017, 06:49 PM   #237
BoxerLove
Scooby Newbie
 
Member#: 411441
Join Date: Jan 2015
Default

Noah,

So today I got it all wired to the ECU and did a test flash on my spare ECU. Here is the log.

Flash Development Toolkit and flash programming components
are provided without support

OS: Windows 10 (Windows 8) [Admin]
Disconnecting
Disconnected

Clock Frequency (External) = 10.0000MHz, Clock Mode = 0, CKM = 4, and CKP = 2
Connecting to device 'SH/7058F' on 'COM4'
Configuration:
'BOOT Mode' connection - using emulated interface
Opening port 'COM4' ...
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\Anon\Desktop\A2ZJB10J.bin"
Loading image file : 'C:\Users\Anon\Desktop\A2ZJB10J.bin'
Operation on User Flash
Loaded the Write operation module
Writing image to device... [0x00000000 - 0x00000E7F]
Writing image to device... [0x00000F80 - 0x00001F7F]
Writing image to device... [0x00001F80 - 0x0007B07F]
Writing image to device... [0x000C0000 - 0x000CADFF]
Writing image to device... [0x000CAE00 - 0x000CD6FF]
Writing image to device... [0x000FFA80 - 0x000FFAFF]
Writing image to device... [0x000FFB80 - 0x000FFFFF]
Data programmed at the following positions:
0x00000000 - 0x00000E7F Length : 0x00000E80
0x00000F80 - 0x00001F7F Length : 0x00001000
0x00001F80 - 0x0007B07F Length : 0x00079100
0x000C0000 - 0x000CADFF Length : 0x0000AE00
0x000CAE00 - 0x000CD6FF Length : 0x00002900
0x000FFA80 - 0x000FFAFF Length : 0x00000080
0x000FFB80 - 0x000FFFFF Length : 0x00000480
546.88 K programmed in 106 seconds
Image written to device
Disconnecting
Disconnected



Does everything look ok here? Seemed quick compared to the OP's post. I noticed some differences in his vs my log. Wondering if thats because my ECU had the 7058 chip?

Just wanted to be sure of myself and my setup before attempting the ECU I believe is locked in my car now.

I was using a purchased Adjustable NE555 device that I set to 125-150 HZ and checked with my Fluke 77 IV multimeter on AC HZ mode, And my USB UART
BoxerLove is offline   Reply With Quote
Old 10-05-2017, 01:50 PM   #238
Noah
( ͡ ͜ʖ ͡)
Moderator
 
Member#: 111510
Join Date: Apr 2006
Chapter/Region: MWSOC
Location: Chicago area
Vehicle:
05 WRX 16 Xtrek
03 SV650S

Default

Quote:
Originally Posted by BoxerLove View Post
Noah,

So today I got it all wired to the ECU and did a test flash on my spare ECU. Here is the log.

Flash Development Toolkit and flash programming components
are provided without support

OS: Windows 10 (Windows 8) [Admin]
Disconnecting
Disconnected

Clock Frequency (External) = 10.0000MHz, Clock Mode = 0, CKM = 4, and CKP = 2
Connecting to device 'SH/7058F' on 'COM4'
Configuration:
'BOOT Mode' connection - using emulated interface
Opening port 'COM4' ...
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\Anon\Desktop\A2ZJB10J.bin"
Loading image file : 'C:\Users\Anon\Desktop\A2ZJB10J.bin'
Operation on User Flash
Loaded the Write operation module
Writing image to device... [0x00000000 - 0x00000E7F]
Writing image to device... [0x00000F80 - 0x00001F7F]
Writing image to device... [0x00001F80 - 0x0007B07F]
Writing image to device... [0x000C0000 - 0x000CADFF]
Writing image to device... [0x000CAE00 - 0x000CD6FF]
Writing image to device... [0x000FFA80 - 0x000FFAFF]
Writing image to device... [0x000FFB80 - 0x000FFFFF]
Data programmed at the following positions:
0x00000000 - 0x00000E7F Length : 0x00000E80
0x00000F80 - 0x00001F7F Length : 0x00001000
0x00001F80 - 0x0007B07F Length : 0x00079100
0x000C0000 - 0x000CADFF Length : 0x0000AE00
0x000CAE00 - 0x000CD6FF Length : 0x00002900
0x000FFA80 - 0x000FFAFF Length : 0x00000080
0x000FFB80 - 0x000FFFFF Length : 0x00000480
546.88 K programmed in 106 seconds
Image written to device

Disconnecting
Disconnected



Does everything look ok here? Seemed quick compared to the OP's post. I noticed some differences in his vs my log. Wondering if thats because my ECU had the 7058 chip?

Just wanted to be sure of myself and my setup before attempting the ECU I believe is locked in my car now.

I was using a purchased Adjustable NE555 device that I set to 125-150 HZ and checked with my Fluke 77 IV multimeter on AC HZ mode, And my USB UART

If you've made it to the highlighted section, you're good to go. The 2004 STI uses the SH 7055 chip, all revisions after 2004 used the 7058 chip so no worries. It looks like you flashed a 2005 STI ROM on to your ECU. If that's correct and it matches your car, plug it in and make sure your car starts.
Noah is offline   Reply With Quote
Old 10-06-2017, 02:17 AM   #239
BoxerLove
Scooby Newbie
 
Member#: 411441
Join Date: Jan 2015
Default

Quote:
Originally Posted by Noah View Post
If you've made it to the highlighted section, you're good to go. The 2004 STI uses the SH 7055 chip, all revisions after 2004 used the 7058 chip so no worries. It looks like you flashed a 2005 STI ROM on to your ECU. If that's correct and it matches your car, plug it in and make sure your car starts.
Looks like I'll be trying this on my actual ecu in the car (attempted my first flash on my spare ecu just so I didn't leave the car dead in the water). The car came with a spare ecu which wasnt programmed to the immobilizer. My car is an 05 STI so correct I have the 7058 chip. Will post back my results tomorrow! Setup was honestly super easy with a $5 555 adjustable timing board and the $3-5 UART being I have a multimeter than could read hz
BoxerLove is offline   Reply With Quote
Old 10-12-2017, 09:13 PM   #240
hopefullynotrice01
*** Banned ***
 
Member#: 472940
Join Date: Aug 2017
Default

bravo
hopefullynotrice01 is offline   Reply With Quote
Old 10-13-2017, 02:17 PM   #241
BoxerLove
Scooby Newbie
 
Member#: 411441
Join Date: Jan 2015
Default

Quote:
Originally Posted by BoxerLove View Post
Looks like I'll be trying this on my actual ecu in the car (attempted my first flash on my spare ecu just so I didn't leave the car dead in the water). The car came with a spare ecu which wasnt programmed to the immobilizer. My car is an 05 STI so correct I have the 7058 chip. Will post back my results tomorrow! Setup was honestly super easy with a $5 555 adjustable timing board and the $3-5 UART being I have a multimeter than could read hz

IT WORKED! Successfully flashed my 05 STI ECU and was able to pull the rom with ECU Flash after.
BoxerLove 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 07:08 AM.


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