Unable to read programming voltage?

[yobtah]

I have a 2003 WRX, and I can correctly read from the ECU using a Cobb cable and an FTDI USB serial adapter. When I try to test flash an image, the test always fails with an "unable to read programming voltage" error. I've read some posts here saying that the Cobb cable may be too slow to properly communicate with the ECU. Is that the case here? It doesn't seem likely to me because EcuFlash is reading and comparing ECU data with the stored file. I've included an example log below.


[5.110] Test flashing image to ECU memory...
[0.000] kernel flash disable
[0.031] found oecu kernel!
[0.000] kernel already resident - skipping kernel load
[1.000] kernel get version
[0.031] kernel version is : OpenECU Kernel V0.91
[0.406] comparing ECU flash memory pages to image file
[0.000] comparing ECU flash memory pages to image file
[0.000] page ecu CRC32 img CRC32 same?
[0.329] 00 8051C4DE 19358932 NO
[0.343] 01 6E84A93E 7FEB9078 NO
[0.328] 02 C949D99B C949D99B YES
[0.344] 03 8D2E0634 FFF36C0E NO
[0.328] 04 71FA9AE0 F6AE956A NO
[0.344] 05 F7FE16D8 92ED48B7 NO
[0.328] 06 56326D4C 56326D4C YES
[0.344] 07 1675D4F1 32273D64 NO
[0.328] 10 9A6BBDA8 99A26C43 NO
[0.344] 11 BDA09DD6 82BDA8E1 NO
[0.000] reading ecu programming voltage
[0.000] rkrv: preamble 1 error
[0.000] unable to read programming voltage!

[fastchip]

Assuming you have the test connectors connected.
The cable needs to provide a 12V regulated programming voltage on OBD pin 11.

[yobtah]

Yeah... test connectors are connected.

Sounds like providing 12V on pin 11 is something the Tactrix cable does correctly and the Cobb cable does not?

[Jeramie]

Yeah... test connectors are connected.

Sounds like providing 12V on pin 11 is something the Tactrix cable does correctly and the Cobb cable does not?

You are correct, thats what makes the tactrix cable special!

[cboles]

The error you are getting actually has nothing to do with the programming voltage. You are getting a communication error, perhaps due to poor communications at the higher baud rate with the AP cable. It is a little strange though, as other communications at this same baud rate are working. I just haven't heard of anyone getting this problem with the Tactrix cable.

Colby

I have a 2003 WRX, and I can correctly read from the ECU using a Cobb cable and an FTDI USB serial adapter. When I try to test flash an image, the test always fails with an "unable to read programming voltage" error. I've read some posts here saying that the Cobb cable may be too slow to properly communicate with the ECU. Is that the case here? It doesn't seem likely to me because EcuFlash is reading and comparing ECU data with the stored file. I've included an example log below.


[5.110] Test flashing image to ECU memory...
[0.000] kernel flash disable
[0.031] found oecu kernel!
[0.000] kernel already resident - skipping kernel load
[1.000] kernel get version
[0.031] kernel version is : OpenECU Kernel V0.91
[0.406] comparing ECU flash memory pages to image file
[0.000] comparing ECU flash memory pages to image file
[0.000] page ecu CRC32 img CRC32 same?
[0.329] 00 8051C4DE 19358932 NO
[0.343] 01 6E84A93E 7FEB9078 NO
[0.328] 02 C949D99B C949D99B YES
[0.344] 03 8D2E0634 FFF36C0E NO
[0.328] 04 71FA9AE0 F6AE956A NO
[0.344] 05 F7FE16D8 92ED48B7 NO
[0.328] 06 56326D4C 56326D4C YES
[0.344] 07 1675D4F1 32273D64 NO
[0.328] 10 9A6BBDA8 99A26C43 NO
[0.344] 11 BDA09DD6 82BDA8E1 NO
[0.000] reading ecu programming voltage
[0.000] rkrv: preamble 1 error
[0.000] unable to read programming voltage!

[brisance]

Tried using 2 separate Tactrix cables on an 04 EDM WRX...

Code: Select all

[00:01:17.201] Version 1.28.716
[00:01:17.211] 8 memory models read.
[00:01:17.501] 71 ROM metadata models read.
[00:01:17.501] checksum module "subarudbw" loaded.
[00:01:17.501] flashing tool "wrx02" loaded.
[00:01:17.501] flashing tool "wrx04" loaded.
[00:01:17.501] flashing tool "sti04" loaded.
[00:01:17.501] flashing tool "sti05" loaded.
[00:01:17.501] flashing tool "mitsukernel" loaded.
[00:01:17.501] flashing tool "mitsukernelocp" loaded.
[00:01:17.501] flashing tool "mitsubootloader" loaded.
[00:01:21.236] 163840 byte image read.
[00:01:25.052] denso02_bootloader_cmd_start
[00:01:26.294] denso02_bootloader_cmd_start
[00:01:26.544] writing denso kernel area addr: 020000 len: 0600
[00:01:28.417] kernel get version
[00:01:28.447] kernel version is : OpenECU Subaru HC16 Kernel V1.01
[00:01:28.467] Flashing image to ECU memory...
[00:01:28.877] comparing ECU flash memory pages to image file
[00:01:28.877] segment   len   ecu CRC32    img CRC32    same?
[00:01:29.198] FB01 00004000   71841F03     71841F03     YES
[00:01:29.538] FB02 00004000   FEB3CD5F     FEB3CD5F     YES
[00:01:29.879] FB03 00004000   0DE09419     0DE09419     YES
[00:01:30.209] FB04 00004000   7410712A     7410712A     YES
[00:01:30.550] FB05 00004000   4A7D58C0     4A7D58C0     YES
[00:01:30.880] FB06 00004000   A574C18F     A574C18F     YES
[00:01:31.221] FB07 00004000   9A20492F     9A20492F     YES
[00:01:31.551] FB08 00004000   D5BD462E     D5BD462E     YES
[00:01:31.892] FB09 00004000   E1D93FB8     63CC0F7D      NO
[00:01:32.222] FB10 00004000   8EE08A33     8EE08A33     YES
[00:01:32.523] reading ecu programming voltage
[00:01:34.545] unable to read programming voltage!

Able to pull the ROM, but unable to write back to it. Tried to reboot, reinstall software/drivers etc to no avail.

[Jeramie]

Did you have a flash block connected? Looks like everything was ok till it trying to write (which is where it needs power, which comes from the flash block)?

[cboles]

if you do a ROM read immediately after this flash failure without turning the car off, does the kernel still respond?

colby

[brisance]

Did you have a flash block connected? Looks like everything was ok till it trying to write (which is where it needs power, which comes from the flash block)?

The flash block is the 4-pin connector, correct? That has been connected. And the green test connectors are connected as well.

[Jeramie]

Did you have a flash block connected? Looks like everything was ok till it trying to write (which is where it needs power, which comes from the flash block)?

The flash block is the 4-pin connector, correct? That has been connected. And the green test connectors are connected as well.

Yep thats what I was talking about.

cboles is the one you want to answer. .. if there is anyone that can help you it's him

[brisance]

if you do a ROM read immediately after this flash failure without turning the car off, does the kernel still respond?

colby

Yes it does.

Code: Select all

[15:20:08.075] denso02_bootloader_cmd_start
[15:20:09.306] denso02_bootloader_cmd_start
[15:20:09.747] writing denso kernel area addr: 020000 len: 0600
[15:20:11.600] kernel get version
[15:20:11.640] kernel version is : OpenECU Subaru HC16 Kernel V1.01
[15:20:11.640] Flashing image to ECU memory...
[15:20:12.040] comparing ECU flash memory pages to image file
[15:20:12.040] segment   len   ecu CRC32    img CRC32    same?
[15:20:12.371] FB01 00004000   71841F03     71841F03     YES
[15:20:12.711] FB02 00004000   FEB3CD5F     FEB3CD5F     YES
[15:20:13.062] FB03 00004000   0DE09419     0DE09419     YES
[15:20:13.402] FB04 00004000   7410712A     7410712A     YES
[15:20:13.753] FB05 00004000   4A7D58C0     4A7D58C0     YES
[15:20:14.103] FB06 00004000   A574C18F     A574C18F     YES
[15:20:14.454] FB07 00004000   9A20492F     9A20492F     YES
[15:20:14.804] FB08 00004000   D5BD462E     D5BD462E     YES
[15:20:15.155] FB09 00004000   E1D93FB8     63CC0F7D      NO
[15:20:15.495] FB10 00004000   8EE08A33     8EE08A33     YES
[15:20:15.806] reading ecu programming voltage
[15:20:17.839] unable to read programming voltage!
[15:20:27.783] denso02_bootloader_cmd_start
[15:20:28.995] denso02_bootloader_cmd_start
[15:20:30.226] denso02_bootloader_cmd_start
[15:20:31.458] denso02_bootloader_cmd_start
[15:20:32.670] denso02_bootloader_cmd_start
[15:20:33.100] kernel get version
[15:20:33.151] found oecu kernel!
[15:20:33.151] kernel already resident - skipping kernel load
[15:20:33.251] kernel get version
[15:20:33.291] kernel version is : OpenECU Subaru HC16 Kernel V1.01
[15:20:33.301] Dumping ECU memory...
[15:20:33.341] kernel read area: addr: 00000000 len: 0400
[15:20:33.711] kernel read area: addr: 00000400 len: 0400
[15:20:34.062] kernel read area: addr: 00000800 len: 0400
[15:20:34.422] kernel read area: addr: 00000C00 len: 0400
[15:20:34.783] kernel read area: addr: 00001000 len: 0400
[15:20:35.143] kernel read area: addr: 00001400 len: 0400
[15:20:35.514] kernel read area: addr: 00001800 len: 0400
... truncated ...

Immediately trying to flash it after a read yields the same error.

Trying to flash it with the same ROM that was read gives the following output:

Code: Select all

[15:22:00.877] denso02_bootloader_cmd_start
[15:22:02.088] denso02_bootloader_cmd_start
[15:22:03.300] denso02_bootloader_cmd_start
[15:22:04.532] denso02_bootloader_cmd_start
[15:22:05.764] denso02_bootloader_cmd_start
[15:22:06.214] kernel get version
[15:22:06.244] found oecu kernel!
[15:22:06.254] kernel already resident - skipping kernel load
[15:22:06.355] kernel get version
[15:22:06.385] kernel version is : OpenECU Subaru HC16 Kernel V1.01
[15:22:06.395] Flashing image to ECU memory...
[15:22:06.795] comparing ECU flash memory pages to image file
[15:22:06.805] segment   len   ecu CRC32    img CRC32    same?
[15:22:07.136] FB01 00004000   71841F03     71841F03     YES
[15:22:07.486] FB02 00004000   FEB3CD5F     FEB3CD5F     YES
[15:22:07.827] FB03 00004000   0DE09419     0DE09419     YES
[15:22:08.177] FB04 00004000   7410712A     7410712A     YES
[15:22:08.508] FB05 00004000   4A7D58C0     4A7D58C0     YES
[15:22:08.848] FB06 00004000   A574C18F     A574C18F     YES
[15:22:09.189] FB07 00004000   9A20492F     9A20492F     YES
[15:22:09.519] FB08 00004000   D5BD462E     D5BD462E     YES
[15:22:09.860] FB09 00004000   E1D93FB8     E1D93FB8     YES
[15:22:10.210] FB10 00004000   8EE08A33     8EE08A33     YES
[15:22:10.210] flash image is identical! exiting.

[Phatlines]

not sure if you still have this issue, but check to see if your getting 12v on the 16th pin on your OBDII. Thats where I would start =) after that, have your OBDII plugged in and check under your dash where you connect the flash block and check to see what kind of voltage your getting to your ECU. The Red/White calbe provides the 12v to the ECU on 02 and 03 wrx's

[brisance]

not sure if you still have this issue, but check to see if your getting 12v on the 16th pin on your OBDII. Thats where I would start =) after that, have your OBDII plugged in and check under your dash where you connect the flash block and check to see what kind of voltage your getting to your ECU. The Red/White calbe provides the 12v to the ECU on 02 and 03 wrx's

Tested the OBDII pin 16... there's 12V on it, so that can be ruled out.

[peewee]

Did you try to reset the ecu by disconnect the battery?
I have the same problem once and this did the yob.
Still don't know why.....

Paul.

[brisance]

Did you try to reset the ecu by disconnect the battery?
I have the same problem once and this did the yob.
Still don't know why.....

Paul.

Yes I've tried this as well, disconnected and left it overnight... didn't work.