RomRaider

Here's my TODO lists for the combined release:

https://github.com/fenugrec/nisprog/issues/8
https://github.com/fenugrec/npkern/issues/3

Of those, 7051 is impossible for me to test; I don't think I have an 7055_18 either.

If I remember, I should be able to test most of them for SH7058 tonight. However, ABS and TCM will always have CAN communication faults. But given how even after multiple drive cycles they haven't done anything, I doubt it matters much. It'll be interesting to see more about whether P0605 can be avoided.

Thanks, I'll probably take you up on that, but nothing's ready to test - I need to clean up some half-finished changes from troubleshooting the other guy's weird problems from a few weeks/months ago, and some other stuff to combine.



Yes true; I reworded that item as "no ECU DTCs after stopkern (P0605 etc) "

Just let me know when it's ready for testing! It'll be nice to be able to type "SH7058" for ROM dumps, as I always had to go back to the guide to figure out the proper command since I've only done a handful of ROM dumps haha



I meaaannn, disabling P0605 would count as no ECU DTCs after stopkernel

I don't mind clearing P0605 afterwards but an amazing for me would be for it to not fire coils on stopkernel reset. I now remove the engine cover and unplug the coil loom before flashing on any vehicles other than my own just in case.

I guess I'd need to buy an oscilloscope to troubleshoot this further.

I have a "release candidate" build for 1.04.

Before releasing I would like some external testing, at least for the items that don't involve reflashing.

So, I'm looking for one volunteer for each category :

7051 (a33b possibly)
7055 350nm (bradsm87)
7055 180nm
7058 (pytrex)

If everything looks fine with 7055_35 and 7058 I may release anyway without testing on the rare 7051 and 7055_18.

The tests :
first part, without npkern


Second block, with npkern

I can test out SH7058 tonight or tomorrow for sure

Yep I can do 7055_35

hey, i tried to reflash the nissan maxima 7051. i read 256kb successfully. booted kernel 7051 and tried to write modified block number 1. erasing was successful, but writing failed, error. unfortunately there are no logs. But the bootloader wrote that do not worry while you are in the bootloader, you can flash. in the end the ecu is broken. Restored. Didn't try again.

I'm sorry to hear that... but what do you want me to do? You gave no logs, no error messages, not even version info, and you took a chance flashing the first block of your ROM - the most critical. You will have to unbrick it using the method in the sticky thread in these forums, it should be very similar to the 7055/7058 procedure.

Pytrex, bradsm87 : thanks. I will PM you a download link shortly.

Tested all of the above plus more and all good. This was on a bench test ECU so I'm unsure about coils firing but they did that before anyway. It gets P0605 after running and stopping the kernel but it's always done that.

The only other think I'd potentially change is to remove "interface dumb" from the default/example nisprog.ini as interface dumb is already the default. Having it in the ini as well causes it to print that interface is dumb twice. This was the same in the old version.

Great work and thanks again. Best of all, I no longer need to use different nisprog.ini files with different setkeys for the different ROMs that I use because of the updated key set list.

I might be able to do 7051 if I didn't wreck my ECU

Thanks guys. I hammed the first RC build (wrong npkern versions from a few months back), I just PM'd a RC2.


sounds reasonable. Pasted in my TODO, I may or may not add that in 1.04. Need to save me some low-hanging fruit for 1.05 eh...

a33b: thanks, that would be awesome. There was a minor change to the 7051 reset (i.e. stopkernel), let me know if I broke anything.

hey, i already unbrick my ecu 7051. i have been 2pcs cpu 7051 in the ecm))) i did it.

Another one to add:

nisprog prints this line when launched but it's not applicable:
nisprog: Type SCAN to start ODBII Scan
And probably this one too:
nisprog: Then use MONITOR to monitor real-time data

I think it'd be a bit easier to see the "Connected to ECU!" in amongst the other text if some of the other text can be taken away or simplified. Another possibility which might work nicely would be after the "nisprog: Settings loaded from nisprog.ini" to print one more time the connected or not connected status so that it's right there on the last line.

I sent you a PM about he SH7055_35 1.04 RC2 npkern

Cheers