RomRaider

Is there a special version of RomRaider we have to use?

I downloaded RomRaider 0.5.9 Release Candidate 3 (0.5.9 RC3)
I git cloned a33b/NissanDefs and pointed RomRaider Definition File manager to cd700.xml
Tried to open a user submitted my_rom.bin and got ECU Definition Not Found.

Then I did a directory diff with Nissan ECU Reflash.zip that stirkac provided and noticed the the Version.class is 0.5.9 Nissan 1.

Are there changelogs about the Nissan 1 version?

You should set Definitions manager to point to nissandefs.xml (combined file) and not cd700.xml.

Hey, I have an issue with the guide.

On the section "ECU Specifics" it states:

However, it appears the site only searches Japan/Europe VINs. I am looking for the ECUID of an USA 350z. Where can I find this?
Further, is it even required? The post heremakes me think otherwise

Ah it's cool, I just ripped my ECU out to get it the manual way.
Turns out I could have also used this site (someone else mentioned it earlier but I didn't see): https://nissan.7zap.com/

Your ECUID will automatically show up in Nisprog. This is just to give you an idea of what flashing kernel to use. You can DUMP the ROM using any of the kernels as long as you specify the proper length in your dumpmem command. But using your ECUID, you'll be able to compare it to similar ones to figure out if you're SH7055/SH7058.

I keep getting errors with Read/write timout.
.ini:
set
debug l1 0x8c
interface dumb
port COM7
dumbopts 0x48
l2protocol iso14230
testerid 0xfc
destaddr 0x10
addrtype phys
up
nc

setdev 1
runkernel C:\npk_SH7055.bin

Input/output:
diag_os_gethrt() resolution <= 0us, avg ~0us
diag_os_getms() resolution: ~16ms.
Calibrating timing, this will take a few seconds...
Calibration done.
nisprog v1.03-01af433
interface is now DUMB
Note concerning generic (dumb) interfaces : there are additional
options which can be set with "set dumbopts". By default
"K-line only" and "MAN_BREAK" are set.
nisprog: Type HELP for a list of commands
nisprog: Type SCAN to start ODBII Scan
nisprog: Then use MONITOR to monitor real-time data
nisprog: **** IMPORTANT : this is beta software ! Use at your own risk.
nisprog: **** Remember, "debug all -1" displays all debugging info.
No such item !
interface is now DUMB
Note concerning generic (dumb) interfaces : there are additional
options which can be set with "set dumbopts". By default
"K-line only" and "MAN_BREAK" are set.
port set to: COM7
dumbopts set to: 72
testerid: using 0xFC
destaddr: using 0x10
diag_l2_iso14230.c:755: Read/Write timeout.
diag_l2.c:435: Read/Write timeout.
L2 StartComms failed
Unrecognized command. Try "help"
Must be connected normally (nc command) !
nisprog: Settings loaded from nisprog.ini

Hello. Thank you very much everyone involved for putting together such a thorough document with ample resources. I do appreciate this very much. I may have some questions when I begin to run with ECUID number if it doesn't exist but I will follow everything you have mentioned. I really can't stress enough how valuable this walkthrough is and how straight forward the instructions are. Just wanted to drop a line.

Hi, i am new to this and willing to learn, but had some obstacles....

Maybe you guys can lend me a hand to get things clearer.

I need to tune the 2006 350z of a mate, because he had mounted 200-cell catalysators and now runs into engine fault codes every few days.
It is a 350Z with CF44A ECU (no definitions, but thats ok for me.

A few weeks ago i managed to dump the bin from the car through nisprog. It was 512kb, and took almost an hour to dump. But it seems ok, as i send this to a guy, who makes tuning files and he said, that the file was ok and he could use to tune and switch off fault codes from cat.

I am running now into some questions

1. In the tutorial it is mentioned, that you know that runkernel runs, when car fans start (with ignition on). This is never the case with the car here??????? But i can connect and finds CF44A as ECUID also through nisprog.
2. Are there some changes in new version 1.04? Looks like the nisprog.ini looks different than mentioned in this tutorial. Also the nissandefs.xml seems to be nowhere in the zip-file.
3. I am not sure, if my programmer already did checksums, does nisprog change them itself, when starting to write? Do i need to check before with Romraider? Can't load the file into Romraider, as i have no definitionsfile...

I don't want to brick the car's ECU, and as it is not my own car, will need this not second time
So i can't really use "try&error"....

Thank you!

Christian

Stupid question but where do I find the latest NISPROG.exe?

Check the bottom of the first message in the Nisprog post here on RomRaider.

For anyone following this old tutorial I just wanted to say, update Nisprog to the newest version. I was able to successfully dump my CD001 ECU Rom.

Does anybody know if 04 350z base and 04 350z roadster definitions would be the same? nobody has defined the roadster. CE820 is base and CE810 is convertible.

do i need to dump my ecu to run a kernel? wont let me command to runkernel but i did do a dump without it since my b15 2003 spec v ECU hasnt been listed yet