OSE12P to DS1230y

[MOPAR]

Long story short, I was using Delco FlashTool to update a Cal, not thinking I clicked Write Bin and have corrupted the NVRam. Its been a few years since I wrote the original OSE12P ONTO THE DS1230Y so my memory is a bit scetchy. I dug out the old willem and have tried writing the latest OSE12P bin to the DS1230Y. It writes and verifies but I cant connect with flashtool or tunerpro? I can't remember what version of the willem software I used previously but I think the programmer is working correctly as I was able to read a std 16k memcal and compare it to one on file. any suggestions?

Just had a thought, Do I need to split the OSE12 bin as it is being written to a 32k NVRam?

[vlad01]

did you use the stacked bin?

[Holden202T]

for a 1230 chip you should not need to stack at all, simply write the bin file that is in the $12P zip file and it should be right to go, you'd only need to use a stacked bin for ds1245y.

[MOPAR]

for a 1230 chip you should not need to stack at all, simply write the bin file that is in the $12P zip file and it should be right to go, you'd only need to use a stacked bin for ds1245y.

That's what I thought. Im not convinced the willem is programming the nvram properly. But at the same time I have tried to update to the latest version of Plugin, Flashtool & Tunerpro. Maybe Im missing somthing there.

[antus]

The file your burning - did it come from the 12P zip file? If you downloaded a cal only then it will be missing the code and only contain the calibration and wont run the ecm. To fix flash in a stock bin from the 12P zip file then load your tune and upload cal with TP or the flashtool. Also check you have plugged the nvram chip in the socket up the right way, and if your nvram circuit board has the 1230 jumper - set it.

[MOPAR]

yep the bin files is 'OSE $12P V111 APNX V6.bin' from the ose package & Flashtool V1.45 the memcal is setup for the ds1230y and was working fine previously. I was using an earlier OSE $12P Version before I corrupted it. Trying to find someone local with a programmer to see if its a problem with my Willem or if im missing something else with the setup. Just not convinced the programmer is writing the NVRAM properly.

[MOPAR]

Ok, I found a local engine builder who has a pocket programmer for his kalmaker gear. We tried copying the OSE12p.bin to my ds1230y a couple of times but it would not verify. was showing a block of data in upper address range was not right so I was thinking maybe the chip is faulty. I went home and tried it anyway, no surprise it didn't work so then I read the NVRAM with my willem and compared it to the ose12p bin using tunerpro difference tool and it shows they are identical I am totally confused now.

[MOPAR]

Finally got this box of shit willem working ended up reinstalling windows XP & drivers, still wouldn't work then I tried programming the ds1230y as a 28c256 eeprom and success! Typical though I just ordered a TOP2011 USB programmer and then this one starts to work!

[Holden202T]

on the positive side you now have a backup programmer