NV RAM REPROGRAM

[v8-tuning]

Hi
Ive reprogrammed a dallas ds1245y off one of vl400s nvram boards
It corrupted during a computer crash so ive re programmed and used the stacked v111 bin 128k.
It writes and verifys fine.
I cant read anything in tuner pro and i have a brand new one sitting here too
same thing.
Is there a way to read and verify in tuner pro ?
I cant use the id function on this either ive found.
Burner is the GQ4X.
Removed sram from board and its straight onto the burner.

[antus]

The plugin doesnt support verification, it could be added but so far there hasnt been interest, in fact your the first person to mention it.

It sounds like you dont have the plugin setup correctly, if you can read it in the flash tool, note the com port and echo setting and configure the plugin the same way in tunerpro then hit detect hardware and see what it says.

If you cant read it in the flash tool, check the basics - does the ecu go in to limp home mode when in the car, or does it run ok? Has the ecu worked beforehand? If you did the comms mod and r/w pin mod your self, re check that its good.

[v8-tuning]

Problem is i can only use the burner to program and verify
I currently got no car to test one on although i will once i find one.
Whats usually the process when burning the stacked v8 bin
on the nv ram?

[VL400]

When burning one of the stacked bins in the 12P zip you load it with zero offset. When you open the bin to burn a dialog box will popup, ensure file offset is 0000. After clicking ok on the right hand side of the main program window (below where it says DS1245Y) there are two boxes file offset and device offset, they should also be 0000.

Thats it, have write and verify boxes checked in the auto mode, click the auto button and it should burn and verify. If your not sure still, do a read of the NVRAM after burning and post the bin here to be checked.

[v8-tuning]

I did exactly that and it burnt and verified ok.
But no way to check i guess without a car.
I thought you could check the bin in tuner pro like other tunes
but comes up as a bunch of 000s yet the 32k 12p bin is fine.
Must be due to being a 128k bin file.
Here is the bin file i read.

[VL400]

Looks good to me, compares exactly to the original stacked bin.

And, you are correct, the offsets from a stacked 12P bin mean you cannot open it and check tables etc in TP.

[antus]

just to be clear as I know there is a bit of confusion out there about stacked bins - they only exist to make it easy to write the nvram for the first time (or if its corrupted) in the gq-4x so that you dont have to worry about offsets. Once you have written a stacked bin and placed the nvram in the ecu, just treat it as normal.

[v8-tuning]

Ok thanks, good to know its right just wasnt 100% sure ,appreciate the help