HDD GURU FORUMS http://forum.hddguru.com/ |
|
F3 Corrupted rom recovery http://forum.hddguru.com/viewtopic.php?f=11&t=34546 |
Page 1 of 1 |
Author: | smecca [ November 21st, 2016, 11:06 ] |
Post subject: | F3 Corrupted rom recovery |
MODEL: ST31000333AS PN: 9FZ136-516 FW: CC4H PCB: 100530756 REV A Drive is UNRECOGNIZED seems to do calibration but no terminal displayed even using shorting techniques. It was too strange for me and so decided to read M25P40 out-board. it seems to have a good header but the following structure is corrupted ( no second half copy, no sn displayed). Is it coming from some other lab that did it on purpose??? Anyway, my question is if can a case like this be faced or just there no way to come up recovering datas? Greeting and thank you for any contribution. PS: 512KB rom attached Attachment:
|
Author: | Tomset [ November 21st, 2016, 11:26 ] |
Post subject: | Re: F3 Corrupted rom recovery |
SN 9TE201S6 ? SN PCB C9356EZV ? ROM - ok: Parsing container segment....... Flash ROM image Segment: BOOTFLOADER Parsing segment....... BOOTFLOADER End parsing segment... BOOTFLOADER Segment: SHAREDFW Parsing segment....... SHAREDFW End parsing segment... SHAREDFW Segment: NONREDN_CNT_0 Parsing container segment....... NONREDN_CNT_0 Segment: ADP_SERVO_DIR Parsing segment....... ADP_SERVO_DIR End parsing segment... ADP_SERVO_DIR Segment: CAP Parsing segment....... CAP End parsing segment... CAP Segment: RAP Parsing segment....... RAP End parsing segment... RAP Segment: SAP Parsing segment....... SAP End parsing segment... SAP Segment: SFW Parsing segment....... SFW End parsing segment... SFW Segment: SHELL Parsing segment....... SHELL End parsing segment... SHELL End parsing container segment... NONREDN_CNT_0 Segment: BOOTFW_CONT_0 Parsing container segment....... BOOTFW_CONT_0 Segment: BOOTFW_DIR Parsing segment....... BOOTFW_DIR End parsing segment... BOOTFW_DIR Segment: GENERAL_DATA Parsing segment....... GENERAL_DATA End parsing segment... GENERAL_DATA Segment: IAP Parsing segment....... IAP End parsing segment... IAP Segment: BOOTFW Parsing segment....... BOOTFW End parsing segment... BOOTFW End parsing container segment... BOOTFW_CONT_0 Segment: BOOTFW_CONT_1 Parsing container segment....... BOOTFW_CONT_1 Segment: BOOTFW_DIR Parsing segment....... BOOTFW_DIR End parsing segment... BOOTFW_DIR Segment: GENERAL_DATA Parsing segment....... GENERAL_DATA End parsing segment... GENERAL_DATA Segment: IAP Parsing segment....... IAP End parsing segment... IAP Segment: BOOTFW Parsing segment....... BOOTFW End parsing segment... BOOTFW End parsing container segment... BOOTFW_CONT_1 End parsing container segment... Flash ROM image |
Author: | fzabkar [ November 21st, 2016, 16:19 ] |
Post subject: | Re: F3 Corrupted rom recovery |
Parsing container segment....... Flash ROM image Code: Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 00000000 9B 00 00 00 40 00 00 00 40 00 00 00 D7 DC 04 00 00000010 63 73 69 44 00 00 21 6B FF FF FF FF 20 FF FF FF 00000020 17 38 00 00 13 00 04 00 24 00 00 01 22 00 00 04 00000030 23 00 00 06 00 00 00 08 ID rel add description ------------------------------------------------------ 17 000038 Segment: BOOTFLOADER 13 000400 Segment: SHAREDFW 24 010000 container segment....... NONREDN_CNT_0 22 040000 container segment....... BOOTFW_CONT_0 23 060000 container segment....... BOOTFW_CONT_1 00 080000 Segment: NONREDN_CNT_0 Parsing container segment....... NONREDN_CNT_0 Code: Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 00010000 FF FF FF FF FF FF FF FF FF FF FF FF 02 00 04 00 00010010 63 73 69 44 00 00 17 49 FF FF FF FF 20 FF FF FF 00010020 14 40 00 00 04 48 00 00 06 58 02 00 05 68 86 00 00010030 03 80 A6 00 0B 80 D6 01 00 80 E7 01 00 00 00 00 ID rel add description ------------------------------------------------------ 14 000040 Segment: ADP_SERVO_DIR 04 000048 Segment: CAP 06 000258 Segment: RAP 05 008668 Segment: SAP 03 00A680 Segment: SFW 0B 01D680 Segment: SHELL 00 01E780 Segment: BOOTFW_CONT_0 Parsing container segment....... BOOTFW_CONT_0 Code: Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 00040000 14 18 00 00 D8 04 00 00 40 8A 00 00 2C 17 04 00 00040010 63 73 69 44 00 00 BB 8A FF FF FF FF 20 FF FF FF 00040020 16 38 00 00 15 40 00 00 0E 40 02 00 10 D0 04 00 00040030 00 D0 F4 01 00 00 00 00 ID rel add description ------------------------------------------------------ 16 000038 Segment: BOOTFW_DIR 15 000040 Segment: GENERAL_DATA 0E 000240 Segment: IAP 10 0004D0 Segment: BOOTFW 00 01F4D0 Segment: BOOTFW_CONT_1 Parsing container segment....... BOOTFW_CONT_1 Code: Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00060000 14 18 00 00 D8 04 00 00 40 8A 00 00 2C 17 04 00 00060010 63 73 69 44 00 00 BB 8A FF FF FF FF 20 FF FF FF 00060020 16 38 00 00 15 40 00 00 0E 40 02 00 10 D0 04 00 00060030 00 D0 F4 01 00 00 00 00 ID rel add description ------------------------------------------------------ 16 000038 Segment: BOOTFW_DIR 15 000040 Segment: GENERAL_DATA 0E 000240 Segment: IAP 10 0004D0 Segment: BOOTFW 00 01F4D0 |
Author: | smecca [ November 22nd, 2016, 7:17 ] |
Post subject: | Re: F3 Corrupted rom recovery |
Just say sorry. I took a crab looking at wrong dump file. Thank you anyway to both of you |
Author: | smecca [ July 11th, 2017, 6:12 ] |
Post subject: | Re: F3 Corrupted rom recovery |
Sorry for resuming this quite old post. Still problems with this model and fw version (CC4H). No terminal output Rom is ok and is original. Just kindly want to ask if someone has this drive and have tested the same problem (no terminal output). Thank you in advance |
Author: | pepe [ July 14th, 2017, 20:24 ] |
Post subject: | Re: F3 Corrupted rom recovery |
probably can't load discfw, that's why it looks dead on terminal it is possible to recover but i need physical access to the drive. pepe |
Author: | smecca [ July 18th, 2017, 19:17 ] |
Post subject: | Re: F3 Corrupted rom recovery |
pepe wrote: probably can't load discfw, that's why it looks dead on terminal it is possible to recover but i need physical access to the drive. pepe F3 arch on this disk shouldn't need dfw to show terminal. For this reason, pepe, I need confirmation on specific fw from the same working drive I don't think it's hd problem, cause patient loop on calib and before to proceed with modifying externaly heads set in rom to look for bads ones and then working phisically on hda I want to be sure to exclude rom corruption. I have tested Pcb with a donor and it worked fine. These are the reasons for which i suppose the rom is not working properly. So I think you are the way out of the problem. Thank you , anyway. My help request is another and really simple: Has somebody tested ST31000333AS with specific FW CC4H ? Is terminal unlocked? Thank you. |
Author: | fzabkar [ July 18th, 2017, 19:56 ] |
Post subject: | Re: F3 Corrupted rom recovery |
There are plenty of CC4H resources here: http://firmware.hddsurgery.com/?manufacturer=Seagate&family=Brinks |
Author: | smecca [ July 18th, 2017, 21:31 ] |
Post subject: | Re: F3 Corrupted rom recovery |
fzabkar wrote: There are plenty of CC4H resources here: http://firmware.hddsurgery.com/?manufacturer=Seagate&family=Brinks fzabkar, probably I'm not clear enough. I have not asked for fw I just need to know if, in this model and firmware version, terminal is locked or is normally shown. That's all |
Author: | labtech [ July 18th, 2017, 21:38 ] |
Post subject: | Re: F3 Corrupted rom recovery |
7200.11 - terminal is not locked |
Author: | fzabkar [ July 19th, 2017, 2:59 ] |
Post subject: | Re: F3 Corrupted rom recovery |
smecca wrote: fzabkar, probably I'm not clear enough. I have not asked for fw I just need to know if, in this model and firmware version, terminal is locked or is normally shown. My thoughts were that you could answer your own question by testing a known good CC4H ROM and loader combination on your donor. BTW, it is not clear what you mean by "show terminal". Are you saying that there is absolutely no output of any kind from the terminal port? In the following thread ... viewtopic.php?t=16740 ... the OP states that ... Quote: It should be noted that when I isolate the PCB, terminal hangs at: Rst 0x20M If you don't get this output on terminal, then I would say that there may be some problem with the I/O pins of your MCU. Also, if you cannot reach the SA, then your drive may still ID, albeit with model number ST_M13FQBL. |
Author: | smecca [ July 19th, 2017, 6:14 ] |
Post subject: | Re: F3 Corrupted rom recovery |
labtech wrote: 7200.11 - terminal is not locked Thanks for your confirmation labtech fzabkar wrote: BTW, it is not clear what you mean by "show terminal". Are you saying that there is absolutely no output of any kind from the terminal port? YES, THAT'S THE PROBLEM! 1)PCB CONNECTED: ABSOLUTELY NO TERMINAL OUTPUT 2)PCB DISCONNECTED: ABSOLUTELY NO TERMINAL OUTPUT The same PCB has been tested on a donor hdd, swapping adaptives chip of donor on patient pcb. The DONOR hdd worked perfectly and terminal output was shown. So, by factors parity, I could be sure that there's a problem on the rom. But image analisys of rom content ( extracted by a programmer) through pc3k says that rom is original and everything is ok. |
Author: | Amarbir[CDR-Labs] [ July 19th, 2017, 7:50 ] |
Post subject: | Re: F3 Corrupted rom recovery |
smecca wrote: labtech wrote: 7200.11 - terminal is not locked Thanks for your confirmation labtech fzabkar wrote: BTW, it is not clear what you mean by "show terminal". Are you saying that there is absolutely no output of any kind from the terminal port? YES, THAT'S THE PROBLEM! 1)PCB CONNECTED: ABSOLUTELY NO TERMINAL OUTPUT 2)PCB DISCONNECTED: ABSOLUTELY NO TERMINAL OUTPUT The same PCB has been tested on a donor hdd, swapping adaptives chip of donor on patient pcb. The DONOR hdd worked perfectly and terminal output was shown. So, by factors parity, I could be sure that there's a problem on the rom. But image analisys of rom content ( extracted by a programmer) through pc3k says that rom is original and everything is ok. Well, Whats The Big Deal Then Find Same FW of rom Transfer Adaptives To New Rom Run It and voila |
Author: | fzabkar [ July 19th, 2017, 20:57 ] |
Post subject: | Re: F3 Corrupted rom recovery |
Do you get any terminal output if you invalidate your ROM by shorting its data pin? Alternatively you could intentionally invalidate the checksum(s) of the BOOTFW module(s). The following thread suggests that you should get an error message from the kernel. Seagate 7200.11 750 gig drive will not spin up-firmware Prob: viewtopic.php?t=14337 Code: TetonST Boot ROM 2.0
Copyright Seagate 2006 Serial FLASH boot code checksum failure! |
Author: | fzabkar [ July 21st, 2017, 0:39 ] |
Post subject: | Re: F3 Corrupted rom recovery |
Your CC4H firmware has a very different structure to SDxx Brinks firmware versions. Are you certain that you should at least see "Rst 0x20M", whether or not the SA is accessible? What do you see if you enable the PUIS flag in your firmware (assuming PC3000 can do this)? When PUIS is enabled, the drive should immediately come ready and ID, albeit with a minimal Identify Device info sector. |
Page 1 of 1 | All times are UTC - 5 hours [ DST ] |
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group http://www.phpbb.com/ |