Bricked ECU - SH Boot Mode help!

Announcements, dicussion about any topic that would have broad interest to the forum members

Moderator: Freon

Re: Bricked ECU - SH Boot Mode help!

Postby hmanxx » Sun Jan 17, 2010 5:30 am

Did you monitor the pin with oscilloscope ? i did..and initially i discovered the Tx pin connected wrongly and also there was dry joint on the watchdog pin..without the scope..i will be rounding the bush...
hmanxx
 
Posts: 45
Joined: Sat Apr 01, 2006 7:36 pm
Location: Singapore

Re: Bricked ECU - SH Boot Mode help!

Postby parso_rex » Mon Jan 18, 2010 3:21 am

Yep had it on the scope the whole time. I also tried swapping the TX and RX round just incase there was a mistake in the terminology but no change

The watchdog I ended up making another one with a 555 but it didn't have any effect. I could see it on the test pad. I could also see the ECU was recieving power correctly

The weird thing is the Ecuflash prog even when correctly configured for the shboot method still wants that genuine openport cable with valid serial number. The program would not even give me the OK prompt using the ono Tactrix FTDI programmed with the same config (apart from the TX line and DTR logic levels).

Anyway the ECU turned out to be OK. The thing was sent to a very helpful company over here in Australia (Chiptorque)and promptly reflashed using either this or most likely some other more reliable technique. Its now back in the car. Apart from yourself I can't see anyone anywhere who's managed to get this shboot technique to actually work or maybe their are variances between certain processors that require some other steps to be carried out. Could just be me of course :lol:

I'm still very happy with the whole ecuflash openport arrangement it really is an amazing bit of gear

unrelated perhaps but I'm wondering what the boot circuitry on the openport 1.3 board used for
User avatar
parso_rex
 
Posts: 13
Joined: Wed May 25, 2005 2:54 am
Location: Sydney Australia

Re: Bricked ECU - SH Boot Mode help!

Postby parso_rex » Fri Feb 12, 2010 3:44 pm

OK I should update this a bit. It turns out that the donor cable I'd used to construct the interface is faulty. In fact this is most likley the reason for the corrupted upload and hence dead ECU in the first place. What I'm getting at is that after all this mucking around above I may have been attempting to connect using shboot mode with a dead chip the whole time. It may have been working correctly after all. :roll: Anyway I'll wait till another dead ECU comes my way before I have another go. I was sure I'd seen some activity with a cro though.

The dead cable still reads but cannot write/flash for some reason. Its had a hard life though so its being replaced with an Openport 2

Mark

Sydney Au
User avatar
parso_rex
 
Posts: 13
Joined: Wed May 25, 2005 2:54 am
Location: Sydney Australia

Re: Bricked ECU - SH Boot Mode help!

Postby hmanxx » Sat Mar 06, 2010 8:20 am

From your log..it seems to be the Tx line is having problem..if you have scope with you,tap on it..during the initial stage (after Write key activation), you should see some pulse train..if you see pulse train..there is no connectivity problem..in this case..it could be the logic convention.try invert the signal..and try again..

By the way, i have tried the process on 2nd Ecu(wiping off ECutek image),it works perfectly.
hmanxx
 
Posts: 45
Joined: Sat Apr 01, 2006 7:36 pm
Location: Singapore

Re: Bricked ECU - SH Boot Mode help!

Postby PARMPS » Sat Mar 27, 2010 10:54 am

Please help.

I have made FTDI based connection to ecu, but EcuFlash don't want to use it

[20:51:05.015] Using interface FT232R USB UART A6007U92
[20:51:05.015] interface close
[20:51:05.015] unable to connect to vehicle interface.
[20:51:10.750] Using interface FT232R USB UART A6007U92
[20:51:10.750] interface close
[20:51:10.750] unable to connect to vehicle interface.
[20:51:10.906] Using interface FT232R USB UART A6007U92
[20:51:10.906] interface close
[20:51:10.921] unable to connect to vehicle interface.
[20:51:11.062] Using interface FT232R USB UART A6007U92
[20:51:11.062] interface close
[20:51:11.078] unable to connect to vehicle interface.
[20:51:11.218] Using interface FT232R USB UART A6007U92
[20:51:11.218] interface close
[20:51:11.234] unable to connect to vehicle interface.
[20:51:11.406] Using interface FT232R USB UART A6007U92
[20:51:11.406] interface close
[20:51:11.406] unable to connect to vehicle interface.

Oscilloscope didn't see anything on TX(1) pin of FTDI chip. But EcuEdit gives some signals on TX(1) pin. What's wrong?
PARMPS
 
Posts: 2
Joined: Sat Mar 27, 2010 10:29 am

Re: Bricked ECU - SH Boot Mode help!

Postby Sasha_A80 » Sat Mar 27, 2010 12:28 pm

EcuFlash ver. 1.29 was the last working with "unsubcribed" FT232R chip.
Sasha_A80
 
Posts: 102
Joined: Sun Aug 31, 2008 3:04 am
Location: Saratov, Russia

Re: Bricked ECU - SH Boot Mode help!

Postby PARMPS » Sat Mar 27, 2010 5:12 pm

Sasha_A80 wrote:EcuFlash ver. 1.29 was the last working with "unsubcribed" FT232R chip.


There are no SH Boot Mode in 1.29. So i can do this only with Tactrix 1.3?
PARMPS
 
Posts: 2
Joined: Sat Mar 27, 2010 10:29 am

Re: Bricked ECU - SH Boot Mode help!

Postby hmanxx » Sun Apr 11, 2010 5:45 am

According to FAQ of SHBOOT mode..it didnt state that SHBOOTMODE must use tactrix based FTDI module...I understood that for reflash..yes..one need to use it..
hmanxx
 
Posts: 45
Joined: Sat Apr 01, 2006 7:36 pm
Location: Singapore

Re: Bricked ECU - SH Boot Mode help!

Postby Mart » Sat Feb 12, 2011 2:27 pm

that is true. But with File -> Options -> Flashing -> Flash Recovery Mode checked, ecuflash has discover my DLP-USB232M:
(ecuflash 1.42.2595)

[14:54:13.113] Using interface DLP-USB232M DPB3MUOI

so I guess the licensing is disabled for Flash Recovery Mode which is a good thing :)

Mart

Sasha_A80 wrote:EcuFlash ver. 1.29 was the last working with "unsubcribed" FT232R chip.
Mart
 
Posts: 29
Joined: Wed May 14, 2008 5:51 pm

Re: Bricked ECU - SH Boot Mode help!

Postby burnzy » Sun Apr 10, 2011 5:17 am

I'm having a bit of a problem, have used an op1.3 to get the rx and tx pins and joined them to the ecu along with the watchdog signal circuit.
At first it seemed ok with "sending init sync bytes" or something but didn't go through i suspect due to a bad solder join, after reading on here about having to reprogram "serialcomm" I downloaded FTprog and reprogrammed the ftdi chip and clicked un invert rx. After flashing ecuflash just does this
[23:12:14.577] Using interface OpenPort 1.3 Universal TXU9LUJF52383ff100000000000000000000000000000000
[23:12:14.577] interface close
[23:12:14.578] unable to connect to vehicle interface.

Doesn't send init sync bytes like before.

It's already in recovery mode. What could be my problem? I'm thinking ecuflash won't use it as it's not "registered" anymore as with 1.3+ locking out older cables but I thought recovery mode didn't care about that. What else could cause this? any help would be greatly appreciated.
burnzy
 
Posts: 6
Joined: Fri Dec 25, 2009 10:31 pm

Re: Bricked ECU - SH Boot Mode help!

Postby subarutech77 » Sat Apr 16, 2011 6:33 am

Hello, I need help with my Sh boot mode set-up. Long story short, I updated to ecuflash 1.43.3150, it updated the OP2 to a new firmware. EcuFlash was being real buggy on the machine it was on, so I went back to 1.42. Wrong idea. The new driver for the OP2 is not backward compatible and when you try to flash with the latest firmware on the OP2 with an earlier ecuflash, it will brick your ecu. I now have 2 ecms that have been bricked this way. In the ecuflash log it showed no errors and was able to read the rom on the 2nd ecm before I tried to flash it. I have since reupdated to 1.43.3150 in the hopes not to have it brick the ecm again.

I have a shboot mode set-up wired up with the schematic shown over at the tactrix website. One of my problems is I seem to be getting a lot of electical noise through the ground circuit when the ecu is powered up, I don't have a oscilloscope, but have a usb one on the way for my computer, hopefully it will meet my needs. I've tested the timer circuit with a buzzer from radioshack and the pitch changes when the ground circuit is added to the breadboard that the timer is on. Also with the timer circuit not powered up, but with the ground wire connected I see about .5V on the timer output wire, when I supply 5V to the timer circuit, I see 2.5V at the output pin.

Here is a log of an alternate flash attempt:

Code: Select all
[22:16:12.954] Using interface USB <-> Serial
[22:16:14.839] sending bit rate sync bytes...
[22:16:14.839] received bit rate adjust response
sending boot command
[22:16:15.370] received bit rate adjust response
sending boot command
[22:16:15.900] received bit rate adjust response
sending boot command
[22:16:16.431] received bit rate adjust response
sending boot command
[22:16:16.961] received bit rate adjust response
sending boot command
[22:16:17.491] received bit rate adjust response
sending boot command
[22:16:18.022] received bit rate adjust response
sending boot command
[22:16:18.537] received bit rate adjust response
sending boot command
[22:16:19.051] received bit rate adjust response
sending boot command
[22:16:19.566] received bit rate adjust response
sending boot command
[22:16:20.081] received bit rate adjust response
sending boot command
[22:16:20.596] received bit rate adjust response
sending boot command
[22:16:21.111] received bit rate adjust response
sending boot command
[22:16:21.625] received bit rate adjust response
sending boot command
[22:16:22.140] received bit rate adjust response
sending boot command
[22:16:22.655] received bit rate adjust response
sending boot command
[22:16:23.170] received bit rate adjust response
sending boot command
[22:16:23.685] received bit rate adjust response
sending boot command
[22:16:24.199] no bit rate adjust response
[22:16:24.199] interface close


I get the same message if the timer circuit is connected or not. My next thought is to power the 7058 similar to hmanxx here:

viewtopic.php?f=2&t=4310&p=22301#p22301

Some questions I have are:

1. Are the Vcc, PVcc1, and PVcc2 all connected to each other? In the thread above he supplied PVcc1 and PVcc2 with 5v and Vcc with 3.3. Will connecting 5V to one PVcc1 and one PVcc2 pin to supply the voltage work, or will 5V need to be supplied to all the PVcc1 and PVcc2 pins on the chip. Same question applies to the Vcc pin(s).

2. Is there a better way to supply ground so that there is less or no noise coming through the ground circuit? In the schematic on the tactrix website, the grounds look like signal grounds according to the symbols. Should the power supply ground circuit of the ECM and the serial to usb, and the timer circuit share the same ground? Or should they be separate?

Thanks
subarutech77
 
Posts: 9
Joined: Fri Oct 23, 2009 7:46 pm

Re: Bricked ECU - SH Boot Mode help!

Postby hmanxx » Sun Apr 17, 2011 10:00 pm

For my setup, I used PC power supply which come handy with stable +5V and +3.3V. Reading the Renesas Flashing circuit..Vcc(3.3V) indeed is required..

For the grounding ..you need to share the ground of your power source, Notebook and ECU...without that common reference..
Do take note that newer ecu (those post 2007) ecu required Ecuflash v1.43 beta which allowed additional freq multiplier(something like that) otherwise you will get through the initial negotiation phase.

From your message response..it seems to be the problem of ecuflash version..that stuck at the freq multiplier stage

What ecu are you trying to revive..if the chip is SH7058S...this is newer ecu that required Ecuflash v1.43-3150 beta software that comes with the new multiplier setting
hmanxx
 
Posts: 45
Joined: Sat Apr 01, 2006 7:36 pm
Location: Singapore

Re: Bricked ECU - SH Boot Mode help!

Postby subarutech77 » Mon Apr 18, 2011 9:26 am

I am trying to revive an ecm from an 05 USDM FXT. I have taken the ECM back to the vehicle and plugged it into the wiring harness to be sure it was being powered and grounded correctly. Still same result. I should have an oscilloscope this evening to double check signals going to and coming from ECM. I am using 1.43.3150 ecuflash.

Another thing I am unsure about is the usb to serial adapter I am using. I was under the assumption that the vag-com cable circuitry was the same as the one in the tactrix shboot schematic, and all that was needed was the TX/RX lines piggybacked from the vag-com board to the ecm P ports. Is this correct?

I also have a dlp-usb232 protochip on it's way. It should provide a good starting point for the usb adapter, rather than trying to bypass extra circuitry of the vag-com cable.

Thank you for your response.
subarutech77
 
Posts: 9
Joined: Fri Oct 23, 2009 7:46 pm

Re: Bricked ECU - SH Boot Mode help!

Postby subarutech77 » Sat Apr 23, 2011 7:46 am

Thank you, hmanxx. I was able to figure it out and now have it working.
subarutech77
 
Posts: 9
Joined: Fri Oct 23, 2009 7:46 pm

Previous

Return to General Discussion

Who is online

Users browsing this forum: No registered users and 9 guests