RomRaider

Has anyone had any experience in unbricking the SH7059 / 370Z 1.5MB ECU's?

I can't seem to connect via Renesas Flash Toolkit..... I've tried for hours now and i'm getting frustrated!

I've been reading the 7059 hardware documentation and am confused with which pins need to go low and high.... Am I to attempt to go into Programmer Mode of Boot Mode?

Boot Mod requires the following pins;
RES: 1
FWE: 1
MD0: 0/1
MD1: 0
MD2: 1

Programmer Mode requires:
RES: 1
FWE: 0/1
MD0: 1
MD1: 1
MD2: 0

Any help would be appreciated!

WDT signal on the board with SH705519N/SH705520N.

SH7059 the same?

SH705927N not checked/tested yet.
Later))

Renesas Flash Development Toolkit works with SH7059 ???

SH7059

Universal UnBrick-Board for SH7055-59. Approximate size 40 х 60mm.
Test points TP83, 84 connect only for SH7059.

WDT signal on the board with SH705927N.

I've had some mixed results so far with a few ECUs here

CD001 (7055) - Will return AA for 55 command and then SCI RX echos SCI TX

Needed 5.6K pullup added to SCI RX for it to filter out cross talk/glitching from SCI TX

I've seen that SCI TX goes straight to the 9762 KLine transceiver chip on this ECU

CE815 (7058). Same setup. Works fine. ECU PCBs almost look identical apart from processor

Thanks for this. This works fine (so pullup WRES to VCC via 15ohms, I used 20 ohms)

Also you used 1.5K pullup on WDG clock line. I've used 1K (which is same as Piasini pullup on their WDG diagrams) and that works the same. Just manged to unbrick my 370Z ECU

Hi Guys,

I have a bit of an issue. I have a 350z APS TT with REVUP ECU, CF43A. ECU is licensed via UPREV. I wanted to apply an updated tune and then when the update finished programming reaching 100% and the ROmeditor said to switch off the car but it seems the ECU did not go out of programming mode and the fan kept running. So i tried to unplug the uprev and reconnect the cable but it did not change and also switched of the car with the same symptom. I have disconnected the battery etc etc. and nothing worked. I contacted UPREV and they said I need to ship the ecu to them. I did just that and await their reply.

So I though, ok, i also have a race 350z with a REVUP ECU with UPREV in it so let me try that one. So I programmed the NATS and keys etc and tried to flash it again as I dont race with my race 350z now and changing the ECU to a Haltec soon. Problem is, the same thing happened as per the first ECU!! Quite pissed off about it I searched the NET and I stumbled on this thread and built a 555 timing board. I can connect and flash the CF43A.BIN file to the ECU but when I plug it back in its just does the same, fans running and ECU still in programming mode.

Are there any settings I need to setup in Renesas Toolkit because I tried flashing a few times and it still does the same?

I will post the log of the flash. Maybe I am missing something? I need some help guys?

Cheers!

You are flashing the original CF43A.BIN ? Show a screenshot of the end of the .bin firmware. Did you read the dump after the firmware and compared it with the original one?

Hi Alex, yes, I am flashing the original CF43A.bin file, I hope. I am a noob on around this Toolkit software so please bare with me

I do not know the Renesas Toolkit software at all so I have been following any SH7055/58 tutorials but I am not winning here and need some guidance please?

So when I open a New project on the Toolkit and select the SH7058 or Generic Boot (HD64F7058) and then select the CF43.bin file it open(I can share this file with you then you can check if its the correct one?). I see there is a "Boot user flash" area with nothing in it. Is it suppose to be like this and if not where can i find this Boot file? Also when I do a Blank Check it says the "User boot Flash" is empty??

I have Anydesk if someone can please guide me in the correct direction will be so much appreciated!!!

Here is the flash log,

OS: Windows 10 (Windows [Non-Admin]
Processing file :"C:\Nissan\CF43A.bin"
Loading image file : 'C:\Nissan\CF43A.bin'
Operation on User Flash
Loaded the Write operation module
Writing image to device... [0x00000000 - 0x00001C7F]
Writing image to device... [0x00002000 - 0x0000447F]
Writing image to device... [0x00004480 - 0x000044FF]
Writing image to device... [0x00004500 - 0x0000457F]
Writing image to device... [0x00004580 - 0x00004A7F]
Writing image to device... [0x00004A80 - 0x00004B7F]
Writing image to device... [0x00004C00 - 0x0000617F]
Writing image to device... [0x00006180 - 0x0000627F]
Writing image to device... [0x00006300 - 0x0000B17F]
Writing image to device... [0x0000B180 - 0x0000C27F]
Writing image to device... [0x0000C280 - 0x0000CAFF]
Writing image to device... [0x0000CB00 - 0x000A7B7F]
Writing image to device... [0x000A9000 - 0x000A91FF]
Writing image to device... [0x000A9200 - 0x000A92FF]
Writing image to device... [0x000A9300 - 0x000A93FF]
Writing image to device... [0x000AFF80 - 0x000B01FF]
Writing image to device... [0x000B0200 - 0x000B0BFF]
Writing image to device... [0x000B0C00 - 0x000B15FF]
Writing image to device... [0x000B1600 - 0x000B1FFF]
Writing image to device... [0x000B2000 - 0x000B29FF]
Writing image to device... [0x000B2A00 - 0x000B31FF]
Writing image to device... [0x000E0400 - 0x000E04FF]
Writing image to device... [0x000E1000 - 0x000E11FF]
Writing image to device... [0x000E1280 - 0x000E13FF]
Writing image to device... [0x000E1400 - 0x000E14FF]
Writing image to device... [0x000FFF80 - 0x000FFFFF]
Data programmed at the following positions:
0x00000000 - 0x00001C7F Length : 0x00001C80
0x00002000 - 0x0000447F Length : 0x00002480
0x00004480 - 0x000044FF Length : 0x00000080
0x00004500 - 0x0000457F Length : 0x00000080
0x00004580 - 0x00004A7F Length : 0x00000500
0x00004A80 - 0x00004B7F Length : 0x00000100
0x00004C00 - 0x0000617F Length : 0x00001580
0x00006180 - 0x0000627F Length : 0x00000100
0x00006300 - 0x0000B17F Length : 0x00004E80
0x0000B180 - 0x0000C27F Length : 0x00001100
0x0000C280 - 0x0000CAFF Length : 0x00000880
0x0000CB00 - 0x000A7B7F Length : 0x0009B080
0x000A9000 - 0x000A91FF Length : 0x00000200
0x000A9200 - 0x000A92FF Length : 0x00000100
0x000A9300 - 0x000A93FF Length : 0x00000100
0x000AFF80 - 0x000B01FF Length : 0x00000280
0x000B0200 - 0x000B0BFF Length : 0x00000A00
0x000B0C00 - 0x000B15FF Length : 0x00000A00
0x000B1600 - 0x000B1FFF Length : 0x00000A00
0x000B2000 - 0x000B29FF Length : 0x00000A00
0x000B2A00 - 0x000B31FF Length : 0x00000800
0x000E0400 - 0x000E04FF Length : 0x00000100
0x000E1000 - 0x000E11FF Length : 0x00000200
0x000E1280 - 0x000E13FF Length : 0x00000180
0x000E1400 - 0x000E14FF Length : 0x00000100
0x000FFF80 - 0x000FFFFF Length : 0x00000080
684.88 K programmed in 176 seconds
Image written to device

Attach .bin and I'll tell you if it's correct or not. https://www.drive2.ru/l/6520480/