RomRaider

Are you able to provide a copy of the variables for A8DH200V to compare. I thought I'd found all the missing ones that were needed at minimum for the 1.6 build but still can't seem to get a successful build.
I wasn't sure if maybe it was because being originally based on the '08 ROM, it's relying on tables such as "cruise" and "non cruise" that obviously this one doesn't have.

Are you also able to confirm that to build using a different CalID I just need to add "A8DH200V" as a build config?

Curious on this too riksk. Any changes you had to do? Cheers

Hello brains trust!

I'm wondering if anyone with the sweet compiling / reverse engineering skills could help me to verify these *.h files I've used to compile the Aijmod v1.6?

I've added anything I could to AZ1G900C and AZ1G301F from the defined A2UI001L / AZ1G202G .h files by comparing ROM logic in Ghidra.

Thanks a lot

Yes there is a few differences between older and newer ROMs, depending on the year.

For older ROMs you might need to enable a variable that will ignore the "cruise" and "non cruise" part of the code. I don't remember it as I re-written most of it already.
However, the way I found out most of the issues was comparing the AZ1G202G variables to the A8D ROMs, there is a lot of variables that is defined on the AZ1G202G that wasn't defined for the A8D. Some variables doesn't exist or works differently so you have to ignore it on the code.

The newer code is so much focused on the newer ROMs that, at best, you will probably need to 'retrofit' the code back to the older ROM logic.

I've got a query re: the programming mode shown here: https://github.com/aijii/aijmod/blob/ma ... OG_MODE.md

In the "newer" models (08+) the test mode connectors are connected normally and the ecu is put into test mode/flash mode via a command from ECUFlash.

How does this work with the programming mode? Do we need to disconnect the test connectors for normal driving, and then manually connect them (either physically, or via a wired switch) to program the ECU functions (map swap, valet, etc) or to flash roms?

Or is this not implemented? Or am I reading too much into it and overthinking before playing with it?

I'm testing with the AZ1G202G rom built in the Aijmod-final-2023 repository, FWIW.

Yeah, you described it very well.

You have to connect them in order to get into the Prog mode. So you can change a few parameters then you disconnect them and crank the engine.

To be honest that's not very convenient unless you wire a switch to easily turn it on/off. I have rewrote that program mode to not use the test connectors and rather use a pedal/buttons combination, way more efficient.

Similar to the MerpMod way? ie, cruise on then clutch+brake+cruise up/down?

Any chance you've got an AZ1 rom built with that, that you'd mind sharing?

Yeah very similar, however I didn't consider the clutch switch since AT vehicles doesn't have a clutch switch, and if you're pressing the brake you already don't conflict with the cruise function (as the brake cancels cruise control anyway), so I saw no point adding the clutch switch to the equation.

My Forester currently uses the cruise control mapswitch, my WRX however I have added a button to control it through the RearO2 0-5V wire.




I do have addresses to build the AZ1 for the SADM (South American) roms. But they're vin locked so even if I share one already built, it's not gonna work for you.

Ah bugger.

I want to patch my stock rom but having too much trouble getting HEW set up and following the guide at the moment.

Maybe I'll have a play with it in this capacity and then work on a new version.

Any chance you could share the code for that functionality as a shortcut for when I get it up and running?

Had a bit of time tonight to look at the downloaded repo.

I can use SharpTune to patch my stock rom, but I can't check if it's the correct one because there's no definition file for the patched rom.

Maybe I'm missing a step, but should be there be a definition file created during patching? Or do I have to manually create a definition file somehow?

Inside the repo, there will be various CALIDs, files with a .h extension.

Those are header files, there is addresses defined for every table, pointer, subroutines, etc. They're different for each rom.

In this case, you'll need to define the header file for your particular rom and find all the addresses required to build the patch.

Once done, you will be able to create a patch for the rom.

I'll look into that later


I flashed the AZ1G202G version for now and have the CEL (only the CEL) flashing - two slow flashes.

Doesn't matter if test connectors are connected or not, engine still runs fine and ECUFlash can still put the ECU into flash mode.

Also, cruise buttons don't cycle the CEL, so don't think it's the programming mode.


Doing a windows update at the moment because romraider logger was having some issues trying to load the logger defs, so will look at it again later.


edit: figured it out. Was the map blending CEL because I'd enabled map blending but hadn't adjusted the CEL thresholds.

Can also get to programming mode now, had to connect the second set of test connectors at the ECU (not just the ones under the drivers side - that are already connected).

However, settings changed don't hold after power cycling - is this correct? How does valet mode work? If you set it to valet, as soon as the ecu is power cycled, it will go back to normal will it not? (haven't tested yet, as haven't explored the valet settings fully).

So my stock rom is AZ1G101M - which already has a header file, and Sharptune patches the rom, but doesn't create a definition file for ECUFlash or for RomRaider Logger.

Hi,
Can someone create file for flexfuel for JDM legacy 04 "A2WD012A.hex"
Regards
Eric

Quick question.

In the rom (for AZ1G202G.Switch.debug.v01.60.d21.9.17.1401), there's an exhaust output configuration.

Because I don't have my head around IDE/HEW yet, I can't explore the code myself.

Where does this output? Is there an address or ECU pin it controls?

Or is it just the start of something else that didn't get finished?

Edit: had a quiet morning at work and managed to get HEW working and looking through the repo.

Some parts are self explanatory, some parts are very confusing and will require more reading tonight with a nice whiskey.

I found 25 instances for exhaustcutout, but can't figure out if there's actually an output yet. It looks like it's part of AuxHacks, so not sure if it's set up or just there for now. Will look further unless someone knows?




Would you mind sharing the addresses/code for the cruise button switch set up?

I think i can figure out how to reverse engineer it from that and find the addresses, and hopefully compile the patch and get it working.