PC-3000 Forum

Hi Guys,

I have few PCB's from ATLANTIS family with ROM embedded inside the MCU, not the external ROM -.
During a firmware repair process i wrote few ROM generated attempts and now the PCB is not responsive at all.
Is someone familair with a way to re-write the ROM content of these type of PCB's using DFL with Boot Rom code or some other way?
When i bought the PC-3000 Express, i didn't get any termianl adpaters for WD? will i need them for this purpose?

Thanks

I am starting to feel like it is some bug with PC3K for this family.
I just took another working Atlantis drive, and wrote ROM from a donor drive, and again PCB is bricked.
Any chance that PC3K in the last version is writing ROM content wrong to this family and corrupts the ROM?

These are 3 example of ROM's, 2 Bricks the PCB, and 1 doesn't:

Bricks the PCB:
https://dl.dropboxusercontent.com/u/495 ... icks-1.bin
https://dl.dropboxusercontent.com/u/495 ... icks-2.bin

Doesn't Brick the PCB:
https://dl.dropboxusercontent.com/u/49559271/ROM-OK.bin

If anyone see what is wrong there i would love to know, Grrrrrr... already bricked 5 PCB's of this revision

As soon as I get a chance later today I'll write these ROM files to a PCB here, let you know if they go OK for me.

If your having problems with writing ROM would it be worth trying to build a good HotSwap donor and reach data this way, would save you needing to write ROM to do this.

Hi Alyn,

I think the mystery is solved - DO NOT USE IT ON YOURS - THEY WILL BRICKED - PLEASE AVOID THAT
I looked into the binary of the good and bad rom up here and the 2 bad ones that brick the PCB are from a differnt type of PCB.
So even though the customer said that this is the original PCB, it was replaced with another completely different one off different # - unbeleiveable how far they'll go to hide the truth.
I just googled this drive PCB and it is 537 and not 590 as it came with - so at least i know whats wrong now instead of keep on bricking my donors anf handle teh real problem of the drive.
Now just need to find a way to restore all these bricked PCB's.

Cheers Mate

All good, managed to find the right PCB and repair the FW problem, all good and recovering the data now, cheers

odedshankar wrote:Source of the postI think the mystery is solved - DO NOT USE IT ON YOURS - THEY WILL BRICKED - PLEASE AVOID THAT

You know that even if you "brick" a WD Marvel PCB you can still fix it using boot ROM code and a good ROM. Back before they implemented this feature I had a stack of bricked PCBs, now they are all fixed.

Yep DataMedics, just started to use it today, works like a charm - just repaired all these dead PCB's, cheers mate

From my experience, if you read from a U12, you need to write back to a U12. If you read from MCU, you need to write back to MCU. I have not had much luck reading from one and writing to the other.

Agreed.