WD10TMVV 11A27S2 USB drive ROM

[ddrecovery]

This drive has head failure, hopefully not an issue as we have a donor. However the USB board has an integral ROM. Originally, I did manage to get the drive live on one head to extract the ROM and ROM modules. I have a matching SATA board with external ROM, but trying to write the ROM to the SATA board gives me an invalid data size error. Donor Drives have boards from this model of drive, some have external ROM's some internal ROM's. So... The SATA board I have is from a Shasta 3 drive, while the USB is Shasta. Is there generally a difference in size between internal and external ROM's? I have tried a few ROM's from different matching drives and some are the correct size which is interesting.

Invalid Data Size (197120). Expected (262144)

[drHDD]

pcb numbers?
Keep trying check board to find with same rom size or use programmator/flasher.

[ddrecovery]

USB 701675-001
SATA 701672-001

[digisupport]

Maybe you need a SATA 701609-004

[MindMergepk]

This drive has head failure, hopefully not an issue as we have a donor. However the USB board has an integral ROM. Originally, I did manage to get the drive live on one head to extract the ROM and ROM modules. I have a matching SATA board with external ROM, but trying to write the ROM to the SATA board gives me an invalid data size error. Donor Drives have boards from this model of drive, some have external ROM's some internal ROM's. So... The SATA board I have is from a Shasta 3 drive, while the USB is Shasta. Is there generally a difference in size between internal and external ROM's? I have tried a few ROM's from different matching drives and some are the correct size which is interesting.

Invalid Data Size (197120). Expected (262144)

you can also add 0s at the end of the original ROM File make the size 262144 bytes and try writing it. This idea was basically from "fzabkar" it is tested and worked don't remember the pcb number, hope it will help.

[drHDD]

Yes, it will work too.

[ddrecovery]

Maybe you need a SATA 701609-004

I have a 701609-001 and the controller and motor chips are both different.

you can also add 0s at the end of the original ROM File make the size 262144 bytes and try writing it. This idea was basically from "fzabkar" it is tested and worked don't remember the pcb number, hope it will help.

I increased the size of the ROM file to 626144 with 0's (attached), but the board will not come live. I tried this with 2 ROM's with the same result. Probably need to solder a SATA connector to the USB board. Not ideal but probably the only option.

Attachments

ROM_new-size.zip

(179.34 KiB) Downloaded 501 times

[fzabkar]

You have uploaded SA module 0x109. Have you been trying to write this image to your PCB as a ROM image?

[pcimage]

You have uploaded SA module 0x109. Have you been trying to write this image to your PCB as a ROM image?

If that's the case it won't work, mod 109 is missing salient information to make a complete ROM image, as fzabkar is implying.

[fzabkar]

You have uploaded SA module 0x109. Have you been trying to write this image to your PCB as a ROM image? :shock:

If that's the case it won't work, mod 109 is missing salient information to make a complete ROM image, as fzabkar is implying.

Have a look at it yourself. The OP is writing 0x109 as is, without stripping the header or adjusting the adaptives.

[ddrecovery]

Yes you are correct. My bad. I am a chump. Its been a busy day but that's not a good excuse... Here are the correct before and after (I hope).

Attachments

ROM_new-size.zip

(359.82 KiB) Downloaded 585 times

[Amarbir[CDR-Labs]]

Yes you are correct. My bad. I am a chump. Its been a busy day but that's not a good excuse... Here are the correct before and after (I hope).

Hi,
Do you folks find it hard to desolder the mcu and solder it on donor boards .I find it not a hard task if you have a good tool at hand .Before i had all the toys to play around dfl,mrt and pc3k this is what i could do .BTW i am surprised .You could connect the board to the pc usb port with HSA assembly .Then wait for 15 minutes and use com port of that usb board to extract rom + rom modules [ its a piece of cake man ] .

[ddrecovery]

@fzabkar. Could you take a look at the uploaded ROM and let me know if I did this correctly? Your help is much appreciated.

[fzabkar]

AFAICT the code sections of the ROM match module 0109, and the adaptive templates have been filled out, so all seems OK to me.

[ddrecovery]

AFAICT the code sections of the ROM match module 0109, and the adaptive templates have been filled out, so all seems OK to me.

Many thanks. This ROM also causes the drive not to come RDY (no status register lights at all), so looks like adding zero's for this drive family doesn't work. Worth a try though.

Hi,
Do you folks find it hard to desolder the mcu and solder it on donor boards .I find it not a hard task if you have a good tool at hand .Before i had all the toys to play around dfl,mrt and pc3k this is what i could do .BTW i am surprised .You could connect the board to the pc usb port with HSA assembly .Then wait for 15 minutes and use com port of that usb board to extract rom + rom modules [ its a piece of cake man ] .

Can you swap the mcu over from one board to another? I would have thought that with the USB board having an internal ROM, the programming/circuitry would not match with a SATA board with external ROM? But then again I have already proved in this topic that I don't know what I'm talking about

[fzabkar]

Does the drive still spin up with the original PCB?

Can you upload photos of your PCBs? There is a resistor (R74) which determines whether the MCU looks for an internal or external ROM. There is also an additional resistor which appears to be present in some implementations, but I don't understand its function.

[ddrecovery]

Does the drive still spin up with the original PCB?

Can you upload photos of your PCBs? There is a resistor (R74) which determines whether the MCU looks for an internal or external ROM. There is also an additional resistor which appears to be present in some implementations, but I don't understand its function.

Sorry for the later response. Here are the two boards.

Attachments

[fzabkar]

The SATA PCB has an 88i9045-TFJ2 MCU whereas the USB PCB has an 88i8946-TFJ2. ISTM this may be your problem. ICBW, but I would think that the ROM code would test the processor's ID and abort if the correct processor is not present. It appears that the motor controllers are both SH6601AD, so that part is OK.

ISTM that there are two resistors that differ in the external/internal ROM configurations. According to the 2060-701640 PCB, these resistors are designated as R74 and R40. Both are present when the ROM is external, otherwise they are absent for an internal ROM. ISTM that R74 is the important one. I don't understand what R40 does.

Attachments

[Mikippp]

Hi,
PCB 2060-701609-000 should be compatible with this ROM
I advise you to try...

Mikippp

[ddrecovery]

@ Fzabkar: Many thanks for the expert analysis as usual.

The Ace Labs USB/SATA PCB matching list is not totally correct. While the SATA board does match the USB for boards with an external ROM, they do not match for this unusual internal ROM version. The advice given above to try 701609 is correct, but needs additional info. I didn't have a 2060-701609-004 (and cannot find that board on Donor Drives), so I looked at a 2060-701609-001 which I had in stock, but the controller didn't match which threw me off the trail a little. However after doing more research and Mikipp's advice, I have found the correct board (see below).

PCB Sticker: 2061-701609-800 03P
PCB Revision: 2060-701609-000 REV P1
Controller Chip: 88I8946-TFJ2

So for anyone that reads this, if you are matching the USB PCB 2060-701675-001, if its an internal ROM check the controller as you may need the above board instead.