Is "2060-800068-001 REV P2" PCB locked?

Lately, I have purchased a new HDD with an 1 TB of capacity. It is Western Digital.

And I have tried to save the SA modules and ROM just in case in the future the PCB may be damaged.

The HDD I have purchased is exactly the following model:

WD10EZEX-00BBHAO

Date of manufacture: 12th June 2021

The Sediv demo shows the following info about this HDD:

HDD FW INFO:
-------------

Family: Unknown õ03D9
SA Cyl: 256
SA SPT: 1920
External ROM: YES
ROM Size: 1024
ROM Version: 0001000C
FW Version: 0001000C
Summary FW Ver: 1.01A01-0001000D
Controller FW Rev: 01.0CC
Servo FW Rev: 09.85
Overlay FW Rev: 01.0DC
DCM Head: A (41)
DCM Media: Z (5A)
Head Count: 2
Head Map: 0,1

The PCB model for this HDD is as follows:

2060-800068-001 REV P2.

I have searched info about this PCB on the Internet. And it says that it has to be unlocked for Data Recovery.

However, surprisingly, I have been successful in saving the SA modules and the ROM of this new HDD with the WDMarvel Demo. (In total, there are 518 modules and 510 tracks).

But I got a few problems when saving this data.

For example, when saving the ROM, it says that its size is 1024 KB. But if I save the ROM modules ("Copy from SA"), in this case the ROM size is 512 KB.

In short, it seems that there are 2 ROMS.

What is the right ROM (512 KB or 1024 KB)?

By the way, module ID109 is also 512 KB.

Again, when saving ROM modules from SA. it shows an error in Module ID107 ("module not in dir?").

And if I check all the modules saved, certainly there is no module ID107.

Is the fact that module ID107 is missing important?

By the way, is the PCB model really locked? And therefore, I would have to unlock it in order to save the modules and ROM.

Finally, if the PCB got damaged in the future. Since the WD10EZEX also has the 2060-771829-005 PCB model.

Could I purchase the 2060-771829-005 PCB model instead of the 2060-800068-001 REV P2? Because the latter is locked and the former is NOT.

I have a copy of all the SA modules and the ROM I have managed to save. I hope they are really valid. And there are also two photos of the HDD (the front and the back views).

If anyone wanted to take a look at the modules, I could send them to him/her by PM. Because its size is about 40 MB and I am not allowed to upload it to this forum because its size is too big.

Now the log when saving the ROM and SA modules with the WD Marvel Demo, just in case it is useful.

**************
WD Marvel LOG

**************

05/03/2022 11:37:08: Controllers search, found 4 devices
05/03/2022 11:37:08: Device selected 0970h 0B72h Master
05/03/2022 11:37:08: Network error, unable to communicate with server.
05/03/2022 11:37:13: Drive: WDC WD10EZEX-00BBHA0, family: 03D9 Unknown, FW: 01.0CC, SN: WD-WCC6Y0LYR04V, LBA 1953525168 - 1000Gb
05/03/2022 11:38:01: Reading modules...
05/03/2022 11:38:20: Successfully read 518 modules
05/03/2022 11:38:41: Started reading tracks...
05/03/2022 11:40:49: Error reading track -1 on head 0, status - DISK_DAM_ERROR
05/03/2022 11:40:52: Error reading track -1 on head 1, status - DISK_DAM_ERROR
05/03/2022 11:40:52: Successfully read 510 tracks
05/03/2022 11:43:20: ROM successfully read
05/03/2022 11:43:56: Reading modules...
05/03/2022 11:43:56: Error reading module ID107, state - Module not in Dir???
05/03/2022 11:43:56: Successfully read 6 modules.

Attachments

: PCB of the new HDD.

: Front view of the new HDD.

I suspect that you have a 1024KB ROM which is divided in two redundant halves. One half is a backup of the other half. I believe that WD does it this way to provide a recovery path in the event of a failed firmware update.

The "2060-800068" PCB is a locked 2.5" PCB whereas your drive is an unlocked 3.5" model. :-?

That's strange.

The "R/N" code on the label is "800039" which would suggest that the PCB should be "2060-800039". Is this an error in the artwork ???

https://www.hdd-parts.com/18093027.html

WD's warranty checker identifies the drive as belonging to the "TRESUL" family (Tressels Ultra ???). You should see the family in SA module 0xC5.

TRESUL

https://support-en.wd.com/app/warrantystatus

Please feel free to send the firmware dump to me.

Edit: Modules 102 - 107 will probably be empty "NOT_INIT". They are usually only valid when the ROM is embedded withing the MCU, not external.

fzabkar wrote:The "2060-800068" PCB is a locked 2.5" PCB whereas your drive is an unlocked 3.5" model. :-? That's strange.

The only reference to the 2060-800068 PCB as a 2.5" model seems to be on the Dolphin Data Lab site. I wonder if they got it wrong?

Firstly, thank you for your reply.

I have taken a closer photo to the sticker which is on the PCB.

And when scanning the QR code, I get this:
XCY1373D9DF00064801

It is also written the following on the PCB sticker:
"800068-091".

The just mentioned number is apparently the exact PCB model.

You can take a look at the photo of the PCB sticker enclosed with this message.

Attachments

: sticker on the PCB

It looks like Dolphin made a mistake.

Your resource dump is here:

http://files.hddguru.com/download/Non-PC-3000%20firmwares/Western%20Digital/TRESUL/WD10EZEX%20ROM%20%20Modules%20by%20WDMarvel.rar

All the 10x modules are "NOT_INIT".

fzabkar wrote:The "R/N" code on the label is "800039" which would suggest that the PCB should be "2060-800039". Is this an error in the artwork ???

In theory, the numbers engraved on the PCB itself are usually the most reliable.

Therefore, the exact PCB model seems to be "2060-800068-001 REV P2".

But, if in the future, my PCB got damaged. Could I replace it with "2060-800039" PCB model?

And I am asking this question because it is easier to find the latter.

Regarding the ROM and modules I have sent you, are they valid just as I sent you?

Or have you modified them?

They aren't encrypted, are they?

Another question:

When there is a ROM chip on the PCB, there is not usually a copy of the ROM in the SA modules.

Is this also so in this case?

Therefore there is not a copy of the ROM in module ID109.

And therefore, in the event of the PCB getting damaged, the replacement PCB would have to be flashed with the ROM file with a size of 1024 KB and not with the file of 512 KB.

And in the event of using a USB-TTL adapter to read the ROM. Would it have to be with a 3.3V TTL interface? Or perhaps with a voltage of 1.8V?

fzabkar wrote:It looks like Dolphin made a mistake.

Yes, the USB C 2.5" board is 2060-800086, not 68. Someone got dyslexic with the numbers and repeated the mistake throughout the entire article.

People have successfully used different PCBs in other models, but you need to ensure that both PCBs have the same MCU and motor controller ICs. I don't know whether 39 is a match for 68, though.

Your latest resource dump is not encrypted.

I don't know whether it is a hard and fast rule, but there are no SA backups for the ROM modules when the ROM is external to the MCU. Module 0x109 always appears to contain the ROM copy, although its adaptive modules are merely templates. Sometimes ROM module 0x47 can be regenerated from SA module 0x40. I have also seen cases where SA module 0x139 contains the adaptive data for module 0x47.

I don't know whether a 512KB ROM could be used in your case. I would need to see a full ROM dump in order to understand what is going on. Other models appear to have "flags" which tell the MCU which half of the ROM is active.

Whether you need a 1.8V or 3.3V adapter depends on the Vcc voltage of your PCB. You would need to measure this.

After pluging the HDD into the SATA power connector and starting Windows, I have tried to measure the voltage between TX and GND and also between RX and GND. But I got no voltage at all.

As shown in the following photo:

http://www.hddoracle.com/download/file.php?id=198

In fact, there are no voltages at all in any of the pins.

How do I measure those voltages?

And what is the pin for Ground?

You can use a screw hole for your ground. In our case at the HDD Oracle, we shorted a particular configuration resistor to Vcc or ground (I can't remember which). That caused the MCU to look for an external ROM. When it was unable to find it (obviously), it began looking for input at the UART port. Then we were able to dump the memory locations corresponding to the internal ROM.

fzabkar wrote:You can use a screw hole for your ground.

Does it mean that in order for me to take the measurements I have to remove the PCB from the HDD?

Is that totally necessary?

material32 wrote:
fzabkar wrote:You can use a screw hole for your ground.

Does it mean that in order for me to take the measurements I have to remove the PCB from the HDD?

No, just use the screw as your ground.

Is "2060-800068-001 REV P2" PCB locked?

Is "2060-800068-001 REV P2" PCB locked?

Re: Is "2060-800068-001 REV P2" PCB locked?

Re: Is "2060-800068-001 REV P2" PCB locked?

Re: Is "2060-800068-001 REV P2" PCB locked?

Re: Is "2060-800068-001 REV P2" PCB locked?

Re: Is "2060-800068-001 REV P2" PCB locked?

Re: Is "2060-800068-001 REV P2" PCB locked?

Re: Is "2060-800068-001 REV P2" PCB locked?

Re: Is "2060-800068-001 REV P2" PCB locked?

Re: Is "2060-800068-001 REV P2" PCB locked?

Re: Is "2060-800068-001 REV P2" PCB locked?

Re: Is "2060-800068-001 REV P2" PCB locked?

Re: Is "2060-800068-001 REV P2" PCB locked?