RomRaider

In case anyone hasn't been following up over here: viewtopic.php?f=65&t=19543

I've finally gotten to a point where I'm able to partially automate the definition generation process. Using IDA and the Diaphora script, I'm able to port over symbols to likely offsets based off how similar the code structure is. Then using a script I made, I'm able to parse the A2L.xml file, the ZB060 a2l file, any pre-existing definition file for the specified ROM, and the actual IDA output file. Using all of this, I'm able to match up the a2l abbreviations and generate a RomRaider formatted definition file. This yields very incredible results, but it's not able to pick up everything. The older ROMs aren't going to benefit as much from automation as newer ROMs will. However, this potentially will change with more and more ROMs getting more tables defined. So this basically means expect more tables to be defined across the board, regardless of whether it's a Z or G ROM!

NissanDefinitions (v1.0) is Up! Can find it here: https://github.com/Pytrex/NissanDefinit ... s/tag/v1.0

Release Notes:
Designed for RomRaider v0.9.3
Editor Definitions
- General Table Refactoring
- Reorganized Folder Layout + Updated "Combine All.bat" file
- Put Scaling Data into an XML File
- Fixed Issue Where Axis Units Would Repeat (ex. "Coolant Temperature (Coolant Temperature(Fahrenheit))")
- Fixed DTC Tables
- Fixed Improperly Sized Tables
- Updated Version Tag in Definition Files


Nothing super duper crazy in this one, but it's a good foundation to build upon! Near future plans are going to continue to automate ROM definitions and after that, it'll be onto manually adding whatever was missed during automation.

I noticed 370z and g37 defs in there. Are we nowadays able to dump and flash CAN based ecus, and if so with what?

Yup! Somewhat recently RomRaider Logger actually added support for reading and writing CAN-based ECUs! viewtopic.php?f=65&t=19033

However, I'm only including them at the moment just to keep things organized nicely. I want to make sure that I cover as many 03-06 K-line based ECU's first. But I intend of adding 370z/G37 (and any CAN-based ROMs really) in the future!

Oh that's great! I've a few friends who will definitely be very interested in that feature

Definitely post up some more CAN ROM dumps if they end up pursuing it! I hardly have any CAN ROMs.

The NissanDefinitions repository is going to be very experimental and unstable for a bit haha So if you want stability, use the release instead! But I finally got around to making a script that parses my main A2L file, grabs the tables that I want it to grab, then imports it automagically So now I can modify just my main A2L template and the changes will immediately transfer over to the repo's A2L template. I'm waiting to see the results of a potential table naming enhancement I suggested. But if that isn't a feasible option, I might start storing every table def as its a2l abbreviation, then translating it to the proper table name once it's inside "NissanDefinitions.xml" via a script. Because the abbreviation will never change, but the name might go through tens of iterations. So I guess we'll see!

Big update! So I'm now going to be keeping my experimental automated definition files up on the NissanDefinitions repo! Meaning, use the release for stability. There are bound to be plenty of errors in the actual repository due to incorporating the automated definition files. So if you're having issues using the repository, go back to the latest release. I'll try to make sure that each release is a stable one, as I'd rather have there be at least one definition file that someone could use at any time.

Just some of what I've been up to (available in the repo, not in a release);
- Parsed through multiple vehicle's DTC structure and generated a nearly complete DTC list that's now available in all ROMs that previously had DTCs defined
- Utilized the Juke a2l to define 0/1 bit operations for ROM flags (so you can actually see what enabling/disabling actually will do)
- Parsed HWID's to properly assign ROM bases where applicable
- Added alt checksums to most ROM definitions (not necessary, but still nice to include)
- More scaling name fixes
- Added "EXPERIMENTAL" tags in place of the version for ROMs that I haven't extensively tested (These definition files POTENTIALLY are safe to use. But I'm including the tag in order to make it clear that they're untested and could have issues)
- Removed the Logger definition file to ensure that everyone is using a known stable logger file (I'm wanting to focus on stabilizing ROM definition files before focusing on Logger definitions)
- Added at LEAST a definition template file for every ROM that I personally have (see note 1 below)

So with that being said, I'm really happy with where the repository is at

Note 1: I decided that for now, my repo will be focused solely on SH7055/SH7058 ROM's. So I currently won't be pursuing other SH variants. But with that being said, post any new SH7055/SH7058 ROMs you have in the stock ROMs thread! Can't define new ROMs without the ROM itself! It would help generate ROM bases as well, as I don't know of any online databases to mass-search ECUID's from HWID.

Awesome work there mate! Once I get through the grunt work on my Skyline swap I will be looking more into romraider and hopefully can help out in some way!

I have a Patrol with VC266 which from 7zap says VD70A is the latest, is this one in the auto definition list?

Unfortunately not. Patrol ROMs have a lot more diversity than other models do it seems

Hmm, hard work ahead of me then I have started to have a look at my 2004 F50 Cima (aka Infiniti Q45) VK45DE rom (AT30A), someone on the forum mentioned that they have identical PCB's to the Patrol TB48DE.

Did a quick bin comparison last night and at a quick glance:
AT30A (Cima F50) has a lot of similarities to the CS500 (Infiniti Q45)
AT30A likewise very similar to VC85A
But AT30A differs a lot from VC264

Will do more bin comparing later but I hope I can get some definitions done. I'll start a new thread later on when I get some results to share.

VC269 is the latest update for VC266. VD70A is for 2006+ models that have 4x O2 sensors, a crank sensor on the bellhousing and an IAT sensor in the MAF.

Hello.
Is it difficult to create a definition file for JDM V36?

That’s going to be a CAN based ECU it seems. Which is unfortunate, as CAN ROM definition automation hasn’t been very successful so far, despite having an a2l for a Juke