Test Write and Writing to ECU Error

[bkknight]

Can any bro out there help me out with this. I have just edite the maps and I would like to save it into my EVO IX ECU. I started of with reading from the rom with ecuflash, no problem it just works like a charm. The problem comes when I was trying to write the edited maps back into the rom. The this the error log after test write. Please help

[02:02:43.750] sending init sequence 1 (0001)
[02:02:47.015] sending init sequence 1 (0003)
[02:02:50.281] sending init sequence 1 (FFFF)
[02:02:53.015] no response to any known code
[02:03:05.921] sending init sequence 1 (0001)
[02:03:06.968] got 0x05 response
[02:03:06.984] sending init sequence 2
[02:03:07.000] got 0x1B response
[02:03:07.015] sending init sequence 3
[02:03:07.406] entering bootloader
[02:03:07.437] sending kernel size (3424)
[02:03:07.484] sending kernel load address (0xFFFF6000)
[02:03:07.531] uploading kernel
[02:03:08.093] verifying kernel checksum response
[02:03:08.109] kernel valid
[02:03:08.328] kernel get version
[02:03:08.328] rkrv: preamble 1 error

[spooky]

hey...same thing that hapen to me as well...was about to post when i see your topic....

any gurus out there can assist?

Can any bro out there help me out with this. I have just edite the maps and I would like to save it into my EVO IX ECU. I started of with reading from the rom with ecuflash, no problem it just works like a charm. The problem comes when I was trying to write the edited maps back into the rom. The this the error log after test write. Please help

[02:02:43.750] sending init sequence 1 (0001)
[02:02:47.015] sending init sequence 1 (0003)
[02:02:50.281] sending init sequence 1 (FFFF)
[02:02:53.015] no response to any known code
[02:03:05.921] sending init sequence 1 (0001)
[02:03:06.968] got 0x05 response
[02:03:06.984] sending init sequence 2
[02:03:07.000] got 0x1B response
[02:03:07.015] sending init sequence 3
[02:03:07.406] entering bootloader
[02:03:07.437] sending kernel size (3424)
[02:03:07.484] sending kernel load address (0xFFFF6000)
[02:03:07.531] uploading kernel
[02:03:08.093] verifying kernel checksum response
[02:03:08.109] kernel valid
[02:03:08.328] kernel get version
[02:03:08.328] rkrv: preamble 1 error

[spooky]

anybody can assist this issue????

hey...same thing that hapen to me as well...was about to post when i see your topic....

any gurus out there can assist?

Can any bro out there help me out with this. I have just edite the maps and I would like to save it into my EVO IX ECU. I started of with reading from the rom with ecuflash, no problem it just works like a charm. The problem comes when I was trying to write the edited maps back into the rom. The this the error log after test write. Please help

[02:02:43.750] sending init sequence 1 (0001)
[02:02:47.015] sending init sequence 1 (0003)
[02:02:50.281] sending init sequence 1 (FFFF)
[02:02:53.015] no response to any known code
[02:03:05.921] sending init sequence 1 (0001)
[02:03:06.968] got 0x05 response
[02:03:06.984] sending init sequence 2
[02:03:07.000] got 0x1B response
[02:03:07.015] sending init sequence 3
[02:03:07.406] entering bootloader
[02:03:07.437] sending kernel size (3424)
[02:03:07.484] sending kernel load address (0xFFFF6000)
[02:03:07.531] uploading kernel
[02:03:08.093] verifying kernel checksum response
[02:03:08.109] kernel valid
[02:03:08.328] kernel get version
[02:03:08.328] rkrv: preamble 1 error

[MalibuJack]

This has been documented before..

Typically this is due to low battery voltage, or some parasitic load, try putting a battery charger on the car while flashing and see if that helps.

[spooky]

o..ok....thanks dude...will try it and revert with a reply once it is done..

thanks!!!

This has been documented before..

Typically this is due to low battery voltage, or some parasitic load, try putting a battery charger on the car while flashing and see if that helps.

[cboles]

have you had success now?

[spooky]

have you had success now?

Hi cboles,

I still cant write back to the e9 ecu...sigh....

at first i thought it only hapen to one particular e9...but than i tried my other friend's e9 but to no avail...

HELP....

[cboles]

can you read from the Evo9?

[spooky]

Hi cboles,

I can download & read the rom image from the evo9...

i can ammend the parameters within the rom image but once i try to flash it back to the original ecu, the same error message appears as of this thread. I have tried reflashing back 3 evo9 but still of no help.

Any advise?

can you read from the Evo9?

[MalibuJack]

Have you tried the same cable in a different machine? And tested it on an Evo8?

It sounds like a driver problem, even possibly a problem with the cable, but I would test it on another computer first.

[spooky]

Hi jack,

I have not tried the cable with a different laptop though. My OS is MS WinXP Pro ver 2002 service pack 2 with all the .Net installed though.

It works beautifully for both evo7 & evo8 but once i tried on evo9, i got this error msg.

i will try to test it with another laptop though... will keep u inform as well..but if on another laptop & it works for evo9 than it will troublesome for me to keep switching the two laptops, needless to say carry two laptops at one go..hahaha..

thanks!

Have you tried the same cable in a different machine? And tested it on an Evo8?

It sounds like a driver problem, even possibly a problem with the cable, but I would test it on another computer first.

[MalibuJack]

Understood, but if the problem is the laptop, at least you can narrow it down to drivers or an OS issue, its easier to back up your important data and rebuild the laptop, or just upgrade.

I have had some issues with older laptops that were a bit slower, and had very early USB ports, but nothing like what you'd describe.

A suggestion for you and your laptop, disable everything that could cause disk access in the background, such as Hard disk protection (software built into the hardware, or software included with the laptop) For the time being, disable any spyware and virus scan tools..

There is a possibility something is preventing something from loading. Why it would work on the EVO7 or EVO8 ecu's and not the 9 is a bit weird, but we have seen the Evo9 ECU be quite sensitive to battery voltage, I wouldn't be surprised if it was also sensitive to timing or other issues.

Now, here's a really silly question, but there is some logic behind this..

1) Do you have any additional hardware tapped into the ECU harness? Something powered off that harness for instance?

2) Do you have a wideband setup that is powered on all the time when the ignition is turned on?

The reason I ask this is knowing the ECU is sensitive, and some troublesome cars need to keep a charger on the battery (or have a really well charged battery) for the reflashing to work sucessfully, perhaps there is something that is drawing alot of current at just the wrong time. For instance the heater in your wideband O2 sensor, or whatnot, or a turbo timer, or amplifiers. Its easy enough to disconnect some of that stuff or wire a switch into some of it to disable things if it proves to be the problem.

I have to admit, your issue is very unique, and if you can read and write an evo8 ECU correctly, then odds are very high the software is okay, the drivers are okay, the cable is okay, but something is interrupting the communications, or causing the 9's ECU to become annoyed.

If it was just your ECU, but it worked with other 9's, then I'd be inclined to think perhaps the ECU has a bad block, but you say it has happened on several others.

But like I said, try the obvious, try a different laptop, clean install, etc, then look for the obvious hardware that could draw enough current or could interfere with the ECU.