RomRaider

Tried bootloader test software on win32, with moded ft232 cable. Not work for me... with fxt02.
But friend successfully tested it on win64. Maybe there is some difference with I/O between win32 and 64?

Maybe I need to install 32-bit win7 to compile software for windows if that's one problem too... Software is compiled in 32-bit mode and should work in 32-bit windows but who knows...

Today I manage to get access to bootloader in windows and start the kernel upload. Found at least one prob more to solve with OP2, but will do it tonight.

Now it is tested on 64-bit Win7, software compiled with 32-bit compiler. Fxt02 method works with both OP2 and modded OBD cable.

Funny, bootloader test software had prog voltage pulse of 212ms (as I was told that 207.9-227.7ms is what ECU wants and that can be calculated from ROM code) and that worked also with new software but only with modded OBD cable. I had to change it to 200ms to access bootloader with OP2 cable. In 16-bit ECUs it is 200ms too in ECUFlash, so maybe it really is 200ms.

@SergArb: Is your cable tested with win64 that it really works? Cause if it is Windows problem, then I need to install 32-bit Win7 to compile software for future versions. And if you can test this new software with both cables (OBD and OP2), that would be nice.

I went back and checked the pulse length.

It is between 0x33 and 0x45 WDT pulses of 3.3ms. Looks like I accidentally converted 0x33 into 63 (octal) when it should have been 51 (decimal). Must have been a late night!

So, the correct pulse length is between 51 and 69 x 3.3ms = 168.3ms to 227.7ms. The middle of this range is 198ms, very close to 200ms.

Interestingly, 212ms should still work but perhaps the OP2 is not as good as producing a sharp pulse...

There is another window which means a pulse length of ~700ms should also work.

I have only win32 system on my laptop. Unfortunately these Foresters a rare guests... Will be waiting for another one))

Did it give any errors or warning or is it just it cannot access to bootloader? If it cannot access bootloader, can you test new software found in github precompiled folder.

No errors, only bad response from bootloader. Downloded new version, need to wait for fxt car.

More updates to FastECU software:

https://www.syvanenmotorsport.fi/forum/ ... sg32#msg32
https://github.com/miikasyvanen/fastecu-oem

Registered on your forum

Some bugfixes and sti05 flashmethod confirmed.

https://www.syvanenmotorsport.fi/forum/ ... sg16#msg16

Very cool project!

If you need some testing for the WA12212930 chip ECU, I can do it for you.

Recently tried to get nisprog running with my 2004 EZ30 Liberty (SH7055), however I always get a set of errors whilst using a Tactrix cable, and yet to read if anyone has had any luck connecting using a Tactrix. Do you guys reckon these errors are related to the Tactrix? If so I'll go grab a cheap VAG-COM and try that, but just want to confirm it's most likely the Tactrix before I go get one. Linked is the text file of my log and errors.
Cheers

As far as I understand, nisprog doesn't support tactrix cable. Why not just test my software? It works with tactrix cable.

Thanks!

I would like to first add unbricking method for these ECUs. I have few extra WA12212920 to play with, and as soon as I have that working, I'll start to add others.

hello everyone, today I managed to read the firmware from my forester cs using a vag kkl cable(ch340). but it turned out only fastecu, subaru bootloader from the first post gives an error. win7 32
fastecu write test - ok
tomorrow I'll try to write it down, today I was afraid to block the ecu

where can i find defs for romraider?


Thanks for your work, it's a big job