Hi Guys,
Thanks for your responses. I've got some more opinions to share. I visited the local TV Repair man and he couldn't remove the chip, said he didnt have the correct tools. As I was walking out, he said 'But I do know someone who can repair your hard drive for you, would you like to speak to him?'. YES PLEASE I SAID
So he called him and put me on the phone with him, here's how the limited conversation went:
Me) Hard drive isn't detected by windows/device manager, just spins quietly. Have tried putting a new PCB into it with the same firmware but still didn't work. Considering swapping the firmware chip to another donor, what do you think?
Him) Firmware corruption is probably the cause. It's on the chip you're considering transferring. You'll be transferring the only thing wrong with your PCB onto a brand new PCB.
Me) Oh.
Him) Firmware repair cannot be done at home unless...
Me) Unless what? I'll try anything at this point.
Him) Firmware corruption can be fixed in some cases by using a special cable and some special commands through Hyper terminal.
Me) So I connect the cable, talk to the firmware and reset it? Where can I find out more?
Him) Search for the BSY firmware repair guide, but the results are not guaranteed.
So as soon as I got home, I looked it up and sure enough, a whole forum of people fixing firmware errors on their seagate drive.
https://www.overclock.net/t/457286/seagate-bricked-firmware-drive-fix-with-pics
Equipment: **broken link removed**
Apparently BSY means the drive has somehow got it self stuck in the BUSY mode, so nothing can access it. Seeing as the firmware is split between the firmware chip and a service area on the platter, it could be 50/50 as to which one is corrupted to cause this.
It seems like officially Seagate have not said much about this, but the problem seems to be identified and surrounding barracuda 7200.11 drives. Mine is not one of them, so I'm not sure if messing with something in this way will cause more damage.
Oblivion, you mentioned you had experience with firmware? Does any of this sound reasonable/plausible?
Any Ideas?
One thing I'm more confused about now is the idea of swapping EEPROM chips. I figured if I swapped this chip from one board with firmware (DE05) and put it into another board with (DE05), then all I'm really doing is making sure the new PCB board has what it needs to read the data off the platter correctly. But what if the chip contains both the DE05 firmware + the unique data the hard drive will need to read the data off the platter, all in one chip. I have always thought the firmware and this data were seperate and so by swapping the ROM chip into an identical PCB of the same firmware, I could bypass any firmware issues. But if they're both on the same chip, and that chip has issues, then moving that chip around is just moving those issues around?
Does swapping an EEPROM chip transfer a corrupt firmware to a new PCB? If this is the case then it sounds like I've only got two hopes, try and repair the firmware or somehow reset it (The other working board has the same firmware DE05, maybe I can transfer it somehow). If this miraculously works and the rest of the PCB is okay, then it might work. If the rest of the PCB is not okay, chips blown as previously suggested, then I'll have to transfer the ROM chip over to the new board, then fix the firmware. Arghh!
Finally, there seems to be a seagate firmware demo tool available here (**broken link removed**), it seems to be able to read/write firmware and repair the actual issue mentioned in the above thread. Maybe this, with the ebay cable might do something? But right now it's just a complete guess and compared to swapping out dead hard drive heads, this seems a nightmare
Time to give up? Try the ROM swap anyway? Try the Firmware fix?
Any opinions or ideas or suggestions welcome
Regards,
Megamox