ok, How do you set ram data using ECUflash?

 

You write the ROM area it is copied from and save the ROM in Ecuflash, then use live map to copy this to RAM.

 

ok, I understand it as:

1) Make an XML entry to include the an "alt mut table" that is included in the 2k you copy from ROM to RAM.

2) Point LiveMap logging address to the RAM Memory instead of the regular Mut table.

3) Edit the ROM to change logged variables and load up using livemap write function.

Is the start address the same as what you show in the images?

 

1. Yes, use a 2d table with static axis, and as many hex16 as you need, 2 for each MUT item, you can see the 18 items I chose on page 6 of this thread. You want to use a free area at the end of the 2k alt map space. I used 0x740 to start mine (out of 0x800 or 2k total), add this to the base address of the alt map area - on mine 0x37b00 giving 0x38240 (you can get your base address from the Data tab when you load up Evo Live Map for your ECU, add 0x740 to that).

2. Yes, use the RAM location (on mine 0xFFFF8500 + 0x740) and put it in live map's logging address.

3. Yes.

I try to keep the addresses similar where possible for the same gen of ECUs, but they are different between 8 and 9.

You can move any map you like into RAM using a similar idea, just copy the header and the map into the ROM shadow area, and in the ECU change the pointer to the equivalent address in RAM.

I thought it was best to get you to play yourself rather than just supply a ROM to you, you'll be a handy asset to help others do lots of funky custom stuff once you get this. Hope you don't mind

 

John,

I haven't tested this yet, and my question may be because of that fact, but can you explain the quote above a little further?

 

You need the ROM loaded into IDA pro. Find the address of a map you're interested in from Ecuflash. Go to the start of the header (eg 03 00 FF FF ....) and find hopefully a single variable that points to the header. Change that to RAM and the map will now be read from RAM where you can edit it.

 

ziad is still having trouble on 96260009 even with valet off and not logging the car shows a CEL and the engine dies periodically (I'm hoping just when running alt maps). I'm wondering if the RAM is getting overwritten, still no one seeing this problem on 96530006 hopefully?

Info here:
http://www.lancerregister.com/showth...22#post2650822

 

I can't get 96530006 to run at all on my car. It doesn't start. Immobilizer is set, all my maps and latencies are copied over..... I bet I'm just missing something STUPID

 

If 96530006 is your home ROM, it should start with just the immobilizer and nothing else changed. If 96530006 is not your home ROM, suggest review the conversion procedure again.

 

Kaymin, did you disable the immobilizer with the Periphery bit.

 

oooopppsss...... I totally forgot that the immobilizer is disabled when you swap not retained!

 

You can retain your Immobilizer but you have to make a few changes. I would try to disable and verify the car starts then work on the immobilizer.

 

sounds good!

 

fjo_newport,

Did you ever get this working with acamus' OBD patches in place?

I finally made a switch harness that I will use from a 5V output to the adc input for map switching and I have John's 96530006 livemap ROM all set and ready to flash and test.

Hopefully I plan to flash it within the next couple of days, but I have the OBD patches in place, and if you didn't get it to work, maybe I will skip that part for now.


Eric

 

Eric,

Sorry never went back to replace it. I figured the the least amount of crap I mess with the better off I'd be for debugging this.

That is the same way I made my ALTmap harness. I don't understand why people were making that crazy circuit. All the A/D I've ever seen have a very high input impedence, so there should be almost no current, but to be on the safe side I measured it and like I figured was very small.

Hurry up and test it, I want to see if you get the same problems as me. I keep throwing a P0505 error (Idle), and can't seem to figure out why. Also when ever I'm logging and the connection drops the ECU seems to reset (engine still runs, but stumbles and SES light flash like after a startup). It may even happen when I get the SES light for the P0505 code, but I need to test some more.