Hello, i've this Maxtor DM9 with damaged ST 25P10 ROM.
Luckily i have the ROM backup but i need to write it on the new ROM chip, i've an eeprom programmer to do that but on this chip my eeprom doesn't write correctly.
I tried on another new 25P10, all same story...
It always write ok on 25p20 and 25p40 ROM chips, but not on 25P10 (i don't know why)
How can i write it properly?

Drive is DM9
Code: YAR41VW0 N,M,B,D
6Y060L0420401
Date: 03 OCT 2002
PCB: Calypso 301599100
MCU: Ardent 040110200

This is the original ROM backup:


This is the eeprom writes it into the chip:




Note that the eeprom program gives error at 0x000000 Chip=0x82 Buffer=0x79


HEX Editor comparing:

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

O sei tu che sbagli qualcosa visto che proprio la vuoi programmare (?), o cambia programmatore.
Questo funziona di sicuro (lo conosco MOLTO bene) :
http://www.hilosystems.com.tw/en/hilo_p ... ifications
e fa tutto questo :
ftp://ftp.hilosystems.com.tw/pub/downlo ... ll-100.pdf

Either it's you doing something wrong , as you really want to program it (?), or you are using the wrong programmer.
This one works (I know it SO well) :
http://www.hilosystems.com.tw/en/hilo_p ... ifications
and can work with all this :
ftp://ftp.hilosystems.com.tw/pub/downlo ... ll-100.pdf

Io ho provato anche a flashare il firmware su una rom 25p40 peró il disco cosí non si accende nemmeno (come se la rom fosse vuota o con contenuto corrotto), eppure sul 25p40 l'ha scritto correttamente.
Sai dirmi perché non funziona correttamente con la rom 25p40?

I tried also to flash the firmware into a 25p40 chip but the drive doesn't spin (as a empty or corrupted rom), and yet was written successfully into 25p40.
Do you know why doesn't work the drive with 25p40 rom?

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

Perche' non la vede.

Because it is not seen.

Con pc3000 pci posso flashare la rom 25p10 correttamente, considerando che non ho alcun accesso al disco (non si accende nemmeno)?
O prima mi devo procurare per forza una rom giá programmata correttamente o una pcb funzionante per lavorare su questo hdd in pc3000?

With pc3000 pci can i correctly flash 25p10 rom, considering that the drive doesn't even spin?
Or first should i get a good rom (or a good pcb) and only then work into pc3000?

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

Si ma la flash e' l'ultimo dei problemi. Ammesso che riesci a comunicare con il PCB.

Yes but the flash is the latest problem . Assuming you can communicate with PCB.

Interesting language lesson
Can you guys add another language in each post?

_________________
SAN, NAS, RAID, Server, and HDD Data Recovery.

FWIW, I notice that bytes 0x80 - 0xFF in the original flash have been written to bytes 0x00 - 0x7F in the target ROM, and 0x180 - 0x1FF have been written to 0x100 - 0x017F, 0x280 -> 0x200, etc.

Bytes 0x00 - 0x7F and 0x100 - 0x17F don't appear in the target.

That sounds like an addressing problem of some kind.

_________________
A backup a day keeps DR away.

I suspect that the same addressing fault may be affecting the chip's access to the internal readonly register where its ID is stored. AISI, the chip is faulty.

_________________
A backup a day keeps DR away.

Can't be faulty chip because i tried in other 2 good 25p10 chips, same story...
Maybe my programmer has a bug for programming 25p10 (on 25p40 works great).

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

Prima di perdere altro tempo dietro una INUTILE programmazione della flash, controllati circuito E il resto, specie se c'e' roba "fumata" intorno al 7250.
se ti piace il fai da te : prova con un altro PCB identico o compatibile . Se te lo brucia, c'e' ben altro. Se "suona" continuamente , 99% HS bruciato. Se non calibra o sbatte, 50% HS bruciato 50% HS danneggiato + altre sorprese. A tuo rischio

Instead of wasting time with a USELESS flash programming check PCB and the rest, especially if there was something "smoked" near the 7250.
DIY option : test another same / compatible PCB. If it is fried, there's much other damage. If it "plays music" , 99% HS is FUBAR. No calibration or clicks , 50% HS FUBAR / 50% FUBAH HS + other gifts. At your own risk

Si ho provato con un altro pcb, il disco si accende ma non viene caricato (ovviamente perchè manca la ROM corretta).
Lo scopo non è riparare il disco di cui non mi frega niente, per quello avrei potuto semplicemente prendere una pcb identica e trasferire fisicamente la rom (dato che il programmatore non ne vuole sapere).
Lo scopo invece è di riutilizzare la stessa pcb del disco (di cui sono sicuro che è funzionante) una volta programmato correttamente il chip.
In pratica sto più che altro cercando di capire perchè il 25P10 non mi viene programmato correttamente, ho infatti inviato una mail a SIVAVA vediamo che mi dicono.
Grazie.

I tried it with another pcb, the drive pins on but does not load (obviously because need the correct ROM).
The aim is not repair the drive that I do not give a damn, for what I could just take an identical pcb and physically transfer the rom (since the programmer doesn't write the rom correctly).
The aim instead is to reuse the same pcb disk (of which i'm sure is working) once correctly programmed the chip.
In practice i'm mostly trying to understand why 25P10 isn't programmed correctly, i sent an email to SIVAVA about it.

Thank you.

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

Very strange.

Would it be possible to program your chip as a 25P40, but restrict the address range to 0x1FFFF?

_________________
A backup a day keeps DR away.

O sbagli tu non so cosa o non funziona correttamente. O tutte e due le cose.
Con l' HiLo non c'e' nessun problema neanche ICP, con le dovute cautele e mai rotto nulla. Sara' ...

Thanks to Nebojsa_28, the answer to your enigma may be in this tech note:
http://www.datasheetcatalog.org/datashe ... Xytxry.pdf

There is a difference between the 25P10AV chip used in the DiamondMax Plus 9 boards and the earlier 25P10V6 chip.

The "A" has a page size of 256 bytes whereas the "V" has 128 bytes.

The "A" IDs as an 05h whereas the "V" IDs as 10h.

The "V" also has a higher Vcc rating.

_________________
A backup a day keeps DR away.

My chip is exactly 25P10V6

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

ISTM that the Willem software may be treating your device as if it had a page size of 256 bytes. That's why the errors occur in the same way and at the same location in every page.

_________________
A backup a day keeps DR away.

I don't know if i can change software option from 256 to 128 byte page
I don't think so...

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

FWIW, my PCB has a 25P10AV chip.

http://malthus.zapto.org/download/file. ... &mode=view

_________________
A backup a day keeps DR away.