Unknown ROM image?
May 21, 2006, 07:10 PM
#1
Evolved Member
Thread Starter
iTrader: (11)
Join Date: Oct 2004
Location: Boston
Posts: 1,456
Likes: 0
Received 0 Likes
on
0 Posts
Unknown ROM image?
Ive been usung the software for a little while now just trying to get a feel for it and ive attempted to open another rom but instead i get this message and i dont know which option too choose from.
Defined from scratch...?
Copied...?
Inherited...?
Ive opened the stock image before and had no problems but for some reason im now promted with this msg and im unaware as to the appropriate option.
Thanks
Defined from scratch...?
Copied...?
Inherited...?
Ive opened the stock image before and had no problems but for some reason im now promted with this msg and im unaware as to the appropriate option.
Thanks
May 21, 2006, 07:28 PM
#2
Is it the same image you opened before? Make sure the paths to the XML files hasn't changed..
If its a brand new rom image that is just different than anything seen yet, it probably can be inherited, but if it is new, then send a copy of it to Jason at Mynes.
If its a brand new rom image that is just different than anything seen yet, it probably can be inherited, but if it is new, then send a copy of it to Jason at Mynes.
May 21, 2006, 07:32 PM
#3
Evolved Member
Thread Starter
iTrader: (11)
Join Date: Oct 2004
Location: Boston
Posts: 1,456
Likes: 0
Received 0 Likes
on
0 Posts
No it is a new image and the path has not changed.
Is there a specific inheritence that i should always follow? As far as the options given to me in the pull down tab
Is there a specific inheritence that i should always follow? As far as the options given to me in the pull down tab
May 22, 2006, 06:47 AM
#4
I was with Sap12687 while trying to retrieve his tune. I have no problems reading my ROM from the ECU, but his could not be pulled. His is a Dynoflash tune for what it's worth.
We would get the unknown rom image error. I tried all 3 of the options listed but could not view the fuel or timing maps. The fonts for all the definitions would be greyed out when trying to view the parameters. And instead of having data when opening up the maps, it would just have a message saying that the data was incomplete???
I don't remember which inheritance option we clicked on but with one of the choices, we were able to pull up definitions which looked normal (font wasn't greyed out). However, the cells inside the fuel and timing maps didn't contain normal values - there was "inf"' in >90% of the cells???
We would get the unknown rom image error. I tried all 3 of the options listed but could not view the fuel or timing maps. The fonts for all the definitions would be greyed out when trying to view the parameters. And instead of having data when opening up the maps, it would just have a message saying that the data was incomplete???
I don't remember which inheritance option we clicked on but with one of the choices, we were able to pull up definitions which looked normal (font wasn't greyed out). However, the cells inside the fuel and timing maps didn't contain normal values - there was "inf"' in >90% of the cells???
Last edited by anjapower; May 22, 2006 at 06:51 AM.
Trending Topics
May 22, 2006, 01:08 PM
#9
Originally Posted by TTP Engineering
You cannot even communicate with the ECU if there was an Ecutek flash on it. So it is not an Ecutek flash ROM.
What I think probably happened is that you did not add .hex at the end of the file when you saved it.
What I think probably happened is that you did not add .hex at the end of the file when you saved it.
I wonder if his cable is screwed up? That was the only common denominator...we tried different laptops, reinstalled ecuflash, reread the rom multiple times, etc.
May 22, 2006, 02:09 PM
#10
Evolved Member
iTrader: (16)
Join Date: Mar 2005
Location: CT
Posts: 1,338
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by TTP Engineering
You cannot even communicate with the ECU if there was an Ecutek flash on it. So it is not an Ecutek flash ROM.
What I think probably happened is that you did not add .hex at the end of the file when you saved it.
What I think probably happened is that you did not add .hex at the end of the file when you saved it.
If you didnt add .hex as the extension EcuFlash would not recognize the file.
