Commit | Line | Data |
---|---|---|
be46310c KM |
1 | .\" Copyright (c) 1980 Regents of the University of California. |
2 | .\" All rights reserved. The Berkeley software License Agreement | |
3 | .\" specifies the terms and conditions for redistribution. | |
4 | .\" | |
970af9d3 | 5 | .\" @(#)tu.4 5.1 (Berkeley) %G% |
be46310c | 6 | .\" |
970af9d3 | 7 | .TH TU 4 "27 July 1983" |
be46310c KM |
8 | .UC 4 |
9 | .SH NAME | |
970af9d3 KM |
10 | tu \- VAX-11/730 and VAX-11/750 TU58 console cassette interface |
11 | .SH SYNOPSIS | |
12 | .B "options MRSP" | |
13 | (for VAX-11/750's with an MRSP prom) | |
be46310c | 14 | .SH DESCRIPTION |
970af9d3 KM |
15 | The |
16 | .I tu | |
17 | interface provides access to the VAX 11/730 and 11/750 TU58 console | |
18 | cassette drive(s). | |
be46310c | 19 | .PP |
970af9d3 KM |
20 | The interface supports only block i/o to the TU58 cassettes. |
21 | The devices are normally manipulated with the | |
22 | .IR arff (8V) | |
23 | program using the ``f'' and ``m'' options. | |
be46310c | 24 | .PP |
970af9d3 KM |
25 | The device driver is automatically included when a |
26 | system is configured to run on an 11/730 or 11/750. | |
27 | .PP | |
28 | The TU58 on an 11/750 uses the Radial Serial Protocol (RSP) | |
29 | to communicate with the cpu over a serial line. This | |
30 | protocol is inherently unreliable as it has no flow | |
31 | control measures built in. On an 11/730 the Modified | |
32 | Radial Serial Protocol is used. This protocol incorporates | |
33 | flow control measures which insure reliable data transfer | |
34 | between the cpu and the device. Certain 11/750's have | |
35 | been modified to use the MRSP prom used in the 11/730. | |
36 | To reliably use the console TU58 on an 11/750 under UNIX, | |
37 | the MRSP prom is required. For those 11/750's without | |
38 | an MRSP prom, an unreliable but often | |
39 | useable interface has been developed. | |
40 | This interface uses an assembly language ``pseudo-dma'' routine | |
41 | to minimize the receiver interrupt service latency. | |
42 | To include this code in | |
43 | the system, the configuration must \fBnot\fP specify the | |
44 | system will run on an 11/730 or use an MRSP prom. | |
45 | This unfortunately makes it impossible to configure a | |
46 | single system which will properly handle TU58's on both an 11/750 | |
47 | and an 11/730 (unless both machines have MRSP proms). | |
be46310c | 48 | .SH FILES |
970af9d3 KM |
49 | .nf |
50 | .DT | |
51 | /dev/tu0 | |
52 | /dev/tu1 (only on a VAX-11/730) | |
53 | .fi | |
54 | .SH "SEE ALSO" | |
55 | arff(8V) | |
be46310c | 56 | .SH DIAGNOSTICS |
970af9d3 KM |
57 | .BR "tu%d: no bp, active %d" . |
58 | A transmission complete interrupt was received with no outstanding | |
59 | i/o request. This indicates a hardware problem. | |
60 | .PP | |
61 | .BR "tu%d protocol error, state=%s, op=%x, cnt=%d, block=%d" . | |
62 | The driver entered an illegal state. The information printed | |
63 | indicates the illegal state, operation currently being executed, | |
64 | the i/o count, and the block number on the cassette. | |
65 | .PP | |
66 | .BR "tu%d receive state error, state=%s, byte=%x" . | |
67 | The driver entered an illegal state in the receiver finite | |
68 | state machine. The state is shown along with the control | |
69 | byte of the received packet. | |
70 | .PP | |
71 | .BR "tu%d: read stalled" . | |
72 | A timer watching the controller detected no interrupt for | |
73 | an extended period while an operation was outstanding. | |
74 | This usually indicates that one or more receiver interrupts | |
75 | were lost and the transfer is restarted (11/750 only). | |
76 | .PP | |
77 | .BR "tu%d: hard error bn%d, pk_mod %o" . | |
78 | The device returned a status code indicating a hard error. The | |
79 | actual error code is shown in octal. No retries are attempted | |
80 | by the driver. | |
be46310c | 81 | .SH BUGS |
970af9d3 KM |
82 | The VAX-11/750 console interface without MRSP prom is unuseable |
83 | while the system is multi-user; it should be used only with | |
84 | the system running single-user and, even then, with caution. |