how can i analyse rom bad or not bad ??

[moiz h/d]

wd royal model rom bad or not bad how can i analyse because sometimes i write a rom pcb is'nt spin up ;;;;;

[DR-Kiev]

wd royal model rom bad or not bad how can i analyse because sometimes i write a rom pcb is'nt spin up ;;;;;

Don't worry , ROM is still fine , but pcb already not .

[moiz h/d]

but how can i trust for pcb write some pcb 1 rom
before writing rom pcb is spin up after write a rom pcb is'nt spin up

what do u think ?

[fzabkar]

http://malthus.zapto.org/viewtopic.php?f=59&t=225&p=548

[moiz h/d]

i already trying to write rom with safemode but problem same to same ??

[louis]

post the rom image here. I'll check it with my own app. the royl roms can be tested well because the rom mods can be revers traced and checked due to known signature&check-sums

otherwise you should write your routines for checking blocks, checksums..mods etc and at the end..there's still the compatibility issue. if you are 100% positive that the rom works with your drive..then, before resetting the drive after flashing rom ...just download again the rom and compare it with what you have flashed. but this should be done by the tool you use...automatically. a sort of "write verify"...before reset, and brick ur pcb

here's a sort of log from my app wile testing a royl rom before flashing.

Code:

Rom image successfully tested
CRC OK.
Performing CRC on Flash Module: 0x4F
CRC OK.
Performing CRC on Flash Module: 0x0D
CRC OK.
Performing CRC on Flash Module: 0x47
CRC OK.
Performing CRC on Flash Module: 0x30
CRC OK.
Performing CRC on Flash Module: 0x0B
CRC OK.
Performing CRC on Flash Module: 0x0A
ROYL mod traced, mode ID: 0x0A
ROM dir module traced...
ROYL mod traced, mode ID: 0x0B
ROYL mod traced, mode ID: 0x30
ROYL mod traced, mode ID: 0x4F
ROYL mod traced, mode ID: 0x47
ROYL mod traced, mode ID: 0x0D
Reached the table end.
Block CRC OK
Header CRC OK
Checking block ID : 08
Block CRC OK
Header CRC OK
Checking block ID : 07
Block CRC OK
Header CRC OK
Checking block ID : 06
Block CRC OK
Header CRC OK
Checking block ID : 05
Block CRC OK
Header CRC OK
Checking block ID : 04
Block CRC OK
Header CRC OK
Checking block ID : 03
Block CRC OK
Header CRC OK
Checking block ID : 02
Block CRC OK
Header CRC OK
Checking block ID : 01
Block CRC OK
Header CRC OK
Checking block ID : 5A
Checking the ROM image file :WDC WD6400AAKS-22A7B0_01.03B0_WD-WCASY114816_DONOR\Rom Firmware\ROM_rev05.6PC.bin

it's a basic test, to ensure that the image it's theoretically "in good shape"

for the so called "marvel" roms..still standardized,..(in fact this was the first time when wd started to introduce a standard for their roms)...firmware..can't be tested..because the missing signature for the rom mods. what was before year 2004....the roms before "Marvel" doesn't have a similar format for the headers found at the beginning of the rom image..and doesn't seems to have crc for the code blocks. these roms...doesn't have modules inside..in fact the 2-3 mods are included in the starting headers...a primitive mod A (head-map)...and a adaptive mode..I think.

Last edited by louis on May 13th, 2013, 20:33, edited 3 times in total.

[moiz h/d]

do u tell me DIY i check what is the software name u check the rom of royal ??

[louis]

the name it's unimportant..since the software it's used, at this moment, by a single person in this world. I'm developing it

[moiz h/d]

why r u jocking mr.louis? ?

[louis]

http://malthus.zapto.org/viewtopic.php?f=59&t=225&p=548

it's the first time I see 16bit crc on rom blocks as well as 20B new rom dir. well..what's true..I didn't tested too extensive my app. this model WDC WD15EACS-11BHUB0 it's quite new (256k rom...year 2011) so it's interesting how the things evolve

I have added some support for this romz.

Code:

Rom image successfully tested
CRC OK.
Performing CRC on Flash Module: 0x4F
CRC OK.
Performing CRC on Flash Module: 0x0D
CRC OK.
Performing CRC on Flash Module: 0x47
CRC OK.
Performing CRC on Flash Module: 0x30
CRC OK.
Performing CRC on Flash Module: 0x20B
CRC OK.
Performing CRC on Flash Module: 0x0B
CRC OK.
Performing CRC on Flash Module: 0x0A
ROM dir module traced...
ROYL mod traced, mode ID: 0x0B
ROYL mod traced, mode ID: 0x0D
ROYL mod traced, mode ID: 0x20B
ROYL mod traced, mode ID: 0x0D
ROYL mod traced, mode ID: 0x47
ROYL mod traced, mode ID: 0x4F
ROYL mod traced, mode ID: 0x30
ROYL mod traced, mode ID: 0x0A
Reached the table end.
Block CRC OK
Header CRC OK
Checking block ID : 06
Block CRC OK
Header CRC OK
Checking block ID : 05
Block CRC OK
Header CRC OK
Checking block ID : 04
Block CRC OK
Header CRC OK
Checking block ID : 03
Block CRC OK
Header CRC OK
Checking block ID : 02
Block CRC OK
Header CRC OK
Checking block ID : 01
Block CRC OK
Header CRC OK
Checking block ID : 5A
Checking the ROM image file :01_0200.FLS

[louis]

also...there are ROYLs with 8bit crc in rom blocks

aaaand the second byte in the rom dir entry..it's the number of copies the mod has on SA+rom img..tht's why the rom mods have that number 1...while the sa mods have 2 copies on H0 and H1

aaand many more...

[louis]

It is not clear to me how the MCU locates the MOD directory.

if you dump the unpacked arm code from RAM and disassemble-it..maybe it will become clear. ROYL it's enough for a scanner, but it could also be hard-coded between arm op-codes.

[fzabkar]

Are you piping the output of your program through a LIFO ???

BTW, "mode ID" should be "MOD ID".

[fzabkar]

also...there are ROYLs with 8bit crc in rom blocks :!:

The WD15EACS-11BHUB0 has a 16-bit checksum for the first PMCBlock, and 8-bit checksums for the remaining PMCBlocks.

[louis]

The WD15EACS-11BHUB0 has a 16-bit checksum for the first PMCBlock, and 8-bit checksums for the remaining PMCBlocks.

which obviously I remarked...and the output is for some code handling this

it's a kind of mark..for a new rom type. when you see this...perhaps you could expect for the 20B?

LIFO ...instead windows vscroll. the log wnd keeps on top the last msg.

about the mod 0d. recently I made a rom regen from SA...for a royl drive. the backed equiv mod0d from sa...doesn't have any version definded in it. after regening the pcb rom, the drive worked fine with no version in its 0d.

[fzabkar]

Why not just redirect your screen output to a file, eg ...

wdt blah_blah >> output.log

[louis]

because.

now it's a gui app.

console apps will always write as u like...new text goes down.

[shahij]

but how can i trust for pcb write some pcb 1 rom
before writing rom pcb is spin up after write a rom pcb is'nt spin up

what do u think ?

what tool r u using for writing ROM?

It seems to me you are writing 192KB ROM into the PCB, that's why spin down after ROM writing. If so, you need to convert it into 256KB.

If your tool is not capable to write 256KB successfully, you have to use External programmer to do so.

[moiz h/d]

WDR wd reparing tool

[shahij]

WDR wd reparing tool

what is the ROM size u r trying to write?