Samsung HM502JX USB2.0 with bad board

[happygo]

hello, every one
I have a Samsung HM502JX portable drive, with a bad USB2.0 board
Now I've found a same model donor, yet they are different in p/n.
I put the donor board on the target drive.
It spins up without any noise, however, it stays BSY and couldn't be recognized.


I tried to download maincode or HTcode with PC3000 into the drive.
But it always shows: Error pulse set error; Terminal is busy
I can't send any command.

Here's the log in terminal.

SPOK
mS1 00000003
A1O=127 A1G=425
O=515 S=0
SK C: 4584 H:0
Scan BS ..
Boot Sector Error! Take a default.
Loaded FIT ( 0: 0: 1)
Reso Table Loaded
RRO1X Read OK
Overlay Code Loaded to 0x1004A000

I'm not sure if it's the compatibility of the PCB or any other problem
any suggestion would be appreciated
many thx

[shahij]

U didn't swap rom. If u swapped then actually the rom is bad.

[fzabkar]

Try repairing the PCB. IIRC, some Samsung USB PCBs have a common problem that can be fixed by reflowing solder to a particular inductor.

Post some photos if you need help.

[happygo]

U didn't swap rom. If u swapped then actually the rom is bad.

Try repairing the PCB. IIRC, some Samsung USB PCBs have a common problem that can be fixed by reflowing solder to a particular inductor.

Post some photos if you need help.

dear shahij and fzabkar
I'm not sure if I can fix the PCB, cuz it's in a very bad condition.
The MCU has been removed before.
I wonder if the chip on the back with 8-pin is EPROM or not?
Havent try it yet. or should I swap the MCU
Thx for helping

Attachments

original board

[happygo]

the front of the board

Attachments

[fzabkar]

These threads might help:
viewtopic.php?f=1&t=25581
viewtopic.php?f=1&t=18075

The EEPROM on the underside is associated with the bridge IC. It doesn't need to be moved. The HDD "ROM" code is embedded within the Marvell MCU. BTW, it doesn't look to me like the MCU has been replaced. If it has, then it's a very neat job.

As for the damage (?) around the USB connector, ISTM that a decent tech should be able to clean it up.

What were the original symptoms? Did the drive spin up? Was it a USB detection issue? Can you measure the voltages at the 4R7 coils? One coil is slightly damaged, but it may still be OK.

If you are unsuccessful with your repairs, and if the drive still spins up but is not detected, then you could try converting the drive to SATA. This will bypass any defective bridge circuitry.

[happygo]

These threads might help:
viewtopic.php?f=1&t=25581
viewtopic.php?f=1&t=18075

The EEPROM on the underside is associated with the bridge IC. It doesn't need to be moved. The HDD "ROM" code is embedded within the Marvell MCU. BTW, it doesn't look to me like the MCU has been replaced. If it has, then it's a very neat job.

As for the damage (?) around the USB connector, ISTM that a decent tech should be able to clean it up.

What were the original symptoms? Did the drive spin up? Was it a USB detection issue? Can you measure the voltages at the 4R7 coils? One coil is slightly damaged, but it may still be OK.

If you are unsuccessful with your repairs, and if the drive still spins up but is not detected, then you could try converting the drive to SATA. This will bypass any defective bridge circuitry.

fzabkar, thx for reply

here's a closer picture, the MCU is floating
I don't know what happened before I get this drive, but I guess it was a fw problem or just not spinning.

I've converted the drive to SATA interface, it's not recognized as well, stayed BSY.
Luckily, it spins up without noise.
And the log in terminal was attached above.

Attachments

closer MCU

[shahij]

I repeat, This is a rom issue according to the terminal.
Chk if the mcu is original, if so, swap it. If needed, take help from high end soldering expert.

[fzabkar]

Originally you said ...

U didn't swap rom. If u swapped then actually the rom is bad.

Now you are saying ...

I repeat, This is a rom issue according to the terminal.
Chk if the mcu is original, if so, swap it.

That's not the same thing.

As for the MCU, its date code is "0949", and this matches the "949" on the SDRAM. It's not conclusive proof, but it would suggest that the MCU is native.

I've converted the drive to SATA interface, it's not recognized as well, stayed BSY.
Luckily, it spins up without noise.
And the log in terminal was attached above.

Converting the donor PCB to SATA would have changed nothing. I was suggesting this as a possible solution for damaged bridge circuitry on the patient PCB.

The log is suggesting that the drive hangs after loading the MOVLY001 module from the SA. This module needs to be compatible with the ROM code on the PCB. That appears to be where your problem lies.

[LarrySabo]

I hesitate to even ask, but I assume that you resoldered the MCU properly? If not, it's no wonder the ROM and SA overlays don't match. My apologies if I've insulted your intelligence.

[shahij]

Dear fzabkar, in my both posts i indicated the issue with rom. While i was with first, the pcb pic was not present, that's why i used the term swap rom, or the rom is bad. In the 2nd post, based ur information that the rom is embedded on mcu n the picture of pcb, i refined the same word its rom either its on eprom or mcu. I just wanted to clarify its rom.
In the next part u r correct that it hangs on movly, yes, it happens when rom mismatch. Either the rom is not native or if native then its bad. Or can be bad soldering job according to the info of larrysabo.

[happygo]

dear fzabkar, LarrySabo, shahij

as i mentioned, the original board was totally messed, i dont wanna try using it.
I understand what shahij suggested
actually, I just want to make sure if there is another way out, like write maincode, except swap the ROM which is written in MCU
(cuz not sure if it is the original. and it's a tough work)

guess I'm having no other options
i'll try swap the MCU

wish me luck
and thanks for helping

[MindMergepk]

The log is suggesting that the drive hangs after loading the MOVLY001 module from the SA. This module needs to be compatible with the ROM code on the PCB. That appears to be where your problem lies.

agreed with fzabkar.
try hot swap since you already have the donor drive.