SOS help needed WD DrgnFly1 ROM regenertion

[MISU]

Hello community
With ref. to my earlier post in hddoracle , I am seeking help from hddguru community

WD Green 5000AVVS AV-GP (WD5000AVVS- 63M8B0) S/N WCAVXXX hard disk is I am working with. Its motor controller ic is burnt.
This model (DragnFly1) is having embedded rom .
I was not having exact pcb (2060-701640-001 Rev. A) so I tried 2060-771640-003 Rev A from WD 10EARS 1TB hard disk.
At that time disk got detected as 250GB (from rom). I tried to apply few loaders (DragnFly2 & others) but couldn't succeed due to lack of knowledge.
I have outsourced this case to another company. They are working & have updated that case is complex and might take time.
I would like to know what could be the solution for this case. Desoldering & reading patient mcu will need lots of skill and again is not easy.
Any hint or suggestion might lead to success. Pls. help.
Thank you

Attachments

[pclab]

Maybe I'm wrong, but if I remember this correctly, ROM should be able to be read even with motor controller burned.

If not, ACElab have several tutorial on how to recover ROM like this one: https://blog.acelab.eu.com/pc-3000-hdd- ... -mode.html

[MISU]

Maybe I'm wrong, but if I remember this correctly, ROM should be able to be read even with motor controller burned.

If not, ACElab have several tutorial on how to recover ROM like this one: https://blog.acelab.eu.com/pc-3000-hdd- ... -mode.html

Thanks pclab
I have visited this blog and have found many useful articles . I have not powered original patient board ,but will check if I could read rom .

[fzabkar]

Maybe I'm wrong, but if I remember this correctly, ROM should be able to be read even with motor controller burned.l

The motor controller generates the Vcore and Vio supplies for the MCU. If the 5V side of the chip is damaged, then no VCore or Vio, so no MCU, ergo no ROM. If you are smart, you could patch external supplies into the Vcore and Vio test points, but then you would need to ensure that POK was active, otherwise the MCU would be stuck in the reset state.

This is the OP's PCB:

https://www.hddoracle.com/download/file.php?id=10234&mode=view

In this case Vcore and Vio would be absent.

[michael chiklis]

I would try to fix the pcb by replacing motor ic.
If you see burnt tracks and pads, you can rebuild them with solder lugs
https://aliexpress.com/item/1005004746483452.html

[MISU]

Maybe I'm wrong, but if I remember this correctly, ROM should be able to be read even with motor controller burned.l

The motor controller generates the Vcore and Vio supplies for the MCU. If the 5V side of the chip is damaged, then no VCore or Vio, so no MCU, ergo no ROM. If you are smart, you could patch external supplies into the Vcore and Vio test points, but then you would need to ensure that POK was active, otherwise the MCU would be stuck in the reset state.

This is the OP's PCB:

https://www.hddoracle.com/download/file.php?id=10234&mode=view

In this case Vcore and Vio would be absent.

What a thorough technical explanation fzabkar you know inn things
Thank you so much

[MISU]

I would try to fix the pcb by replacing motor ic.
If you see burnt tracks and pads, you can rebuild them with solder lugs
https://aliexpress.com/item/1005004746483452.html

Hi michael
yes if everything else failed then possibly that is the only option left.
thanks

[pclab]

Maybe I'm wrong, but if I remember this correctly, ROM should be able to be read even with motor controller burned.l

The motor controller generates the Vcore and Vio supplies for the MCU. If the 5V side of the chip is damaged, then no VCore or Vio, so no MCU, ergo no ROM. If you are smart, you could patch external supplies into the Vcore and Vio test points, but then you would need to ensure that POK was active, otherwise the MCU would be stuck in the reset state.

This is the OP's PCB:

https://www.hddoracle.com/download/file.php?id=10234&mode=view

In this case Vcore and Vio would be absent.

Understood. Thanks Fzabkar.

[MISU]

Maybe I'm wrong, but if I remember this correctly, ROM should be able to be read even with motor controller burned.l

The motor controller generates the Vcore and Vio supplies for the MCU. If the 5V side of the chip is damaged, then no VCore or Vio, so no MCU, ergo no ROM. If you are smart, you could patch external supplies into the Vcore and Vio test points, but then you would need to ensure that POK was active, otherwise the MCU would be stuck in the reset state.

This is the OP's PCB:

https://www.hddoracle.com/download/file.php?id=10234&mode=view

In this case Vcore and Vio would be absent.

You are true genius fzabkar .Thanks for the indepth details.

[MISU]

This case is unsolved yet as many DR companies have failed , ACE is also not able to solve .Anyone wants to give it a try before I return disk
Anyway customer is also not keen on data so I will not get any money & in turn will be able to give.
Its only a technical challenge who want to take there skills

[fzabkar]

Did any of the DR companies swap or test the heads? There is always a risk of preamp damage when the drive has been overvolted on the 5V side.

[MISU]

Did any of the DR companies swap or test the heads? There is always a risk of preamp damage when the drive has been overvolted on the 5V side.

Thank you fzabkar
No they tried to match different pCB's and tried to regenerate ROM ,they suspected head issue but since rom native rom itself was not present they did not changed heads.

[fzabkar]

You can measure the resistance between ground and each of the preamp supply pins. Do this with the PCB on and off the drive. This will tell you if the preamp is damaged.

Attachments

HDA_preamp_supplies.jpg (132.82 KiB) Viewed 864 times

Preamp_negative_supply.jpg (88.17 KiB) Viewed 864 times

[MISU]

You can measure the resistance between ground and each of the preamp supply pins. Do this with the PCB on and off the drive. This will tell you if the preamp is damaged.

Good Morning fzabkar
I don't have words for gratitude , a big Thank you
I will check & revert.

[northwind]

What is so difficult about this case that has caused 'many DR companies' to fail?

It's called hotswap.

[MISU]

What is so difficult about this case that has caused 'many DR companies' to fail?

It's called hotswap.

ROM is embedded inside MCU , and hot swap is not supported or working for this model they said.

[pepe]

well, it should not be that difficult, idk what they were talking about... either hotswap or ldr should give sa access pretty easily.
If not, there is other problem, like preamp or even data erasure due to damaged preamp, but as i read, head swap wasn't even tried...
I would surely evaluate this option and check the head signal if SA is still not accessible. Plus i have a few other things to try if there is data erasure as mentioned.
pepe

[northwind]

and hot swap is not supported or working for this model they said.

This is probably the most ridiculous thing I've read in a very long time.

[MISU]

and hot swap is not supported or working for this model they said.

This is probably the most ridiculous thing I've read in a very long time.

Oh its strange , they are well reputed having all gizmos and big business ,why can't they solve this simple case even with the help of ace support.