CA_FLUSH_ALL_GOT_CANCELED - what's wrong?

[pikus_09]

Same PCB is very slowly,
as presented for same PCB:

And, attach ROM modules, and ROM CODE.

Attachments

ROM code.rar

(189.56 KiB) Downloaded 780 times

[Moltke]

Modules are read without error?

[pikus_09]

Modules are read without error?

Yes

[Moltke]

ok.
Now slide the regions and check sa

[pikus_09]

ok.
Now slide the regions and check sa

But, screw the PCB to drive?

[Moltke]

first slide, then screw the controller

[pikus_09]

SA REGIONS

[Moltke]

reg0: 0 +1
reg1: 497920 +1

[pikus_09]

OK, I will try.
Btw. Screw PCB and Check SA?

[Moltke]

Btw. Screw PCB and Check SA?

yes.
you need to WDMarvel forum to ask how to deal with the shift regions.
type "Как мне работать со сдвинутыми регионами ?"
I can not explain in English

[pikus_09]

No problem Frend, SA checked, and SA Is Empty, Can't Read modules, I Created new theard in WD MARVEL forum, and we are waiting for a reply.

[Moltke]

I Created new theard in WD MARVEL forum, and we are waiting for a reply.

ok. but today we (exUSSR) celebrate the new year, so you have to wait a long time

[pikus_09]

No problem. We Poles also celebrate the new year

[pikus_09]

SA
SA region editor

just enough for now wrote vlad

[pikus_09]

Well, I don't know. I suspect that detects a drive ok but the UA will blocked. What do you mean write bruch firmware?
BTW. I have some doubts as to the PCB reaction to commands is beyond time limits. Understand me?
Thanks for all replies friends

Last edited by pikus_09 on December 31st, 2015, 20:26, edited 1 time in total.

[pikus_09]

I mean sytuaution when backup rom module's and rom. Initialization mcu Exceeded timeout. Reaction same PCB is very slowly.

[fzabkar]

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

No, my own program was faulty. It wasn't able to detect the code modules in the second half of the ROM. I have since fixed the problem and all the checksums are OK.

BTW, I'm not sure I understand your problem. You appear to be saying that your drive is OK but WDMarvel doesn't give you access to the SA. So is your question just a technical one rather than a data recovery issue or a HDD performance issue?

If so, and assuming that WDMarvel does not have a bug, ISTM that either the ROM code or a particular SA module is locking you out of the SA (by disabling VSCs?). IIUC, Moltke replaced the ROM code with a version which he believed was not locked, but you were still unable to access the SA, so this would point to an SA module as the culprit. The next line of attack was to hide the SA from the ROM by displacing SA regions 0 and 1 by +1 sector in module 0x20B. Would it not have been advisable to also adjust the location of module 01 by -1 sector? In this way the ROM would still find module 1 but would not be able to find the others.

[Moltke]

Would it not have been advisable to also adjust the location of module 01 by -1 sector? In this way the ROM would still find module 1 but would not be able to find the others.

shifting regions we have access to the service area under the loader.
we need to analyze all modules, not just the 01h. how to do it in wdmarvel I do not know, and better to consult the author
since the ROM module are read without an error (experiment with only one controller) , the block comes from SA

[pikus_09]

shifting regions we have access to the service area under the loader.
we need to analyze all modules, not just the 01h. how to do it in wdmarvel I do not know, and better to consult the author
since the ROM module are read without an error (experiment with only one controller) , the block comes from SA

In this situation I think it is helpful to take a backup of Reg 0 and reg 1 because the WD Marvel does not allow you to edit modules from the level SA Editor, or block loading firmware, then access to SA from the level DIR Modules. Understand me?

I would say WD changed something on the ARCO procedure and now you can't start it with WDMarvel, same as when they changed SS so it requires unlocking.
Test with drive from the exact same model.
If it doesn't work then WDMarvel can't run ARCO on those drives. If it does work then the problem is with your specific drive.

Arco procedure can be run on my disk, without unlocking, tests 6A, 6B are going perfectly, while Zone TPI and Head Qual no longer have access to the User Area, based on previous test results and what is revealed DISK_DAM_ERROR on all the heads, the same way ARCO 46 All DISK_DAM_ ERROR on all heads.
Self Test also does not require unlocking.

Frank, he can access SA.
What he can't do is RUN ARCO (calibration that he needs to do prior to self scan).
He is trying to self-scan the drive an he can't but he can read modules ok.

Exacly, but
by the end it is not, when regions SA are original, is accses for SA, all modules from the level DIR can read, write all access from the DIR there is no time when regions are on head 0 and 1 are changed, you must then using editor, which does not have the WD marvel. Understand me?

[Moltke]

. Understand me?

no. now the modules can be read or not ?! the reason (calibrator or selfscan) do not interest me. only the type of lock