Kind ROM request WD10EADS-22M2B0 board 2061-701640-700 02PD1

[Corsari]

Hello to all of you

The board of the drive in subject is really much dead

I can't read the ROM neither through terminal

Unfortunately it is a board WITHOUT U12 so I have no info about ROM version.

I've tried many in my DB and from the hddguru stock

So if you kindly want to help providing the .bin ROM file, please verify the FULL board number
2061-701640-700 02PD1

The drive is made in THAILAND it is manufactured OCT 2009 and the s/n is WCAV5269XXXX

needless to say DragonFly2

Thank you so much in advance for any help

[pcimage]

Try this, from nearest s/n I have (WCAV5230xxxx)...

Attachments

ROM.rar

(175.29 KiB) Downloaded 792 times

[Corsari]

Thank you M8!

[Corsari]

Ouch!

Unfortunately I don't have the right donor board

All of mine 2061-701640-xxx are equipped with the U12

I need one U12-less

I'll update you thank you

[Corsari]

Thank you Spildit
But I must admit this confuses me.
I've tried a bunch of ROMS from my db and from hddguru files, but maybe I do something wrong

In fact I got also this info: "write a bare ROM then write needed modules"

I never had to deal with this before and also acelab support doesn't help so much with this case.

What do you kindly mean?

P.S. There is no way to read the original ROM, I have 6.0.16 and also through terminal, no way.

Thank you for some more details

[Corsari]

This is the point
I have only two boards with same number but different revision.
Both have the U12
So i'm not sure they are good.
With both I have the drive that clicks and spins off.

[Corsari]

Rebuild from SA is my original goal

The problem I face is the drive that don't keep on spinning

and blocking SA access I suppose makes no sense if the board basically "points head to the wrong place"

Though the two board I have are not from a 22M2B0

[Corsari]

So I tried to burn ROMS from various 22M2B0

But also writing those ROMS (which some are not fine and go to brick the board) no way, still the same behavior

Drive clicks and spins off

Ok maybe that when the board blown off (it is exploded the head/spindle controller), also the heads preamplifier went dead too.

[Corsari]

Yes
That was the final option.
I've located one with same board label

Thank you really much for the suggestions

[Wkyeri]

On WD drives with burnt VCM highly likely also have burned preamp.
You need firstly check +-5V resistance.

PS. WD drives after 2009 year doesn't contain in SA modules for rebuild ROM.

[jermy]

PS. WD drives after 2009 year doesn't contain in SA modules for rebuild ROM.

in the link provided above by "Spildit"

Get a compatible PCB. Drive should spin up ok, then try to gain access to SA so that you can rebuild original ROM from modules on SA.

http://blog.acelaboratory.com/pc-3000-f ... -v6-x.html

the guinea pig drive were used by ace lab was manufactured on 05 OCT. 2009

[Amarbir[CDR-Labs]]

Hello to all of you

The board of the drive in subject is really much dead

I can't read the ROM neither through terminal

Unfortunately it is a board WITHOUT U12 so I have no info about ROM version.

I've tried many in my DB and from the hddguru stock

So if you kindly want to help providing the .bin ROM file, please verify the FULL board number
2061-701640-700 02PD1

The drive is made in THAILAND it is manufactured OCT 2009 and the s/n is WCAV5269XXXX

needless to say DragonFly2

Thank you so much in advance for any help

Well,
Have You Tried This -> http://ts.acelaboratory.com/index.php?/ ... connection .Also Note That When You Power On The Board Inspect All IC With Fingers And See If Something Is Getting Too Hot If It Does Its Short If Not You Have a Chance

[Corsari]

Hello Amarbir
I've written that above

where I've written that the board is dead so much and also the attempt to read through terminal didn't work.

[fzabkar]

If the MCU survived the surge, then I suspect that retrieving its embedded ROM contents may be as simple as adding two external supplies (+2.5V and +1.2V) and asserting the POR (power-on reset) signal to the MCU.

[fzabkar]

If the MCU survived the surge, then I suspect that retrieving its embedded ROM contents may be as simple as adding two external supplies (+2.5V and +1.2V) and asserting the POR (power-on reset) signal to the MCU.

Assuming that it would work and assuming you wouldn't jtag to the MCU then you would still need for either the TX/RX X-Modem component of the circuit to be functional or for the SATA components to be functional in order to issue VSC to the MCU and extract the ROM in PSV/Kernel mode.

All those components are part of the MCU. JTAG wouldn't be required.

[fzabkar]

The voltage test points would be easy to find. I haven't checked my PCB, but I think the attached image is correct.

NPOR is probably one of the 8 signals that run between the SMOOTH IC and the MCU. It is probably high when the supply rails are OK and low when they are out of spec. That's a matter for experimentation, though. I would use a 1K resistor to test each of these signals, either as a pullup to Vio or pulldown to ground

Attachments

2060-701640_MCU_signals_2.JPG (105.76 KiB) Viewed 12724 times

2060-701640_MCU_signals.JPG (152.99 KiB) Viewed 12724 times

2060-701640_regs.JPG (114.12 KiB) Viewed 12724 times

[fzabkar]

The OP hasn't provided a photo or the results of any TVS diode tests, so it's not possible to say whether the surge hit the +5V supply or the +12V supply. A 12V surge is survivable.

[Corsari]

The first (and unique at the moment) test we did,
has been to completely remove the SMOOTH ic.
Since it made no difference, we abandoned the idea to go further with diagnoses of the board.
But all above is really interesting and requires some tests and measures.

[fzabkar]

The SMOOTH IC generates the supply voltages. Without it, you get 0V for both Vcore and Vio.

[Corsari]

Uh-oh
Never dealt with those type of researches, thank you Fzabkar you are always an authority in matter of knowledge.

That faked our test so, since we thought other components could been burned, while SMOOTH ic could be the unique one so.

Instead we thought (but for a while only) to feed power to the Marvell IC alone, but without schematics...

now you provided important hints.

Thank you