TOSHIBA MK7575GSX - ROM Problem

[fzabkar]

Those MCUs are based on an ARM core, so you would need ARM tools.

BTW, I assume that you are aware that the prevailing opinion is that it is not possible to reconstruct a Toshiba ROM.

You might like to read my attempts to understand Toshiba's CPs:

Analysis of Toshiba CPs:
http://www.hddoracle.com/viewtopic.php?f=59&t=2044

I have written a tool to extract the CPs from the ROM:
http://www.hddoracle.com/viewtopic.php?f=22&t=1724

[mhp666]

BTW, I assume that you are aware that the prevailing opinion is that it is not possible to reconstruct a Toshiba ROM.

I prefer to think that it is very difficult without the orginal, but having a corrupted ROM, I think it could be feasible to get it, although I assume that I am not the best person, not even close.
By the way, from what I've seen of the ROM, I assume that this HDD has changed the PCB. It does not match the model of the sticker with that of the ROM.

Thanks for the links.

[BGman]

For Toshiba drives the order of initialization is:

1. Embeded in MCU ROM program
2. Flash ROM FW
3. SA FW

FL ROM and SA contain modules (not CP's) that are unique for each drive. If both copies of these modules not match the drive will be recognized as:
DRIVE UNDER CONSTRUCTON

This is the maximum you can get...

[mhp666]

FL ROM and SA contain modules (not CP's) that are unique for each drive. If both copies of these modules not match the drive will be recognized as:
DRIVE UNDER CONSTRUCTON

This is the maximum you can get...

Thank you for this information.
I will try to do something with all this information that you have provided me.

[fzabkar]

BTW, I assume that you are aware that the prevailing opinion is that it is not possible to reconstruct a Toshiba ROM.

I prefer to think that it is very difficult without the orginal, but having a corrupted ROM, I think it could be feasible to get it, although I assume that I am not the best person, not even close.

My approach to this problem would be to determine which CPs are necessary to reach the SA. To this end I would take a working drive and manipulate those CPs which appear to be head or media related. I would limit my changes to head #0, and I would vary each parameter, up and down, until the drive ceases to boot. This will tell us the sensitivity of each parameter.

I would also import a foreign SN or MN CP, just to see how the drive identifies itself.

[mhp666]

It would be interesting to get 2 operating ROMs of the same HDD model and the same firmware version.
If I find them I will upload them to do some test.