Ecuflash error on X
#1
Evolving Member
Thread Starter
Join Date: Jun 2007
Location: New Zealand
Posts: 109
Likes: 0
Received 0 Likes
on
0 Posts
Ecuflash error on X
I have been running a modified rom for a couple of months and last night i was bored so i thought i would flash my old rom back and do some logging so i could see the difference between the 2. That flashed back fine and drove fine but logging didnt work.
So this morning i couldnt be bothered spending hours trying to get the logging going so i went to flash back my modified rom and it comes up with a ecuflash error. I cant test write, compare or do anything to my old rom or new rom. I cant even read the rom that is in there now.
The error comes up like this:
[11:42:14.055] 52370024 (149 tables) inheriting evo10base (173 tables)
[11:42:14.055] 52360018 (7 tables) inheriting 52370024 (181 tables)
[11:42:14.086] 1048576 byte image read.
[11:42:56.247] J2534 API Version: 04.04
[11:42:56.247] J2534 DLL Version: 0.50.2464 Jan 29 2009 10:58:58
[11:42:56.247] Device Firmware Version: 1.05.2463
[11:42:57.827] -- loading kernel --
[11:42:57.827] -- connecting to kernel --
[11:42:57.827] kernel get version
[11:42:58.201] ECU HW part number : 1860A933
[11:42:58.233] ECU SW part number : 1860A93300
[11:42:58.248] VIN : CZ4A-0000556
[11:42:58.248] -- unlocking ECU --
[11:42:58.248] starting session...
[11:42:58.295] requesting seed...
[11:42:58.591] interface close
[11:42:58.607] interface close
the orig rom is a 52360016. I have been running a 52360018 for a couple of months with no trouble. Please help me because the standard ROM is boring
So this morning i couldnt be bothered spending hours trying to get the logging going so i went to flash back my modified rom and it comes up with a ecuflash error. I cant test write, compare or do anything to my old rom or new rom. I cant even read the rom that is in there now.
The error comes up like this:
[11:42:14.055] 52370024 (149 tables) inheriting evo10base (173 tables)
[11:42:14.055] 52360018 (7 tables) inheriting 52370024 (181 tables)
[11:42:14.086] 1048576 byte image read.
[11:42:56.247] J2534 API Version: 04.04
[11:42:56.247] J2534 DLL Version: 0.50.2464 Jan 29 2009 10:58:58
[11:42:56.247] Device Firmware Version: 1.05.2463
[11:42:57.827] -- loading kernel --
[11:42:57.827] -- connecting to kernel --
[11:42:57.827] kernel get version
[11:42:58.201] ECU HW part number : 1860A933
[11:42:58.233] ECU SW part number : 1860A93300
[11:42:58.248] VIN : CZ4A-0000556
[11:42:58.248] -- unlocking ECU --
[11:42:58.248] starting session...
[11:42:58.295] requesting seed...
[11:42:58.591] interface close
[11:42:58.607] interface close
the orig rom is a 52360016. I have been running a 52360018 for a couple of months with no trouble. Please help me because the standard ROM is boring
#2
Evolved Member
iTrader: (1)
Join Date: Jun 2008
Location: Kanagawa, Japan
Posts: 1,018
Likes: 0
Received 0 Likes
on
0 Posts
I have been running a modified rom for a couple of months and last night i was bored so i thought i would flash my old rom back and do some logging so i could see the difference between the 2. That flashed back fine and drove fine but logging didnt work.
So this morning i couldnt be bothered spending hours trying to get the logging going so i went to flash back my modified rom and it comes up with a ecuflash error. I cant test write, compare or do anything to my old rom or new rom. I cant even read the rom that is in there now.
The error comes up like this:
[11:42:14.055] 52370024 (149 tables) inheriting evo10base (173 tables)
[11:42:14.055] 52360018 (7 tables) inheriting 52370024 (181 tables)
[11:42:14.086] 1048576 byte image read.
[11:42:56.247] J2534 API Version: 04.04
[11:42:56.247] J2534 DLL Version: 0.50.2464 Jan 29 2009 10:58:58
[11:42:56.247] Device Firmware Version: 1.05.2463
[11:42:57.827] -- loading kernel --
[11:42:57.827] -- connecting to kernel --
[11:42:57.827] kernel get version
[11:42:58.201] ECU HW part number : 1860A933
[11:42:58.233] ECU SW part number : 1860A93300
[11:42:58.248] VIN : CZ4A-0000556
[11:42:58.248] -- unlocking ECU --
[11:42:58.248] starting session...
[11:42:58.295] requesting seed...
[11:42:58.591] interface close
[11:42:58.607] interface close
the orig rom is a 52360016. I have been running a 52360018 for a couple of months with no trouble. Please help me because the standard ROM is boring
So this morning i couldnt be bothered spending hours trying to get the logging going so i went to flash back my modified rom and it comes up with a ecuflash error. I cant test write, compare or do anything to my old rom or new rom. I cant even read the rom that is in there now.
The error comes up like this:
[11:42:14.055] 52370024 (149 tables) inheriting evo10base (173 tables)
[11:42:14.055] 52360018 (7 tables) inheriting 52370024 (181 tables)
[11:42:14.086] 1048576 byte image read.
[11:42:56.247] J2534 API Version: 04.04
[11:42:56.247] J2534 DLL Version: 0.50.2464 Jan 29 2009 10:58:58
[11:42:56.247] Device Firmware Version: 1.05.2463
[11:42:57.827] -- loading kernel --
[11:42:57.827] -- connecting to kernel --
[11:42:57.827] kernel get version
[11:42:58.201] ECU HW part number : 1860A933
[11:42:58.233] ECU SW part number : 1860A93300
[11:42:58.248] VIN : CZ4A-0000556
[11:42:58.248] -- unlocking ECU --
[11:42:58.248] starting session...
[11:42:58.295] requesting seed...
[11:42:58.591] interface close
[11:42:58.607] interface close
the orig rom is a 52360016. I have been running a 52360018 for a couple of months with no trouble. Please help me because the standard ROM is boring
#3
Evolving Member
Thread Starter
Join Date: Jun 2007
Location: New Zealand
Posts: 109
Likes: 0
Received 0 Likes
on
0 Posts
damn, i was hoping that wasnt the case. It flashed fine when i put it back to stock, nothing out of the ordinary. But when i tried to put it back to the modified rom it wont do anything.
oooohhhhhhh now i have to live with stock boost untill its fixed
oooohhhhhhh now i have to live with stock boost untill its fixed
Last edited by onboost; Jun 26, 2009 at 06:35 PM.
#5
Evolved Member
iTrader: (4)
Join Date: Feb 2008
Location: Edmonton, Alberta
Posts: 610
Likes: 0
Received 0 Likes
on
0 Posts
This might sound dumb, but do you have anything else open that could be using the interface?
EvoScan, PCMScan, etc?
I recall a while back I was getting a similar error log, I think I just closed everything and it worked fine.
Generally the problem is much more complicated, but I thought I'd throw this out in case it was a simple fix.
EvoScan, PCMScan, etc?
I recall a while back I was getting a similar error log, I think I just closed everything and it worked fine.
Generally the problem is much more complicated, but I thought I'd throw this out in case it was a simple fix.
#6
Evolving Member
Thread Starter
Join Date: Jun 2007
Location: New Zealand
Posts: 109
Likes: 0
Received 0 Likes
on
0 Posts
This might sound dumb, but do you have anything else open that could be using the interface?
EvoScan, PCMScan, etc?
I recall a while back I was getting a similar error log, I think I just closed everything and it worked fine.
Generally the problem is much more complicated, but I thought I'd throw this out in case it was a simple fix.
EvoScan, PCMScan, etc?
I recall a while back I was getting a similar error log, I think I just closed everything and it worked fine.
Generally the problem is much more complicated, but I thought I'd throw this out in case it was a simple fix.
i tried the evoX recovery info off openecu.org but that doesnt work either.it comes up with this instead:
[15:45:20.054] J2534 API Version: 04.04
[15:45:20.054] J2534 DLL Version: 0.50.2464 Jan 29 2009 10:58:58
[15:45:20.054] Device Firmware Version: 1.05.2463
[15:45:27.391] sending init sequence 1 (0001)
[15:45:30.698] sending init sequence 1 (0003)
[15:45:34.005] sending init sequence 1 (FFFF)
[15:45:37.312] sending init sequence 1 (F0F0)
[15:45:40.058] no response to any known code
[15:45:40.058] interface close
The car still runs which is a good thing, but it has the 'boring factory' tune rather than my one i sent a email to tactrix so hopefully ill get a reply soon
Thread
Thread Starter
Forum
Replies
Last Post
BlackHawk_Tsi
Evo X Engine Management / Tuning Forums
0
Apr 20, 2015 04:25 PM