RomRaider

Donations are welcome!

New release to support some features related to the CarBerry ROM.

--------------
- Change Log -
--------------

0.5.3b RC10 (build #334) (2011-09-12)
------------------------------------

--- Editor ---

• Added support for multiple-state switches. Switch Tables will now use Radio Buttons rather than a Checkbox.
• Added ECU defintion data validation for Switch Tables. If the ROM image data does not match one of the switch states according to the definition then a warning is presented and the table is locked from editing.
• Added ROM Checksum validation on image open for 32 bit ROMs. An ERROR message is presented warning not to use the ROM image as it may be corrupt.
• Added ROM Checksum calculation for 32 bit ROMs. Upon file save the new Checksums (if not previously disabled) are written to the ROM.
• Added a ROM Edit Stamp to 32 bit ROMs consisting of the YYMMDD and an incremental count value. This Edit Stamp is displayed in the View->ROM properties menu item.
• Fixed the missing Table Tree problem when running RomRaider on systems using IcedTea or OpenJDK JVM.

--- Logger ---

• Added more selections to the Right-click menu associated with the LogFile text field.
• Made Fast Polling the default mode for the Logger connection.

Please download it and give it a workout!

Downloads: Windows Installer | Windows ZIP | Linux Installer | Linux ZIP


RomRaider Troubleshooting FAQ for Windows Vista/Windows 7

Awesome work, thanks a ton

Fantastic! Glad you own a Subaru, dschultz!

Ones again, great work




Got a problem with that, when opening diesel ROMs:
all ECU-read-out dumps are marked to have incorrect checksums..
The same, when I open them with ScoobyROM...

SDC got allready patches with they drive, so they have to recalcuted the checksum correctly. Via mail they told that EURO4 Diesel got the same checksum algothymus then pentrol 32-bit ECU..

But why the hell of all tools tell to have in incorrect checksum ??
What will happend, if I use my original dumps as basic for a tune-dump ?
Does it work or should the checksum be disabled ?

Very confusing by the Diesels..

I am not sure, better to give a warning for the Diesels as long as we are not sure, that the checksum is correct calculated ?

Best regrads

p.s.:
I very glad, that RomRaider supports the Diesels as mutch as they can

I'm sorry I did not check the diesel ROM regarding this checksum validation/recalculation.
I looked at the JZ2F401A ROM and of the 17 checksums defined the 5th one is in error.
The 5th checksum is almost a duplicate of the 2nd checksum except that it covers 64 more bytes. It is in the last 64 bytes that the calculation becomes invalid. That 64 bytes is immediately before the reflash counter, the region 0x0ffac0 - 0x0ffaff. The last four bytes are the only thing that is not 0xff in that area.

The same to all complete Diesel dumps I got: everytime 5th one is idecated as incorrect in ScoobyROM


When I compare this area of all diesel dumps, everytime this last 4 bytes are differnt..

I don´t know if this helps..
IMO more imported is to know, if the ECU cares about this worng 5th checksum..

Tool like ECUtek, Piasini, Byteshooter or Firling can flash the Denso Diesel ECU allrady, so someone has to know, how to handle this problem..

BR

well i can say i am probably the most computer illiterate person alive and have no idea how to make the new romraider work, heck i even delted the 5.2beta and redownloaded this ne and now it wont even open atleast before it would open but just wouldnt give me certain menus

aand now i keep getting a data mismatch for every obd P0 code along with a few of the mew files

Not sure if this is a problem, or if it related to this thread.

Since RC10, it looks like whenever I open an edited ROM I get a warning that 'All Checksums are disabled'. My stock ROM loads without warning.

I am about to start flashing soon (waiting for my OP2) and I don't want to muck anything up. Should I be concerned about this? This seems different then a checksum error, but I am not clear about what this is telling me.

Thanks

You have nothing to worry about.

Prior to RC10, when you edit a ROM with RomRaider and saved it the Checksums would be "disabled". This disabled mode meant that you could edit any part of the ROM and when the ECU calculated the Checksum it would match the disabled value.
So the warning is telling you that the Checksums are disabled, i.e.: not in stock format.

If you want Checksums enabled, open a stock ROM and your modified ROM. Copy the modified tables to the stock ROM and then save the stock ROM as your new tuned ROM. The checksums will be recalculated properly and upon opening the ROM again in the future you will not see the warning.

BTW: EcuFlash gives the same warning when opening ROMs edited with pre-RC10 RomRaider.

Thanks....so the warning has nothing to do with the integrity of the ROM. Great.

The OP2 came today....oh boy!

Only in that the integrity of the entire ROM space can not be verified when the Checksums are disabled.

When the Checksum is enabled and detects a corruption in the ROM you'll get a different message.

I have an issue on my smaller laptop installing romraider. its running windows 7 professional and 32bit java... My main tuning computer runs windows 7 ultimate with no issues... is there something really dum im missing?

What part of the install does not work?

ones again comming to this checksummproblem:

Just for me to unterstand:
I try to unterstand how the checksum is calculatet:

Do I unterstand correct:
the algorithmus looks at the checksum table and calculates the area with is displayed in the dump. If the result of its calculation the same then the checksum in the table, verything is allright. IF not, I got a problem ?

So the areas are not fixed and depent ont the values of the dump for this algorithums ?

So, if I bend the 5th checksume of the area of the 2nd, we expact a correct result ?

If I want to deleate the checksum, I have to set all areas to "00 00 00 00 00 00 00 00 5A A5 A5 5A"
But best way is to have a correct CS for original and tuned dump

At SDC someone mentioned the same problem, because scoobyrom do also displayed the original checksumms as wrong.
They give not really a answer to it, only it is possible that this this CS does not care..
I don´t know, they worte they drive with there one patched software, so CS is a thema form them

BR

(edit)

bwt:

Logger works perfect with the Diesel..
In comparison to ECUFlash stand-alone logger, the ECU-parameter are more then 10 times faster to log..

So if you like to log ECU-parameter, stand-alone logger is no alternative to RR

It may be true that the failed checksum has no impact on the operation of the ECU, it may truly not care.

The checksum table contains up to 17 areas to validate. The form of the table is:
To calculate the checksum start at the start address and sum the Dword values together up to the end address (drop any carry-over). Subtract the summation result from 0x5aa5a55a and this should equal the Difference value in the checksum table.
So to "disable" a checksum use the form above. The checksum is still calcualted but the sum of address 0x0 to 0x0 is 0x0 therefore 0x5aa5a55a - 0x0 = 0x5aa5a55a.