HDD GURU FORUMS

loader wanted for
ST3500418AS
Firmware : CC38

Here you go:

thanks in advance data-medics. i appreciate your help

Update:
terminal out put
LED:000000CC FAddr:0028931D
LED:000000CC FAddr:0028931D

when update microcode to SA or ram . i got error :
Test : Update microcode
Loading LOD from folder................. : F:\SgF3LDR\SgF3LDR.lod
Mode.................................... : 7
Device error detected (ABR)
ErrCode = 05269921
Result.................................. : Error
===============================================
any advice here?

05269921 "Download overlay incompatible"
Version of the overlay in the loader(18.09.14-25 18/09/2009) don't match with version of your rom.

ErrCode = 05269921 - "Download overlay incompatible"
The loader contain overlay only and their version(18.09.14-25 18/09/2009) don't match with version of your rom.

dodoz wrote:ErrCode = 05269921 - "Download overlay incompatible"
The loader contain overlay only and their version(18.09.14-25 18/09/2009) don't match with version of your rom.

ok what should i do ?

Upload your ROM and hope that someone can match a loader to it?

Thanks fzabkar
here is the Rom

Would it make sense to use Data-Medics' ROM and patch your own adaptives into it? Then you could use Data-Medics' loader.

I have patched a Pharaoh CC49 ROM with your adaptives and compiled a CC49 loader to suit. You may need to confirm the ROM checksum(s). Hopefully this will enable you to reach the SA and retrieve the drive's native resources.

Thank you very much for your Efforts .I'll try and let you know

Update :
* First of all thanks Mr. Frank again for your time and efforts .

* Second : I write the modified rom (CC49)with terminal but pcb is power Off. so i will Re write original Rom with programmer and strat again . any new clues over here ?

Try this ; it's compatible overlay's loader for your original rom.

Maybe I was unlucky and picked a CC49 ROM where Power Up In Standby (PUIS) was enabled. If so, then the drive would have identified itself to BIOS and all that would have been required would have been to disable the PUIS using a tool such as HDAT2.

I used this CC49 firmware update ...

Barracuda 7200.12 Firmware Update (Pharaoh CC49):
http://knowledge.seagate.com/articles/e ... Q/213891en
http://www.seagate.com/staticfiles/supp ... L-CC49.iso

... and this CC49 resource dump:

http://files.hddguru.com/index.php?acti ... eagate/F3&

I patched the CC49 ROM by copying the CC38 ROM's CAP/RAP/SAP modules. The code sections of the CC49 ROM matched the corresponding code sections in the CC49 firmware update.

This is the CC38 ROM header:

Code:

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

00000000  F6 1D 00 00 40 00 00 00 40 00 00 00 49 C3 04 00
00000010  02 38 00 00 04 38 16 06 06 48 18 06 03 58 9C 06
00000020  0B 58 CC 07 05 58 DD 07 0E 70 FD 07 00 00 00 08

It is similar in layout to the CC49 ROM.

Code:

ID  Start  Size   Description

       00     38  header
02     38  61600  code
04  61638    210  Controller Adaptive Parameters (CAP) - serial no. / model / date
06  61848   8410  Read Adaptive Parameters (RAP)
03  69C58  13000  code
0B  7CC58   1100  code
05  7DD58   2018  Servo Adaptive Parameters (SAP)
0E  7FD70    290  size is probably only 8 bytes, remainder is FFh

These are the code sections contained in the LOD file that ships with the CC49 firmware update:

Code:

Sect Size  - Description

1     2000 -
2    12FF0 - ROM (ID 03)
3     1100 - ROM (ID 0B)
4     1100 - same as section 3
5     2000 - same as section 1
6    61638 - ROM (header + ID 02)
7     C3C0 -
8    20000 - SA OVLY (for loader)
9    30000 - SA OVLY (for loader)
10   10000 - SA OVLY (for loader)
11   10000 - SA OVLY (for loader)

I compiled a CC49 loader using sections 8 - 11.

The only thing I didn't touch was the following section of the ROM:

Code:

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

0007FD70  20 00 0A 00 00 00 8C 06 FF FF FF FF FF FF FF FF   PUIS enabled ?

0007FD70  20 00 00 00 00 00 00 00 FF FF FF FF FF FF FF FF   PUIS disabled ?

I suspect that the drive may have spun up if I had replaced the "20 00 0A 00 00 00 8C 06" with "20 00 00 00 00 00 00 00", but I wasn't sure about the function of this section of the ROM.