Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
July 31st, 2009, 11:58
I've got an ST96812A that I was attempting to load the ROM for onto a new PCB. The PCB worked fine on the drive it belonged to, was detected normally, etc. After using the Salvation tool to upload the patient ROM to it, it now detects as MASKROM instead of MERC2. For the purposes of experimentation I took a functional ST96812A, saved the ROM, re-uploaded the same ROM, and the drive now detects as MASKROM. To me this implies that the Salvation tool is incorrectly uploading the ROM or corrupting it in the process.
Any other thoughts?
July 31st, 2009, 14:55
Indeed, examining the ROM after uploading something, the ROM contents do not even closely match the file that was uploaded. I have monitored the commands that are being sent when uploading. Anyone who knows more about uploading ROM through terminal please PM so we can compare what it is doing with what it should be doing.
July 31st, 2009, 15:06
It doesn’t surprise me with the poor ROM support on the WD doctor that the Seagate would have problems. I would say, ask Rocky and the gang, but they usually answer quickly and rarely ever fix anything. Good luck.
July 31st, 2009, 15:28
Had to flash a mercury recently...
F>d400,0
sdld rom image
F>f
ok
ok
ok
.
.
.
So I guess you should change the 400 to read buffer for merc2
July 31st, 2009, 16:59
Yeah, I'm not surprised, but I am disappointed. At least in the case of Seagates it should be pretty straightforward to implement a workaround.
August 2nd, 2009, 13:25
Well ,
I Had a Word With Thier Fellow Called Alex ,thier Seagate tool stinks old shitty interface and no documentation for the terminal commands ,If You Do Not Now how the seagate family works how the hell are you going to repair one ,Also How Can they Foolishly Assume Newbies Do .
August 2nd, 2009, 23:57
viktdev wrote:So I guess you should change the 400 to read buffer for merc2
not to read buffer but to flash buffer
different families have different flash buffers and that's why it is easy to screw up ROM when you writing and using incorrect SDLD buffer for flash
I guess the reason why SD does it incorrect hides in early versions of PC3K which were obviously "researched" (or should I say copypasted) by SD guys
PC3K still has problems with some Seagate families ROM writings but I think AceLab fixed Merc2
August 4th, 2009, 20:50
Well, with collaboration from viktdev (thanks!) I have worked out the issue and gotten my tester drives back up and functional. Turns out Salvation is just doing it wrong.
August 4th, 2009, 21:54
My SD tools give me a lot of cruppted ROMs in Seagate and WD...
Keep hearing that they were working on and improving it but I haven't seen much lately.
It is a bit disapointing.
August 4th, 2009, 23:45
hddmania wrote:My SD tools give me a lot of cruppted ROMs in Seagate and WD...
Keep hearing that they were working on and improving it but I haven't seen much lately.
It is a bit disapointing.
I won't even attempt to write to rom on a WD with SD, until
they solve this problem.Original WD dr worked great, but all the
latest updates don't properly write (actually they don't properly
read the roms)
August 5th, 2009, 0:16
Now days, I'm using the actual external ROM writer to read and write ROMs. HD DR killed a lot of good PCBs by not be able to property write to the ROMs... But it does work well on Royl for some features!!!
August 5th, 2009, 0:38
My external writer that they sent has never worked properly. I don't think I have ever used it successfully.
August 7th, 2009, 14:23
Yep, I gave up on the external writer, never worked properly. It would only write every other byte.
SD's answer was "well, our test one works"
January 21st, 2011, 7:56
I resume this old post to write that I have the same problem with a ST9250827AS .
did a safety copy of donor and patient ROM and then Swapped heads
After that, i needed, for some other reasons, to put back the original ROM readed with SD tool for seagate.
Now terminal show such MASKROM problem.
Some of you knows how to bypass or to solve this problem?
Please, PM me for solutions, if any.
Thank you
January 21st, 2011, 9:44
You'll have to send the rom image with the sdld protocol at the good flash buffer adress. I don't know if sd dr seagate will do it from terminal....
January 21st, 2011, 9:59
If you don't want to research - programmer will help you
Powered by phpBB © phpBB Group.