Rom routines - Tephra Mfred etc etc
Because of the load-store architecture of the SH2 every variable longer than a byte loaded into a restricted register set has to be read from ROM or RAM. Even a "hard" setting would really be soft if you just updated the address of the rev limit in Ecuflash, although I would think he wouldn't have moved it.
Presumably 16km/h to account for wheelspin on launch but to make sure the rev limiter resets to 7606 by the time you're at the top of first gear.
Presumably 16km/h to account for wheelspin on launch but to make sure the rev limiter resets to 7606 by the time you're at the top of first gear.
Last edited by codgi; Jul 27, 2008 at 12:51 PM.
Yes.
If speed <= 16km/h use the value at address xx (new created position)
else use the value at address "normal ref limit"
The 16 (8 in the raw variable of vehicle speed) is hardcoded right now, but can be changed to "adjutable" quite easy.
If tephra timeline is like evoscan's timeline
, then you can send me your rom with your xml file than I can patch it. But if he is ready next week it may be a waste of time.
(Send me a PM then I give you my email. Some of my email accounts was checked rare.)
Why 16? During dissasembly I have found somewhere in the code this value for vehicle speed (8 in raw).
This value has been burned into my brain so I must use it. 
...and I was sure that this is a small value that the ecu can processing without testing it.
If speed <= 16km/h use the value at address xx (new created position)
else use the value at address "normal ref limit"
The 16 (8 in the raw variable of vehicle speed) is hardcoded right now, but can be changed to "adjutable" quite easy.
If tephra timeline is like evoscan's timeline
, then you can send me your rom with your xml file than I can patch it. But if he is ready next week it may be a waste of time.(Send me a PM then I give you my email. Some of my email accounts was checked rare.)
Why 16? During dissasembly I have found somewhere in the code this value for vehicle speed (8 in raw).
This value has been burned into my brain so I must use it. ...and I was sure that this is a small value that the ecu can processing without testing it.
.
Evolved Member
Joined: May 2006
Posts: 2,399
Likes: 6
From: UK
Even if he did move it you could move it back by changing the address he uses to look it up - wouldn't even need to touch the assembly. My point is that very little is hardcoded on the SH2 because of its architecture. Very rarely would you have an op code and a constant rolled into the instruction, even then it would usually be 8 bits into R0.
Evolving Member
Joined: Sep 2006
Posts: 152
Likes: 0
From: Germany
Today I have take a look on the 90550001 V5 Disassembly.
The problem with the rev limiter is, that tephra has already used it (and modify it) for his patches.
This means that it will be much more work, because I must edit tephra's code and cannot use my code to edit the OEM Address.
@tephra
Is your 5.8 for the 90550001 ready in time?
The problem with the rev limiter is, that tephra has already used it (and modify it) for his patches.
This means that it will be much more work, because I must edit tephra's code and cannot use my code to edit the OEM Address.
@tephra
Is your 5.8 for the 90550001 ready in time?
Evolved Member
Joined: Aug 2007
Posts: 569
Likes: 1
From: UK
Looking forward to it Tephra.
@JoeBee, Thanks for looking into it for everyone with 90550001.
You have got alot further than any of us that were looking at it a while back could, as none of use could even disassemble it propperly
@JoeBee, Thanks for looking into it for everyone with 90550001.
You have got alot further than any of us that were looking at it a while back could, as none of use could even disassemble it propperly
Thread
Thread Starter
Forum
Replies
Last Post
David Buschur
Evo X Engine Management / Tuning Forums
9
Jun 25, 2010 10:01 AM
