Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
April 23rd, 2018, 6:52
Hi, I have this seagate/samsung drive which doesn't power up, I tried a rom swap with different 100767980 pcbs but the drive doesn't spin. I tried to fix the usb board but no luck with that.
I was thinking it was a preamp issue but the the rom doesn't spin at all even when I put it on another drive.
The terminal gives me "&&&&" with patient rom and donor pcb
I am thinking the problem is the rom itself or wrong pcb compatibility.
I attach the ROM here please let me know if you have had same issue with this drive.
Thank you
- Attachments
-
- ROM.zip
- (343.61 KiB) Downloaded 417 times
April 23rd, 2018, 7:28
here is the Patient pcb
- Attachments
-
April 23rd, 2018, 7:29
front side
- Attachments
-
April 23rd, 2018, 11:39
here is the Rom, sorry but I attached the wrong size above
- Attachments
-
- ROM.zip
- (348.62 KiB) Downloaded 422 times
April 23rd, 2018, 11:52
How did you try to fix the original board ?
Can you post pictures of the new donor board you are using ?
Also, in the original board, you can try to clean the oxidation in the hda contacts. Maybe it changes nothing, but just in case.
April 23rd, 2018, 12:25
hi rogfanther,
thanks for asking, I didn't do much to the original pcb just tried to reflow the connectors close to the usb and give it a clean up.
Here is one of the donors I used
- Attachments
-
-
April 23rd, 2018, 12:59
Maybe I´m wrong, but it seems from the pictures that you transferred the flash rom chip that contains the usb bridge firmware, not the the main controller one.
In the picture you called Patient pcb, it would be the chip near the second screw hole in the top side.
April 23rd, 2018, 13:49
I didn't have many of those drive but I thought the one that contains the bridge fw was on the outer part of the pcb, here is the rom that I swaped, please tell me is the rom otherwise would be really embarassing form me
- Attachments
-
April 23rd, 2018, 13:58
mrDRECula wrote:here is the Rom, sorry but I attached the wrong size above
I was banging my head to figure out, how did you ended up with a ROM half of the size its supposed to be
April 23rd, 2018, 14:13
mrDRECula wrote:I didn't have many of those drive but I thought the one that contains the bridge fw was on the outer part of the pcb, here is the rom that I swaped, please tell me is the rom otherwise would be really embarassing form me
Yes, that is the right chip. From your picture, it looked like you had soldered the bridge firmware chip, that´s why I commented on it.
Hopefully someone will correct me if I´m wrong, but if you isolate the hds contacts ( piece of paper ) does the disk spin ?
April 23rd, 2018, 14:18
@jermy I used MRT to read the rom the size is chosen manually
@rogfanther
I am not in the labnow, I will try tomorrow, but I already did the test with another donor pcb and it didn't spin, will update you tomorrow, thank meantime
April 23rd, 2018, 14:47
mrDRECula wrote:@jermy I used MRT to read the rom the size is chosen manually
you've used MRT to read/flash the chip ?
or moved it physically ?
April 23rd, 2018, 16:06
I did both, rom swap to the patient pcb and as it didn't work I removed it and used the MRT rom programmer to read the chip hoping anyone could help out here.
If you have used the new MRT you should know the flash reader/programmer reads directily from the rom
I attach a pic of the reader for you in case you haven't seen it yet.
As I am a bit new to MRT I thought the programmer would pick the size automatically but you actually need to chose it manually that's why I posted the 512k file in first place.
thanks
- Attachments
-
April 23rd, 2018, 16:17
I have parsed the OP's ROM and it checks out OK. My tool might not be completely trustworthy, though.
- Code:
Checksum of Boot Block header = 0x63 - OK
Checksum of Boot Block (Actual/Expected) = 0x7173 / 0x7173 - OK
Searching for FIPS block (expected checksum = 0x0000) ...
Found FIPS text string at 0x001000
Checksum for 0x1000 byte FIPS block = 0x0000 - OK
Searching for FLASHTBL ...
Found FLASHTBL text string at 0x002024
Parsing FLASHTBL at 0x002000 ...
ID Byt1 Byt3 Size ROM address RAMaddrs Cksm (Exp/Act)
-----------------------------------------------------------------
00 00 FF 00000000 FFFFFFFF 00000000 N/A
01 40 FF 00000000 FFFFFFFF 00014D00 N/A
02 02 FF 00000300 00002000-000022FF FFF02000 00 9A - BAD (Note 2)
03 08 FF 00001EF4 00002300-000041F3 FFF02300 F2 F2 - OK
04 00 FF 00014CF0 000041FC-00018EEB 00000000 7B 7B - OK
05 40 FF 00002FB0 00018EF4-0001BEA3 00014D00 DE DE - OK
06 00 FF 00000B60 0001BEAC-0001CA0B 00080000 3A 3A - OK
07 00 FF 00000384 0001CA14-0001CD97 00085C00 D7 D7 - OK
08 00 FF 00000234 0001CDA0-0001CFD3 00088000 F9 F9 - OK
09 80 FF 0004C790 0001CFDC-0006976B 10018000 39 39 - OK
0A 81 FF 00005548 00069774-0006ECBB 10064790 00 FB - BAD (Note 1)
0B 00 FF 00006810 0006977C-0006FF8B 900003C0 FF FF - OK
Searching for SERVOTBL ...
Found SERVOTBL text string at 0x071024
Parsing SERVOTBL at 0x071000 ...
ID Byt1 Byt3 Size ROM address RAMaddrs Cksm (Exp/Act)
-----------------------------------------------------------------
00 02 FF 000000C0 00071000-000710BF FFF71000 00 3A - BAD (Note 2)
01 00 FF 0000CED0 000710C4-0007DF93 00000000 6A 6A - OK
02 00 FF 00000F68 0007DF9C-0007EF03 00080000 80 80 - OK
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.
April 23rd, 2018, 16:28
If the OP's serial TTL adapter is a 3.3V type, then it may have difficulty communicating with a 1.8V "PCBA I/O Voltage". I would also be concerned about the possibility of powering a 1.8V preamp from a 2.5V supply, if indeed that is what the following ROM excerpt is implying.
- Code:
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
0000D570 50 43 PC
0000D580 42 41 20 49 2F 4F 20 56 6F 6C 74 61 67 65 20 3A BA I/O Voltage :
0000D590 20 32 2E 35 56 0A 00 00 25 6E 50 52 45 41 4D 50 2.5V...%nPREAMP
0000D5A0 20 3A 20 32 2E 35 56 0A 00 00 00 00 25 6E 50 43 : 2.5V.....%nPC
0000D5B0 42 41 20 49 2F 4F 20 56 6F 6C 74 61 67 65 20 3A BA I/O Voltage :
0000D5C0 20 31 2E 38 56 0A 00 00 25 6E 50 52 45 41 4D 50 1.8V...%nPREAMP
0000D5D0 20 3A 20 31 2E 38 56 0A 00 00 00 00 25 6E 46 4C : 1.8V.....%nFL
0000D5E0 41 53 48 20 3A 20 38 4D 62 69 74 ASH : 8Mbit
April 23rd, 2018, 16:43
what about a donor ROM ?
have you tried it ?
does it spin up with a donor ROM (same F/W ver.)?
April 23rd, 2018, 16:54
Many Thanks fzabkar
As I said above I used the programmer to read the rom, I need to check tomorrow but am pretty sure it uses 3.3V type to read.
If the rom is ok this should move the problem on the pcb(probably incompatible) or the preamp
As for the preamp I did test it putting a paper between the pcb and the heads but the drive didn't spin
I believe I am using an incompatible pcb as the patient HDA with donor pcb and donor rom doesn't spin also I tried the patient rom and donor pcb combo on different donor HDAs and it didn't spin on any of them.
That's why I thought the rom was corrupted and I was hoping you could confirm it but now I don't have any clues...
April 23rd, 2018, 16:57
@jermy
sorry I was writing the answer for fzabkar, as I was saying to fzabkar I tried and didn't work, to be honest I didn't check if they had the same fw, tomorrow I will check,
thanks jermy
April 23rd, 2018, 17:02
@mrDRECula, what are the voltages at the serial TTL Tx/Rx pads? Are they 1.8V or 2.5V?
BTW, if you isolate the HDA, then the PCB fimware has no way to identify the preamp, in which case it will not command the drive to spin up.
April 23rd, 2018, 17:36
if the donor and patient have different preamp the drive will not spin
Powered by phpBB © phpBB Group.