RomRaider

My 50 cents for next planned release then



It's a 384 kb ROM from SH7054 CPU and I needed to recompile npkernel to move comms from SCI1 to SCI0. Surprisingly watchdog was on the same pin.

Not really sure what the car is as it is declared to be JDM Primera P12 with QG18DE while googling gives Nissan Serena with the same engine.

Actually I was thinking that putting the keylist inside the application code is a kind of non-optimal. External definition file would be much more handy... But yeah, it's all about time to be spent for implementation

Added to the list, thanks.



Maybe, but the main ROM transfers the port + pin number to npkern when starting up, so it should work on any pin def.
I'm more surprised that the other stuff works - wdt timer, reflash algo, etc !



It is optimal for me ! the code is simpler, and updating the list only takes a few seconds, and then "make".

But yes, it would be pretty easy to read from a plaintext external file. Anyone can submit patches - so far you're the only one to have done so !

I didn't try reflashing it - I was 100% sure that ECU is based on 7055 CPU and didn't want to wait for ~2 hours for slow dump.

So I grabbed just the area 0x15000..0x22000 to get keys, spent some time wondering why kernel doesn't work but ECU doesn't reset - first idea was to check the SCI and luckily the bootloader shows its initialization in first ~500 bytes exactly to the "unusual" one

SH7054 is about SH7055F 0.6um version with less RAM\ROM memory.
It does not include embedded Erase\Write routine and does not not follow Renesas Protocol C bootmode as SH7055SF \ SH7058 0.35um and SH7058S do.
Watchdog pin for a similar chip is the same historically.

23710-CM37A 0x3722E94F 0x1FF13669

duplication

{"CM30B", 0x3722E94F},
{"CM31C", 0x634D157A},
{"CM32A", 0x3722E94F},
{"CM32A", 0x3722E94F},
{"CM41C", 0x634D157A},

Hello need keys for 23710-AM900, because non worked correctly it saying sid36 problem when trying to run kernel 7055_35.

Thanks in advance

If it was a wrong key it would be a SID27 InvalidKey error. SID36 is something else, you'll have to post a log with the exact error.

***EDIT***

Was my fault! Exactly kernel had wrong file size ( downloading issue ), flashed, works great! Please accept my apologies.

Hi all,
somehow I've been dragged into working on nisprog again. I'm preparing a new release, and I'm doing a "last call" if any of you would like to add keys that you have, and that are not already in https://github.com/fenugrec/nissutils/b ... uid_list.c

In a few days I'll be packaging and releasing nisprog 1.03.

Nice! Thanks again for the great product. Any hints on what the main changes will be?

Yes please. VC269. Same keys as VC266 and VD70A.

How does it work with s36k keys? They are not on that list.

Cheers

hello, add pls keys for 1ju01a, bt67a, bt47a 1ju00a and other same rom. key1 : C6E19CF0 key2: 685BFBBA

Hi,
I've just packaged release 1.03 and updated the first post in the thread with download links.

Summary of changes:
- improved common SID27 error messages
- warn of possible invalid kernel file
- updated freediag backend
- added lots of keys via nissutils backend, thanks for the submissions
- **** add "guess key" command ****

Please note, the freediag backend update changed a lot of stuff and I HIGHLY recommend doing plenty of testing (dumpmem, flverif, practice mode reflash) before proceeding with an actual reflash. I've tested the build and it "works here", but as usual, this is experimental software that you use at your own risk.

I'll say again : any question, by email, PM or via the forum, that can be answered in 10 seconds of typing "help" or reading USING.txt will either be left unanswered, or get an "RTFM" depending on how I feel.

I'm looking forward to trying 1.03. Looking at freediag changes, it looks like there were Windows timing improvements. Is that right?

Sadly it looks like my VC269 submission was missed. I was kinda looking forward to using the same nisprog.ini for all vehicle types that I flash without needing ones with different setkeys commands.

No, they all made it into nissutils, but somehow I half-assed the nisprog udpate and didn't update the reference in there before compiling...
I just pushed out 1.03b to replace 1.03.

VC269 isn't on ecuid_list.c in nissutils on github.