I will give this a shot tonight. Thanks!

EDIT: OH YEAH! Got this working quickly. Thanks for the help!

Since I moved the initialization values location of the RAM MUT in the ROM from 0x49B00 to 0x4A280 is there a way to define this in ELM so the RAM2DISK and RAMInitialize functions don't overwrite some other tables?

 

Ram initialise..will bring the ecu to what was flashed state...so if the new stuff has not been flashed it's lost...same with loss of battery.
ram 2 disc..copies the contents of ram to a file which can them be flashed via ecuflash to your ecu to commit the changes. So do this.

Did you read the manual....I think I covered it...but maybe it didn't explain well...let met know

 

I did read the manual several times...i have a grasp of what the buttons do. However, since i moved the ram mut table from 0x49b00 in the ROM to the new location at 0x4A280. Now when i click ram2disk it copies the table to the old location and not the new one. Since I have expanded the table to 128B it will overflow into other tables in the ROM i am assuming, since i had to move the table i guess i assume the wasnt enough room. When i opened the saved rom in ecuflash the new table isnt populated. I guess i didnt explained very well...plague of an engineer i guess. Or i may have done something wrong since i throught that the dma code just copied like 2K from rom to RAM on a reset of dead. How does your code know in rom where to put the ram mut table in the rom? Sorry im being a pain in the a$$.

 

no no u are not mate, and even i sometimes find it hard to explain things.... or is that all the time

anyway to answer ur question, seeing u have read the thread from john. my program basically works exactly like what john's original program did, actually i got a copy of his program and incrementally modified it along the way.. just like my uni assignments.. haha.

anyway here is what happes... incase other ppl are looking too.

E0: this command is sent with a location of the ram mut table. the ecu code goes and fetches the results of the mut table requests and via dma sends them to my program. i catch them i display them and do stuff

E1/E2: reads and writes memory address directly. just a dump.. i use them to read write tables.

now reset DEAD (initialize ram) gets the code to copy the 2k segment from rom to ram. this overwrites any changes u have made since the last flash. the reset does not care where ur mut table is. if u didnt flash with a ram mut table it wont show up.

hence i find it strange that it would move the ram table back to the old position (actually u may be confused. as both the old and new locations will have a ram mut table... simply because u didnt empty the location the first time.

i will email u a few screenshots of what i mean

EDIT: this is a picture, hopefully it explains what i am tring to say

 

ziad did you get my email?

thanks andy

 

AAAHHH! So when you do a RAM2DISK it copies the entire 2K from RAM to the ROM on the computer. I must have messed it up when I was checking it. Sorry to spread confusion!

 

The RAM address 0xFFFA780 is smack in the middle of the RAM location of the Alt Ignition. So when I do the "Build RAM MUT..." checkbox it corrupts my Alt Ignition table. I assume that you had me move the RAM MUT table to the end of the 2k, from the ROM addresses you gave me (which seem to be correct since 0x00049B00 + 0x0000800 - 0x00000080 = 0x0004A280). The 2k of RAM we are interested in spans addresses 0xFFFFA230 to 0xFFFFAA30. So the new MUT address to be put in MUT Requests is 0xFFFFA9B0 (or 0xFFFFAA30 - 0x00000080). Does this logic hold up or am I missing something again?

I just wanted to clarify just in case someone wants to use the instructions...

 

ahhhh fk me.... i didnt fix my ecuflash definations after the issue with 8859 i am seriously haveing a bad time.

ur ram mut table should be at FFFF A9B0... which u have worked out properly... and i have done nothing but confuse you... i do appologise for that..... you are right. in ELM the address you have worked out is teh correct one. please enter that.


hmm what did they say... never argue with an engineer, cuz they are always right (might not be true... but in this case you were)

 

No worries at all! I am always trying to figure out how something works in the background. I like the details...and how things work.

I try not to be THAT engineer...but sometimes it happens.

Now to work on SD2.0...

 

I have been getting some CEL code while running donnor's 8859 ROM. I am also getting the ocasional stutter/misfire followed by a DMA read error in ELM. Has anyone else had these issues? I am using a pretty gutless Asus EEE PC netbook so i may be causing the read errors if it choaks. But the CEL and misfires worry me...dont want they happening at WOT. I am going to flash back to my old rom for the drive home and see if i get the CEL again.

MUTII DTC from EvoScan:
Oxygen sensor
Intake temperature sensor
Throttle position sensor
Isc motor position sensor
Engine coolant temperature sensor
Crankshaft position sensor
Knock sensor
Injector circuit
Fuel pump relay
Egr sensor

The car is running fine so i am guessing these are ghosts... I get the CEL wheither i am logging or not...but the missfires only seem to happen when logging via ELM. Guessing the comms hang the DMA routine and it misses the CAS interupt or something...buts thats just a WAG.

 

Don't use rom at wot if you see this kind of problems, it needs then some attention. I tested rom on my own EDM IX by driving it around about 20-30 miles, used alt maps and tuned it with live just to see it works. And it worked back then, don't know what happens now, need to test it again...

 

Yeah I haven't used it at WOT. I can do any testing you want...i can point my RAM MUT at other variable if you want and just ease it around town. Or however i can help... It has happened 4 or 5 times since having the car flashed Sunday night and drivning it around quite a bit since then.

 

So you just used my rom and did not modify that at all? I'm not sure when I have time to test this again as pretty busy at the moment but all mods can be seen from xml. So if you are disasm sort of guy, you can try to dig it out by yourself what's wrong.

I tested it only once so maybe something odd happens on the long run. I had problems with 9653 sd2.0 rom as I needed to extend ram copy area to copy VE too and something was overwriting ram area even there was not direct references to that area of ram and this happened only in the longer run (like few hundred miles of running), not immediately. Thats why 9653 sd2.0 VE map is smaller But not any other ideas really, sorry mate

 

MUTII DTC is for 1997 Evo4 only.

OBDII DTC is for 1998+ Evo5/6/7/8/9

CAN DTC is for 2007+ EvoX

 

it says i need to register to use ram to disk. Id really like to get started and put my email in the field before my download. What else do i need? a link maybe?

thanks