RomRaider

You've probably figured it out by now. I only discovered this after doing it a much harder way. Download nissutils here:

https://github.com/fenugrec/nissutils

Compile nisrom and run it against your ROM. It outputs a bunch of info including checksum locations.

Compiling is a bit of a pain for non-programmers like myself. I haven't yet worked out how to to compile it as a windows exe that has no dependencies on cygwin.dll and goodness knows what else.

Hey guys,
Looking for some assistance in creating a definition for the attached ROM dump from a very early 2003 350z touring VIN #JN1AZ34D93T108423. I'm a software engineering but totally new to this so any assistance would be GREATLY appreciated!

Thanks!
Josh

Hey guys,
After posting the last ROM I was informed it was a really old version that wasn't worth building a definition file for. Just had the ecu updated by the dealership and pulled the new ROM. It was also suggested the updated ROM would likely already have a definition file. I'm not sure how to tell if a definition file is available for this ROM? Any help greatly appreciated!

Thanks,
Josh

My_rom - 1CD001
Updated_rom - 1Cd002.
What do you want find? Say maps name.

Thank you for the reply. I'm trying to find out if there's currently a definition file for this ROM? If not what is the process for developing one?

Thanks!
Josh

Hey Josh welcome here, sorry didn't notice your posts over the weekend. There's a how-to make defs thread here.

I would recommend using at least the CD002 ROM file if you are going to start a def from scratch. See the stock ROM list http://www.romraider.com/forum/viewtopic.php?f=65&t=11098

I also updated the first post in this thread with the most current fork of the defs. CD700 should probably be a good starting point for finding the maps in your ROM.

Awesome, thanks!

So with Cd002 it was suggested to use the Cd700 bin and def. I grabbed the defs from git and ran the bat to combine it, pointed romraider at the xml and loaded the bin. Just looking at the ignition timing map I think I've messed something up since these are not plausible values.

I tried opening several bins with the same results... What did I do wrong?!? Thanks guys!

First, you should grab the updated defs I linked to earlier as the axis descriptions have been updated. This will help you understand that the timing map is an ignition trimming map, not an absolute BTDC value.

Second, the values that have +128 added to them are a high knock sensitivity region for the ECU. Unfortunately RR has no built-in method of filtering those values out for display, so I often manipulate ignition maps in a spreadsheet and then paste them back into RR.

Lastly, as far as using cd700 as a reference. I expect the map structures to be identical though likely at different addresses. You can easily identify the major maps in wols 2d view, it could be that all the maps are offset a certain amount.

What do you mean, did we talk about this before?

Yeah, we did. The 'byte to expression' logic is simple; just an if statement or an AND. Restoring the byte is more difficult without keeping a record of which values have been edited for display purposes.

A33b thanks for the help. Here's the def I came up with for the cd002 rom. I was able to find most of the important tables. I'm not sure how to locate the checksum and hardware ID though? Any suggestions for those?

When you say I need to up date my defs, this is where they came from:
https://github.com/murphyslaw05/NissanDefs

Is this not the correct location to get the defs?

I ran nischeck.exe and found the checksums. I'm curious because I changed the bin saved as a separate file and then looked at the checksum values in wols but they still are the same between the two bins... (yes I recompiled the defs xml ) Is this calculated over the whole bin file or a subset? Just trying to validate the checksum.

Assuming that is all correct all that is left is the hardware id (hwid)

Make a new version of your project in wols based on the modified file and see if you can see the changes.

I'll be done fixing up your def (nice effort) in a couple shakes! I'll upload it to the current repo https://github.com/a33b/Nissandefs

I didn't think this would take so long. Ran into a bit of trouble and not sure what's going on with these parameters. I've double-checked the addresses and they are correct, but the values displayed start 0x1 position lower. I'm going to try deleting all the comments to see if they're doing something. I was using the wrong ROM.

Attached and I've updated the git repo. Download the repo linked above to use the definition attached.