PC-3000 Forum

I have HD502HJ with the same problem as described in this post

viewtopic.php?f=33&t=7812&start=0

i.e. drive does not spin and stays busy with client PCB and donor PCB with client ROM. I have gained terminal access as per instruction manual. ROM dump is

Dump size............................... : 524288 bytes
Firmware checksum....................... : Ok
FIPS offset............................. : 0x00070000
FIPS size............................... : 1024 bytes
FIPS checksum........................... : Error
Firmware type........................... : Main Code
Original name........................... : 1AJc3suM.125
Platform Id............................. : 0x19
Head map................................ : 0, 1, 2, 3

I understand this is a FIPS error.

I have copied FIPS section from the donor to client ROM.bin file using HexEdit. When I check this Repaired_rom.bin file in utility everything looks fine like this

Information about dump
Dump size............................... : 524288 bytes
Firmware checksum....................... : Ok
FIPS offset............................. : 0x00070000
FIPS size............................... : 1024 bytes
FIPS checksum........................... : Ok
Firmware type........................... : Main Code
Original name........................... : 1AJc3suM.125
Platform Id............................. : 0x19
Head map................................ : 0, 1, 2, 3
Test completed

I am now trying to write this Repaired_ROM.bin file to the ROM via utility terminal. The utility copies 256kb only (ROM is 512kb) and stops with error:

Write ROM
From file............................... : E:\List\13377-Repaired_rom.bin
Download via terminal................... : Yes
Disable checking HDD Patform Id......... : No
Checksum verification................... : Ok
Loader checking......................... : Ok
Loading................................. : Error downloading file via terminal; Terminal is busy
Operation aborted
Test completed

I understand that the easiest solution is to use external EPROM programmer (as the guy in the earlier post did), which I don't have and this job is rather urgent.

How can I write ROM via terminal - am I doing something wrong here?

If you have problems writing ROM and no access to programmer, you can try to write donor overlays to patient after hotswap, then proceed to try data access via donor PCB & ROM?

Thank you AJ2008, I'm sure this solution will work, unfortunately I don't have donor drive, only replacement PCB. It's cheaper and probably as quick to get the programmer than a donor drive so I have ordered the programmer (I'm sure it will come handy many times in the future). Will post the result once I get the programmer.

I obtained a programmer and uploaded repaired ROM image as per my original post. Drive now fully functional, cloned 100%, data intact. Problem solved, thank you for your help.