CA_FLUSH_ALL_GOT_CANCELED - what's wrong?

[pikus_09]

CA_FLUSH_ALL_GOT_CANCELLED - what's wrong? Blocked? Or Bad ROM?

Code:

HDD: WD2002FAEX-007BA0 FW: 00050016F
    2015-12-29 18:34:07: Error reading module ID0A, state - CA_FLUSH_ALL_GOT_CANCELED
    2015-12-29 18:34:08: Error reading module ID0A, state - CA_FLUSH_ALL_GOT_CANCELED
    2015-12-29 18:34:08: Error reading module ID0A, state - CA_FLUSH_ALL_GOT_CANCELED
    2015-12-29 18:34:09: Error reading module ID0A, state - CA_FLUSH_ALL_GOT_CANCELED
    2015-12-29 18:34:09: Error reading module ID0A, state - CA_FLUSH_ALL_GOT_CANCELED
    2015-12-29 18:34:09: Error reading module ID0A, state - CA_FLUSH_ALL_GOT_CANCELED
    2015-12-29 18:34:09: Error reading module ID0A, state - CA_FLUSH_ALL_GOT_CANCELED
    2015-12-29 18:34:13: Error editing the model
    2015-12-29 18:34:46: Error reading module Dir, state - CA_FLUSH_ALL_GOT_CANCELED
    2015-12-29 18:35:46: Error reading ROM Dir, state - CA_FLUSH_ALL_GOT_CANCELED
    2015-12-29 18:36:14: Error reading module ID47, state - CA_FLUSH_ALL_GOT_CANCELED


Btw. My drive is not slow, all heads works perfectly, no bad sectors in Sa Surface, all mods good. I suspect PCB and main MCU MARVEL 88i9045TJF2, What do you think?



Edit: Rewrite ROM(oryginal ROM copy), drive Work, but not solve this problem. UserArea is blocked, ARCO not work on this HDD(DISK_DAM_ERRORs, on all heads which is not true)

[Moltke]

read and show ROM

[pikus_09]

OK, Frend

Attachments

00050016.rar

ROM FW: 00050016F

(187.76 KiB) Downloaded 852 times

[Moltke]

Modules 0Bh and 02Bh use different PBA module 01h.
what will happen if swap their position?
it is a bit strange, 2 module 01h in the same region

[pikus_09]

Are you using WDR ?
WDR can't properly handle newer WD drives ...

Hello frends, no i not using WDR, I using Wd marvel.
No, I do not have a second PCB, but I have the same processor in another PCB and I want solder.

Modules 0Bh and 02Bh use different PBA module 01h.
what will happen if swap their position?
it is a bit strange, 2 module 01h in the same region

I don't no, but
probably drive will disappear, or will be as XYZ SN.

[fzabkar]

This ROM differs a little from others I have analysed, so I've had to rewrite my ROM checker. The code sections appear to be duplicated in each half of the ROM, except for the first LDSC/PCMBlock.

Code:

C:\>wdromvf3 00050016.bin

Analysing 00050016.bin ...

Searching for LDSCs and verifying PCMBlocks ...

LDSC   LDSC    PCMBLock       PCMBlk CS
Start  ID CS   Start - End     Exp/Act
---------------------------------------
00000  5A AB   00020 - 00918    4B   4B   OK
01000  01 E1   01140 - 02838    02   02   OK
01020  02 79   02839 - 09CC5    EE   EE   OK
01040  03 5F   09CC6 - 0F4D2    19   19   OK
01060  04 D3   0F4D3 - 0FD7B    E1   E1   OK
01080  05 E4   0FD7C - 0FF80    09   09   OK
010A0  06 2C   0FF81 - 104D1    C6   C6   OK
010C0  07 02   104D2 - 10902    76   76   OK
010E0  08 4C   10903 - 26FCF    10   10   OK
01100  09 88   26FD0 - 2F858    C8   C8   OK
41000  01 E1   41140 - 42838    02   02   OK
41020  02 79   42839 - 49CC5    EE   EE   OK
41040  03 5F   49CC6 - 4F4D2    19   19   OK
41060  04 D3   4F4D3 - 4FD7B    E1   E1   OK
41080  05 E4   4FD7C - 4FF80    09   09   OK
410A0  06 2C   4FF81 - 504D1    C6   C6   OK
410C0  07 02   504D2 - 50902    76   76   OK
410E0  08 4C   50903 - 66FCF    10   10   OK
41100  09 88   66FD0 - 6F858    C8   C8   OK

LDSC   = PM Loader Config String (32 bytes)
ID     = ID byte of LDSC (byte #0)
CS     = Checksum byte or word
PCMBlk = Program Code Memory Block
Exp    = Expected checksum for PCMBLock
Act    = Actual checksum for PCMBLock

[pikus_09]

O Hello Frank, so are you suggesting that it may be fault ROM code?

[pikus_09]

Modules 0Bh and 02Bh use different PBA module 01h.
what will happen if swap their position?
it is a bit strange, 2 module 01h in the same region

Moltke Friend, can you develop your thought more broadly?

[Moltke]

Moltke Friend, can you develop your thought more broadly?

no. I do not know much English.
I recommend playing with the flag of activity modules 0Bh and 020Bh. after all, and 0Ah 01h are described in them. or only change individual entry description rom modules

[pikus_09]

I compared two different roms with the same microcode and mod 20b and 0b standard variety. I Suspect main mcu on pcb. What do you think?

[Moltke]

I Suspect main mcu on pcb. What do you think?

I don't think it's ROM or pcb. something with attribute mask bits
for checking fill another ROM. Will read modules 0Ah and 01h?

[pikus_09]

Did you get any reply on WDMarvel forum ?

I did buy a full lifetime license of yesterday at night and recieved my codes today but i'm suposed to wait 24 hours to have my account activated on their forum.

yes i asked on WD MARVEL forum, but Vlad playing with me cat and mouse, zero concrets. Vlad says that he should WD MARVEL to handle it.

I don't think it's ROM or pcb. something with attribute mask bits
for checking fill another ROM. Will read modules 0Ah and 01h?

Yes, i have full backup Modules and all Backup ROM modules. I attach.
btw. Moltke friend, if you do not feel up to writing in the English language, please write in her, I later translater translate it yourself.

[pikus_09]

It's simple, WD ROM MODE MANPLRE SN-XYZ.

[Moltke]

another 00050016

Attachments

pcr.7z

(187.18 KiB) Downloaded 751 times

[pikus_09]

Ok, I write this ROM and check if work.

[pikus_09]

I Write this ROM, and still the problem is the same.

Code:

    2015-12-31 15:05:26: The drive WD2002FAEX-007BA0                  Disk size 3907029168 - 2000Gb
    2015-12-31 15:05:29: Error reading ROM Dir, state - CA_FLUSH_ALL_GOT_CANCELED
    2015-12-31 15:05:57: Error reading module Dir, state - CA_FLUSH_ALL_GOT_CANCELED
    2015-12-31 15:06:02: Error reading module ID02, state - CA_FLUSH_ALL_GOT_CANCELED
    2015-12-31 15:06:02: Error reading device configuration , state - CA_FLUSH_ALL_GOT_CANCELED
    2015-12-31 15:06:02: Error reading device configuration , state - VSCE_UNSUP_ACTION_CODE
    2015-12-31 15:06:24: Error reading the P-list, state - CA_FLUSH_ALL_GOT_CANCELED
    2015-12-31 15:06:35: Started LBA scan...
    2015-12-31 15:06:45: Not ready for 10 seconds, Soft Reset ...
    2015-12-31 15:06:55: Not ready for 10 seconds, Soft Reset ...
    2015-12-31 15:06:55: LBA scan completed, elapsed time - 00:00:20
2015-12-31 15:11:34: Error reading ROM Dir, state - CA_FLUSH_ALL_GOT_CANCELED
2015-12-31 15:11:38: Error reading ROM, state - CA_FLUSH_ALL_GOT_CANCELED
2015-12-31 15:11:39: Error reading ROM, state - CA_FLUSH_ALL_GOT_CANCELED

[Moltke]

is nothing else comes to mind.
but if you read the rom modules with pcb only ?

[pikus_09]

No i do not read modules ROM on same PCB, PCB is screwed to disk. Try the same PCB?

[Moltke]

No i do not read modules ROM on same PCB, PCB is screwed to disk.

Remove the pcb and try to read

[pikus_09]

Ok I will try.