SimError-Remaining in Boot FW

Moderator: Nick_TS


AT3000_user
Newbie
Posts: 10
Joined: 05.06.24
Reputation: 0 / (0)

SimError-Remaining in Boot FW

Postby AT3000_user » 14.06.24, 02:27

Hello
Does anyone know how to solve the following Seagate Rosewood drive issue?
It appears that Rom F/W is unable to load disk F/W throughout the remaining boot
process (possibly Module 20D from the disk surface).
PCB is original and head seems to be OK. There is no click sound or unusual noise. Becomes ready at power on.

Please look at the last two lines of the terminal log.

SimError-Remaining in Boot FW
Perform a double download without a power cycle

Model: ST2000LM007
F/W: EV01

---------------- Terminal Log -------------------------------------------
Boot0x80M
TCC:001C
[LBA=0x0000040E][LBA=0x0000040E]
DSC PASS
SIMFileFD=FC00320DErrorCode=43110081DiscLBA=000000000000040EDuration=00000AC5ms[LBA=0x0000DE06][LBA=0x0000DE06]
SIMFileFD=FC00320DErrorCode=43160080DiscLBA=000000000000DE06Duration=00000046ms
SimError-RemaininginBootFW
Performadoubledownloadwithoutapowercycle
-----------------------------------------------------------------------------


AT3000_user
Newbie
Posts: 10
Joined: 05.06.24
Reputation: 0 / (0)

Re: SimError-Remaining in Boot FW

Postby AT3000_user » 14.06.24, 04:55

This is the terminal's output after uploading compatible microcode.
It remains ready after microcode upload. However, any attempt to access SA, results in an endless busy mode.

Boot0x80M
TCC:0022
[LBA=0x0000040E][LBA=0x0000040E]
DSC PASS
SIMFileFD=FC00320DErrorCode=43110081DiscLBA=000000000000040EDuration=00000ADCms[LBA=0x0000DE06][LBA=0x0000DE06]
SIMFileFD=FC00320DErrorCode=43160080DiscLBA=000000000000DE06Duration=00000047ms
SimError-RemaininginBootFW
Performadoubledownloadwithoutapowercycle
0x0000 0x3FFFFFFF
FTU

User avatar
igen
New user
Posts: 51
Joined: 03.07.08
Reputation: 1 / (11)

Re: SimError-Remaining in Boot FW

Postby igen » 17.06.24, 09:46

Hello,

This message:

SimError-RemaininginBootFW
Performadoubledownloadwithoutapowercycle


It's means that for some reason there is a problem with the heads reading the overlays correctly.

Theoretically there are three explanations for this situation.

1) Incorrect reading of the heads,
2) Non-original, damaged or modified ROM,
3) Physical damage the surface in the critical SA area (or incorrect overwriting of this area).

I would start by thoroughly analyzing the ROM content.
If everything is OK with the ROM, then you have to replace the heads.
When the third possibility occurs - it's game over...
Any man is liable to err, only a fool persists in error.
Marcus Tullius Cicero


AT3000_user
Newbie
Posts: 10
Joined: 05.06.24
Reputation: 0 / (0)

Re: SimError-Remaining in Boot FW

Postby AT3000_user » 18.06.24, 01:16

Hello igen,

Thank you so much for the helpful comment.
I already have checked the ROM contents and compared it to a similar version. I think it's fine.
I haven't replaced the heads yet, but I will do it as a last hope!
I also will post the results here once I have completed the head swap and checked the outcome.


AT3000_user
Newbie
Posts: 10
Joined: 05.06.24
Reputation: 0 / (0)

Re: SimError-Remaining in Boot FW

Postby AT3000_user » 18.06.24, 01:41

Forgot to mention that there were some repeated WARNINGS when reading the ROM.
The content pattern appears to be normal, however. Only visually compared to a similar ROM.


Segment: Segment ID : 0x0000002B
Parsing segment....... Segment ID : 0x0000002B
WARNING! Segment whole space check sum is invalid!
WARNING! Segment used space check sum is invalid!

End parsing segment... Segment ID : 0x0000002B


Segment: Segment ID : 0x0000002C
Parsing segment....... Segment ID : 0x0000002C
WARNING! Segment whole space check sum is invalid!
WARNING! Segment used space check sum is invalid!

End parsing segment... Segment ID : 0x0000002C


Segment: Segment ID : 0x0000002D
Parsing segment....... Segment ID : 0x0000002D
WARNING! Segment whole space check sum is invalid!
WARNING! Segment used space check sum is invalid!

End parsing segment... Segment ID : 0x0000002D
.....
Last edited by AT3000_user on 18.06.24, 03:20, edited 1 time in total.


AT3000_user
Newbie
Posts: 10
Joined: 05.06.24
Reputation: 0 / (0)

Re: SimError-Remaining in Boot FW

Postby AT3000_user » 18.06.24, 02:46

FLASH ROM Info
==============
Image size............... : 1048576

QNR Revisions:
Flash ROM image.......... : 7
GLOB_FLASH_DIR........... : 7
BOOTFW_CONT_0............ : 0
GLOB_FLASH_DIR........... : 6
BOOTFW_CONT_1............ : 0


CAP
###
Validation Key........... : 0x00000020
Fam ID................... : 0xAF (Rosewood_AF)
Fam Member............... : 0x1
Head count............... : 4
Date (ERROR!)............ : ?? - ?? - ????
SN....................... : WDZV87ZW
PCB SN................... : K132AB0M
PCB PN................... :
WWN...................... : 5000C500D617223C

RAP
###
Format revision.......... : 0x0208
Contents revision........ : 0x840B0100
Number Sys Zones......... : 1
Number User Zones........ : 150
Heads count.............. : 4
FW Implementation Key.... : 0x1E

SAP
###
Addr 0................... : 0x00118B00
Addr 1................... : 0x80000000

Fam ID................... : 0xAF (Rosewood_AF)
Fam Member............... : 0x1
SN....................... : WDZV87ZW
Servo FW rev code........ : 0x797F
Max head................. : 3
Seek mode................ : 2000
Flags.................... : 1A09
Head vendor.............. : default
RRO mode................. : 0005
Preamp type.............. : 0000
Heads polarity........... : 00 00 00 00
Logical head map......... : 00 01 02 03
Phys head maps........... : 00 00 00 00

IAP
###
ID, code................................ : 0xFFFF
PUIS.................................... : OFF
Active config........................... : 35C78D40, Default
Active config (M11 like)................ : FFFF35C7
NAND ROM cache flag, Kahuna like........ : FFFFFFFF
NAND ROM cache flag, Rosewood like...... : FFFFFFFF

IAP 1
###
ID, code................................ : 0xFFFF
PUIS.................................... : OFF
Active config........................... : 35C78D40, Default
Active config (M11 like)................ : FFFF35C7
NAND ROM cache flag, Kahuna like........ : FFFFFFFF
NAND ROM cache flag, Rosewood like...... : FFFFFFFF

CODE info
#########
Bank 0
ProdType................. : R1AEA06.SBC2
Controller FW Rev........ : 09291939
Customer Release......... : EV01
Changelist............... : 01773760
Build date / time........ : 9/29/2019 7:39:08 PM
Package Global ID........ : 00305567
Package Builder ID....... :
Build Rev................ :
Package Rev.............. : AA0094
Pkg P/N.................. : 100860472
Servo FW................. : 797F / ---- / ---- / ----
Package Version.......... : R1AEA06.SBC2.AA0094.EV01
Pkg CFW Ver.............. : R1AEA06.SBC2.01773760.00305567

Bank 1
ProdType................. : R1AEA06.SBC2
Controller FW Rev........ : 09291939
Customer Release......... : EV01
Changelist............... : 01773760
Build date / time........ : 9/29/2019 7:39:08 PM
Package Global ID........ : 00305567
Package Builder ID....... :
Build Rev................ :
Package Rev.............. : AA0094
Pkg P/N.................. : 100860472
Servo FW................. : 797F / ---- / ---- / ----
Package Version.......... : R1AEA06.SBC2.AA0094.EV01
Pkg CFW Ver.............. : R1AEA06.SBC2.01773760.00305567

User avatar
igen
New user
Posts: 51
Joined: 03.07.08
Reputation: 1 / (11)

Re: SimError-Remaining in Boot FW

Postby igen » 19.06.24, 11:28

Hello again,

I wouldn't worry about these checksum errors (when reading ROM)...
As FZabkar suggests - see in the post below:

https://forum.hddguru.com/viewtopic.php?f=11&t=42757

If you are sure, that the content of the ROM is correct - then you have no choice - but to replace the heads only.

As I wrote earlier - the message:

SimError - Remaining in BootFW
Perform a double download without a power cycle


... one of the reasons is that the heads cannot write or read (especially the main system H0).
Or/and the surface became damaged via Service area.

And rather don't try to change the head mapping in ROM.
So these head map changes must be used very carefully. With damaged heads (weak, dirty) it is very dangerous.
I had early a lot of drives that others persons tried to recover by changing head map.
Fnally resulting was serious surface damages.

In the SAP segment, you have the default head supplier - so you shouldn't have any problems finding a donor.

Best regards and good luck... :thumbup:

P.S.

For peace of mind, you can still replace the PCB (after swapping the ROM).
But I estimate the chances of this solution at less than 1%...
Any man is liable to err, only a fool persists in error.
Marcus Tullius Cicero


AT3000_user
Newbie
Posts: 10
Joined: 05.06.24
Reputation: 0 / (0)

Re: SimError-Remaining in Boot FW

Postby AT3000_user » 09.07.24, 07:30

Thanx Igen,

Replaced the PCB and swapped out the ROM. The same error.
Replaced the head with a compatible one. No help.
As a result, I came to a dead end and had to give up on this case. :cry: :cry: :cry:


Return to “Arch F3”

Who is online

Users browsing this forum: No registered users and 3 guests