Page 1 of 2

tried the reflash

PostPosted: Sat Mar 11, 2006 12:50 pm
by gethin
4.32v programming voltage is too low

what am I doing wrong? Any ideas? I'm flashing the 192Kb file (which should work).

this is an 02 wrx A4SGC00C ecu and I have a UTEC in there too...wonder if that is leeching some voltage?

I've connected the green test connectors and jumpered the 2 connectors in the white block with wire.



190.253] Flashing image to ECU memory...
[0.000] kernel flash disable
[3.095] denso02_bootloader_cmd_start
[0.030] 1452 byte kernel read.
[0.000] kernel checksum is valid (n = 2).
[0.200] writing denso kernel area addr: 020000 len: 05AC
[2.854] kernel get version
[0.030] kernel version is : OpenECU Kernel V0.91
[0.401] 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.340] 00 9E7D9C31 9E7D9C31 YES
[0.351] 01 8F606882 8F606882 YES
[0.330] 02 0216DE1B 0216DE1B YES
[0.341] 03 D3FE83A7 D3FE83A7 YES
[0.330] 04 3ED4232E 3ED4232E YES
[0.321] 05 9B898AB6 9B898AB6 YES
[0.320] 06 939D0A27 939D0A27 YES
[0.351] 07 4BE24516 4BE24516 YES
[0.340] 10 CC471A1C 57C1C10E NO
[0.331] 11 20A51562 C6D6FF9A NO
[0.010] reading ecu programming voltage
[0.030] programming voltage is 4.32 volts
[0.000] programming voltage is too low!

PostPosted: Sat Mar 11, 2006 1:16 pm
by cboles
Do you have an OpenPort 1.2? You need to use the EcuFlash (GUI based) version of the tool. It knows how to switch on the reflash voltage on the OpenPort 1.2. The command line program does not. Really, everyone should use the GUI tool. It's just better.

Colby

PostPosted: Sat Mar 11, 2006 1:28 pm
by gethin
Hi Colby,

Yeah i'm using the GUI version, 1.01.72 dated 2005/11/14 with OpenPort 1.2

Gethin.

PostPosted: Sat Mar 11, 2006 1:42 pm
by cboles
Then I would say that either the jumper or the UTEC wiring isn't right, preventing the reflash voltage from reaching the ECU (the voltage reported comes from an ECU A/D converter). The UTEC probably isn't connected to this wire, but it may not pass it through to the ECU. Have you ever reflashed with this cable? I guess it's possible that the cable is broken, but that would be a first for the OpenPort 1.2. I test the reflash voltage on each of them before packing them up.

Colby

PostPosted: Sat Mar 11, 2006 1:52 pm
by gethin
Ok. It might be the jumper i'm using. I'll get a proper one made up with spades and try again with a properly crimped cable.

If that fails i'll disconnect the UTEC and try again (pain in the butt if that's the case, unless I can wire in a toggle switch!).

Cheers,

Gethin.

WORKED!

PostPosted: Sat Mar 11, 2006 3:10 pm
by gethin
Worked!

I made up a short cable with spades on either end and it worked like a charm, reflashed stock ROM to test, then flashed my modified ROM and worked fine.

The soldered bit of wire I was using obviously was not working.

Great stuff.

Now to test that the CEL is actually defeated........wideband time!

Gethin.

Update. CEL defeated

PostPosted: Sat Mar 11, 2006 5:00 pm
by gethin
Worked! Superb. No more pesky rear o2 CEL!!

Gethin.

PostPosted: Sun Apr 09, 2006 12:31 am
by treefrogaz
Anybody know how to do this for a A4TF800F ECU?

PostPosted: Sun Apr 09, 2006 9:13 am
by gethin
These are the offsets that I replaced on my ROM.

MIL / CEL error P0037 - Rear O2 Sensor Heater Control Circuit Low **
offset 0x0002DBB5 HEX value 030037
MIL / CEL error P0038 - Rear 02 Sensor Heater Control Circuit High **
offset 0x0002DBAD HEX value 030038
MIL / CEL error P0139 - Rear O2 Sensor Circuit Slow Response **
offset 0x0002DAF1 HEX value 030139

I downloaded someone's A4TF800F ECU that they posted in the ROM section and had a peek around for you. I've attached the modified one. Use at your own risk etc. Here's what I changed with 05 00 00 :-

MIL / CEL error P0037 - Rear O2 Sensor Heater Control Circuit Low **
offset 0x0002C575 HEX value 030037
MIL / CEL error P0038 - Rear 02 Sensor Heater Control Circuit High **
offset 0x0002C56D HEX value 030038

The 030139 did not exist in that ROM file. I've attached the file after the above changes, use at your own risk etc.

If you want to check it, just open up your ROM and the modified one in a program called HexCmp (hex compare) and make sure there are only two changes.

PostPosted: Sun Apr 09, 2006 9:44 am
by treefrogaz
cool man thanks i will try it out later on today.

PostPosted: Sun Apr 09, 2006 9:58 am
by Freon
Maybe I'm looking at it wrong, but I looked at your modified ROM and did not see the values "05 00 00" at the offsets you listed. ???

edit: nevermind I see it now...

PostPosted: Sun Apr 09, 2006 5:05 pm
by treefrogaz
Also do you guys know how to do it to this ecu A4TF300F and were did you find the offsets for the CELs

PostPosted: Sun Apr 09, 2006 5:43 pm
by gethin
Did it work?

You search for the HEX string using a HEX editor.

PostPosted: Sun Apr 09, 2006 5:49 pm
by treefrogaz
I have tried it on the A4TF800F ECU yet im waiting on my buddy to get here with it but my friend is he now with his wagon with the A4TF300F ecu and his cel is on for 02.

PostPosted: Sun Apr 09, 2006 6:05 pm
by gethin
I've dug up a copy of A4TF300F and i'll post a fix for you.