Flashing the 4G69
Newbie
Joined: Feb 2006
Posts: 10
Likes: 0
From: PR
Any news on this subject? Did someone get through the Boot Loader issue? Anything that you think I can do count on me, I Have a OpenPort 1.3M cable, if it has to be modified to test something just tell me, i am electronics/software savvy so I'm willing to take the risks, I can even get a spare ECU, So far i can tell you that this ECU has the VIN embedded because i could pull it with OBD Scan Tech (OBD-Generic) and it indeed was my actual VIN.
Newbie
Joined: Feb 2006
Posts: 10
Likes: 0
From: PR
kernel
Well I've done som reading lately and I think that our problem relies on the development of the H8 Kernel, been reading about this on openecu, It seems hat our ECU's processor is from the H8 family (Correct me if i'm wrong), Colby promised a Kernel for H8 for September 2006 But it looks that hasn't been possible, there is a post from someone with custom code that could read H8 processor ECU's if some one has access to this tool or if someone (Maybe Colby himself) has this kernel I'm willing to try it.
Newbie
Joined: Feb 2006
Posts: 10
Likes: 0
From: PR
Folks, I've been playing a few minutes ago with ecuflash 1.29 as 1.30 says can not connect to vehicle interface.
with 1.29 this is what I could get, selecting Read form ECU Evo 7/8 and Evo 9
At least I could get a reply, Hope this helps
If i Disconnect the white connector nothing happens.
[01:06:03.619] Version 1.29.906
[01:06:03.639] 8 memory models read.
[01:06:05.892] 146 ROM metadata models read.
[01:06:05.892] checksum module "subarudbw" loaded.
[01:06:05.892] flashing tool "wrx02" loaded.
[01:06:05.892] flashing tool "wrx04" loaded.
[01:06:05.892] flashing tool "sti04" loaded.
[01:06:05.892] flashing tool "sti05" loaded.
[01:06:05.892] flashing tool "mitsukernel" loaded.
[01:06:05.892] flashing tool "mitsukernelocp" loaded.
[01:06:05.892] flashing tool "mitsubootloader" loaded.
[01:06:17.018] sending init sequence 1 (0001)
[01:06:18.040] got 0x05 response
[01:06:18.040] sending init sequence 2
with 1.29 this is what I could get, selecting Read form ECU Evo 7/8 and Evo 9
At least I could get a reply, Hope this helps
If i Disconnect the white connector nothing happens.[01:06:03.619] Version 1.29.906
[01:06:03.639] 8 memory models read.
[01:06:05.892] 146 ROM metadata models read.
[01:06:05.892] checksum module "subarudbw" loaded.
[01:06:05.892] flashing tool "wrx02" loaded.
[01:06:05.892] flashing tool "wrx04" loaded.
[01:06:05.892] flashing tool "sti04" loaded.
[01:06:05.892] flashing tool "sti05" loaded.
[01:06:05.892] flashing tool "mitsukernel" loaded.
[01:06:05.892] flashing tool "mitsukernelocp" loaded.
[01:06:05.892] flashing tool "mitsubootloader" loaded.
[01:06:17.018] sending init sequence 1 (0001)
[01:06:18.040] got 0x05 response
[01:06:18.040] sending init sequence 2
Last edited by wiredboy; Apr 29, 2007 at 07:36 PM.
Some new information that might be useful.
I was discussing some of this stuff a few weeks back with Colby, it seems that the new generation Mitsubishi ECU's are CAN bus. Which means they aren't compatible with the current Tactrix cable (or any older style OBD-II cable)
I don't know for sure if this is indeed the case for the Ralliart Lancer, but the new Mivec motor does use a new ECU in the Ralliart.
If someone locally or has access to a cable, with a newer MIVEC Ralliart I'd like to see if the logger can connect, and if regular ISO OBD-II can connect.
Not that any of this information is very accurate, only a bit of logic after seeing the new generation of cars mitsubishi is releasing which appear to use a new ECU that utilizes CAN bus.
I was discussing some of this stuff a few weeks back with Colby, it seems that the new generation Mitsubishi ECU's are CAN bus. Which means they aren't compatible with the current Tactrix cable (or any older style OBD-II cable)
I don't know for sure if this is indeed the case for the Ralliart Lancer, but the new Mivec motor does use a new ECU in the Ralliart.
If someone locally or has access to a cable, with a newer MIVEC Ralliart I'd like to see if the logger can connect, and if regular ISO OBD-II can connect.
Not that any of this information is very accurate, only a bit of logic after seeing the new generation of cars mitsubishi is releasing which appear to use a new ECU that utilizes CAN bus.
If the tactrix cable is not capable of connecting, then its a matter of rewiring for the OBD connect. I would also be kind of surprized if this was the case.
Newbie
Joined: Feb 2006
Posts: 10
Likes: 0
From: PR
The tactrix cable should be able to connect. Ultimately, it's just a serial device. But from what I have learned, anything on the CAN bus is likely using IS0-9141 (KW2000) protocol to communicate with the devices on the CAN bus.
If the tactrix cable is not capable of connecting, then its a matter of rewiring for the OBD connect. I would also be kind of surprized if this was the case.
If the tactrix cable is not capable of connecting, then its a matter of rewiring for the OBD connect. I would also be kind of surprized if this was the case.
Last edited by wiredboy; Apr 29, 2007 at 07:34 PM.
In fact this ECU isn't CAN Bus, It is OBDII using protocol ISO-9141 and as I stated In my previous post, I got a reply from ECU using Open Port 1.3M Cable when trying to read from ECU, I don't know much about the Technical Steps involved in ECU Flashing but based on the fact that ECU Acknowledged some request I believe that as MalibuJack said before that the issue we are facing right now relies on the boot loader. I even tried to read with the engine running and soon after the acknowledge the engine stalled, so i think that the ECU has resetted and I believe this is a good sign.
I got the wrong ISO number, but in general, the implementation of the CAN bus implies that we can't use the existing communication methods in ECUflash. It's a different protocol layered on top of the OBD-II layer as far as I am aware of.
Well I've done som reading lately and I think that our problem relies on the development of the H8 Kernel, been reading about this on openecu, It seems hat our ECU's processor is from the H8 family (Correct me if i'm wrong), Colby promised a Kernel for H8 for September 2006 But it looks that hasn't been possible, there is a post from someone with custom code that could read H8 processor ECU's if some one has access to this tool or if someone (Maybe Colby himself) has this kernel I'm willing to try it.
Has anyone been able to identify the person with custom code, or verify if our processor is H8 or not?
