openecu.org

by **prana** » Sat Dec 02, 2006 3:08 am

Unfortunately, I associated it with the wrong XML file and I don't know how to link it back to the correct xml file. But I can see A8DH100H at offset 0xc0000. The market at 0x2000 is wrong and I cannot find the associated A8DH100H.

Thanks for any help

by **prana** » Sat Dec 02, 2006 4:03 am

I found some offsets to start off with creating a new XML file , unless one already exists. I couldnt find one by searching

- Intake Cam Advance Angle B (AVCS) CF73C
- table name="X" address="CF76E" elements="15"
- table name="Y" address="CF6FC" elements="16"

Low det fuel table

- table name="Low Detonation Fuel B" address="C900C"
- table name="X" address="C8F88"
- table name="Y" address="C8FC4"

by **merchgod** » Sat Dec 02, 2006 7:03 am

The market shows to be ADM. It looks like someone changed the calid at 0x2000. Was this map tuned? Sometimes tuners will change the calid thinking this will prevent you from looking at their tune with the openecu tools.

by **prana** » Sat Dec 02, 2006 4:11 pm

no I changed it at location 0x2000 as I was trying to change the association xml (yup I havent figured out how to do that yet if I have associated it wrong, even tried redownloading it). When I downloaded it first, no XML was associated so I tried one and all the numbers were silly. So I looked into the Forester directory and tried to manually change it using hex editor tp match the other XML files but didnt work, one by one. THen i looked through the whole file and found the "identifier" and 0xc0000 where the normal XML shows it to me at 0x2000, thats why I said above that I messed up

lol what a mess. Took me about 6 hours and only got 2 tables out (as above). No tune, totally stock quite new I see :lol:

Cheers

by **merchgod** » Sat Dec 02, 2006 5:58 pm

Enginuity has support for this rom. Change the calid back at 0x200 and open it with Enginuity.

by **prana** » Sun Dec 03, 2006 2:08 pm

G'day Merchgod,

I was just looking at the latest changelogs as well as opening the rom in enginuity. It appears there is support for A8DH100P and A8DH100I but not A8DH100H. "ECU definition not found"

by **merchgod** » Sun Dec 03, 2006 3:05 pm

I thought you had the A8DH100P. My bad. Is this a stock unmodified rom? I can add it to Enginuity's definitions for the next definition release. You may also want to try xmlwrite which generates xml defs for certain roms. See the Enginuity FAQ for details or search this site.

by **prana** » Sun Dec 03, 2006 11:28 pm

ooo xmlwrite ? I didnt know there was such a thing. Ok sounds good.

The ROM is completely stock, except where I made that booboo at 0x2000 but the original was in fact at 0xc0000 anyway. I gotta do some logs with some E5 fuel tonight whilst but after that, I'll give the XMLWrite tool a go'er. Wayyy easier than comparing hex strings and populating manually like I was doing, not to mention most of them came out wrong

I paid 20% more for this tank of fuel so I can log the RON100 effects

I really need to get a disassembler for 68HC16 for IDA4.9. Do you know where to find the processor instructions for the 68HC16 ? Are they similar to the 68HC12 chipset (I have 6812 support) ? Sorry, lots of questions, thought I could do something to help back in return but so much to learn. But if it hasnt come across already, fantastic work from everyone here!!!

by **prana** » Mon Dec 04, 2006 12:05 am

C:\> xmlwrite A8DH100H 4

XMLWRITE v8 by tinywrex

Command line syntax
C:\> XMLWRITE.EXE <CALID> <XML OUTPUT TYPE>

<CALID> up to 8 characters
<OUTPUT TYPE> 1=ECUEDIT 2=ENGINUITY 3=ECUEDIT SINGLE OFFSET 4=ECUFLASH

CALID not found or invalid parameters specified

Location at 0xc0000

000c0000:41 38 44 48 31 30 30 48 00 38 35 44 41 55 5f 41 A8DH100H.85DAU_A
000c0010:54 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 T
000c0020:05 02 28 43 6f 70 72 2e 44 45 4e 53 4f 32 30 30 ..(Copr.DENSO200
000c0030:35 20 ff ff 00 00 00 00 03 33 14 00 00 00 10 00 5 ÿÿ.....3......
000c0040:01 e5 01 e9 03 78 03 7c 00 62 40 00 00 20 60 .å.é.x.|.b@.. `

I noticed the FAQ, most of the support was for A2 and A4 chips, maybe no support for A8 yet ... (oh yes it does, I think I misunderstood what you said then). It does support many A8DH100I,P,etc but not H. Stuck .... :oops:

by **merchgod** » Mon Dec 04, 2006 5:44 am

Looks like xmlwrite doesn't support it. I can add your rom to the Enginuity definitions for the next definition release, which will be in a few weeks.

by **prana** » Mon Dec 04, 2006 1:06 pm

thank you. look forward to it

Can you post the offsets so I can create an xml file for ecuflash too ?

by **merchgod** » Mon Dec 04, 2006 1:25 pm

The definitions are in xml.

by **prana** » Wed Jan 31, 2007 4:40 pm

Hi merchgod, just wondering if you have had an opportunity on this image. Ta.

by **merchgod** » Wed Jan 31, 2007 8:24 pm

Yes, it is done. I'm releasing an update along with other additions/fixes which I should have done in a week or so. Check the Enginuity site on the main page soon.

by **prana** » Thu Feb 01, 2007 1:16 pm

man thats fantastic, I wish I could do this... thanks. Can't wait to see it

openecu.org

Forester XT Aust 2006 model

Forester XT Aust 2006 model

Who is online