7 Nov
2011
7 Nov
'11
1:30 p.m.
On Nov 7, 2011, at 2:57 PM, Glen Slick wrote:
I haven't seen any behavior like that with any of
the CQD-220/TM that
I have. What version of the firmware are you using? The latest image
I have is CQD-220/TM B3A.02 (F220Y1B3A, F220Y2B3A) 10/17/95. Swapping
in different EPROMs would be trivial to try, but might not be too
likely to change the behavior. The only PAL I have looked at is the
CSR decode PAL, which I reverse engineered to be able to convert
CQD-220/T and CQD-220/M versions into CQD-220/TM versions.
Right, I remember, I conversed with you on a different forum (and got your ROM and PAL
images). It's interesting; dropping the ROM image into new EPROMs won't even let
me boot the code (the 8086 part works, because it copies it to the host and I can start
executing it, but it won't let me use the board; I don't recall the exact error
message, but it's something like "NOT A SCSI BOARD" and I haven't had
time to disassemble that part of the PDP-11 executable).
Burning the CSR PAL to a new GAL didn't change anything, which I suppose is good. I
put the original back in so I wouldn't have to use up one of my relatively small
supply of GAL22V10s. :-)
None of the other PLDs are socketed, so pulling them just to read them is not something
I'd do on a whim.
I suppose I ought to check what the firmware's criteria are for rejecting the board.
That might give me at least a bit of a hint as to what's going on.
- Dave