pcmhacking.net

Never tried to burn while on the board, I always remove the NVRAM and place it directly on the programmer

The1 has an excellent guide on this topic here http://pcmhacking.net/forums/download/file.php?id=11662

yep I agree, take it out.

Ive had dramas with just EERPOMs with a memcal adapter. The1 adapter and well as my own made.

I think its something to do with the ZIF socket not liking solid ridged pins and failing to make proper contact on them when closed.

Thanks Burner turned up today_ that was quick. I will give it a shot tonight

had problems with the burner, it wrote the stacked bin file but got this error on verification.

Verify Failed, Address=0x008000, Device=0x07, Buffer=0x00

Does anyone have any ideas on fixing this. tried googling it and found something but couldn't make much sense of it. Not at this time of night anyway.

I tried ignoring the error and hooked it back up but neither TP or Flashtool could find the hardware on bank A.
Cheers

did you select the correct device from the list? if so does it ID correctly?

Yes, selected the correct device, but it is NVRAM chip and doesn't ID. Thanks.

I posted a query on their forum so hopefully someone posts a reply.

Best way to help is to see what you have done. Take a pic of the nvram in the burner and a screenshot of the burner screen. That error means its expecting location 0x8000 to be 0x00 but the nvram is showing 0x07. What bin have you burnt and the file size? Did you specify any offset

The stacked bins in the 12P package are they ready for burning to a DS1245Y?
From memory they are 64kb not 128? I stacked a stock 32k bin 4 times recently and wrote it straight over a corrupt DS1245Y no problem. Would not ID had to find it.

They are 128K as they are provided for exactly this. It looks like one of the pins isnt making good contact or the chip is incorrectly inserted or less likely but possible it could be damaged. I agree with Jayme send a pic of it in the burner for us to check and the software setup.

Thanks guys, finally got it to verify this morning. After about the 20th attempt I unticked the verify box, wrote the bin and then used the HxD program to verify and it gave me the same error as the USB programmer verification, was just about to give up when I stuck it back in once more for a last chance effort and forgot to untick verify and it went through the entire write and verify procedure with no errors. Then I compared the bins on HxD and it confirmed files were identical. I hooked it up to TP and Flashtool and both found the v112 bin.

Problem is now I get an error writing back the CAL. Could this be because the CAL I saved was from v111 and now the bin is v112? I didn't have any chance to take any screen shots as I was running late for work.

I reckon the error message was pretty close to what Dylan experienced here. I didn't change any jumpers from what I had before other than the bank A/B jumpers

http://pcmhacking.net/forums/viewtopic. ... riting+CAL