RomRaider

Looking on those resistanse I think they are related to ignition. There is also 4 resistors with 470 ohms (marking 471) and controlling ic somewhere near those. Maybe they or ic is also damaged.

EDIT: actually not sure about ic. Top side there is those 471 resistors in the middle of the board. Also check that coils are still ok and not burnt out.

How do I check those, and are they those larger black things?

With coils I mean ignition coils. 471 resistors are top side of the board, in the center, at least the one ecu I have.

Those larger black ones are diodes, could be burnt too.

I replaced the both coils with backup coils and known good coils....


I'll check the topside for those 471s and see if they are no good

so, does anyone know where the circut goes after the diodes on my ecu? i cant seem to fallow the trace....

I replaced the resistors, and then replaced the diodes that fallow directly afterward.... it fires up... but still missing on 1 and 4...

anyone have any ideas?

Is it possible to use an aftermarket ignition system... Since this ECU won't fire 1 and 4?

Hello to all.

I know this is quite old thread, but is there anyone that could help me trying to recover a 2015 WRX ECU with a SH72543R MCU?
I loaded a tune file with PCMFlash and all went well, but ECU now seems to be in "Boot Loop" and doesnt work....

Anyone here that might have experience on this?

Thanks

So I've been working on patches for my 07 forester NA/T, and along the way I manged to lock up two of my ecus. I figured it was time to learn how to repair ecus before I go too much further. All I got to say is we have some smart people here! No way would I have been able to do the without all the posted info and suggestions. Both my ecus were brought back to life!

I built the timer using the info on here 2 of 1K,47.5K resistor, 100nf capacitor etc. and puts out a 150hz 50% duty signal. Some things worth mentioning, I saw a few posts with pin 4 of the 555 connected to 5V, I tried it both ways and found it didn't change my signal, if there is a reason to do this I would like to know. Secondly I found the 47.5K resistor it looks like it can vary slightly in resistance and still put out the correct signal.

For my USB to serial connection I used a Vagcom, personally if I did it again I would order a DLP-USB232M or equivalent. If using the Vagcom make sure it gets 12V to the OBD power and a shared ground to the ecu, Pins 1 and 5 (for my chip FT232rl) need to be pulled off the board and solder to the wire going to the ecu.

My ecu connections were the same as others, the only difference is I didn't connect a ground to the negative side of a capacitor on the ecu board.
5v - p405
Gnd - p413
RX - p411
TX - p409
Timer - p407

(2007 Forester 2.5i ej253)
I connected 12V to pins A7, B2, B5, B27.
and a single ground at D1.

I found all the info needed to do this on this topic and these links.
viewtopic.php?f=7&t=7136&start=15
https://forums.nasioc.com/forums/showth ... e_vignette

I couldn't get the Ecu Flash software to work

Flash Development Toolkit
https://www.renesas.com/en/software-too ... gzGK0FG6XG
I used “Flash Development Toolkit V.4.09 Release 00 Upgrade “ I found that the newest one “Flash Development Toolkit V.4.09 Release 03 Upgrade “ did not have an option for a com port and looked like it used a specific flash device, I might be missing something though.

“Flash Development Toolkit V.4.09 Release 00 Upgrade “ however has issues with windows 10 and 11 so I had to use my windows 7 laptop.

My log file looks a little different than others, also I dont know why its only 661.63 K the file should be 1024K.

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\victor\Desktop\mafscake.bin"
Loading image file : 'C:\Users\victor\Desktop\mafscake.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 - 0x0008FC7F]
Writing image to device... [0x00090000 - 0x0009037F]
Writing image to device... [0x000BD800 - 0x000BEE7F]
Writing image to device... [0x000BF000 - 0x000BF2FF]
Writing image to device... [0x000C0000 - 0x000C1B7F]
Writing image to device... [0x000C1B80 - 0x000D037F]
Writing image to device... [0x000DB800 - 0x000DECFF]
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 - 0x0008FC7F Length : 0x0008DD00
0x00090000 - 0x0009037F Length : 0x00000380
0x000BD800 - 0x000BEE7F Length : 0x00001680
0x000BF000 - 0x000BF2FF Length : 0x00000300
0x000C0000 - 0x000C1B7F Length : 0x00001B80
0x000C1B80 - 0x000D037F Length : 0x0000E800
0x000DB800 - 0x000DECFF Length : 0x00003500
0x000DF800 - 0x000DF87F Length : 0x00000080
0x000FFA80 - 0x000FFAFF Length : 0x00000080
0x000FFB80 - 0x000FFFFF Length : 0x00000480
661.63 K programmed in 170 seconds
Image written to device

Hi,

Can someone try this without soldering and extracting your ECUs from the car just through the OBD2 port?

If you just want to pull the tune use a Tactrix and ECU flash or a Vagcom and Fast ECU.