UNIBUS and QBUS termination - Revision history

Jnc: /* External links */ Bitsavers has reorganized a bit

2026-10-08T10:21:17Z

External links: Bitsavers has reorganized a bit

← Older revision		Revision as of 10:21, 8 October 2026
Line 49:		Line 49:
	==External links==		==External links==

	* [http://www.bitsavers.org/pdf/dec/qbus/~~Digital_Microcomputer_Products_Handbook_1985~~.pdf Microcomputer Products Handbook] (EB-26078-41) - Chapter 52, "Introduction to Backplanes, Enclosures, and Expansion Cables" contains a good introduction to QBUS termination issues		* [http://www.bitsavers.org/pdf/dec/qbus/EB-26078-41_Digital_Microcomputer_Products_Handbook_1985.pdf Microcomputer Products Handbook] (EB-26078-41) - Chapter 52, "Introduction to Backplanes, Enclosures, and Expansion Cables" contains a good introduction to QBUS termination issues
	* [http://www.bitsavers.org/pdf/dec/qbus/~~Digital_Microcomputer_Interfaces_Handbook_1980~~.pdf microcomputer interfaces handbook] - configuration of multi-backplane systems is covered on pp. 68-73 (pp. 76-81 of the PDF)		* [http://www.bitsavers.org/pdf/dec/qbus/EB-20175-20_Digital_Microcomputer_Interfaces_Handbook_1980.pdf microcomputer interfaces handbook] - configuration of multi-backplane systems is covered on pp. 68-73 (pp. 76-81 of the PDF)
	* [https://www.ibiblio.org/pub/academic/computer-science/history/pdp-11/hardware/micronotes/numerical/micronote29.txt Q-bus Expansion Concepts] ([[MicroNote]] #029)		* [https://www.ibiblio.org/pub/academic/computer-science/history/pdp-11/hardware/micronotes/numerical/micronote29.txt Q-bus Expansion Concepts] ([[MicroNote]] #029)
	* [https://www.ibiblio.org/pub/academic/computer-science/history/pdp-11/hardware/micronotes/numerical/micronote35.txt Backplane Expansion/Termination] ([[MicroNote]] #035)		* [https://www.ibiblio.org/pub/academic/computer-science/history/pdp-11/hardware/micronotes/numerical/micronote35.txt Backplane Expansion/Termination] ([[MicroNote]] #035)

Jnc: /* External links */ +Q-bus Expansion Concepts

2025-05-30T11:08:53Z

External links: +Q-bus Expansion Concepts

← Older revision		Revision as of 11:08, 30 May 2025
Line 51:		Line 51:
	* [http://www.bitsavers.org/pdf/dec/qbus/Digital_Microcomputer_Products_Handbook_1985.pdf Microcomputer Products Handbook] (EB-26078-41) - Chapter 52, "Introduction to Backplanes, Enclosures, and Expansion Cables" contains a good introduction to QBUS termination issues		* [http://www.bitsavers.org/pdf/dec/qbus/Digital_Microcomputer_Products_Handbook_1985.pdf Microcomputer Products Handbook] (EB-26078-41) - Chapter 52, "Introduction to Backplanes, Enclosures, and Expansion Cables" contains a good introduction to QBUS termination issues
	* [http://www.bitsavers.org/pdf/dec/qbus/Digital_Microcomputer_Interfaces_Handbook_1980.pdf microcomputer interfaces handbook] - configuration of multi-backplane systems is covered on pp. 68-73 (pp. 76-81 of the PDF)		* [http://www.bitsavers.org/pdf/dec/qbus/Digital_Microcomputer_Interfaces_Handbook_1980.pdf microcomputer interfaces handbook] - configuration of multi-backplane systems is covered on pp. 68-73 (pp. 76-81 of the PDF)
	* [https://www.ibiblio.org/pub/academic/computer-science/history/pdp-11/hardware/micronotes/numerical/micronote35.txt Backplane Expansion/Termination] (~~uNote~~ #035)		* [https://www.ibiblio.org/pub/academic/computer-science/history/pdp-11/hardware/micronotes/numerical/micronote29.txt Q-bus Expansion Concepts] ([[MicroNote]] #029)
			* [https://www.ibiblio.org/pub/academic/computer-science/history/pdp-11/hardware/micronotes/numerical/micronote35.txt Backplane Expansion/Termination] ([[MicroNote]] #035)
	* [http://www.bitsavers.org/pdf/dec/pdp11/1103/EK-LSI11-TM-002.pdf LSI-11, PDP-11/03 user's manual] (EK-LSI11-TM-002) - Appendix E, "H9270 Backplane Configurations" (pp. 157-158 of the PDF)		* [http://www.bitsavers.org/pdf/dec/pdp11/1103/EK-LSI11-TM-002.pdf LSI-11, PDP-11/03 user's manual] (EK-LSI11-TM-002) - Appendix E, "H9270 Backplane Configurations" (pp. 157-158 of the PDF)

	[[Category: UNIBUS]]		[[Category: UNIBUS]]
	[[Category: QBUS]]		[[Category: QBUS]]

Jnc: /* External links */ uNote at Frain Research went offline; switch to iBiblio copy

2025-05-30T10:59:56Z

External links: uNote at Frain Research went offline; switch to iBiblio copy

← Older revision		Revision as of 10:59, 30 May 2025
Line 51:		Line 51:
	* [http://www.bitsavers.org/pdf/dec/qbus/Digital_Microcomputer_Products_Handbook_1985.pdf Microcomputer Products Handbook] (EB-26078-41) - Chapter 52, "Introduction to Backplanes, Enclosures, and Expansion Cables" contains a good introduction to QBUS termination issues		* [http://www.bitsavers.org/pdf/dec/qbus/Digital_Microcomputer_Products_Handbook_1985.pdf Microcomputer Products Handbook] (EB-26078-41) - Chapter 52, "Introduction to Backplanes, Enclosures, and Expansion Cables" contains a good introduction to QBUS termination issues
	* [http://www.bitsavers.org/pdf/dec/qbus/Digital_Microcomputer_Interfaces_Handbook_1980.pdf microcomputer interfaces handbook] - configuration of multi-backplane systems is covered on pp. 68-73 (pp. 76-81 of the PDF)		* [http://www.bitsavers.org/pdf/dec/qbus/Digital_Microcomputer_Interfaces_Handbook_1980.pdf microcomputer interfaces handbook] - configuration of multi-backplane systems is covered on pp. 68-73 (pp. 76-81 of the PDF)
	* [~~http~~://~~web~~.~~frainresearch~~.org~~:8080~~/~~projects~~/pdp-11/micronotes/micronote35.txt Backplane Expansion/Termination] (uNote #035)		* [https://www.ibiblio.org/pub/academic/computer-science/history/pdp-11/hardware/micronotes/numerical/micronote35.txt Backplane Expansion/Termination] (uNote #035)
	* [http://www.bitsavers.org/pdf/dec/pdp11/1103/EK-LSI11-TM-002.pdf LSI-11, PDP-11/03 user's manual] (EK-LSI11-TM-002) - Appendix E, "H9270 Backplane Configurations" (pp. 157-158 of the PDF)		* [http://www.bitsavers.org/pdf/dec/pdp11/1103/EK-LSI11-TM-002.pdf LSI-11, PDP-11/03 user's manual] (EK-LSI11-TM-002) - Appendix E, "H9270 Backplane Configurations" (pp. 157-158 of the PDF)

	[[Category: UNIBUS]]		[[Category: UNIBUS]]
	[[Category: QBUS]]		[[Category: QBUS]]

Jnc: /* See also */ Link to DEC terminators

2023-11-28T12:32:21Z

Jnc: /* External links */ +Backplane Expansion/Termination

2023-07-10T00:15:08Z

External links: +Backplane Expansion/Termination

← Older revision		Revision as of 00:15, 10 July 2023
Line 45:		Line 45:
	* [http://www.bitsavers.org/pdf/dec/qbus/Digital_Microcomputer_Products_Handbook_1985.pdf Microcomputer Products Handbook] (EB-26078-41) - Chapter 52, "Introduction to Backplanes, Enclosures, and Expansion Cables" contains a good introduction to QBUS termination issues		* [http://www.bitsavers.org/pdf/dec/qbus/Digital_Microcomputer_Products_Handbook_1985.pdf Microcomputer Products Handbook] (EB-26078-41) - Chapter 52, "Introduction to Backplanes, Enclosures, and Expansion Cables" contains a good introduction to QBUS termination issues
	* [http://www.bitsavers.org/pdf/dec/qbus/Digital_Microcomputer_Interfaces_Handbook_1980.pdf microcomputer interfaces handbook] - configuration of multi-backplane systems is covered on pp. 68-73 (pp. 76-81 of the PDF)		* [http://www.bitsavers.org/pdf/dec/qbus/Digital_Microcomputer_Interfaces_Handbook_1980.pdf microcomputer interfaces handbook] - configuration of multi-backplane systems is covered on pp. 68-73 (pp. 76-81 of the PDF)
			* [http://web.frainresearch.org:8080/projects/pdp-11/micronotes/micronote35.txt Backplane Expansion/Termination] (uNote #035)
	* [http://www.bitsavers.org/pdf/dec/pdp11/1103/EK-LSI11-TM-002.pdf LSI-11, PDP-11/03 user's manual] (EK-LSI11-TM-002) - Appendix E, "H9270 Backplane Configurations" (pp. 157-158 of the PDF)		* [http://www.bitsavers.org/pdf/dec/pdp11/1103/EK-LSI11-TM-002.pdf LSI-11, PDP-11/03 user's manual] (EK-LSI11-TM-002) - Appendix E, "H9270 Backplane Configurations" (pp. 157-158 of the PDF)

	[[Category: UNIBUS]]		[[Category: UNIBUS]]
	[[Category: QBUS]]		[[Category: QBUS]]

Jnc: /* External links */ Another interesting one

2023-07-08T05:39:48Z

External links: Another interesting one

← Older revision		Revision as of 05:39, 8 July 2023
Line 45:		Line 45:
	* [http://www.bitsavers.org/pdf/dec/qbus/Digital_Microcomputer_Products_Handbook_1985.pdf Microcomputer Products Handbook] (EB-26078-41) - Chapter 52, "Introduction to Backplanes, Enclosures, and Expansion Cables" contains a good introduction to QBUS termination issues		* [http://www.bitsavers.org/pdf/dec/qbus/Digital_Microcomputer_Products_Handbook_1985.pdf Microcomputer Products Handbook] (EB-26078-41) - Chapter 52, "Introduction to Backplanes, Enclosures, and Expansion Cables" contains a good introduction to QBUS termination issues
	* [http://www.bitsavers.org/pdf/dec/qbus/Digital_Microcomputer_Interfaces_Handbook_1980.pdf microcomputer interfaces handbook] - configuration of multi-backplane systems is covered on pp. 68-73 (pp. 76-81 of the PDF)		* [http://www.bitsavers.org/pdf/dec/qbus/Digital_Microcomputer_Interfaces_Handbook_1980.pdf microcomputer interfaces handbook] - configuration of multi-backplane systems is covered on pp. 68-73 (pp. 76-81 of the PDF)
			* [http://www.bitsavers.org/pdf/dec/pdp11/1103/EK-LSI11-TM-002.pdf LSI-11, PDP-11/03 user's manual] (EK-LSI11-TM-002) - Appendix E, "H9270 Backplane Configurations" (pp. 157-158 of the PDF)

	[[Category: UNIBUS]]		[[Category: UNIBUS]]
	[[Category: QBUS]]		[[Category: QBUS]]

Jnc: Add section on QBUS termination, along with links to manuals

2023-07-04T15:14:32Z

Add section on QBUS termination, along with links to manuals

← Older revision		Revision as of 15:14, 4 July 2023
Line 1:		Line 1:
	'''UNIBUS and QBUS termination''' are very similar, since in [[analog]] terms the two [[bus]]es are very similar (e.g. their use of the same transceiver [[integrated circuit\|chips]], such as [[DS8641]]'s).		'''UNIBUS and QBUS termination''' are very similar, since in [[analog]] terms the two [[bus]]es are very similar (e.g. their use of the same transceiver [[integrated circuit\|chips]], such as [[DS8641]]'s).

	Their ~~terminators~~ do a number of things:		Their [[terminator]]s do a number of things:

	* they provide analog ~~[[terminator\|~~termination]] the otherwise un-terminated [[transmission line]]s of the bus (i.e. a [[resistor\|resistance]] at the end of a transmission line that prevents reflections of [[signal]]s passing down it, 'bouncing' off its end);		* they provide analog termination of the otherwise un-terminated [[transmission line]]s of the bus (i.e. a [[resistor\|resistance]] at the end of a transmission line that prevents reflections of [[signal]]s passing down it, 'bouncing' off its end);

	* provide pullups (so those [[wired-OR]] [[broadcast]] transmission lines normally float at roughly 3 [[volt]]s, unless actively driven low by one of the boards plugged into the bus);		* provide pullups (so those [[wired-OR]] [[broadcast]] transmission lines normally float at roughly 3 [[volt]]s, unless actively driven low by one of the boards plugged into the bus);
Line 9:		Line 9:
	* in some cases, (such as the [[M9302 UNIBUS terminator‎]]), they do 'SACK turnaround' (an 'unused' [[bus grant]] from the [[Central Processing Unit\|CPU]] is 'turned around' by the terminator, and returned to the CPU as the SACK signal); this is discussed at greater length below.		* in some cases, (such as the [[M9302 UNIBUS terminator‎]]), they do 'SACK turnaround' (an 'unused' [[bus grant]] from the [[Central Processing Unit\|CPU]] is 'turned around' by the terminator, and returned to the CPU as the SACK signal); this is discussed at greater length below.

	The first is not ''absolutely'' necessary; this can be seen in small [[QBUS]] systems which can get away without it in small configurations. Whether it's needed on particular system is hard to predict, theoretically; the easiest thing is to just try it and see. Note: it ''may'' 'work' without it, but not be as ''reliable'' as with it.		The first is not always ''absolutely'' necessary; this can be seen in small [[QBUS]] systems which can get away without it in small configurations. Whether it's needed on particular system is hard to predict, theoretically; the easiest thing is to just try it and see. Note: it ''may'' 'work' without it, but not be as ''reliable'' as with it.

	The second is necessary, but can be provided anywhere on the bus; most [[UNIBUS]]/QBUS CPUs do so, with the notable exception of the [[KD11-D CPU\|KD11-D]] of the [[PDP-11/04]], and the [[KD11-E CPU\|KD11-E]]/[[KD11-EA CPU\|-EA]] of the [[PDP-11/34]]-[[PDP-11/34A\|34A]]. (In the [[PDP-11/40]], there's an oddball exception: the M981 UNIBUS jumper does it - but that's 'sort of' part of the CPU.)		The second is necessary, but can be provided anywhere on the bus; most [[UNIBUS]]/QBUS CPUs do so, with the notable exception of the [[KD11-D CPU\|KD11-D]] of the [[PDP-11/04]], and the [[KD11-E CPU\|KD11-E]]/[[KD11-EA CPU\|-EA]] of the [[PDP-11/34]]-[[PDP-11/34A\|34A]]. (In the [[PDP-11/40]], there's an oddball exception: the M981 UNIBUS jumper does it - but that's 'sort of' part of the CPU.)
Line 15:		Line 15:
	(Note that the first and second are usually both done by a single set of components.)		(Note that the first and second are usually both done by a single set of components.)

	==SACK turnaround==		==UNIBUS SACK turnaround==

	The full story of the third function, 'SACK turnaround', is somewhat complex. The need for it is, as mentioned, that an 'unused' bus grant, theoretically for a [[peripheral\|device]]'s [[interrupt]], can, if not 'turned around' by the terminator, can cause the CPU to freeze up. This because if the CPU does not have an 'interrupt grant [[timeout]]' [[circuit]], then after such an 'un-needed' grant has been sent out, the CPU can ''potentially'' freeze up, waiting for the interrupt bus cycle to come in.		The full story of the third function, 'SACK turnaround', is somewhat complex. The need for it is, as mentioned, that an 'unused' bus grant, theoretically for a [[peripheral\|device]]'s [[interrupt]], can, if not 'turned around' by the terminator, can cause the CPU to freeze up. This because if the CPU does not have an 'interrupt grant [[timeout]]' [[circuit]], then after such an 'un-needed' grant has been sent out, the CPU can ''potentially'' freeze up, waiting for the interrupt bus cycle to come in.
Line 32:		Line 32:

	(SACK turnaround could potentially be used for a start-up 'safety check' for grant line continuity, where an un-requested - and thus 'un-grabbed' by any device - bus grant from the CPU on start-up is turned around by the terminator; this would verify that the grant line is continuous between the CPU and the terminator. Apparently no CPU does this, though.)		(SACK turnaround could potentially be used for a start-up 'safety check' for grant line continuity, where an un-requested - and thus 'un-grabbed' by any device - bus grant from the CPU on start-up is turned around by the terminator; this would verify that the grant line is continuous between the CPU and the terminator. Apparently no CPU does this, though.)

			==QBUS termination==

			The QBUS uses a somewhat complex termination scheme, particularly in system which contain multiple [[backplane]]s. (By the time [[Digital Equipment Corporation\|DEC]] got to the QBUS, they had necessarily gained a lot more experience with large wired-OR broadcast buses, and the issue of signal reflections on them in various configurations, and the problems those could cause. They thus paid much more attention to carefully specifying how to configure and terminate larger systems.)

			Each QBUS line is a 120-ohm transmission line, which must be terminated at each end by an appropriate terminator, in order to prevent reflections from the end. This type of termination is provided by an appropriate terminator module, or is built in to some backplanes and expansion cable connector cards. (Note that the required termination can be give by a combination of two modules, each providing 220 ohms to ground; many QBUS processor modules supply 220 ohms to ground.)

			QBUS system which have multiple backplanes (up to three) formally require separate configuration rules from those which have only a single backplane. Notionally, termination must be provided at the start of the first backplane, and the end of the last. In practice, especially in single-backplane systems, it was usual to ignore termination requirements; such systems usually ran without noticeable problems.

			==External links==

			* [http://www.bitsavers.org/pdf/dec/qbus/Digital_Microcomputer_Products_Handbook_1985.pdf Microcomputer Products Handbook] (EB-26078-41) - Chapter 52, "Introduction to Backplanes, Enclosures, and Expansion Cables" contains a good introduction to QBUS termination issues
			* [http://www.bitsavers.org/pdf/dec/qbus/Digital_Microcomputer_Interfaces_Handbook_1980.pdf microcomputer interfaces handbook] - configuration of multi-backplane systems is covered on pp. 68-73 (pp. 76-81 of the PDF)

	[[Category: UNIBUS]]		[[Category: UNIBUS]]
	[[Category: QBUS]]		[[Category: QBUS]]

Jnc: /* SACK turnaround */ Noise can cause an unused grant

2022-04-20T14:44:42Z

SACK turnaround: Noise can cause an unused grant

← Older revision		Revision as of 14:44, 20 April 2022
Line 21:		Line 21:
	So SACK turnaround is therefore ''required'' by ''some'' UNIBUS CPUs, which do not have that circuit; this includes the [[KD11-D CPU]] of the [[PDP-11/04]] and the [[KD11-E CPU]] of the [[PDP-11/34]] (although the optional [[M8264 No-SACK Timeout Module]] can be used on both of these to add that functionality). However, most PDP-11 CPUs (including all QBUS CPUs, such as the [[KDF11 CPUs]]) have it, and will time out unused grants. (This takes somewhat longer than the SACK turnaround mechanism, which is why that is preferred.)		So SACK turnaround is therefore ''required'' by ''some'' UNIBUS CPUs, which do not have that circuit; this includes the [[KD11-D CPU]] of the [[PDP-11/04]] and the [[KD11-E CPU]] of the [[PDP-11/34]] (although the optional [[M8264 No-SACK Timeout Module]] can be used on both of these to add that functionality). However, most PDP-11 CPUs (including all QBUS CPUs, such as the [[KDF11 CPUs]]) have it, and will time out unused grants. (This takes somewhat longer than the SACK turnaround mechanism, which is why that is preferred.)

	How can a device not accept the grant of an interrupt that it requested? ~~For example,~~ if, having requested an interrupt, the device is reset ''just'' as the CPU is granting that interrupt, by the time the grant arrives at the device, it will have 'forgotten' that it was ever requesting an interrupt, and pass the grant on through. If no downstream (on the bus) device is requesting an interrupt, the grant will go unused - hanging a CPU which does not have a grant timeout circuit.		How can a device not accept the grant of an interrupt that it requested? There are several possible causes for an unused grant. One possibility is that [[noise]] on a request line will look to the arbitrator (in the CPU) like a valid request. Another possible cause is that if, having requested an interrupt, the device is reset ''just'' as the CPU is granting that interrupt, by the time the grant arrives at the device, it will have 'forgotten' that it was ever requesting an interrupt, and pass the grant on through. If no downstream (on the bus) device is requesting an interrupt, the grant will go unused - hanging a CPU which does not have a grant timeout circuit.

	Machines which do not have a grant timeout circuit will function correctly ''most'' of the time without a terminator with SACK turnaround functionality; they are potentially vulnerable to the 'un-claimed grant' bug described above, though.		Machines which do not have a grant timeout circuit will function correctly ''most'' of the time without a terminator with SACK turnaround functionality; they are potentially vulnerable to the 'un-claimed grant' bug described above, though.

Jnc: Write up 'SACK turnaround' issues in detail

2022-03-31T21:42:33Z

Write up 'SACK turnaround' issues in detail

← Older revision		Revision as of 21:42, 31 March 2022
Line 5:		Line 5:
	* they provide analog [[terminator\|termination]] the otherwise un-terminated [[transmission line]]s of the bus (i.e. a [[resistor\|resistance]] at the end of a transmission line that prevents reflections of [[signal]]s passing down it, 'bouncing' off its end);		* they provide analog [[terminator\|termination]] the otherwise un-terminated [[transmission line]]s of the bus (i.e. a [[resistor\|resistance]] at the end of a transmission line that prevents reflections of [[signal]]s passing down it, 'bouncing' off its end);

	* provide pullups (so those [[wired-OR]] transmission lines normally float at roughly 3 [[volt]]s, unless actively driven low by one of the boards plugged into the bus);		* provide pullups (so those [[wired-OR]] [[broadcast]] transmission lines normally float at roughly 3 [[volt]]s, unless actively driven low by one of the boards plugged into the bus);

	* in some cases, they do 'SACK turnaround' (an 'unused' [[bus grant]] from the [[Central Processing Unit\|CPU]]~~, theoretically for a [[peripheral\|device]]'s [[interrupt]],~~ is 'turned around' by the terminator, and ~~retuned~~ to the CPU as the SACK signal); this ~~prevents the CPU from freezing up~~.		* in some cases, (such as the [[M9302 UNIBUS terminator‎]]), they do 'SACK turnaround' (an 'unused' [[bus grant]] from the [[Central Processing Unit\|CPU]] is 'turned around' by the terminator, and returned to the CPU as the SACK signal); this is discussed at greater length below.

	The first is not ''absolutely'' necessary; this can be seen in small [[QBUS]] systems which can get away without it in small configurations. Whether it's needed on particular system is hard to predict, theoretically; the easiest thing is to just try it and see. Note: it ''may'' 'work' without it, but not be as ''reliable'' as with it.		The first is not ''absolutely'' necessary; this can be seen in small [[QBUS]] systems which can get away without it in small configurations. Whether it's needed on particular system is hard to predict, theoretically; the easiest thing is to just try it and see. Note: it ''may'' 'work' without it, but not be as ''reliable'' as with it.
Line 15:		Line 15:
	(Note that the first and second are usually both done by a single set of components.)		(Note that the first and second are usually both done by a single set of components.)

	The third is required by ''some'' UNIBUS CPUs ~~(ISTR~~ that the [[PDP-11/04]] ~~won't run without it~~), ~~but~~ most (including all QBUS CPUs, such as the [[KDF11 CPUs]]) ~~don~~'~~t need~~ it; they ~~will~~ [[~~timeout~~]] ~~unused grants~~. (SACK turnaround could potentially be used for a start-up 'safety check' where an un-requested - and thus 'un-grabbed' by any device - bus grant from the CPU on start-up is 'turned around' by the terminator; this ~~verifies~~ that the ~~[[bus~~ grant line~~]]s are un-broken~~ between the CPU and the terminator ~~- e~~.~~g. by someone forgetting to plug in a [[grant continuity card]]~~.)		==SACK turnaround==

			The full story of the third function, 'SACK turnaround', is somewhat complex. The need for it is, as mentioned, that an 'unused' bus grant, theoretically for a [[peripheral\|device]]'s [[interrupt]], can, if not 'turned around' by the terminator, can cause the CPU to freeze up. This because if the CPU does not have an 'interrupt grant [[timeout]]' [[circuit]], then after such an 'un-needed' grant has been sent out, the CPU can ''potentially'' freeze up, waiting for the interrupt bus cycle to come in.

			So SACK turnaround is therefore ''required'' by ''some'' UNIBUS CPUs, which do not have that circuit; this includes the [[KD11-D CPU]] of the [[PDP-11/04]] and the [[KD11-E CPU]] of the [[PDP-11/34]] (although the optional [[M8264 No-SACK Timeout Module]] can be used on both of these to add that functionality). However, most PDP-11 CPUs (including all QBUS CPUs, such as the [[KDF11 CPUs]]) have it, and will time out unused grants. (This takes somewhat longer than the SACK turnaround mechanism, which is why that is preferred.)

			How can a device not accept the grant of an interrupt that it requested? For example, if, having requested an interrupt, the device is reset ''just'' as the CPU is granting that interrupt, by the time the grant arrives at the device, it will have 'forgotten' that it was ever requesting an interrupt, and pass the grant on through. If no downstream (on the bus) device is requesting an interrupt, the grant will go unused - hanging a CPU which does not have a grant timeout circuit.

			Machines which do not have a grant timeout circuit will function correctly ''most'' of the time without a terminator with SACK turnaround functionality; they are potentially vulnerable to the 'un-claimed grant' bug described above, though.

			===SACK turnaround and CPU hangs===

			On machines which use the [[KY11-L to CPU interface]] (the KD11-D CPU of the PDP-11/04, the KD11-E CPU of the PDP-11/34, and the [[KD11-EA CPU]] of the [[PDP-11/34A]]), SACK turnaround terminators can hang the CPU if the machine is powered on with a break in the [[bus grant line]]s somewhere between the CPU and the terminator - e.g. by someone forgetting to plug in a [[grant continuity card]].

			That is because the KY11-L to CPU interface uses SACK for the [[front panel]] to signal to the CPU that it should remain halted; if there is a break in a grant line, the resulting 'open' input to the [[transistor-transistor logic\|TTL]] [[gate]] monitoring the grant line in the device immediately down-stream from the break will float high, thereby looking like a permanent incoming grant. The device will pass it on, and the SACK turnaround circuit in the terminator will turn it into a permanent assertion of SACK - which will cause the CPU to hang forever once it halts.

			(SACK turnaround could potentially be used for a start-up 'safety check' for grant line continuity, where an un-requested - and thus 'un-grabbed' by any device - bus grant from the CPU on start-up is turned around by the terminator; this would verify that the grant line is continuous between the CPU and the terminator. Apparently no CPU does this, though.)

	~~[[Category: DEC Buses]]~~
	[[Category: UNIBUS]]		[[Category: UNIBUS]]
	[[Category: QBUS]]		[[Category: QBUS]]

Jnc: also the -11/04

2022-02-20T21:49:10Z

also the -11/04

← Older revision		Revision as of 21:49, 20 February 2022
Line 11:		Line 11:
	The first is not ''absolutely'' necessary; this can be seen in small [[QBUS]] systems which can get away without it in small configurations. Whether it's needed on particular system is hard to predict, theoretically; the easiest thing is to just try it and see. Note: it ''may'' 'work' without it, but not be as ''reliable'' as with it.		The first is not ''absolutely'' necessary; this can be seen in small [[QBUS]] systems which can get away without it in small configurations. Whether it's needed on particular system is hard to predict, theoretically; the easiest thing is to just try it and see. Note: it ''may'' 'work' without it, but not be as ''reliable'' as with it.

	The second is necessary, but can be provided anywhere on the bus; most [[UNIBUS]]/QBUS CPUs do so, with the notable exception of the [[KD11-E CPU\|KD11-E]]/[[KD11-EA CPU\|-EA]] of the [[PDP-11/34]]-[[PDP-11/34A\|34A]]. (In the [[PDP-11/40]], there's an oddball exception: the M981 UNIBUS jumper does it - but that's 'sort of' part of the CPU.)		The second is necessary, but can be provided anywhere on the bus; most [[UNIBUS]]/QBUS CPUs do so, with the notable exception of the [[KD11-D CPU\|KD11-D]] of the [[PDP-11/04]], and the [[KD11-E CPU\|KD11-E]]/[[KD11-EA CPU\|-EA]] of the [[PDP-11/34]]-[[PDP-11/34A\|34A]]. (In the [[PDP-11/40]], there's an oddball exception: the M981 UNIBUS jumper does it - but that's 'sort of' part of the CPU.)

	(Note that the first and second are usually both done by a single set of components.)		(Note that the first and second are usually both done by a single set of components.)

← Older revision		Revision as of 12:32, 28 November 2023
Line 40:		Line 40:

	QBUS system which have multiple backplanes (up to three) formally require separate configuration rules from those which have only a single backplane. Notionally, termination must be provided at the start of the first backplane, and the end of the last. In practice, especially in single-backplane systems, it was usual to ignore termination requirements; such systems usually ran without noticeable problems.		QBUS system which have multiple backplanes (up to three) formally require separate configuration rules from those which have only a single backplane. Notionally, termination must be provided at the start of the first backplane, and the end of the last. In practice, especially in single-backplane systems, it was usual to ignore termination requirements; such systems usually ran without noticeable problems.

			==See also==

			* [[M930 UNIBUS terminator]]
			* [[M9302 UNIBUS terminator]]
			* [[TEV11 Terminator]]

	==External links==		==External links==