Welcome to the North American Subaru Impreza Owners Club Sunday December 8, 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-20-2016, 07:30 PM   #201
talon2.5RS
Scooby Newbie
 
Member#: 55033
Join Date: Feb 2004
Chapter/Region: MAIC
Location: Liverpool, NY
Vehicle:
2001 Impreza 2.5 RS
Project 2.5RSRX Underway!

Default

Here's the top side of the board on the SH7058 end:


And the bottom side where the test pads typically are on the turbo ECU's:


Why no labelling?! Any hardware engineers in the house?

Let me know if you want more pictures. These are from my phone, but I have access to a camera with a macro lens if needed.

Thanks!
Garrison
* Registered users of the site do not see these ads.
talon2.5RS is offline   Reply With Quote
Sponsored Links
* Registered users of the site do not see these ads.
Old 04-20-2016, 08:18 PM   #202
teds-rex
Scooby Specialist
 
Member#: 400886
Join Date: Sep 2014
Chapter/Region: NESIC
Location: outside Boston, MA
Vehicle:
2004 STi
PSM

Default

Looks pretty straight forward...

ON bottom side, bottom left corner:


pretty much exact same as turbo locations, just not labelled:
teds-rex is offline   Reply With Quote
Old 04-20-2016, 09:35 PM   #203
talon2.5RS
Scooby Newbie
 
Member#: 55033
Join Date: Feb 2004
Chapter/Region: MAIC
Location: Liverpool, NY
Vehicle:
2001 Impreza 2.5 RS
Project 2.5RSRX Underway!

Default

I noticed those looked like test pads. I hope it's really that simple. I'll grab my multi-meter and see if I can verify where they end up.

The soldering I did on my Forester ECU looks awful, makes me cringe. I had a nice Hakko unit, but I can't find the replacement elements for it. Used a crappy weller for the Forester. I bought a better iron with a super fine tip with adjustable temp for this go around on Amazon.

Thanks!
talon2.5RS is offline   Reply With Quote
Old 04-20-2016, 11:34 PM   #204
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 talon2.5RS View Post
I noticed those looked like test pads. I hope it's really that simple. I'll grab my multi-meter and see if I can verify where they end up.

The soldering I did on my Forester ECU looks awful, makes me cringe. I had a nice Hakko unit, but I can't find the replacement elements for it. Used a crappy weller for the Forester. I bought a better iron with a super fine tip with adjustable temp for this go around on Amazon.

Thanks!
Yes, those are definitely test points. From what I can tell, the traces all run similar to the WRX ECU routes in addition to the test point placement.
teds-rex is offline   Reply With Quote
Old 05-01-2016, 11:13 AM   #205
zcivic
Scooby Newbie
 
Member#: 199691
Join Date: Jan 2009
Chapter/Region: South East
Location: ETown TN
Vehicle:
04 Forester XT
Black

Default

I was just wondering/gauging interest in some SH bootloader boards or possible unlock services. At this time I've only done the 04 ECU because that's all I have. I used to do ECU conversions on OBD1 Honda/Acura P-series ECUs. Just wanted to gauge interest before I drop money into something that no one interested/needing.
Here are the boards I've made. Both tested and work like any board I'm building.


https://goo.gl/photos/NKpkdvDr94QGzDaB6


As for offering unlocking I can verify the write is successful but I'm looking to do those on a bench and wont have a vehicle to test each ECU on.
Thanks,
Randy

Last edited by zcivic; 05-01-2016 at 11:22 AM.
zcivic is offline   Reply With Quote
Old 05-01-2016, 12:19 PM   #206
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 zcivic View Post
I was just wondering/gauging interest in some SH bootloader boards or possible unlock services. At this time I've only done the 04 ECU because that's all I have. I used to do ECU conversions on OBD1 Honda/Acura P-series ECUs. Just wanted to gauge interest before I drop money into something that no one interested/needing.
Here are the boards I've made. Both tested and work like any board I'm building.


https://goo.gl/photos/NKpkdvDr94QGzDaB6


As for offering unlocking I can verify the write is successful but I'm looking to do those on a bench and wont have a vehicle to test each ECU on.
Thanks,
Randy
I was interested in trying to support this as well... but the big issue I saw was powering the ECUs. When I did this, I reflashed with it in my car. Between different year ECUs I think the pinnouts for connecting to wire harness were different... maybe there is some super-set, not sure.
teds-rex is offline   Reply With Quote
Old 05-01-2016, 01:43 PM   #207
zcivic
Scooby Newbie
 
Member#: 199691
Join Date: Jan 2009
Chapter/Region: South East
Location: ETown TN
Vehicle:
04 Forester XT
Black

Default

Quote:
Originally Posted by teds-rex View Post
I was interested in trying to support this as well... but the big issue I saw was powering the ECUs. When I did this, I reflashed with it in my car. Between different year ECUs I think the pinnouts for connecting to wire harness were different... maybe there is some super-set, not sure.
I'm considering getting a 12v converter and a harness. Worst case I can just use cig adaptor to power it.
zcivic is offline   Reply With Quote
Old 05-06-2016, 09:34 AM   #208
teds-rex
Scooby Specialist
 
Member#: 400886
Join Date: Sep 2014
Chapter/Region: NESIC
Location: outside Boston, MA
Vehicle:
2004 STi
PSM

Default

We're you able to find a list of required power and grounds though? I started looking based on wiring diagrams but
a) wasn't able to find all the required pins needing 12
b) several different diagrams for 32bit ECU I compared have different power/ground.
teds-rex is offline   Reply With Quote
Old 05-06-2016, 04:48 PM   #209
mikeyPSF
NASIOC Supporter
 
Member#: 236475
Join Date: Jan 2010
Chapter/Region: BAIC
Location: San Francisco
Vehicle:
2002 WRX
Black

Default

If you're going to recover an ECU and you're anything other than 100% sure of the wiring, you should use a dedicated power source that has current limiting. When I recover Subaru ECUs on the bench, I generally limit the current to 500 - 600 mA. Most Subarus pull 300-500 mA and will instantly trip a 600 mA limit without any damage to the ECU if the wiring is wrong.

-Mike
Tactrix
mikeyPSF is offline   Reply With Quote
Old 05-06-2016, 08:45 PM   #210
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 mikeyPSF View Post
If you're going to recover an ECU and you're anything other than 100% sure of the wiring, you should use a dedicated power source that has current limiting. When I recover Subaru ECUs on the bench, I generally limit the current to 500 - 600 mA. Most Subarus pull 300-500 mA and will instantly trip a 600 mA limit without any damage to the ECU if the wiring is wrong.

-Mike
Tactrix
Totally agree with using a bench supply. Do you have any recommendations on harness pinnout for the different years?
teds-rex is offline   Reply With Quote
Old 05-07-2016, 12:32 PM   #211
zcivic
Scooby Newbie
 
Member#: 199691
Join Date: Jan 2009
Chapter/Region: South East
Location: ETown TN
Vehicle:
04 Forester XT
Black

Default

Quote:
Originally Posted by teds-rex View Post
Totally agree with using a bench supply. Do you have any recommendations on harness pinnout for the different years?
I've only been able to find ones listed in this post. As for power supply are you using just a small power converter like for home electronics or is it a larger more industrial type.
zcivic is offline   Reply With Quote
Old 05-07-2016, 05:16 PM   #212
teds-rex
Scooby Specialist
 
Member#: 400886
Join Date: Sep 2014
Chapter/Region: NESIC
Location: outside Boston, MA
Vehicle:
2004 STi
PSM

Default

As it's better to use one which can limit and display current to indicate any issues as well as a bit of protection.
teds-rex is offline   Reply With Quote
Old 06-02-2016, 07:30 PM   #213
SubiCarLous
Scooby Newbie
 
Member#: 402221
Join Date: Sep 2014
Default

Is it actually possible just to buy a PL2303HX Cable and a NE555 Adjustable Frequency Module (set manual to 150 Hz) and just connect all without soldering except to the ECU? Would this work?
SubiCarLous is offline   Reply With Quote
Old 06-04-2016, 05:02 AM   #214
Johnnyc85
Scooby Newbie
 
Member#: 448280
Join Date: Jun 2016
Default

Isnt it easier just to get a used ecu
Johnnyc85 is offline   Reply With Quote
Old 06-04-2016, 01:39 PM   #215
Noah
( ͡ ͜ʖ ͡)
Moderator
 
Member#: 111510
Join Date: Apr 2006
Chapter/Region: MWSOC
Location: Chicago area
Vehicle:
04 WRX 16 Xtrek
19 XSR900

Default

Quote:
Originally Posted by SubiCarLous View Post
Is it actually possible just to buy a PL2303HX Cable and a NE555 Adjustable Frequency Module (set manual to 150 Hz) and just connect all without soldering except to the ECU? Would this work?
I don't see why it wouldn't, provided everything gets connected properly.
Noah is offline   Reply With Quote
Old 07-03-2016, 02:26 PM   #216
jlangholzj
Scooby Newbie
 
Member#: 377640
Join Date: Jan 2014
Chapter/Region: MWSOC
Location: Lincoln, NE
Vehicle:
2014 WRX hatch
DGM

Default

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

Last edited by jlangholzj; 07-03-2016 at 02:37 PM.
jlangholzj is offline   Reply With Quote
Old 07-26-2016, 05:25 PM   #217
BrickedScoob
Scooby Newbie
 
Member#: 451433
Join Date: Jul 2016
Default Unbricking a SH7058 ECU from a type UK '06 Impreza WRX

Just wanted to say a massive thanks to Franko and this thread and share my experience unbricking my ECU.

I wanted to turn off the secondary air pump fault codes, because I was sick of the engine management light being on for no real reason. Maybe being a bit blase I decided not to get a tactrix cable and instead use the ODB2 cable I bought off ebay. This worked for FreeSSM to turn off the fault codes and I got it to read the ECU with EcuFlash 1.29 after some digging on the web.

So I downloaded the image and modified it with RomRaider. The next step I'm not so proud of... Instead of doing the test write, I went straight in to writing to the ECU and I did not even cycle the ignition directly beforehand. Not sure if doing otherwise would have made any difference, but in any case I realised my mistake too late and ended up seeing a number of fail messages appear in the log.

So EcuFlash tells you not to reset the ECU and to try the write again, but this just would not work, so I had no choice but to turn off. This was when I discovered the engine would not fire up. Tried disconnecting the battery to reset everything, but still no luck.

That's when I found the tactrix shbootmode instructions. Now Flash Recovery Mode was not available in EcuFlash 1.29 so I installed the latest version 1.42. However, even if EcuFlash seemed to think it was successfully writing to the ECU (which took hours btw), the ECU was still bricked.

Following Franco's post I was able to do a successful write using Renesas Flash developer toolkit (FDT) which was also a lot faster than EcuFlash's attempts. I used the basic version - you just need to know which chip number you have and accept all of the other defaults during the setup, making sure your COM port is the right one.

For anyone trying to do the same, I just want to detail what I did to (finally) get it to work, which took many hours, sleepless nights and working from home ;)

1. I did not have a 555 timer, so I used a PSOC development kit I had from Cypress Semiconductor to output a 5V, 150Hz square wave powered by the laptop USB port.

2. I used a VagCom cable I had bought for an old Alfa, to wire from the FTDI chip to the test points as shown on the shbootmode.pdf (note, the FTDI chip on my cable was an FT232R instead of the one shown here, so I had to do a search to find the right pinout).

3. Make sure you install the FTDI drivers

4. I powered the ECU using the following pins:
B134 : 7 - Control unit PS = 12V
B135 : 19 - Ignition Switch = 12V
B137 : 1 - Engine Ground = 0V
Using a mains fixed power supply with a 700mA max output.
Note, I did try connecting more pins, as suggested in Franko's original post, when I couldn't get it to work, but I later found many of these are connected to those listed above on the ECU PCB anyway, so it's not really necessary.

5. I ended up using the PSOC dev kit to pass all of the signals to the ECU so that I could control the interface and also I had read that the Tx and Rx signals might need inverting - In the end, they didn't, but the fact I could use the PSOC board to adapt the type of digital interface presented to the ECU seemed to help. I ended up with the following, but that's not to say it wouldn't have worked otherwise:
P407 - Watchdog = Open-drain
P409 - Tx = Resistive pull-up
P411 - Rx = Open-drain
P405 - FWE = 5V strong drive
P413 - !Boot = 0V strong drive

6. Now what I didn't realise for a long time (too long!) was that the 0V and 5V pins were not going to the Micro's power supply and when I finally got an oscilloscope on the Rx signal I could see that it was being clipped which was why the FDT couldn't see the response from the ECU. So I linked the 12V PSU's ground to the USB ground of my dev kit and hey-presto, success!

Unfortunately for anyone trying to use this info, I did not want to retry every option and permutation of what I did to get it work to see if it actually mattered - sorry, but can't risk it, especially as I managed to get my modified image in there :)

So, to summarise, I would say the important points are:
1. CONNECT THE USB GROUND TO THE ECU GROUND
2. No need to supply all the different 12V / ground connections on the ECU header.
3. Renesas Flash developer toolkit basic over EcuFlash - just rename your image to have the extension ".bin" as Franco mentioned.

Hope this helps someone to hear the amazing sound of their engine firing up after the gut-wrenching feeling you've bricked your ECU!
BrickedScoob is offline   Reply With Quote
Old 07-26-2016, 05:41 PM   #218
mikeyPSF
NASIOC Supporter
 
Member#: 236475
Join Date: Jan 2010
Chapter/Region: BAIC
Location: San Francisco
Vehicle:
2002 WRX
Black

Default

I would also suggest adding to your list of "important points":

4) Avoid using software released in October of 2006 (EcuFlash 1.29) as the subsequent 9+ years have seen a lot of improvements in reliability.

also, your point of "so I installed the latest version 1.42" would only be true if we went back 7 years to June of 2009. Current version of EcuFlash is 1.44.4799.

"Using a mains fixed power supply with a 700mA max output."

I usually use 400mA or in some rare cases 500mA to keep the safety margin tight.

-Mike
Tactrix
mikeyPSF is offline   Reply With Quote
Old 11-12-2016, 06:38 PM   #219
menbolduc001
Scooby Newbie
 
Member#: 458047
Join Date: Nov 2016
Default

i want to buy a tool from anybody that have it properly done, i have no problem to solder to the ecu but not sure to find all needed parts to get it properly done like i saw on this thread. I want to unbrick subaru ecu of all years to flash over ecuteck or cobb please help me


Thanks
menbolduc001 is offline   Reply With Quote
Old 01-19-2017, 04:53 AM   #220
vietdiesel
Scooby Newbie
 
Member#: 461569
Join Date: Jan 2017
Location: Vietnam
Wink Help me to unbrick this ECU

Dear all .
I tried but I could not found P405 to P413 point in mainboard . Here is the picture of my mainboard . Hopefully someone can help me read and write this ECU
https://1drv.ms/i/s!AoLE0w8hGfMnoH79z7mOiUoHJblA
https://1drv.ms/i/s!AoLE0w8hGfMnoH8v8CZ6D_xv_whX
Thanks you
vietdiesel is offline   Reply With Quote
Old 01-19-2017, 07:42 AM   #221
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 vietdiesel View Post
Dear all .
I tried but I could not found P405 to P413 point in mainboard . Here is the picture of my mainboard . Hopefully someone can help me read and write this ECU
https://1drv.ms/i/s!AoLE0w8hGfMnoH79z7mOiUoHJblA
https://1drv.ms/i/s!AoLE0w8hGfMnoH8v8CZ6D_xv_whX
Thanks you
Check post 202 out and see if that answers it
teds-rex is offline   Reply With Quote
Old 01-19-2017, 07:47 AM   #222
vietdiesel
Scooby Newbie
 
Member#: 461569
Join Date: Jan 2017
Location: Vietnam
Unhappy

Quote:
Originally Posted by teds-rex View Post
Check post 202 out and see if that answers it
It's not same . I checked . please take 1 minuter to look my picture
Thanks brother
vietdiesel is offline   Reply With Quote
Old 01-19-2017, 12:45 PM   #223
Noah
( ͡ ͜ʖ ͡)
Moderator
 
Member#: 111510
Join Date: Apr 2006
Chapter/Region: MWSOC
Location: Chicago area
Vehicle:
04 WRX 16 Xtrek
19 XSR900

Default

Quote:
Originally Posted by vietdiesel View Post
It's not same . I checked . please take 1 minuter to look my picture
Thanks brother
What year and model is this coming out of?
Noah is offline   Reply With Quote
Old 01-19-2017, 06:47 PM   #224
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 vietdiesel View Post
It's not same . I checked . please take 1 minuter to look my picture
Thanks brother
Definitely looks different...
Looks like the reference designators may all be different and the existing test point numbers probably don't exist at all. Looks like test points changed from P* as seen on other boards to T* on your board. Curious what MY/model this is from.

Hoping mikeyPSF may have seen this.
teds-rex is offline   Reply With Quote
Old 01-19-2017, 09:46 PM   #225
vietdiesel
Scooby Newbie
 
Member#: 461569
Join Date: Jan 2017
Location: Vietnam
Exclamation

Quote:
Originally Posted by teds-rex View Post
Definitely looks different...
Looks like the reference designators may all be different and the existing test point numbers probably don't exist at all. Looks like test points changed from P* as seen on other boards to T* on your board. Curious what MY/model this is from.

Hoping mikeyPSF may have seen this.
Yes brother
It's komatsu PC200-8 pump controller . it have same chip "renesas sh7055"
If someone know the way to connect direct to Pins of the Chip maybe can solve problem . i think renesas e1 emulator can do it. but i also dont know how to connect because renesas does not support this Chip
vietdiesel 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 09:36 AM.


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.