General Category > Lisa Troubleshooting and Repair

BLU and Priam Datatower puzzlement

(1/3) > >>

Al Kossow:
I'm trying to test Alex's priam interface board.
So far, no joy. Trying on a couple of different drives and controllers I can't get the drive to spin up.
In BLU, ID returns error 8000E5CB and spin down returns 9A40E5CB but I have no idea what those status
bytes correspond to looking at the DS101 document

Al Kossow:
Hooked up a cable tap with a saleae on it
Here are the traces doing a boot, and blu ID and spindown
http://bitsavers.org/projects/datatower/d7-d0_a2-a0_wr_rd_rst_req

Al Kossow:
i've been staring at the logic traces and i think the data bits ended up scrambled somehow

it is active high logic on the bus, the boot prom goes

send command 7 soft reset
wait for status 16
send command 82 spin up and wait
wait for status 0

but what i see is
wr adr 0 01100001
rd 0  00000000
rd 0  00000101
wr 0 01101001
wr 2 00011001


also, i'm not sure if BLU has code in it to spin up the priam

Al Kossow:

I'm thinking I just need to sort out the cabling situation between the controller board and the interface and also build a little priam tester out of an arduino. There really isn't a compelling reason to stick with the 25 pin connector of the original lisa priam interface card. I think I have the last known stash of datatowers (4 complete ones) and I don't have any cables. the controller card in the priam has a 40 pin ribbon connector, that gets converted to a 37 pin d-sub, then that gets converted to 25. You can just use a 37 pin on the lisa card then use a ribbon to 37 d or 40 ribbon on the other end.

sigma7:

--- Quote from: Al Kossow on June 10, 2024, 03:42:25 pm ---In BLU, ID returns error 8000E5CB and spin down returns 9A40E5CB but I have no idea what those status bytes correspond to looking at the DS101 document

--- End quote ---

For BLU v0.92


--- Code: ---
* Priam Errors $yyzzE5xx ; xx are error code, yy is $80|transaction status (might be the same as the error code), zz is register 3 supplementary status
PriamErrCode EQU $E500
* when Priam returns an error, bits 6,7 are device select, so are always 0, so we set bit 7,6 for our errors
PriamErrIntNBsy EQU $E5C1 ; Priam did not accept command: "interface busy" not set
PriamErrCmdComp EQU $E5C2 ; Priam did not Acknowledge Command Completion: "interface busy" remained set
PriamErrNotRun EQU $E5C3 ; Priam is not attached or is not turned on
PriamErrWaitRFB EQU $E5C4 ; Priam did not Acknowledge Command Completion: "interface busy" remained set
PriamErrCmdRej EQU $E5C5 ; Priam rejected command
PriamErrInvSect EQU $E5C6 ; Priam invalid sector
PriamErrCmdTime EQU $E5C7 ; Priam command timeout with no data transfer nor completion request
PriamErrCmdCpl EQU $E5C8 ; Priam command completion timed out
PriamErrNoXfer EQU $E5C9 ; Priam asked for command completion before data transfer
PriamErrParity EQU $E5CA ; Priam parity error during read
PriamErrSoftR EQU $E5CB ; Priam error from software reset
PriamErrSoftRW EQU $E5CC ; Priam error waiting for register file free after software reset
PriamErrSeqUp EQU $E5CD ; Priam error from sequence up
PriamErrSeqUpW EQU $E5CE ; Priam error waiting for register file free after sequence up
PriamErrSetLog EQU $E5CF ; Priam error from set logical mode
PriamErrSetPrm0 EQU $E5D0 ; Priam error from set parameter 0
PriamErrSetPrm1 EQU $E5D1 ; Priam error from set parameter 1
PriamErrRdParms EQU $E5D2 ; Priam error from read drive parameters
PriamErrNotRdy EQU $E5D3 ; Priam error not ready for a command
PriamErrEndDD EQU $26 ; end of defect directory, not an error, but consumes this value
PriamErrNoDD EQU $27 ; no defect directory, not an error, but consumes this value


--- End code ---

This error code info may change: now that I've seen the LOS Priam driver, I have worked a bit on improving the error reporting, mainly since my own DataTower is no longer working properly for mysterious (to me) reasons.

Navigation

[0] Message Index

[#] Next page