ST9160821AS - F/W Repair

[DioNuM]

I have a ST9160821AS Seagate HDD that I wanted to reset the SMART values for some errors. Through experimentations, I accidentally managed to erase part of its F/W from the HDD. Now, when I'm using a terminal with my RS232-TTL adapter, I'm getting the following.

Code:

Reset4096k x 16 DRAM
VENUS - 1_Disk    M-37   12-01-06_14:56
HM SFI
!
ERR Read App Code
(
F>

I know that I've reached F level and in order to repair this I need to upload APP/CERT/TBL/VEND information back in its memory. However, I didn't take a backup and I can't find a set in the upload section. So, I was wondering if anyone has a donor backup which I can use.

Thanks in advance.

[DioNuM]

Sending you the tracks for your drive wouldn't solve anything as you would need tools (not free) to send the tracks back to the drive by sdld.

I understand that if you have a PC3K device for fixing it, will be a piece of cake as it is an automated process. However, I'm just trying to do this myself for educational reasons and cheaper solution. I'm using ST_MEM_SDLD for uploading the codes to the HDD but I just don't have a backup of the files that are needed.

[DioNuM]

I'm also reading that an application known as WDR can ease the process only if the modules for the specific HDD exist.
The module format can be the same as PC3K, so if anyone has a backup please post.
The HDD is a Seagate with:

Model No - ST91160821AS
S/N - 5MA59HC2
F/W ver: 3.ALC

[DioNuM]

Spildit
Thanks for your interest. I do apologize for the delay on my replies but it seems that every single post needs to be accepted by the admins before it gets posted.

Anyway, I've already seen these files and most are in the file section of this site. You are right with the last one that it is closer to my HDD's F/W, however I'm getting incompatible APP Code at the end.

Here is the output that I'm getting from ST_MEM_SDLD

Code:

Reset
4096k x 16 DRAM
VENUS - 1_Disk    M-37   12-01-06_14:56

Buzz HM SFI
!
ERR Read App Code
(
F>
скорость порта установленна в:19200

пауза 4000 м.сек.

посылаем D:\st_mem_SDLD\app.trc 08E блоков по 2048 байт
посылаем блоки :
001
002
.
. (all the way)
.
08D
000
послали файл D:\st_mem_SDLD\app.trc блоками по 2048 байт
F>R
Buzz HM SFI
!
    Code - FF  Track 0EF01.0.01E  Sns 01E
F>


Sorry for the Russian, blame the developer.

Also, in addition with the incompatible ROM Rev. the date and time are different as well. The APP module from the archived file says 12-12-06_13:26 while mine is 12-01-06_14:56.

Still, if someone has a copy of my HDD's modules, his contribution would be greatly appreciated.

[DioNuM]

int0x13
I can't send any PMs yet. So, send me in private your MSN account and I will add you.

[DioNuM]

Do you have an external soic 8 programmer, spi flash ?

Nope, for the time being my only tool is a RS232/TTL adapter, which I can upload code to the HDD using SDLD through the Tx and Rx pins located next to the SATA connector.

Also, I read a post that says:

There are two places where the firmware is stored. The bulk of it is written to a firmware zone in the hidden System Area on the platters, while a small portion of the boot firmware resides in an 8-pin serial flash memory IC on the PCB. This flash memory also stores unique, drive specific "adaptive" information. Therefore a firmware transfer from flash memory to flash memory would be pointless. In fact it would only compound the problem due to wrong adaptives being transferred.

[DioNuM]

Spildit
I might be able to get hold of a programmer so maybe then go down the lane of re-flashing the ROM. Although, from the looks of the PCB it could be a tough procedure as it is minute.
Though, I'm not sure which one is the ROM, I can see a single 8-pin IC but I'm not sure if the ROM in this PCB is integrated in a larger chip. I'm including some photos of the PCB so you can have a look.




Now, which file do I use to flash the ROM, is it the rom.bin from the archives that you've included in previous posts?

Thanks

[DioNuM]

What are the numbers on the chip ?

No numbers, just a few characters. Here is a rough drawing of it.


But the chip is so small that I'm not willing to taking it off the PCB, in case I damage it.

I've noticed that the file ST9120822AS-3.ALC-M-37_12-01-06.S-0C.13Q.027.rar has the same ROM version and date & time stamps. However, the archive includes a LDR file (SgLDR.ldr).

Which applications work with these extensions?

[mr_spokk]

Spildit
I might be able to get hold of a programmer so maybe then go down the lane of re-flashing the ROM. Although, from the looks of the PCB it could be a tough procedure as it is minute.
Though, I'm not sure which one is the ROM, I can see a single 8-pin IC but I'm not sure if the ROM in this PCB is integrated in a larger chip. I'm including some photos of the PCB so you can have a look.




Now, which file do I use to flash the ROM, is it the rom.bin from the archives that you've included in previous posts?

Thanks

Thats not ROM, if there had been any it had been on the opposite side...where it's empty...so in this case your ROM is embedded in the MCU

[fzabkar]

The mystery component appears to be a FETKY (MOSFET + Schottky diode). The clue to its function is that it connects to a nearby 2R2 coil. This suggests that it is part of a switchmode regulator. In fact it looks like the regulator is either the Vio or Vcore supply for the LSI MCU.

The other regulator appears to be located near the SATA power connector. It has a discrete Schottky diode plus either a MOSFET or a PWM controller with an integrated MOSFET.

The clue that the vacant 8-pin location may be reserved for an EEPROM is that several of the IC's pins connect to the MCU. The FETKY would be controlled by the motor controller IC.

NTTD4401FR2G, ON Semiconductor, marking BG, FETKY, 20V 3.3A P-ch MOSFET, 1A diode:
http://pdf.datasheet.su/on%20semiconduc ... 401fr2.pdf
http://www.onsemi.com/pub/Collateral/NTTD4401F-D.PDF

Just FYI, I find that you get a better quality image if you use a scanner rather than a camera.

See http://malthus.zapto.org/viewforum.php? ... 406b5414ab

[visz]

it isnt easy as it seems..perhaps,you can find the exact firmware or get another equal drive as advised which I will do the same

[DioNuM]

Just FYI, I find that you get a better quality image if you use a scanner rather than a camera.

I didn't know that, thanks for the tip. If I get time I will re-take them and provide links for anyone that is interested.
Now, if I remember right. I think there are posts that show points where you can short circuit the PCB in order to flash the ROM which apparently is integrated.

At any rate i think that your best shot is to try and get another equal drive or someone with a drive with the same firmware that you need ...

I totally agree with trying to get another copy of the modules from an identical HDD. Meanwhile, I'm playing around with SDLD and AT interface commands.