Firmware problem with ShrekLT

[PeskyBit]

I have a ShrekLT drive that is behaving very strangely. I can get the drive into safe mode, load mod 11 and mod 1 and read out all firmware, but cannot get the drive to identify correctly in normal mode. i am attaching a picture of the DFL screen once I have booted to safe mode and loaded the modules.

When I try to access the drive normally, the drive does not identify correctly, but I can get access to the ROM.

Anyone have any thoughts as to what is going on with the drive? Is the ROM possibly corrupted? I tried a fix for a similar problem with this drive series but it did not work: http://forum.dolphindatalab.com/thread-1616.html.

Attachments

[fzabkar]

FWIW, I can check the ROM for you.

[PeskyBit]

Here you go.

Attachments

ROM.zip

(238.32 KiB) Downloaded 323 times

[thatdellguy]

0A.bin Read error - Heads map
0B.bin Read error - Flash Rom

[fzabkar]

FWIW, I can check the ROM for you.

Those Shrek .... Remember the threads with tools having trouble reading ROM MODULES or correctly ID the active ROM module or whatever ?

Maybe it's something related ?

That's what I was thinking, although the error message isn't clear.

0A.bin read error
0B.bin read error

If it is reading the wrong copy of 0A, then it would encounter a bad checksum (for the heap map section). If 0B is in error, then why not look for 20B? Does "read error" mean that the module cannot be read at all, or can it mean that there is some problem with its content?

[fzabkar]

ROM analysis attached. All seems OK. Module 20B is the active module, not 0B. That's a common bug/limitation in pro tools.

Attachments

PeskyBit.rar

(4.25 KiB) Downloaded 339 times

[fzabkar]

Sorry for the double post. BTW, the double line spacing is annoying, but I don't know how to prevent it.

[thatdellguy]

0047 FFFF 00000800 01FFFE00 0003F4FE FFFFFE00 BAD

[fzabkar]

0047 FFFF 00000800 01FFFE00 0003F4FE FFFFFE00 BAD

It's inactive (0B). Shouldn't be a problem.

Active in 20B is ok :

0047 OK 00000800 OK 0003E4FE 00000000 OK

Yes, that's how I see it. Some tools, including PC3K, incorrectly report that module 47 is bad. That's because they don't understand how to determine which of the two module directories (0B or 20B) is the active one.

[fzabkar]

Maybe OP should try to play with SED flag changing/unlocking and see what happens ?

Could we see module 02?

[PeskyBit]

Here you go.

Attachments

02.zip

(1.22 KiB) Downloaded 351 times

[fzabkar]

The SED flag is set.

Code:

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

000007D0                                      00 00 00 00
000007E0  00 00 01

[thatdellguy]

So, DFL doesn't tell you the drive is SED before working on it?

[Amarbir[CDR-Labs]]

So, DFL doesn't tell you the drive is SED before working on it?

Well,
DFL solves the sed issue in a funny way .They call it firmware locked