SCSI connecting problems (Compaq Win NT Wide Ultra SCSI3)

Thread View: comp.periphs.scsi

7 messages

[T] Back to Threads [V] Tree View [G] Group Articles

7 total messages Started by Martin Praekelt Wed, 17 May 2000 00:00

#17799

Author: Martin Praekelt
Date: Wed, 17 May 2000 00:00

43 lines
2612 bytes

Hello Forum,
We have developed an own communiation device. The interface to the host PC
is SCSI-2 (single ended 8 bit).
This works fine for years as long, as there were SCSI-2 controllers
available and approved by server vendors.
Now we have to adopt our communication device to a new COMPAQ server running
Win NT 4.0. The only approved SCSI controller is a wide ultra SCSI-3
controller delivered by COMPAQ.
The driver file is named "cpq32fs2.sys".
This adapter card should be compatible to SCSI 2 peripherals.
Now, my problem is the following:
Windows NT detects our communication device. All inquiry data is correctly
read out and is copied to the SCSI-controller section of the control panel
of the WIN-NT desktop.
But if I am trying to assert the INQUIRY command using the MS-Visual C
function
"DeviceIoControl" in  IOCTL_SCSI_PASS_THROUGH_DIRECT - mode
it fails!

Using an old Symbios 810 controller instead of the COMPAQ one works fine.
But our customers do not accept a controller built into their server, which
is not approved by COMPAQ.

My research debugging the communication device firmware and tracing the SCSI
bus data and control lines brought the following result concerning the
INQUIRY command:
SELECTION PHASE ok
MESSAGE OUT Phase: "Identify" and "Sync. Data Transfer Request" are asserted
MESSAGE IN Phase: "Message Reject" (due to not supported Sync. Data Tr.)
COMMAND PHASE ok
MESSAGE IN PHASE "Save Data Pointer", "Disconnect" and "Indentify"

DATA PHASE
but then during the transfer of the first byte of inquiry data the ATN Line
goes active!
After completing data phase...
MESSAGE OUT " Abort" and "Indentify" is following.

DeviceIoControl reports error code "1117" finally.

Perhaps some other SCSI peripherals firmware developer has had similar
problems with this COMPAQ controller and could give me some hints for
solving the problem.

Re: SCSI connecting problems (Compaq Win NT Wide Ultra SCSI3)

#17800

Author: bart Bart Lagerweij
Date: Wed, 17 May 2000 00:00

10 lines
1230 bytes

>MESSAGE OUT Phase: "Identify" and "Sync. Data Transfer Request" are
>asserted MESSAGE IN Phase: "Message Reject" (due to not supported Sync.
>Data Tr.) COMMAND PHASE ok

Is your comm. device async?
Can your comm. device do sync xfers?

-- 
Bart Lagerweij - Computer Technology Systems - http://www.cts-bv.nl
(Please don't email me, reply to the newsgroup)

Re: SCSI connecting problems (Compaq Win NT Wide Ultra SCSI3)

#17801

Author: Martin Praekelt
Date: Wed, 17 May 2000 00:00

23 lines
1609 bytes

Bart Lagerweij schrieb in Nachricht <8F37AA23Bbartctsbvnl@195.86.111.154>...
<snip>
>Is your comm. device async?
>Can your comm. device do sync xfers?
>
>--
>Bart Lagerweij - Computer Technology Systems - http://www.cts-bv.nl
>(Please don't email me, reply to the newsgroup)
<snip>

In general the comm device is capable of doing async and sync xfers.
The data rate is sufficient using async data xfer and rejecting sync data
xfer.
We hoped to get more immune against cabling problems by avoiding sync xfer.
And our logic analyzer is a little bit old-fashioned and tracing SCSI bus is
easier in async mode.

But now - a new fact:

If I am asserting RESCAN TAPE DEVICES from control panel the inquiry command
works fine without any problems. But if I try to assert the command using my
test program it fails!

Re: SCSI connecting problems (Compaq Win NT Wide Ultra SCSI3)

#17802

Author: Martin Praekelt
Date: Thu, 18 May 2000 00:00

9 lines
1079 bytes

Martin Praekelt schrieb in Nachricht <8fu73f$vt5$1@power1.vcs.de>...
>Now we have to adopt our communication device to a new COMPAQ server
running
>Win NT 4.0. The only approved SCSI controller is a wide ultra SCSI-3
>controller delivered by COMPAQ.

Update:
I have opened the server and found, that the chip is named LSI 53C875

Re: SCSI connecting problems (Compaq Win NT Wide Ultra SCSI3)

#17803

Author: bart Bart Lagerweij
Date: Fri, 19 May 2000 00:00

9 lines
1219 bytes

>Update:
>I have opened the server and found, that the chip is named LSI 53C875

I didn't have any problems with that SCSI chip coding scsitool (Dos).
Did you check latest firmware, latest driver?

-- 
Bart Lagerweij - Computer Technology Systems - http://www.cts-bv.nl
(Please don't email me, reply to the newsgroup)

Re: SCSI connecting problems (Compaq Win NT Wide Ultra SCSI3)

#17804

Author: Martin Praekelt
Date: Fri, 19 May 2000 00:00

28 lines
1582 bytes

Martin Praekelt schrieb in Nachricht <8fu73f$vt5$1@power1.vcs.de>...
>Hello Forum,
>Now we have to adopt our communication device to a new COMPAQ server
running
>Win NT 4.0. The only approved SCSI controller is a wide ultra SCSI-3
>controller delivered by COMPAQ.
>The driver file is named "cpq32fs2.sys".
It seems that I have solved the problem
 code sequence
Original-Version:
<snip>
if ( (CDB[0] == OPC_SEND) || (CDB[0] == OPC_WBUF))
  IOControl.ScsiDescr.DataIn = SCSI_IOCTL_DATA_IN;
else
  IOControl.ScsiDescr.DataIn = SCSI_IOCTL_DATA_OUT;
<snip>

... has to be replaced by this one...

<snip>
if ( (CDB[0] == OPC_SEND) || (CDB[0] == OPC_WBUF))
  IOControl.ScsiDescr.DataIn = SCSI_IOCTL_DATA_IN;
else
  IOControl.ScsiDescr.DataIn = SCSI_IOCTL_DATA_UNSPECIFIED;
<snip>

I don't have any idea why, but it works

Re: SCSI connecting problems (Compaq Win NT Wide Ultra SCSI3)

#17805

Author: Martin Praekelt
Date: Fri, 19 May 2000 00:00

30 lines
1650 bytes

Martin Praekelt schrieb in Nachricht <8fu73f$vt5$1@power1.vcs.de>...
>Hello Forum,
>We have developed an own communiation device. The interface to the host PC
>is SCSI-2 (single ended 8 bit).
>
The problem seems to be solved!

Original-Version:
<snip>
if ( (CDB[0] == OPC_SEND) || (CDB[0] == OPC_WBUF))
  IOControl.ScsiDescr.DataIn = SCSI_IOCTL_DATA_IN;
else
  IOControl.ScsiDescr.DataIn = SCSI_IOCTL_DATA_OUT;
<snip>

has to be replaced by....

<snip>
if ( (CDB[0] == OPC_SEND) || (CDB[0] == OPC_WBUF))
  IOControl.ScsiDescr.DataIn = SCSI_IOCTL_DATA_OUT;
else
  IOControl.ScsiDescr.DataIn = SCSI_IOCTL_DATA_IN;
<snip>

That means, we have defined data flow direction in a wrong way.
Some SCSI device drivers seem to ignore this data field of control data, but
this special one does not.
The error condition is an unexpected DATA IN phase which causes a UNIT
ATTENTION condition!

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads