WD80EMZZ PCB Replacement

[allen labarge]

Hi All,

I need to replace the PCB on a WD80EMZZ with burnt out diodes on the
12v side. I have the replacement board, but am not sure if it would be
best to swap the Firmware from the original board to the new, or
replace the burnt out components on the original board.

Does anything other than the Firmware chip need to be swapped to the new board?

Any guidance would be appreciated.

[Alandata Recovery]

 test the board after removing the diode... 

Might just work... 

--
Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
---
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/datarecoverycertification/CAA7UCOq0uAUh4mJXz2u4Gm6NN%2BMBtT2ELpnfz9E6L0QGP6Qovw%40mail.gmail.com.

[pbzcbf...@gmail.com]

This board has a location which is reserved for a dual e-fuse. It also has two smt fuses and two TVS diodes.

If yours is the latter version, then remove the shorted diode and check the corresponding fuse. If the short goes away after removing the diode, you should be OK. 

If you upload a photo of the PCB, I can show you the test points. IMO moving the ROM(s) is much riskier than fixing the PCB.

[allen labarge]

I have attached an image of the board in question.

Both of the Diodes on the 12v side, show short in diode mode in both directions. The fuse was open and a capacitor was shorted. I removed the shorted capacitor, fuse, and the diode in the Red Square (23M27). The Diode in the Orange Square (BG2C105) also shows Short. Nothing is out of sorts on the 3.3v/5v logic side.

Since I was unable to find replacements for the bad components, my thought was to swap the firmware from this to the new one but there appears to be 2 chips for storage. An 8 pin, most likely Firmware and a BGA, which I am not sure the purpose of. I dont want to move the firmware chip and find out I need the BGA as well.

--

Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
---
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/datarecoverycertification/9b9fec9a-5222-487d-9c8a-a89249be79a0n%40googlegroups.com.

[Alandata Recovery]

Did you bridge the fuse? 

To view this discussion on the web visit https://groups.google.com/d/msgid/datarecoverycertification/CAA7UCOrWa8Haq4K8X3gtNpau770v492aWJUOvn%3D2x5%2BdU%3DDaag%40mail.gmail.com.

[allen labarge]

I have bridged the fuse, removed one of the shorted diodes, and
removed the shorted smoothing cap.

> To view this discussion on the web visit https://groups.google.com/d/msgid/datarecoverycertification/CAH-%2BjWR84X-6-ie6aUFaV%3Dx0oN%2Bk0ynvRDWESn4LxFKV6inDaw%40mail.gmail.com.

[pbzcbf...@gmail.com]

I doubt that the cap was shorted. The shorted TVS diode probably made it look bad because they are connected in parallel.

Can you measure the voltages in the attached screenshots?

[Alandata Recovery]

Usually moving the ROM does it. 

It's easy to read and write with a pogo pin reader. 

With encrypted WD sed drives you need to move the CPU to use another board. 

So move ROM, if data encrypted then... 

--
Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
---
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/datarecoverycertification/3582822e-187c-4f6f-b589-ee495d1fcd8en%40googlegroups.com.

[pbzcbf...@gmail.com]

If you decide to dump the ROM, I can check its integrity for you.

[allen labarge]

Sorry its been a few days since my response. I was working on some
other projects. I would greatly appreciate if you would check the
integrity of the file for me. I looked through it, but it did not look
like it was correct. I did however dump it, and then reconnect and
verify against my dump, so I know the dump is accurate.

On Sun, Jul 28, 2024 at 12:03 PM pbzcbf...@gmail.com
<pbzcbf...@gmail.com> wrote:
>
> If you decide to dump the ROM, I can check its integrity for you.
>

> --
> Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
> ---
> You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/datarecoverycertification/4b63392e-d46f-462d-b92a-04fe0c4346f8n%40googlegroups.com.

[pbzcbf...@gmail.com]

Looks OK.

Analysing WD8000 Customer Drive.BIN ...

Searching for LDSCs and verifying PCMBlocks ...

LDSC   LDSC    Att   PCMBlock          RAM         size      PCMBlk CS
Start  ID CS        Start -  End     address     RAM / ROM    Exp/Act
-----  -- --   --   -----   -----   --------   ------ -----  ---------
    0  5A C9   04      20 -   C4F       1000      C2C   C2C  0004E14E 0004E14E OK (not digitally signed)
 1000  01 AE   04    1120 -  327C      55688     215C  215C    09   09   OK
 1020  02 26   11    327D -  7289   30080000 c   548C  400C    FB   FB   OK
 1040  03 31   0C    728A -  762E   24000000      3A4   3A4    31   31   OK
 1060  04 1C   01    762F -  C647          0 c   6688  5018    BB   BB   OK
 1080  05 2C   01    C648 -  CA44      15D38 c    4CC   3FC    9A   9A   OK
 10A0  06 FB   03    CA45 -  F4BD      402E0 c   35D0  2A78    77   77   OK
 10C0  07 22   03    F4BE -  F706   60319A00 c    3F0   248    48   48   OK
 10E0  08 02   01    F707 - 22567   3842E800 c  19234 12E60    23   23   OK
 1100  09 83   01   22568 - 4C428   38000230 c  3D92C 29EC0    BF   BF   OK
81000  01 AE   04   81120 - 8327C      55688     215C  215C    01   01   OK
81020  02 26   11   8327D - 87289   30080000 c   548C  400C    FB   FB   OK
81040  03 31   0C   8728A - 8762E   24000000      3A4   3A4    31   31   OK
81060  04 1C   01   8762F - 8C647          0 c   6688  5018    BE   BE   OK
81080  05 2C   01   8C648 - 8CA44      15D38 c    4CC   3FC    89   89   OK
810A0  06 FB   03   8CA45 - 8F4BD      402E0 c   35D0  2A78    A5   A5   OK
810C0  07 1A   03   8F4BE - 8F702   60319A00 c    3F0   244    87   87   OK
810E0  08 7E   01   8F703 - A253B   3842E800 c  19204 12E38    C8   C8   OK
81100  09 72   01   A253C - CC3C0   38000230 c  3D8C0 29E84    7E   7E   OK

LDSC   = PM Loader Config String (32 bytes)
ID     = ID byte of LDSC (byte #0)
CS     = Checksum byte or word
Att    = Attributes
PCMBlk = Program Code Memory Block
Exp    = Expected checksum for PCMBLock
Act    = Actual checksum for PCMBLock
c      = compressed PCMBlock
size   = size of decompressed (in RAM) and compressed (in ROM) PCMBlock in bytes


ROYL directory module 0x000B found at 0x7F5DE

Active directory flag = 0x16

Identifying SA regions ...

Reg#    Reg size     Reg loc
----  ----------  ----------
0x00  0x000C8FA0  0x00000000
0x01  0x000C8FA0  0x000EC860

Verifying ROYL modules ...

 ID          Size (bytes)         Address    Checksum
 dir   hdr        dir       hdr
----  ----   --------  --------   --------   --------
0001  N/A    00004000  N/A        00085DD2             N/A
000A  OK     0000004E  00000200   0007E000   00000000  OK
000B  OK     00000129  00000200   0007F5DE   00000000  OK
020B  OK     00000129  00000200   0007D5DE   00000000  OK
0181  OK     00000BA0  00000C00   000FF400   00000000  OK
0030  OK     00000400  OK         000FF000   00000000  OK
0047  OK     00000B28  00000C00   0007EAB6   00000000  OK
000D  OK     00000108  00000200   0007E04E   00000000  OK
0303  OK     00000060  00000200   0007E156   00000000  OK
004F  OK     00000900  00000A00   0007E1B6   00000000  OK

ROYL directory module 0x020B found at 0x7D5DE

Active directory flag = 0x15

Identifying SA regions ...

Reg#    Reg size     Reg loc
----  ----------  ----------
0x00  0x000C8FA0  0x00000000
0x01  0x000C8FA0  0x000EC860

Verifying ROYL modules ...

 ID          Size (bytes)         Address    Checksum
 dir   hdr        dir       hdr
----  ----   --------  --------   --------   --------
0001  N/A    00004000  N/A        00085DD2             N/A
000A  OK     0000004E  00000200   0007C000   00000000  OK
000B  OK     00000129  00000200   0007F5DE   00000000  OK
020B  OK     00000129  00000200   0007D5DE   00000000  OK
0181  OK     00000BA0  00000C00   000FF400   00000000  OK
0030  OK     00000400  OK         000FF000   00000000  OK
0047  OK     00000B28  00000C00   0007CAB6   00000000  OK
000D  OK     00000108  00000200   0007C04E   00000000  OK
0303  OK     00000060  00000200   0007C156   00000000  OK
004F  OK     00000900  00000A00   0007C1B6   00000000  OK

dir  -  Module ID/Size as reported in directory module (0x20B or 0x0B)
hdr  -  Module ID/Size as reported in module's header
N/A  -  Not Applicable
BAD  -  Module has invalid checksum. This may be due to non-existent module.

ROM modules saved to Flash_00\000Bmods and Flash_00\020Bmods

Active directory is 0x0B

Analysing active 0x0A module ...

Head map checksum (Expected / Actual) = 0x0000 / 0x0000 - OK
Number of heads (physical / in use) = 10/10
Head map #1 = 0x03FF / 0b0000001111111111
Head map #2 = 0x03FF / 0b0000001111111111

DCM = | W | | W S 4 | | 1
      : : : : : : : : : :
      : : : : : : : : : unknown
      : : : : : : : : top VCM
      : : : : : : : ACA
      : : : : : : bottom VCM
      : : : : : HSA
      : : : : media
      : : : preamp
      : : latch
      : base
      spindle motor

Analysing active 0x0D module ...

Firmware Version = 81.00A81
World Wide Name = 50014EE2C074547C
Model Number = WDC WD80EMZZ-11B4FB0                    
Serial Number =                    

PUIS flag byte is 0x02
PUIS Disabled

Analysing active 0x4F module ...

ROM version = 00810008

Analysing active 0x47 module ...

Preamp values
-----------
0  0535A592
1  0B33A492
2  0439A598
3  0435A598
4  0439A46C
5  0433A698
6  052DA598
7  0533A48D
8  0533A598
9  062DA492

Microjogs
-------
0  0000
1  0000
2  0000
3  0000
4  0000
5  0000
6  0000
7  0000
8  0000
9  0000

Head/Media DCM = SW

[allen labarge]

Thanks for everyone's assistance.

As a sanity check, I verified the resistance on the motor as well
against a similar drive before putting the donor board, with the
patient Firmware, on the drive, Looks like it is a full recovery from
the drive.

> --
> Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
> ---
> You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/datarecoverycertification/b916b1f2-089c-49f8-9ebc-fc8c2cf1c357n%40googlegroups.com.