EcuFlash - Stock rom wants 53600016 definition file
Apr 8, 2012, 09:41 PM
#1
EcuFlash - Stock rom wants 53600016 definition file
I preface this by saying I'm a complete NOOB to all this, but have been reading a lot and trying to get a handle on things.
Just got my Tactrix adaptor, and was going through the "ECU Stuff For Dummies" thread pretty much step by step.
I kept having issues with EcuFlash not being able to read my stock ROM after I pulled it out of the car. It kept telling me the ROM was not found, and I should quit.
I downloaded pretty much every single .XML file I could off the GoldenEvo site, with no luck, knowing this was the problem.
After a while of this, I told it to make a definition file and used the 53600010 as a template (or copied from, or something like that). It made a definition file with 53600016.XML as the filename. I edited it to include the 53600010 file, like the 53600009 and 53600008 do.
It is *sorta* working. The tables I see are, what I would call corrupt. Some of the data looks right, but some looks way off. So I'm guessing some of the information isn't getting read from the correct memory addresses.
I searched for 53600016 and came up empty.
Next step??
Any help would be appreciated.
BTW... EvoFlash does come back with 1860B106 as the ECU code, and the second version of that is 1860B10604. That seems right for this car, from what I have read.
Just got my Tactrix adaptor, and was going through the "ECU Stuff For Dummies" thread pretty much step by step.
I kept having issues with EcuFlash not being able to read my stock ROM after I pulled it out of the car. It kept telling me the ROM was not found, and I should quit.
I downloaded pretty much every single .XML file I could off the GoldenEvo site, with no luck, knowing this was the problem.
After a while of this, I told it to make a definition file and used the 53600010 as a template (or copied from, or something like that). It made a definition file with 53600016.XML as the filename. I edited it to include the 53600010 file, like the 53600009 and 53600008 do.
It is *sorta* working. The tables I see are, what I would call corrupt. Some of the data looks right, but some looks way off. So I'm guessing some of the information isn't getting read from the correct memory addresses.
I searched for 53600016 and came up empty.
Next step??
Any help would be appreciated.
BTW... EvoFlash does come back with 1860B106 as the ECU code, and the second version of that is 1860B10604. That seems right for this car, from what I have read.
Apr 9, 2012, 01:50 AM
#2
Evolved Member
Hi, and welcome to the ROM ID Dance. 
You've got the "latest" 2009 USDM Ralliart ROM ID that I've seen. Nobody has made a definition file for it yet.
The most basic thing you'd want to do with that particular ROM file is to use it to "reflash to stock". For that task, you really only need a dummy (place-holder) XML... enough to make EcuFlash happy to load it up and work with it. The one you've done is good for that - you can discard the scale/table data if you wish.
The more advanced thing that can be done with that ROM of yours is to use it as a base for tuning. That requires a full definition workup for it.
The easy workaround for tuning your car is to simply use an older "5360" ROM as a base - one that is already well defined, with patches available, etc. So if you were to (say) apply the GST Base Map to you car, you'd be overwriting your stock 53600016 with a tuned 53600009 ROM. This is a common approach. It's generally accepted as "safe" to mix'n'match ROMs, as long as the first 4 digits match.
Hope that makes sense!
Rich
You've got the "latest" 2009 USDM Ralliart ROM ID that I've seen. Nobody has made a definition file for it yet.
The most basic thing you'd want to do with that particular ROM file is to use it to "reflash to stock". For that task, you really only need a dummy (place-holder) XML... enough to make EcuFlash happy to load it up and work with it. The one you've done is good for that - you can discard the scale/table data if you wish.
The more advanced thing that can be done with that ROM of yours is to use it as a base for tuning. That requires a full definition workup for it.
The easy workaround for tuning your car is to simply use an older "5360" ROM as a base - one that is already well defined, with patches available, etc. So if you were to (say) apply the GST Base Map to you car, you'd be overwriting your stock 53600016 with a tuned 53600009 ROM. This is a common approach. It's generally accepted as "safe" to mix'n'match ROMs, as long as the first 4 digits match.
Hope that makes sense!
Rich
Apr 9, 2012, 07:32 AM
#3
Yes, makes perfect sense, and...
That's what I wanted to hear. I had planned on flashing the latest GST map (which EcuFlash has had zero problem reading), but was a little concerned after reading my stock ROM, and it being undefined.
I just picked up this car a month ago, so I'm not familiar with all the service its had, but I guess it's fair to say that at some point the dealer put a new ROM flash into it. It has a 11/3/2008 production date, so it's a fairly early production car, although it wasn't delivered until 10/2009.
CarFax shows it was just in for service late last year to get the timing chain replaced as well as the "Spark Control pick up sensor." I'd assume this was the point the dealer installed the new ROM, given the "newness" of it.
Thank you for responding and putting my mind somewhat at ease. I was hoping to play with the stock ROM a bit before making the jump to the GST ROM, but I guess it's going to be easier to just jump forward and make the leap.
I just picked up this car a month ago, so I'm not familiar with all the service its had, but I guess it's fair to say that at some point the dealer put a new ROM flash into it. It has a 11/3/2008 production date, so it's a fairly early production car, although it wasn't delivered until 10/2009.
CarFax shows it was just in for service late last year to get the timing chain replaced as well as the "Spark Control pick up sensor." I'd assume this was the point the dealer installed the new ROM, given the "newness" of it.
Thank you for responding and putting my mind somewhat at ease. I was hoping to play with the stock ROM a bit before making the jump to the GST ROM, but I guess it's going to be easier to just jump forward and make the leap.
Last edited by Struc; Apr 9, 2012 at 08:28 AM.
Apr 9, 2012, 09:19 AM
#5
I preface this by saying I'm a complete NOOB to all this, but have been reading a lot and trying to get a handle on things.
Just got my Tactrix adaptor, and was going through the "ECU Stuff For Dummies" thread pretty much step by step.
I kept having issues with EcuFlash not being able to read my stock ROM after I pulled it out of the car. It kept telling me the ROM was not found, and I should quit.
I downloaded pretty much every single .XML file I could off the GoldenEvo site, with no luck, knowing this was the problem.
After a while of this, I told it to make a definition file and used the 53600010 as a template (or copied from, or something like that). It made a definition file with 53600016.XML as the filename. I edited it to include the 53600010 file, like the 53600009 and 53600008 do.
It is *sorta* working. The tables I see are, what I would call corrupt. Some of the data looks right, but some looks way off. So I'm guessing some of the information isn't getting read from the correct memory addresses.
I searched for 53600016 and came up empty.
Next step??
Any help would be appreciated.
BTW... EvoFlash does come back with 1860B106 as the ECU code, and the second version of that is 1860B10604. That seems right for this car, from what I have read.
Just got my Tactrix adaptor, and was going through the "ECU Stuff For Dummies" thread pretty much step by step.
I kept having issues with EcuFlash not being able to read my stock ROM after I pulled it out of the car. It kept telling me the ROM was not found, and I should quit.
I downloaded pretty much every single .XML file I could off the GoldenEvo site, with no luck, knowing this was the problem.
After a while of this, I told it to make a definition file and used the 53600010 as a template (or copied from, or something like that). It made a definition file with 53600016.XML as the filename. I edited it to include the 53600010 file, like the 53600009 and 53600008 do.
It is *sorta* working. The tables I see are, what I would call corrupt. Some of the data looks right, but some looks way off. So I'm guessing some of the information isn't getting read from the correct memory addresses.
I searched for 53600016 and came up empty.
Next step??
Any help would be appreciated.
BTW... EvoFlash does come back with 1860B106 as the ECU code, and the second version of that is 1860B10604. That seems right for this car, from what I have read.
Thread
Thread Starter
Forum
Replies
Last Post
