Not able to pull rom image Ecuflash MY02 WRX

[TheHighestCrew]

Mods this is a repost of what I posted in the general forum if that was incorrect please delete that post.

I just got my tactrix 2.0 cable and flash block for MY02 wrx. Tried connecting and kept getting the same error over and over. Had all the latest definitions in romraider, everything was set up how it should be. I am running windows 7 64 bit ultimate. I went ahead and followed the directions on this link http://www.romraider.com/Documentation/ ... rFAQ#toc39 Exactly. Step by step every reboot and step in the exact order. Now I try to download my rom and get the same error. When I first connected after following that procedure it seemed for a moment that it would pull the rom saw a few characters I hadn't previously, but sure enough it failed again. it is getting very frustrating after following all the romraider and ecuflash troubleshooting guides. I searched for similar problems and some seemed to solve it by following the FAQ steps for windows vista/7. Does anyone have any insight into this issue? I have pasted the full log below that was created after completing the romraider W7 install guide...


[22:11:50.142] EcuFlash Version 1.43.3150
[22:11:50.142] OS Version Windows 7
[22:11:50.142] Qt Version 4.6.2
[22:11:50.158] 62 memory models read.
[22:11:50.158] scanning for metadata models in C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata
[22:11:54.495] 354 ROM metadata models scanned.
[22:11:54.495] checksum module "subarudbw" loaded.
[22:11:54.495] checksum module "mitsucan" loaded.
[22:11:54.495] checksum module "mitsuh8" loaded.
[22:11:54.495] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[22:11:54.495] patch module "Mitsu CAN RAM Parameter Logging" loaded.
[22:11:54.495] flashing tool "wrx02" loaded.
[22:11:54.495] flashing tool "wrx04" loaded.
[22:11:54.495] flashing tool "sti04" loaded.
[22:11:54.495] flashing tool "sti05" loaded.
[22:11:54.495] flashing tool "mitsukernel" loaded.
[22:11:54.495] flashing tool "mitsukernelocp" loaded.
[22:11:54.495] flashing tool "mitsubootloader" loaded.
[22:11:54.495] flashing tool "shbootmode" loaded.
[22:11:54.604] flashing tool "shaudmode" loaded.
[22:11:54.604] flashing tool "subarucan" loaded.
[22:11:54.604] flashing tool "mitsucan" loaded.
[22:12:54.820] reading firmware
[22:12:54.851] flash file version is 1.11.3137
[22:12:55.069] main code version : 1.10.3020
[22:12:55.069] waiting for bootloader (may be installing drivers)... press any key to abort
[22:13:07.206] connecting to bootloader on \
[22:13:07.237] tri bootloader version : 1.00.1923
build date : Jul 31 2008
build time : 18:07:47
IAP boot code version : 03.03
part ID : 1600F902
code protection : 87654321
serial number : TAwpJoSR
[22:13:08.283] ---erasing---
[22:13:08.392] erasing 1
[22:13:08.501] erasing 2
[22:13:08.610] erasing 3
[22:13:08.704] ---writing---
[22:13:08.735] writing 1k
[22:13:08.766] writing 2k
[22:13:08.797] writing 3k
[22:13:08.829] writing 4k
[22:13:08.891] writing 5k
[22:13:08.922] writing 6k
[22:13:08.953] writing 7k
[22:13:08.985] writing 8k
[22:13:09.016] writing 9k
[22:13:09.047] writing 10k
[22:13:09.078] writing 11k
[22:13:09.109] writing 12k
[22:13:09.141] writing 13k
[22:13:09.172] writing 14k
[22:13:09.203] writing 15k
[22:13:09.234] writing 16k
[22:13:09.265] writing 17k
[22:13:09.297] writing 18k
[22:13:09.328] writing 19k
[22:13:09.359] writing 20k
[22:13:09.390] writing 21k
[22:13:09.421] writing 22k
[22:13:09.453] writing 23k
[22:13:09.484] writing 24k
[22:13:09.515] writing 25k
[22:13:09.546] writing 26k
[22:13:09.577] writing 27k
[22:13:09.609] writing 28k
[22:13:09.640] writing 29k
[22:13:09.671] writing 30k
[22:13:09.702] writing 31k
[22:13:09.733] writing 32k
[22:13:09.765] writing 33k
[22:13:09.796] writing 34k
[22:13:09.827] writing 35k
[22:13:09.858] writing 36k
[22:13:09.889] writing 37k
[22:13:09.921] writing 38k
[22:13:09.952] writing 39k
[22:13:09.983] writing 40k
[22:13:10.014] writing 41k
[22:13:10.045] writing 42k
[22:13:10.077] writing 43k
[22:13:10.108] writing 44k
[22:13:10.139] writing 45k
[22:13:10.170] writing 46k
[22:13:10.201] writing 47k
[22:13:10.233] writing 48k
[22:13:10.264] writing 49k
[22:13:10.295] writing 50k
[22:13:10.326] writing 51k
[22:13:10.357] writing 52k
[22:13:10.389] writing 53k
[22:13:10.420] writing 54k
[22:13:10.451] writing 55k
[22:13:10.482] writing 56k
[22:13:10.513] writing 57k
[22:13:10.545] writing 58k
[22:13:10.576] writing 59k
[22:13:10.607] writing 60k
[22:13:10.638] writing 61k
[22:13:10.669] writing 62k
[22:13:10.701] writing 63k
[22:13:10.732] writing 64k
[22:13:10.763] writing 65k
[22:13:10.794] writing 66k
[22:13:10.826] writing 67k
[22:13:10.857] writing 68k
[22:13:10.904] flash complete!!!
[22:13:14.944] J2534 API Version: 04.04
[22:13:14.944] J2534 DLL Version: 1.00.3147 Sep 3 2010 00:11:07
[22:13:14.944] Device Firmware Version: 1.11.3137
[22:13:14.944] Device Serial Number: TAwpJoSR
[22:13:25.629] interface close
[22:14:26.433] J2534 API Version: 04.04
[22:14:26.433] J2534 DLL Version: 1.00.3147 Sep 3 2010 00:11:07
[22:14:26.433] Device Firmware Version: 1.11.3137
[22:14:26.433] Device Serial Number: TAwpJoSR
[22:14:47.510] denso02_bootloader_cmd_start
[22:14:48.742] denso02_bootloader_cmd_start
[22:14:49.975] denso02_bootloader_cmd_start
[22:14:51.207] denso02_bootloader_cmd_start
[22:14:52.440] denso02_bootloader_cmd_start
[22:14:52.861] kernel get version
[22:14:53.173] interface close
[22:14:53.188] interface close



Every time I connect I always get this error. this is the one that was happening before I followed the windows 7 install guide step by step, and now it continues after:


[22:14:47.510] denso02_bootloader_cmd_start
[22:14:48.742] denso02_bootloader_cmd_start
[22:14:49.975] denso02_bootloader_cmd_start
[22:14:51.207] denso02_bootloader_cmd_start
[22:14:52.440] denso02_bootloader_cmd_start
[22:14:52.861] kernel get version
[22:14:53.173] interface close
[22:14:53.188] interface close



any help would be much appreciated, thanks!

[TheHighestCrew]

So I am reading around and I see that some people have issues with the flash blocks no being completely connected so I am going to make sure the reflash adapter and green plugs are connected very well and look for broken links or pulled pins. hopefully it was a bad connection, I am going to try again after work.

[TheHighestCrew]

Sweet, I got home and checked it out, looks like I had a wire coming lose on one of the green connectors. Fixed the wire and it pulled the rom right away!! So stoked, now I can sit here and go through table after table!

[radsdau]

Well found, that wouldn't have been immediately obvious.