Samsung HM320HJ BSY, no spin

[Nick_CT]

I feel a bit rusty on these...

HM320HJ - MP4 family. BSY but won't spin. Heads are good. Patient ROM on good donor PCB has the same symptoms.

Terminal output is:

ActiveFW : 00
FWVer : 0001
DDR size detected =
SATA PLL cal done
*PA VID=0007 PN=0000 Rev=0004
*PA VID=0007 PN=0000 Rev=0004
U
S_0
[DEBUG HALT @):10006FCB L0 1000BF35]
SSC EN

Can someone prod me in the right direction please?

[unknown]

Donor ROM on patient PCB?

[BGman]

Maybe FIPS problem.

[fzabkar]

If you can dump the ROM, I can check it for you.

[Nick_CT]

Donor ROM on patient PCB?

The drive does spin with the above so the issue seems related to patient ROM. I hardly get any of these drives in for recovery where I am so I'm not very experienced with this issue on them.

[Nick_CT]

If you can dump the ROM, I can check it for you.

I have attached ROM. Well I tried to but it won't allow .bin - have attached it as compressed.

Attachments

ZAJR0021 ROM.rar

(162.51 KiB) Downloaded 654 times

[fzabkar]

The FIPS section at 0x3000 - 0x3FFF is empty. I suspect that your tool (PC3K?) should be able to fix this.

Code:

Verifying Samsung SpinPoint ROM:  C:\Samsung\Firmware\HM320HJ\ZAJR0021 ROM.bin

Checksum of Boot Block header = 0xF9  - OK
Checksum of Boot Block (Actual/Expected) = 0x0742 / 0x0742  - OK

Searching for FIPS block (expected checksum = 0x0000) ...

Found FIPS text string at 0x014362
Checksum for 0x0400 byte FIPS block = 0xCE80  - BAD
Checksum for 0x0800 byte FIPS block = 0x8337  - BAD
Checksum for 0x0C00 byte FIPS block = 0x4A34  - BAD
Checksum for 0x1000 byte FIPS block = 0x66E0  - BAD

Found FIPS text string at 0x0194BC
Checksum for 0x0400 byte FIPS block = 0xD568  - BAD
Checksum for 0x0800 byte FIPS block = 0x535F  - BAD
Checksum for 0x0C00 byte FIPS block = 0x9CE2  - BAD
Checksum for 0x1000 byte FIPS block = 0x26E4  - BAD

Found FIPS text string at 0x019CB8
Checksum for 0x0400 byte FIPS block = 0x8279  - BAD
Checksum for 0x0800 byte FIPS block = 0xC52D  - BAD
Checksum for 0x0C00 byte FIPS block = 0x5B54  - BAD
Checksum for 0x1000 byte FIPS block = 0x98EC  - BAD

Could not find a FIPS block with valid checksum

Searching for FLASHTBL ...

Found FLASHTBL text string at 0x004024
Parsing FLASHTBL at 0x004000 ...

ID Byt1 Byt3    Size   ROM address range   RAMaddrs  Cksm (Exp/Act)
-----------------------------------------------------------------
00  00   FF         0                             0            N/A
01  02   FF       320     4000 - 431F      FFF04000  F8 80   - BAD (Note 2)
02  08   FF       614     4320 - 4933      FFF04320  99 99   - OK
03  00   FF     1480C     4938 - 19143            0  6D 6D   - OK
04  01   FF      2CBC    19148 - 1BE03        14D00  00 0C   - BAD (Note 1)
05  00   FF       B68    1914C - 19CB3      4000000  67 67   - OK
06  00   FF       228    19CB8 - 19EDF      4005C00  EC EC   - OK
07  00   FF     18E30    19EE4 - 32D13     10000300  7B 7B   - OK
08  01   FF     182A4    32D18 - 4AFBB     1002E300  00 A8   - BAD (Note 1)
09  00   FF      2978    32D1C - 35693     18052300  E8 E8   - OK
0A  00   FF      1794    35698 - 36E2B     20015FF0  FA FA   - OK
0B  00   FF       180    36E30 - 36FAF     FFFE1000  EB EB   - OK
0C  00   FF       C90     1800 - 248F      FFF01800  49 49   - OK
0D  02   FF         0                      FFF04000            N/A
0E  08   FF         0                      FFF04320            N/A
0F  20   FF         0                      FFF01800            N/A
10  00   FF         0                      FFFC0000            N/A
11  00   FF         0                      20015FF0            N/A

Found FLASHTBL text string at 0x02AF53
Inconsistent ID


Searching for SERVOTBL ...

Found SERVOTBL text string at 0x037024
Parsing SERVOTBL at 0x037000 ...

ID Byt1 Byt3    Size   ROM address range   RAMaddrs  Cksm (Exp/Act)
-----------------------------------------------------------------
00  02   FF       100    37000 - 370FF     FFF37000  61 DB   - BAD (Note 2)
01  00   FF      94C0    37104 - 405C3            0  97 97   - OK
02  00   FF       7F4    405C8 - 40DBB      4000100  0D 0D   - OK
03  00   FF       240    40DC0 - 40FFF     FFFE1000  0F 0F   - OK
04  02   FF         0                      FFF37000            N/A


Size            - size of module in ROM expressed in bytes
ROM address     - absolute address range of module in ROM
RAMaddrs        - load point of module in RAM
Cksm (Exp/Act)  - Expected Checksum / Actual Checksum


Note 1:  The address range of affected module may conflict with another module,
          in which case this is probably a false negative.

Note 2:  If this module is the FLASHTBL or SERVOTBL, then this is most likely
          a false negative.

Note 3:  This may or may not be a genuinely BAD module. Examine the checksum
          of the first half of the ROM. If 0x0000, then module is probably OK,
          otherwise it may or may not be bad. Also examine the "adjusted"
          checksum, if applicable.

Note 4:  The address range of the module is outside the limits of the ROM.

[Nick_CT]

Thanks guys, FIPS issue indeed. Seems PC3K can resolve the issue and then saves a *fixed* version of the ROM. I wrote that back to the PCB and it's sorted. First time for everything. Gracias.

[unknown]

Good job
Glad it worked out for you Nick