Switch to full style
Discussions related to DFL tools: general chat, firmware requests
Post a reply

Case Study for WD10EAVS-00D7B0

November 6th, 2018, 20:47

Hi, this is a short case study for the said drive.
The drive had come in an external enclosure with USB FIREWIRE extension board 4061-705016 having Oxford Semiconductor controller
The PCB that the drive had is 2060-701537-004 REV A

The drive suffered a PCB failure and had masked rom.
the following steps were executed

1)Procured an identical board
2)Downloaded the rom code from HDD surgery. I had no clue for the microcode, hence had to near match the S/N to take a wild guess.
3)The drive SPUN up with the donor rom and SA was accessed and all modules were backed up. Drive IDed here, scanning was slow, poor microjogs or poorly matched 47 was doubted.
4)ROM was regenerated.
5)The generated ROM was patched.
6)The Drive IDed correctly.
7)Relo was cleared.
8)Slow Read Fix was done.
9)Drive had all its heads working and was imaged using DeepSpar

All data was recovered as drive was having working heads but it clicked a few times before it detected indicating partial failure.

Any way some one can lead me to identify the MAGIC RESISTORS so that the protocol can be switched over from masked rom to external U12 Chip?

Thanks.
--

Re: Case Study for WD10EAVS-00D7B0

November 6th, 2018, 22:31

Well done, @sin! Thanks for sharing. For the resistors question, see the "WD Royl PCB Resurrection" post by @pcdiag in DFL's user forum.

Re: Case Study for WD10EAVS-00D7B0

November 7th, 2018, 8:52

Thankyou @LarrySabo

thanks for the link.

--
Post a reply