Wish List for future updates on WD Marvell tool :

[Takanashi_Hina]

Hi !

If someone working on the development of the PC-3000 UDMA tools are reading this post, I would like to propose for the next update on the Marvell WD tool an option to re-create the P-List from the factory self scan logs.

Just on the last weeks I had at least 2 cases of drives with damaged translator and P-List on both copies.

I couldn't find any "easy" way using PC-3000 UDMA to get the original P-List (without patching bits form copy 0 with bits from copy 1) by reading the SS logs left at factory.

This shouldn't be very hard to implement, as at least 2 other "Chinese" tools already have that option (Regen P-List from SS logs). On the 2 cases that I have plus some more testing that I've done, by damaging P and translator with UDMA, I was able to do a simple one click fix by re-creating the P-List from SS logs using tools from "china". It would be great to have this function implemented on PC-3000 UDMA Marvell tool as well.

Regards.

[Takanashi_Hina]

Another thing that could be implemented would be the function to restore ROM on pcbs by shorting points to enter in x-modem mode (tiny console) and erase ROM and upload a working copy from there.

This would be of some use for people without external programmer or if PCBs have masked ROM.

I can help with some ideas about how to implement this, if someone developing the tools on ACE would want, PM me and I will provide some more details.

Again this is a operation that it's possible with other sort of tools and could well be incorporated on UDMA.

Regards.

[Maxim_TS]

Hi Takanashi_Hina!

Thank you for the propose, we will forward it to ACE developers team.

[drdoc]

I would like to see.
1)
Automatic logging for log and terminal screens
my process is always to start log in both screens - on to log0 other to term0.txt, next session I use log1.txt and term1.txt

2)
Save roms with checksum appended and microjogs appended to name.

So I read a rom, modify it, write it back.
Or I do a hotswap and read that rom with the same drive, so now I dont know which rom is which.
So I have to generate a sha256 hash code in order to compare two rom files.
I would like the checksum or sha256 added to the names.
so instead of rom_.bin
it would be rom_386.bin

and for wd drives for rom_module 47 and full rom
rom_386_mjae8.bin <<< indicates mj value for head 0 is ae8

3)
converter to import drive resources into database.
I always backup a drives resources whenever I attach a new drive.
but dont always take the time to also import it into the database.
Would be nice if I could easily take all my profiles and import them into the database.

4)
webbased database.
What if we could all share our resources in a server thats on the web?
people are alwys hunting for modules and firmwares.
How about a web based solution where we can all ul our databases.

[drdoc]

5)
when reading modules read critical A modules first
then B,C,D

sometimes it takes alot of time top read modules.
Also I dont want to crash the heads trying to read logs or other unimportant modules.

[Bruno]

YES what drdoc says:
3)
>converter to import drive resources into database.
>I always backup a drives resources whenever I attach a new drive.
>but dont always take the time to also import it into the database.
>Would be nice if I could easily take all my profiles and import them into the database.
That would be realy a great help, i think for all DR engineers!

A tool to organice the tatabase where also help full, because after a update in the past, the WD, Seagate are stored under Intel SSD Folder.....
To solve it, i have to create the hole database new